docs: document static dual-namespace Gitea MCP deployment model (#143)
Record the #139 accepted decision as a deployment doc: two static per-role MCP namespaces (gitea-author, gitea-reviewer), one credential per process, with dynamic profile switching and dispatcher routing explicitly rejected for now. Covers rationale (audit clarity, credential concentration, two-party review boundary, fail-closed behavior), reference-only client setup via GITEA_MCP_CONFIG/GITEA_MCP_PROFILE, the 'Auth unsupported' client-badge caveat, and reconnect/reload requirements after profile/config/code changes. Cross-linked from the execution-profiles model doc and the workflow runbooks; guarded by docs-content tests. Closes #143 Co-Authored-By: Claude Fable 5 <[email protected]>
This commit is contained in:
@@ -485,6 +485,7 @@ scripts/release-tag v0.4.0 --notes-file /tmp/release-notes.md --push
|
||||
|
||||
- [`../skills/llm-project-workflow/SKILL.md`](../skills/llm-project-workflow/SKILL.md) — portable cross-project LLM workflow skill.
|
||||
- [`gitea-execution-profiles.md`](gitea-execution-profiles.md) — the profile model.
|
||||
- [`gitea-dual-namespace-deployment.md`](gitea-dual-namespace-deployment.md) — static author/reviewer namespace deployment (#139 decision).
|
||||
- [`llm-agent-sha.md`](llm-agent-sha.md) — opaque agent attribution metadata (never an eligibility input).
|
||||
- [`safety-model.md`](safety-model.md) — trust boundaries and audit logging.
|
||||
- [`tool-boundaries.md`](tool-boundaries.md) — per-tool allowed operations.
|
||||
|
||||
Reference in New Issue
Block a user