Repository navigation
Conversation
The "Auth" entry in the backend-architecture package overview omitted internal/delegated (RFC 9068 delegated access-token verification, E2A_DELEGATED_ENABLED), even though it's a real, fully documented feature elsewhere (docs/deployment.md, docs/observability.md) and has its own prober scenario. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01LC5BiFF9aj57azyV481g5z
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
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.
Summary
Scheduled documentation audit. Before starting, I checked open PRs and unmerged
claude/*branches to avoid duplicating work already in flight:rfcmessageid,filterquery,domainteardown,suppressionsync,webhooknotify,sendingaccessnotice,billingnotify).update_protectionexample inplugins/e2a/docs/setup.md/SKILL.mdfrom a flat JSON body to a nested one. I re-verified this against current code and it's not a bug: that example is calling theupdate_protectionMCP tool, whose Zod input schema (mcp/src/tools/agents.ts) is intentionally flat (outbound_gate_policy,outbound_gate_allowlist, …) and does its own read-modify-write translation into the nested RESTProtectionConfigRequestshape internally. The flat example is correct for MCP-tool callers, so I left it alone.Everything else audited (root docs, CLI/SDK docs, MCP + example docs, web/plugin docs, exit codes, coverage-floor list, MCP tool-count claims, broken-link scan) checked out against current code — no other high-confidence issues found.
What was outdated → what changed
AGENTS.md— the "Auth" entry under "Backend architecture" → "Key packages, grouped" listed onlyauthandoauth, omittinginternal/delegated(RFC 9068 delegated access-token verification, gated byE2A_DELEGATED_ENABLED). It's a real, shipped feature documented elsewhere (docs/deployment.md:35,217,219,docs/observability.md:142-143,265,274,459,461) with its own prober scenario (delegated_auth), so it belongs in the architecture inventory like every other package. Added it.No behavior changes — one doc line, nothing else.
Test plan
bash scripts/check-repository-text-integrity.shpassesinternal/delegatedexists (internal/delegated/{delegated,jwks,verify,classify}.go) and is documented elsewhereGenerated by Claude Code