Repository navigation
docs: publish native setup and clarify security scope - #20
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The provider setup guide now links the separately published native orchestrator build required for Punch Livepeer staging. It distinguishes the orchestrator, external Punch adapter and our payer signer, with exact artifact checksums, extraction path, prerequisites and retained-state upgrade boundaries. The security guide describes the released19.5 service lifecycle and scopes the existing checks without claiming an independent audit.
Validation: existing public documentation validator PASS; actual published native archive checksum and extraction/version proof PASS. The old flat executable path failed with exit127; the corrected nested path reported0.9.2-31bb2224 from the same archive. CLI19.5 runtime/archive/tag and production configuration remain unchanged. Native publication is an opt-in staging prerelease, not a production or Pon-host activation.