docs: update operator runbooks and roadmap docs for Jenkins/GlitchTip MCP status (#154)

- Updated jenkins-readonly and glitchtip-readonly skills in _PROJECT_SKILLS:
  - Descriptions and notes now use actual server names (jenkins-mcp, glitchtip-mcp)
  - Explain historical -readonly skill names vs registration in mcp-control-plane #55
  - Note gated trigger in jenkins-mcp (see #56), partial filing in glitchtip (see #57)
- Updated docs/safety-model.md: naming note, corrected mutation gating claims for trigger/filing
- Updated docs/architecture/jenkins-readonly-build-status-design.md: naming note, updated Phase 1 to account for gated trigger
- No behavior change to skill status/availability; no secrets exposed
- AC: stale naming explained, actual names documented, Jenkins claims corrected, GlitchTip filing as partial, no over-claiming

Closes #154

mcp_server.py

@@ -1820,34 +1820,29 @@ _PROJECT_SKILLS = {
     },
     "jenkins-readonly": {
         "description": "Read-only Jenkins CI inspection (jobs, builds, "
-                       "logs).",
+                       "logs). Actual server name: jenkins-mcp (see mcp-control-plane).",
         "when_to_use": "Checking CI state once Jenkins MCP tools exist.",
         "required_operations": ["jenkins.read"],
         "status": "designed-not-implemented",
-        "notes": "Design exists (issues #72/#77); no Jenkins MCP server is "
-                 "connected yet. Report SKIPPED rather than substituting "
-                 "shell or direct API calls.",
+        "notes": "Server code exists in mcp-control-plane as jenkins-mcp (read tools + gated trigger); registration pending (#55); docs in Gitea-Tools use historical name. Report SKIPPED if not connected. Do not substitute shell/API. Trigger requires dedicated profile (see #56).",
         "steps": [
-            "Confirm a Jenkins MCP server is connected; if not, report "
+            "Confirm a Jenkins MCP server is connected (jenkins-mcp); if not, report "
             "SKIPPED.",
-            "Use read-only operations only; never trigger, cancel, or "
-            "configure builds.",
+            "Use read-only operations only; never trigger unless using dedicated profile + confirmation.",
         ],
     },
     "glitchtip-readonly": {
-        "description": "Read-only GlitchTip error/event inspection.",
+        "description": "Read-only GlitchTip error/event inspection. Actual server name: glitchtip-mcp (see mcp-control-plane).",
         "when_to_use": "Investigating reported errors once GlitchTip MCP "
                        "tools exist.",
         "required_operations": ["glitchtip.read"],
         "status": "designed-not-implemented",
-        "notes": "Design exists (issue #73); no GlitchTip MCP server is "
-                 "connected yet. Report SKIPPED rather than substituting "
-                 "shell or direct API calls.",
+        "notes": "Server code exists in mcp-control-plane as glitchtip-mcp (read-only tools); registration pending (#55); filing orchestrator is partial in mcp-control-plane (see #57). Report SKIPPED if not connected. Filing to Gitea is separate orchestrator, not in this server.",
         "steps": [
-            "Confirm a GlitchTip MCP server is connected; if not, report "
+            "Confirm a GlitchTip MCP server is connected (glitchtip-mcp); if not, report "
             "SKIPPED.",
             "Use read-only operations only; never mutate issues or "
-            "settings.",
+            "settings. Filing tracked in #57.",
         ],
     },
     "release-operator": {