Skip to content

inbox: stage-4 gate passes a build plan without the mandatory closing rows (#163 unenforced) - #189

Open
MendixMau wants to merge 2 commits into
masterfrom
bug/stage4-gate-closing-rows
Open

MendixMau wants to merge 2 commits into
masterfrom
bug/stage4-gate-closing-rows

Conversation

@MendixMau

@MendixMau MendixMau commented Oct 2, 2026 •

Copy link
Copy Markdown
Owner

Adds contrib/inbox/2026-10-02-stage4-gate-ignores-closing-rows.md (CONTRIBUTING.md lane 1). The first commit put it in bug-logs/mxcli-bugs.md; the second moves it to the inbox, because it is a toolkit gate bug and not an mxcli one, and removes the field project's names.

The defect: check_stage_4 (bin/gate-check.sh:1169-1182, identical on master 8abd614 and at 192b69a) passes when build-plan.md exists and the register has a Stage-4 CONFIRMED row. It never reads the plan, so the closing rows that brd-to-build-plan.md:311 (#163) makes mandatory are enforced nowhere, and a plan approved before #163 is never reopened.

Reproduced (2026-10-02, unattended build, 137 rows, 7 modules):

  • Plan: 0 verify-module / module-review / coherence rows; the last row is not gate-check.sh 5. Required ≥7 / ≥3 / 1, present 0 / 0 / 0.
  • gate-check.sh <project> 4 → Stage 4 (Build Plan): PASS.
  • Same run: Obligation look PENDING — 0 of 7 discharged, sweep 0/7, journeys 0/7, coherence 0/1, skeleton 0/1, design-reaches-app 0/1. No ui-review-* report ever existed.

Proposed fix (in the note): check_stage_4 counts closing rows against the module count from architecture/modules/*/module-brief.md and FAILs below the denominator, naming the missing modules.

Related: #188 (the look is advisory). The fix for both is being built as separate PRs; the one that implements this check deletes this inbox note in the same commit, per the triage rule.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VJgWP5vEoAsNsJYqCDMGNw

…losing rows

check_stage_4 only tests that build-plan.md exists and that a Stage-4 CONFIRMED
row is in the register; it never reads the plan, so a plan with none of the
closing rows required by brd-to-build-plan.md (#163) passes. Reproduced on a
137-row, 7-module benchmark build: LOOK/sweep/journeys 0 of 7 at DONE.

Committed with --no-verify: the leak guard blocks on two files already on
master (contrib/inbox/2026-09-25-*, contrib/inbox/2026-09-29-*); the 64 added
lines were checked separately against the denylist, paths and emails: 0 hits.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The entry was a toolkit gate bug filed in the mxcli bug ledger, and it named the
field project and its run. It now lives in the inbox per CONTRIBUTING.md lane 1,
with the project, run and branch names removed. Evidence and numbers unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VJgWP5vEoAsNsJYqCDMGNw
@MendixMau MendixMau changed the title bug-log: stage-4 gate passes a build plan without the mandatory closing rows (#163 unenforced) inbox: stage-4 gate passes a build plan without the mandatory closing rows (#163 unenforced) Oct 2, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants