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

Complete GlitchTip-to-Gitea filing orchestrator #153

New Issue
Closed
opened 2026-07-05 01:57:33 -05:00 by jcwalker3 · 2 comments
jcwalker3 commented 2026-07-05 01:57:33 -05:00
Owner
Copy Link
Copy Source

Context

Child implementation issue from the accepted Jenkins/GlitchTip MCP audit decision.

The accepted audit status is the working source of truth:

  • GlitchTip MCP server code exists as glitchtip-mcp.
  • GlitchTip read-only tools exist and are tested.
  • GlitchTip-to-Gitea filing exists only as a partial library path.
  • The current filing path uses mocked GlitchTip fetch behavior.
  • GlitchTip dedup/linking code exists and is tested, but it is not integrated into the filing path.
  • There is no mutation audit for filing.
  • There is no MCP exposure for filing.
  • Do not reopen #6 directly; this issue is the follow-up that completes the missing filing-orchestrator acceptance criteria.

Scope

  • Replace mocked GlitchTip fetch behavior with the real GlitchTip read path.
  • Wire glitchtip_dedup before any Gitea create action.
  • Add fail-closed mutation audit for filing/linking actions.
  • Decide whether filing should be MCP-exposed and under which write-boundary server.
  • Keep read-only GlitchTip MCP behavior clearly separate from any mutating Gitea filing surface.

Acceptance criteria

  • Filing orchestration uses real GlitchTip read behavior, not mocked issue data.
  • Dedup runs before any create action.
  • Dedup create/link/skip decisions are represented in tests.
  • Existing GlitchTip dedup/linking logic is integrated into the filing path rather than duplicated or bypassed.
  • Mutation audit is fail-closed before any Gitea create/link mutation.
  • Tests cover audit failure.
  • The implementation explicitly decides and documents whether filing is exposed through MCP.
  • If MCP-exposed, filing is only available through an appropriate write-boundary server/profile, not the read-only GlitchTip surface.

Non-goals

  • Do not solve Jenkins trigger safety here.
  • Do not use this issue for generic client registration except where needed for the filing exposure decision; registration belongs to #151.
  • Do not mark #6 complete by inference until this issue's acceptance criteria are met.

Ordering

This is implementation issue 3 of 5 and should follow #151 and #152. It is the explicit follow-up for the missing filing-orchestrator work.

## Context Child implementation issue from the accepted Jenkins/GlitchTip MCP audit decision. The accepted audit status is the working source of truth: - GlitchTip MCP server code exists as `glitchtip-mcp`. - GlitchTip read-only tools exist and are tested. - GlitchTip-to-Gitea filing exists only as a partial library path. - The current filing path uses mocked GlitchTip fetch behavior. - GlitchTip dedup/linking code exists and is tested, but it is not integrated into the filing path. - There is no mutation audit for filing. - There is no MCP exposure for filing. - Do not reopen #6 directly; this issue is the follow-up that completes the missing filing-orchestrator acceptance criteria. ## Scope - Replace mocked GlitchTip fetch behavior with the real GlitchTip read path. - Wire `glitchtip_dedup` before any Gitea create action. - Add fail-closed mutation audit for filing/linking actions. - Decide whether filing should be MCP-exposed and under which write-boundary server. - Keep read-only GlitchTip MCP behavior clearly separate from any mutating Gitea filing surface. ## Acceptance criteria - Filing orchestration uses real GlitchTip read behavior, not mocked issue data. - Dedup runs before any create action. - Dedup create/link/skip decisions are represented in tests. - Existing GlitchTip dedup/linking logic is integrated into the filing path rather than duplicated or bypassed. - Mutation audit is fail-closed before any Gitea create/link mutation. - Tests cover audit failure. - The implementation explicitly decides and documents whether filing is exposed through MCP. - If MCP-exposed, filing is only available through an appropriate write-boundary server/profile, not the read-only GlitchTip surface. ## Non-goals - Do not solve Jenkins trigger safety here. - Do not use this issue for generic client registration except where needed for the filing exposure decision; registration belongs to #151. - Do not mark #6 complete by inference until this issue's acceptance criteria are met. ## Ordering This is implementation issue 3 of 5 and should follow #151 and #152. It is the explicit follow-up for the missing filing-orchestrator work.
jcwalker3 added the mcpsecuritygiteamutatingtestingreliabilityglitchtipworkflow labels 2026-07-05 01:57:36 -05:00
jcwalker3 commented 2026-07-06 10:45:41 -05:00
Author
Owner
Copy Link
Copy Source

Duplicate triage: closing #148 as a duplicate of this issue. #148 ("Complete GlitchTip-to-Gitea filing orchestrator") carried five acceptance bullets — real GlitchTip read path, dedup wired before create, fail-closed mutation audit, MCP-exposure decision, dedup/audit tests — all already present in this issue's fuller scope and acceptance criteria. No unique content existed on #148 (empty comment thread). This issue remains the canonical tracker. Triage by jcwalker3 / prgs-author; duplicate-check evidence: full open-issue inventory + side-by-side body comparison.

Duplicate triage: closing #148 as a duplicate of this issue. #148 ("Complete GlitchTip-to-Gitea filing orchestrator") carried five acceptance bullets — real GlitchTip read path, dedup wired before create, fail-closed mutation audit, MCP-exposure decision, dedup/audit tests — all already present in this issue's fuller scope and acceptance criteria. No unique content existed on #148 (empty comment thread). This issue remains the canonical tracker. Triage by `jcwalker3 / prgs-author`; duplicate-check evidence: full open-issue inventory + side-by-side body comparison.
jcwalker3 added the status:in-progress label 2026-07-06 11:42:09 -05:00
jcwalker3 commented 2026-07-06 11:42:14 -05:00
Author
Owner
Copy Link
Copy Source

Claimed for verification and Gitea-Tools closure tracking.

Queue context: #151 closed; mcp-control-plane child #57 (filing orchestrator) is closed with real fetch, dedup-before-create, and fail-closed audit in mcp_control_plane/glitchtip_gitea_filing.py. This issue tracks the Gitea-Tools-side acceptance criteria and cross-repo documentation alignment.

Branch: feat/issue-153-glitchtip-filing-orchestrator

Next steps:

  1. Verify filing orchestrator tests in mcp-control-plane satisfy all AC here
  2. Align Gitea-Tools docs/safety-model references (library-only exposure decision)
  3. Open PR with any doc/test gaps; Closes #153
Claimed for verification and Gitea-Tools closure tracking. **Queue context:** #151 closed; mcp-control-plane child #57 (filing orchestrator) is closed with real fetch, dedup-before-create, and fail-closed audit in `mcp_control_plane/glitchtip_gitea_filing.py`. This issue tracks the Gitea-Tools-side acceptance criteria and cross-repo documentation alignment. **Branch:** `feat/issue-153-glitchtip-filing-orchestrator` **Next steps:** 1. Verify filing orchestrator tests in mcp-control-plane satisfy all AC here 2. Align Gitea-Tools docs/safety-model references (library-only exposure decision) 3. Open PR with any doc/test gaps; `Closes #153`
sysadmin removed the status:in-progress label 2026-07-06 12:28:54 -05:00
jcwalker3 added the status:in-progress label 2026-07-07 03:24:19 -05:00
sysadmin removed the status:in-progress label 2026-07-07 04:05:24 -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 gitea glitchtip mcp mutating reliability security testing workflow
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#153