Trace dependency evidence before /loop inactivity (#202) #203
No reviewers
Labels
No labels
accessibility
bug
documentation
duplicate
enhancement
good first issue
help wanted
invalid
P1
P2
P3
question
wontfix
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
Creatidy/scarcity-router!203
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "issue-202-dependency-eligibility"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Refs #202
Change
Evidence-gated full-queue dependency tracing before /loop inactivity: current producer revisions/accepted artifacts, unfinished local predecessor assessment, owner/evidence/stage classification, downstream acceptance preserved, missing evidence UNVERIFIED. Exact label/priority/order/review/currentness/merge/acceptance safeguards unchanged.
Technical-recovery narration is nonterminal, not an owner handoff or confirmation gate; recover uncertain validation through live-state inspection/durable logs/exit receipts, no duplicate processes. Shared full-queue requirement is explicitly /loop-only; standalone implementation/finish/review keeps selected-issue/PR-local authority.
Four workflow/test files, no runtime/product/dependency engine change.
Validation
Latest sanitized full make check PASS2782tests/17skips/605.391s,basedpyright0; explicit uv run basedpyright0, uv sync --only-dev and diff/staged whitespace PASS; focused26 original workflow contract tests PASS. Durable complete log and independent exit0 receipt retained. Eight new guards cover the six requested scenarios, nonterminal recovery and standalone-scope boundary; declarative table/text consistency, not runtime orchestration or downstream installed acceptance proof.
Exact Objects and Authority
Base/merge-base3834b52f93522fa81af6bd92d5073e04b5d0e050; HEAD3e2a76737d730ff6c37892b338046f30181e7a86. Two ordinary scoped owner commits, no merges/history rewrite. Explicit owner NEW /loop authorization: exact-approved Forgejo merge -> integrated acceptance/closure -> normal fresh SELECT in SAME primary context. Historical histories/counters retained. Not security_critical; no trust/credential/isolation/network change. No main/release/deploy/cross-repository mutation.