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

Add concurrent-session MCP restart safety tests (dogfooding) #666

New Issue
Open
opened 2026-07-10 15:32:58 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-10 15:32:58 -05:00
Owner
Copy Link
Copy Source

Problem statement

No realistic concurrent-session test suite proves restart governance: unilateral deny, drain behavior, checkpoints, lease safety, scoped restart non-interference.

Operational impact

Regressions ship unnoticed; dogfooding requirement unenforceable.

Scope

Automated tests proving:

  1. One LLM cannot restart MCP unilaterally
  2. New work stops during drain
  3. Active safe work can finish
  4. Unsafe mutations block restart
  5. Session state is durably checkpointed
  6. Leases/locks not silently orphaned
  7. Sessions resume or receive canonical next action
  8. Failed drain creates durable incident work
  9. Restart of one component does not unnecessarily interrupt unrelated work
  10. Restart/upgrade workflows do not require manual chat reconstruction

Use fixtures/fakes for multi-session; integration where safe.

Non-goals

  • Live kill of developer machines in CI.
  • Full HA multi-node tests (later).

Required implementation investigation

#655 children; pytest patterns; compliance harness.

Proposed implementation direction

tests/test_mcp_restart_governance.py multi-agent simulation harness.

Security / workflow-safety

Tests must not disable fail-closed gates globally.

Failure behavior

Test fail = release blocker for restart features.

Acceptance criteria

  1. All 10 dogfooding bullets covered by tests (or explicitly marked pending with issue if env-blocked).
  2. CI runs suite on restart-related changes.
  3. Links #652 #653 #655.

Required tests

This issue is the test delivery.

Observability and audit

N/A beyond test logs.

Dependencies

  • Parent #655 · Soft-depends #658–#665 · Vision #652 · Roadmap #653

Rollout

Land tests alongside features; expand coverage incrementally.

Canonical issue state

STATE: ready-for-author
WHO_IS_NEXT: author
NEXT_ACTION: Implement concurrent restart safety tests
NEXT_PROMPT: Author dogfooding tests under #655; PR; stop

Required proof

Green test suite output in PR.

Required final response and handoff

Brief PR → reviewer.

## Problem statement No realistic concurrent-session test suite proves restart governance: unilateral deny, drain behavior, checkpoints, lease safety, scoped restart non-interference. ## Operational impact Regressions ship unnoticed; dogfooding requirement unenforceable. ## Scope Automated tests proving: 1. One LLM cannot restart MCP unilaterally 2. New work stops during drain 3. Active safe work can finish 4. Unsafe mutations block restart 5. Session state is durably checkpointed 6. Leases/locks not silently orphaned 7. Sessions resume or receive canonical next action 8. Failed drain creates durable incident work 9. Restart of one component does not unnecessarily interrupt unrelated work 10. Restart/upgrade workflows do not require manual chat reconstruction Use fixtures/fakes for multi-session; integration where safe. ## Non-goals * Live kill of developer machines in CI. * Full HA multi-node tests (later). ## Required implementation investigation #655 children; pytest patterns; compliance harness. ## Proposed implementation direction `tests/test_mcp_restart_governance.py` multi-agent simulation harness. ## Security / workflow-safety Tests must not disable fail-closed gates globally. ## Failure behavior Test fail = release blocker for restart features. ## Acceptance criteria 1. All 10 dogfooding bullets covered by tests (or explicitly marked pending with issue if env-blocked). 2. CI runs suite on restart-related changes. 3. Links #652 #653 #655. ## Required tests This issue *is* the test delivery. ## Observability and audit N/A beyond test logs. ## Dependencies * Parent **#655** · Soft-depends **#658–#665** · Vision **#652** · Roadmap **#653** ## Rollout Land tests alongside features; expand coverage incrementally. ## Canonical issue state ```text STATE: ready-for-author WHO_IS_NEXT: author NEXT_ACTION: Implement concurrent restart safety tests NEXT_PROMPT: Author dogfooding tests under #655; PR; stop ``` ## Required proof Green test suite output in PR. ## Required final response and handoff Brief PR → reviewer.
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 anti-stomp mcp-health status:ready type:feature workflow-hardening
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#666