docs: the E2E section tells the truth about provin-line/e2e - #18
Merged
Conversation
The harness is public, and its scenarios run against the allow-all pdpstub — auth integration is exercised only by oss deploy/quickstart. Both facts predate e2e publication and had gone stale here. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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.
External review caught two stale facts in the E2E section, both verified:
provin-line/e2eis described as "an internal compose harness (not published)" — it is public (private: false).cmd/pdpstub(allow-all) and cover "never JWT issuance or a policy-decision deny". The real auth stack is exercised only byprovin-line/ossdeploy/quickstart.The section now states both facts as they are.
🤖 Generated with Claude Code