Repository navigation
test(status-guards): pin the recursive readiness and status guard - #94
Merged
49115566 merged 3 commits intoOct 14, 2026
Conversation
The recursive readiness algorithm, the derived-state precedence at a node, and the /status render shape were documented and swept but pinned by no committed fixture deeper than two levels: tests/checks/87-backtrack-guards.sh deliberately skips decomposing nodes and the cycle fixture is depth 2, so a regression that flattened the model, mis-derived a nested or hybrid node, or dropped the /status indentation would still pass the suite unnoticed. Add the additive tests/fixtures/recursive-status/ tree, three levels deep with a hybrid node, a .gitkeep-only leaf, a deliberate dependency cycle, every dependency-satisfaction case, the decomposing-target cases, and the derived-state overlay cases, plus the new AC27 area tests/checks/89-recursive-status-guards.sh. The area computes each fixture node's readiness, derived phase, and per-container summary from the authority and compares them to reviewed literal expected blocks, pins the recursive /status render contract against docs/workflow.md and the status prompts, and asserts its own read-only and no-duplication contract. It adds no production checker and edits no non-test surface. Refs: work/0015-recursive-workflow-guards/0002-recursive-readiness-status-guard
…-workflow-guards/0002-recursive-readiness-status-guard Tick all eight build tasks and add verify.md (617 passed, 0 failed, 0 skipped on bash tests/run.sh; 66 of them the new AC27 area) and review.md (verdict approve, no surviving finding of any severity). Refs: work/0015-recursive-workflow-guards/0002-recursive-readiness-status-guard
…-recursive-readiness-status-guard Record the branch, commits, PR #94, and the fast-forward reconcile with origin/main in ship.md; its presence is the shipped signal. Refs: work/0015-recursive-workflow-guards/0002-recursive-readiness-status-guard
49115566
deleted the
test/0015-recursive-workflow-guards+0002-recursive-readiness-status-guard
branch
October 14, 2026 15:22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Adds
tests/checks/89-recursive-status-guards.sh(suite tokenAC27) and the committed fixture roottests/fixtures/recursive-status/, pinning recursive readiness, derived-state precedence, and the/statusrender shape at depth >= 3. Work item:work/0015-recursive-workflow-guards/0002-recursive-readiness-status-guard.Changes
tests/checks/89-recursive-status-guards.sh— new AC27 area: recursive readiness, nested readiness, dependency satisfaction (shipped / approved-unshipped / changes-requested / no review / recalled / ship-presence precedence), decomposing-target own-signal-only plus sibling-only resolution, cycle readiness, derived phase, overlay precedence, per-container summary,/statusrender pins, determinism, no-stored-readiness, and the structural fixture-existence / read-only-contract / no-duplication assertions.tests/fixtures/recursive-status/items/— new fixture tree, three levels deep, with a hybrid node, a.gitkeep-only leaf, a deliberate dependency cycle, and every dependency and derived-state case.work/0015-recursive-workflow-guards/0002-recursive-readiness-status-guard/{tasks.md,verify.md,review.md}— the build, test, and review artifacts for the item.Testing
bash tests/run.sh->TOTAL: 617 passed, 0 failed, 0 skipped(exit 0); 66 of them the new AC27 area.Conflict detection
origin/main,ddda28c): merge basef657156;git merge-tree --write-treereported no conflicting paths; no duplicateNNNN/MMMMprefix at any node; no manifestDepends ondangling/missing/unlisted/cyclic reference; no README inventory/count drift; no cross-branch sequence collision.Reconcile
f657156->ddda28coforigin/main)work/paths (sibling0003/0004artifacts), thework/artifact reconcile was re-run on the merged tree: no duplicate prefix, no graph fault, no renumber.bash tests/run.sh-> 617 passed, 0 failed, 0 skipped; item checks (FRAMEWORK_TEST_AREAS=89-recursive-status-guards) -> 66 passed (seeverify.md).Risks
bash tests/mutation.shpass is transiently red until0005-guard-registration-sweepregisters the new fixture root in the mutation runner staged-copy list — registration is owned downstream per the spec non-goals.bash tests/run.sh(the CI command) is unaffected, andtests/mutation.shis not run in CI.verify.md.Artifacts
Workflow artifacts under
work/are committed working state, so these paths exist on the branch and resolve for a reviewer who does not share the working tree:work/0015-recursive-workflow-guards/0002-recursive-readiness-status-guard/spec.mdwork/0015-recursive-workflow-guards/0002-recursive-readiness-status-guard/design.mdwork/0015-recursive-workflow-guards/0002-recursive-readiness-status-guard/verify.mdwork/0015-recursive-workflow-guards/0002-recursive-readiness-status-guard/review.md