Relationships
#4984 stagecraft: a reconcile view that cross-checks reality (git ancestry / registry) against work-item and ticket status
Opened by kneel · 11/21/2026
Problem
publish is the single writer of a work item's status. Work done outside the loop diverges silently:
- Ticket filed, work done by direct git merge or
extension push, work item never started -- no work item exists, so no stagecraft-internal check can detect the divergence. Ticket staysopenwhile the change is shipped. - Driven to terminal
donebutpublishnever run -- ticket status never synced.
A 2026-11-19 sweep found ~19 such tickets across build/change/content/pub trackers. Because the worst mode is defined by the absence of a work item, nothing inside stagecraft surfaces it; only a human diffing git history against the tracker catches it.
Proposed
A reconcile/audit view joining ticket + work-item status against external reality:
- terminal work-item
run.statusvs.issue.status(catches done-but-unpublished), - registry/published-extension state vs. open publish tickets,
- git ancestry (is the ticket's change on the default branch?) vs. a ticket with no started work item (catches the no-work-item mode).
Output: a list of "reality says shipped, tracker says open" discrepancies for a human or cleanup step to reconcile.
Alternative considered
A stagecraft-internal lint -- can't see the no-work-item mode; the check must reach outside stagecraft's own records.
Upstream repository: https://github.com/swamp-club/swamp-extensions
Environment
- Extension:
@swamp/stagecraft@2026.11.12.1 - swamp:
20261121.015048.0-sha.7129f14c - OS:
linux(x86_64) - Deno:
2.9.8 - Shell:
/bin/zsh
Open
No activity in this phase yet.
system commented 11/21/2026, 2:49:03 AM
Classified automatically when this issue was filed.
- Source: Extensions
If you feel this classification is incorrect, add a ripple to tell us so.
Sign in to post a ripple.