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

Web Console: Stale-runtime recovery, worktree rebinding, and reconciliation controls (Phase 2) #644

New Issue
Open
opened 2026-07-10 14:40:56 -05:00 by jcwalker3 · 0 comments
jcwalker3 commented 2026-07-10 14:40:56 -05:00
Owner
Copy Link
Copy Source

Problem statement

Stale runtimes, unbound/missing worktrees, and incomplete reconciliation currently require expert shell recovery. The console needs canonical recovery controls: detect stale runtime, rebind worktrees, and trigger sanctioned reconciliation — with live revalidation.

User and operational impact

Workers fail mid-stage; humans babysit recovery; dirty/root worktrees violate branches-only rules.

Scope

  • Detect stale runtime and worktree mismatch via inventory/health APIs.
  • Gated actions: rebind session worktree, trigger reconciler cleanup preview/apply where allowed, mark blocked until healthy.
  • Always revalidate live Gitea/Git state after recovery.
  • Integrate contamination rules (#630) and master-parity resolver authority (#610).

Explicit non-goals

  • No root-checkout mutations for feature work.
  • No unsanctioned process kill.
  • No automatic destructive worktree deletion without confirmation.

Required implementation investigation

#641, #636, #634, #642, #610, #618, reconciler workflows, author_mutation_worktree.py, #631.

Proposed architecture or implementation direction

Recovery playbook DTOs + gated actions; UI wizard: diagnose → preview → confirm → verify.

Security and workflow-safety requirements

RBAC; confirmation; audit; fail closed; branches-only enforcement.

Acceptance criteria

  1. Diagnosis surfaces stale runtime and worktree binding errors.
  2. Rebind/reconcile actions gated and audited.
  3. Post-recovery verification required before clean status.
  4. Tests for diagnose/preview/apply/deny paths.
  5. Docs list sanctioned recovery only.

Required tests

Gated recovery tests; contamination interaction tests.

Observability and audit requirements

Full audit trail of recovery steps.

Dependencies and linkage

Canonical issue state

STATE: ready-for-author
WHO_IS_NEXT: author
NEXT_ACTION: Implement gated recovery controls after inventory+auth
NEXT_PROMPT: Author recovery gates; PR; stop

Required final evidence

PR with actions, UI, tests, docs.

Required final response and handoff expectations

Brief PR → reviewer.

## Problem statement Stale runtimes, unbound/missing worktrees, and incomplete reconciliation currently require expert shell recovery. The console needs **canonical recovery controls**: detect stale runtime, rebind worktrees, and trigger sanctioned reconciliation — with live revalidation. ## User and operational impact Workers fail mid-stage; humans babysit recovery; dirty/root worktrees violate branches-only rules. ## Scope * Detect stale runtime and worktree mismatch via inventory/health APIs. * Gated actions: rebind session worktree, trigger reconciler cleanup preview/apply where allowed, mark blocked until healthy. * Always revalidate live Gitea/Git state after recovery. * Integrate contamination rules (#630) and master-parity resolver authority (#610). ## Explicit non-goals * No root-checkout mutations for feature work. * No unsanctioned process kill. * No automatic destructive worktree deletion without confirmation. ## Required implementation investigation #641, #636, #634, #642, #610, #618, reconciler workflows, `author_mutation_worktree.py`, #631. ## Proposed architecture or implementation direction Recovery playbook DTOs + gated actions; UI wizard: diagnose → preview → confirm → verify. ## Security and workflow-safety requirements RBAC; confirmation; audit; fail closed; branches-only enforcement. ## Acceptance criteria 1. Diagnosis surfaces stale runtime and worktree binding errors. 2. Rebind/reconcile actions gated and audited. 3. Post-recovery verification required before clean status. 4. Tests for diagnose/preview/apply/deny paths. 5. Docs list sanctioned recovery only. ## Required tests Gated recovery tests; contamination interaction tests. ## Observability and audit requirements Full audit trail of recovery steps. ## Dependencies and linkage * Parent: #631 · Depends: #633, #636, #641 · Related: #642, #610, #618, #630 ## Canonical issue state ```text STATE: ready-for-author WHO_IS_NEXT: author NEXT_ACTION: Implement gated recovery controls after inventory+auth NEXT_PROMPT: Author recovery gates; PR; stop ``` ## Required final evidence PR with actions, UI, tests, docs. ## Required final response and handoff expectations 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 dashboard stale-runtime 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#644