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

Update operator runbooks and roadmap docs #149

New Issue
Closed
opened 2026-07-05 01:56:43 -05:00 by jcwalker3 · 1 comment
jcwalker3 commented 2026-07-05 01:56:43 -05:00
Owner
Copy Link
Copy Source

Purpose

Update operator runbooks and roadmap docs to correct stale naming and reflect actual Jenkins and GlitchTip capabilities.

Acceptance criteria

  • Remove or explain stale *-readonly naming.
  • Document actual server names, tool namespaces, capabilities, and registration/reload steps.
  • Correct Jenkins read-only claims now that trigger code exists.
  • Document GlitchTip filing/dedup as partial until the follow-up issue lands.

Related to parent integrations discussion.

## Purpose Update operator runbooks and roadmap docs to correct stale naming and reflect actual Jenkins and GlitchTip capabilities. ## Acceptance criteria * Remove or explain stale `*-readonly` naming. * Document actual server names, tool namespaces, capabilities, and registration/reload steps. * Correct Jenkins read-only claims now that trigger code exists. * Document GlitchTip filing/dedup as partial until the follow-up issue lands. Related to parent integrations discussion.
jcwalker3 commented 2026-07-06 10:54:45 -05:00
Author
Owner
Copy Link
Copy Source

Closing as duplicate of #154 (canonical, closed). Same scope: all four bullets here appear in #154's fuller criteria.

Because #154 was closed without a closure comment, verification was done against live master before closing this one:

  • Stale *-readonly naming explained, not lingering: docs/mcp-client-registration.md:15 ("Historical names such as jenkins-readonly and glitchtip-readonly are…"), and docs/architecture/jenkins-readonly-build-status-design.md:8 carries the explicit note "Actual package/server is jenkins-mcp" — remaining mentions are historical design docs with disclaimers and profile-name (not server-name) examples.
  • Actual server names + registration/reload steps documented: docs/mcp-client-registration.md (landed via merged PR #190, 9a35b80).
  • Jenkins read-only claims corrected: same design-doc note — "The server boundary now contains gated trigger (see #56), but read tools remain as designed."
  • GlitchTip filing/dedup partial status: tracked by open canonical #153 (orchestrator) per the audit-family ordering; roadmap separation is #154's landed scope.

Remaining substantive work continues on the open canonicals #152 (trigger boundary), #153 (filing orchestrator), #155 (discoverability). Closed under duplicate-triage rules by jcwalker3 / prgs-author (gitea.issue.close resolved allowed; duplicate-check evidence: full open-issue inventory, #154 body comparison, live-master doc grep).

Closing as duplicate of #154 (canonical, closed). Same scope: all four bullets here appear in #154's fuller criteria. Because #154 was closed without a closure comment, verification was done against live master before closing this one: - Stale `*-readonly` naming explained, not lingering: `docs/mcp-client-registration.md:15` ("Historical names such as `jenkins-readonly` and `glitchtip-readonly` are…"), and `docs/architecture/jenkins-readonly-build-status-design.md:8` carries the explicit note "Actual package/server is `jenkins-mcp`" — remaining mentions are historical design docs with disclaimers and profile-name (not server-name) examples. - Actual server names + registration/reload steps documented: `docs/mcp-client-registration.md` (landed via merged PR #190, `9a35b80`). - Jenkins read-only claims corrected: same design-doc note — "The server boundary now contains gated trigger (see #56), but read tools remain as designed." - GlitchTip filing/dedup partial status: tracked by open canonical #153 (orchestrator) per the audit-family ordering; roadmap separation is #154's landed scope. Remaining substantive work continues on the open canonicals #152 (trigger boundary), #153 (filing orchestrator), #155 (discoverability). Closed under duplicate-triage rules by `jcwalker3 / prgs-author` (`gitea.issue.close` resolved allowed; duplicate-check evidence: full open-issue inventory, #154 body comparison, live-master doc grep).
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#149