Scaled-Tech-Consulting/Gitea-Tools
2
0
Fork 0
Code Issues 77 Pull Requests 10 Actions Packages Projects Releases Wiki Activity

Document static dual-namespace Gitea MCP deployment model #143

New Issue
Closed
opened 2026-07-05 01:51:42 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-05 01:51:42 -05:00
Owner
Copy Link
Copy Source

Purpose

Document the accepted #139 decision: use static per-role MCP namespaces for now.

Acceptance criteria

  • Docs state the preferred model:
    • gitea-author for authoring
    • gitea-reviewer for review/merge
  • Docs explicitly reject dynamic switching and dispatcher routing for now.
  • Explain why:
    • clearer audit
    • less credential concentration
    • simpler two-party review boundary
    • safer fail-closed behavior
  • Include setup examples for MCP clients where safe:
    • author namespace
    • reviewer namespace
    • environment/profile variables
  • Explain that “Auth unsupported” in some clients can be normal for custom/local MCP servers.
  • Explain reconnect/reload requirements after profile/config/tool changes.
  • No secrets, tokens, keychain IDs, or raw service URLs.
  • Update operator guide / workflow docs.

Related to #139.

## Purpose Document the accepted #139 decision: use static per-role MCP namespaces for now. ## Acceptance criteria * Docs state the preferred model: * `gitea-author` for authoring * `gitea-reviewer` for review/merge * Docs explicitly reject dynamic switching and dispatcher routing for now. * Explain why: * clearer audit * less credential concentration * simpler two-party review boundary * safer fail-closed behavior * Include setup examples for MCP clients where safe: * author namespace * reviewer namespace * environment/profile variables * Explain that “Auth unsupported” in some clients can be normal for custom/local MCP servers. * Explain reconnect/reload requirements after profile/config/tool changes. * No secrets, tokens, keychain IDs, or raw service URLs. * Update operator guide / workflow docs. Related to #139.
jcwalker3 added the status:in-progress label 2026-07-05 02:15:41 -05:00
sysadmin removed the status:in-progress label 2026-07-05 02:29:23 -05:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
allocator
Controller-owned work allocator
 anti-stomp
Prevent concurrent LLM session stomping
 architecture
Architecture / structural design
 bug
chore
codex
OpenAI Codex client / workflow session surface
 concurrency
Concurrent session safety
 contamination
Workflow or session contamination incident
 control-plane
MCP control-plane coordination and allocation authority
 dashboard
MCP operational dashboard/queue view
 database
Internal coordination storage (SQLite/Postgres)
 design
Design / investigation, no implementation
 documentation
Docs / runbooks
 enhancement
New feature or improvement
 gitea
Gitea MCP workflow
 glitchtip
GlitchTip integration
 important
incident
Operational or process incident requiring durable audit trail
 incident-bridge
Sentry-to-Gitea incident bridging
 integration
Integration testing
 jenkins
Jenkins integration
 labels
Label taxonomy management
 leases
Lease adopt/release/expire lifecycle
 mcp
MCP server / tooling
 mcp-health
MCP namespace and runtime health
 mcp-menu
MCP menu surface
 multi-project
Work spanning multiple monitoring projects or Gitea repos
 mutating
Mutating action; requires gating
 nice-to-have
observability
Observability, metrics, traces, error reporting
 portability
Cross-platform / portability
 preflight
Shared preflight gates before mutation
 protected-branch
Protected branch / stable-branch policy concern
 queue
Work queue visibility and allocation
 read-only
Read-only, no mutation
 reconnect
MCP client reconnect/reload recovery path
 recovery
Recovery paths for stale/foreign leases
 refactor
Code refactor / restructure
 release
Release / versioning
 reliability
Reliability / failure handling
 resumable-review
Persist and resume prepared review verdicts across sessions
 reviewer
Reviewer workflow tooling
 roadmap
Roadmap / umbrella issue
 safety
Safety rails and fail-closed mutation guards
 security
Security / trust boundary
 self-hosted
Self-hosted infrastructure integration
 sentry
Sentry error monitoring integration
 stale-runtime
Stale backend daemon / runtime-vs-master parity failures
 status:blocked
Issue is blocked
 status:in-progress
Issue is being worked on
 status:pr-open
Issue has an open pull request
 status:ready
Issue is ready for work
 terminal-lock
Terminal review lock (#332) path
 testing
Tests / test coverage
 tracker
Issue tracker hygiene / meta
 type:bug
Bug or defect
 type:feature
Feature or enhancement
 type:feature
Feature or enhancement
 type:guardrail
Safety gate or guardrail
 visibility
Workflow state visibility for LLMs/operators
 workflow
Cross-tool workflow
 workflow-hardening
LLM workflow coordination hardening
 workflow-hardening
LLM workflow coordination hardening
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
jcwalker3 sysadmin
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Scaled-Tech-Consulting/Gitea-Tools#143