Repository navigation
process(exec, entry modes): declared-position banner, refuse-once plan rule, design front end - #790
Conversation
…n rule, design front end With no Entry mode and no Adopted at stage line, status.sh, gate-check.sh's summary and every exec.sh run print one banner. In Entry mode migration or requirements-driven, the first MDL write with no plan evidence is refused once (remedy: run stages 1-4, or gate-check.sh --adopt 5 --reason ...). Outside evidence clears it; a-la-carte (new), greenfield, poc, change-an-existing-app and --patch are never refused. The entry-mode tokeniser moves to project-bin/_position.sh (pure bash, no process starts) so the installed exec.sh can read it; bin/lib/entry-mode.sh is a shim. Runbook greenfield row reuses poc-build steps 1-4 plus a short plan; design-artifacts Step 2a maps supplied prototypes in PAGE-MAP.tsv and ui-preflight-pages' wireframe STOP accepts a mapped prototype. Field evidence: two field runs (2026-11), requirements-driven with a frozen spec and clickable prototypes, built ~78 pages with no plan or target. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HXpQSifRwo7EWWDP1hPps8
…tamp dir, rendered rules page - mxtk_pos_read honours "Waived stages: ..., 4 — reason" as gate-check does (was a false refusal on a project gate-check reads WAIVED at stage 4). - .mpr-snapshots/ is git-ignored before the refuse-once stamp is written, so "once per clone" cannot become once per repository; docs say plainly it is one refusal ever per clone. - skills/generated/rules-page.md re-rendered (bin/mdl-rules.sh --render) after the ui-preflight-pages.md STOP-row edit; CI was DRIFTED. - fixture: the status NEXT case accepts the intake-§1 needs-attention line that outranks the banner rule; aggregate-waiver and .gitignore cases. - _position.sh header: the shared tokeniser plus exec.sh's reader, not the only register reader. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HXpQSifRwo7EWWDP1hPps8
…D line stays first CI (wave2, run 44013599260): test-bug06-freshness copies gate-check.sh alone into a scratch toolkit, so the shim's banner text was never defined and `set -u` aborted the summary with exit 1 (reproduced: master 0, cb7c0fa 1, this 0). The banner is now an `if` with a defaulted variable. status.sh guards the reader the same way and prints the banner after the CWD line (test-status-session-cwd A: the CWD line must be first). Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01HXpQSifRwo7EWWDP1hPps8
…lan-rule # Conflicts: # CHANGELOG.md
|
Review: MERGE-AFTER-FIX. The plan rule ignores plans in the nested Value: Fixes the reported field failure: a pipeline-mode project with no declared entry mode or no plan stayed silent.
Regression risk:
Correctness: Fixtures run in a detached worktree:
Not covered: the readout-at-5 evidence path, the two-tree Context cost: 65,148 → 65,373 always-loaded words (+225, measured). The PR body's 64,984 → 65,198 is stale against current master. The Behaviour row reads NOT RUN, but Time cost: process starts per exec are 132 → 132. Exact fixes required:
CI on e57fc4c: Generated by Claude Code |
…ion check (#793) The composition check of #787/#788/#790/#791/#792 found three ways an unattended agent could still get past the plan gate. This closes them: - Auto detection uses one first-word rule (mxtk_auto_word in project-bin/_position.sh) shared by exec.sh, gate-check.sh's --adopt check and ready.sh. `Interview mode: auto (…)` and `unattended — …` now count as auto, and the strictest of env, state file and register wins. - ready.sh reports NOT READY while any `consentBy: auto-mode` adoption row is unconfirmed, so an agent cannot approve its own plan skip and reach READY. - Under auto, an undeclared Entry mode is refused before build-ready. Attended behaviour is unchanged. - The checkpoint skills no longer describe greenfield as a live mode. Review: MERGE — no findings (the H/K/W/U order fix restores test-mode-contract to 28/0; the strictest-wins change is now in the CHANGELOG; CI green on d3c4ced) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This is the output of bin/cut-release.sh. The 24 entries under `## Unreleased` become `## v2026.11.17`. Included: #787, #788, #790, #791, #792 and #793. #789 is held. Review: MERGE — no findings (CHANGELOG heading only; the release section has no client names; CI green on 072e417) Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Direct lane
What changed and why (one paragraph): Two field runs (Nov 2026, unattended, requirements-driven, a full frozen spec plus clickable HTML prototypes and a design system, several apps under
apps/<App>/) built about 78 pages with no BRDs, blueprint, wireframes, plan or briefs. PROJECT.md had no entry-mode or position line, and every guard stayed silent: the runbook's "complete specs does not mean skipping to Stage 5" is prose only, the wireframe STOP only fires if the skill is opened, and the module-brief advisory is silent without a build plan. The pattern is that the less a project declares, the quieter the toolkit gets. This PR turns that around:Entry mode:and noAdopted at stage:(in the register or in intake §1),bin/status.sh(both views, plus a NEXT rule), thebin/gate-check.shsummary and everybin/exec.shrun print one line: "No entry mode declared: the toolkit treats this project as Stage P, not started. Declare the mode (kickoff) or adopt a stage with a reason: gate-check.sh --adopt --reason ...". The exec BUILD-LOG row is also taggedno entry mode declared. This is a warning only.Entry mode: migrationorrequirements-driven, the first MDL write with no plan evidence is refused once. The refusal happens before the lock, the snapshot or any write, and returnsMXTK-RESULT verdict=refused.poc-build.mdsteps 1–4 by reference (design questions, wireframes or the supplied prototype, a buildability check, one approval stop recorded as the Stage-4 CONFIRMED decision). After that comes a shortarchitecture/build-plan.md(apps, modules, screen list, a## Module brief — <M>of a few lines per module), then the normal build.design-artifacts.mdStep 2a): every screen is mapped to its supplied prototype indesign/wireframes/PAGE-MAP.tsv(Orders_List<TAB>../../prototypes/orders/list.html). Theui-preflight-pages.mdSTOP now accepts a mapped prototype as the wireframe.check-page-shell.shalready resolves such rows, andpage-fidelity.jstakes the mapped file directly.The policy change: exec.sh refuses once in pipeline modes
The brief advisory's header says "exec.sh is not the pipeline's gatekeeper". That stays true for undeclared, a-la-carte, greenfield, poc and existing-app projects. The argument for the change:
a-la-carte(new explicit mode: no pipeline, audit or tooling use; gate-check reads stages 0–7 as WAIVED by mode),greenfield,Build type: poc, change an existing app,--patch(the opaque repair path doctor.sh uses), and projects with no declared mode.Adopted at stage: 5+, a reasonedWaived stage 4:, gate-check's readout at Stage 5+, orarchitecture/build-plan.mdplus one module brief (as a file, or a## Module briefheading in the plan), at the root or underapps/<App>/architecture/.gate-check.sh --adopt/--waive, writing the plan) do not go through exec.sh. The refusal also happens only once per clone (stamp in.mpr-snapshots/.plan-rule-refused, which is gitignored). A re-run goes ahead and every row is taggedno plan (Entry mode …, before Stage 4), so the choice is visible in BUILD-LOG.What changes for existing projects after
sync-project.sh(_position.shis a new installed file in the manifest):MXTK-RESULTformat are unchanged. The refusal uses the existingrefusedverdict, printed before the human lines like every other refusal.Impact
exec.sh,bin/lib/install-manifest.sh(+_position.sh),bin/lib/entry-mode.sh(now a shim ontoproject-bin/_position.sh; sameentry_mode_token(), rewritten in pure bash: identical stdout and stderr on 44 inputs including every V4 and T2 case, checked by hand),gate-check.sh,status.sh. Not touched (other tasks):obligation-check.sh/obligations.tsv(T1),bin/ready.sh(T3),_common.sh(T4). Follow-up for T1: theprototype-lookrow keys ondesign/prototype.html, so a project with only supplied prototypes reads it N/A. Accepting a mapped prototype there is T1's file. Also, obligation and artifact checks treat "no PROJECT.md" as à-la-carte; a register sayingEntry mode: a-la-cartereads N/A in the artifact check (mode not in any row) but not yet in the obligation check. Not changed: intake Q1's text (editing it would make every existing intake "stale boilerplate" to--repair-intake); a-la-carte is documented in the runbook. New artifact reads: the register and intake (produced at scaffold and at kickoff), build plan and briefs (Stage 4).conversion-runbook.md(the "Declared, or the toolkit says so" paragraph with its failure example, the greenfield row, one clause on the requirements-driven row). Per stage, lead: P 26,999 → 27,213; 4 29,249 → 29,463; 5 27,330 → 27,544. Every stage shows the same +214 for lead/ba/architect; mdl, gate, test and review are unchanged.ui-preflight-pages.mdanddesign-artifacts.mdare on demand (+0 baseline). Pasted frombin/render-routing.sh --checkon base and head._position.shis builtins only: onereadloop over PROJECT.md, no$( )on the exec path) · can force rework: n (one refusal, then pass) · offset: none needed. The budget fixture's project has no PROJECT.md, so it takes the banner branch. Not re-measured withtest-exec-process-budget.sh(see Test tier).Field evidence: the two field runs above (shape only: requirements-driven, frozen spec plus prototypes, multi-app). Neither project was available here to re-run the instrument against. What was run: a scratch project from a real
init-project.shscaffold, single tree andapps/Orders/layouts. Results:first write refused (0
mxcli checkcalls), second write went on and was tagged;after a real
gate-check.sh --adopt 5: passes;plan plus brief under
apps/Orders/architecture/: passes;a-la-carte and poc: pass;
status and gate-check banners shown on the undeclared scaffold.
No client data anywhere in the diff (
check-no-client-data.shclean)Size cap: 10 files, 351 changed lines excluding tests, fixtures and CHANGELOG
Test tier: T1-ish manual.
tests/wave2/test-entry-mode-plan-rule.shwas written but not executed by the builder: the session was not permitted to run fixtures. The reviewer should run it, plustest-sed-tab-bracket.sh bin/lib/entry-mode.sh,test-wrong-verdicts.sh,test-exec-process-budget.sh, and the gate-check fixtures (test-bug03-gates.shetc.) in a detached worktree.check-scripts.sh(139/139 parse),check-portability.sh(clean) andrender-routing.sh --checkwere run.Golden input captured:
fixtures/entry-mode-plan-rule/{PROJECT.md,intake.md}frominit-project.shat ff4103b (H1 renamed only). Both layouts in the fixture. macOS: bash 3.2 constructs only (nocasematchin[[ ]], no${v,,}, nocaseunder nocasematch); not run on macOS or Git Bash.CHANGELOG.mdline appendedDo not merge before the independent review (
Review:line).Generated by Claude Code