You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Commit 6164bc6
Browse filesBrowse the repository at this point in the historyBrowse files
A HOME or toolkit path with a space broke copy-paste of the printed
`<path> --write` and install-hint commands. Both are now single-quoted,
with embedded ' escaped via sed for bash 3.2. The ~/.claude/bin copy
(claude-hooks/bin/close-task.sh) printed a bare checkpoint.sh, though
~/.claude/bin is usually not on PATH; it now prints its sibling's full
path, quoted. The fixture gains T7a-c (space in HOME, space and ' in the
toolkit path, quoted install hint; each printed line is eval'd) and T8
(hooks copy): 14/14 pass, 11 fail on master.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01VJgWP5vEoAsNsJYqCDMGNw
Copy file name to clipboardExpand all lines: CHANGELOG.md
+1-1Lines changed: 1 addition & 1 deletion
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -19,7 +19,7 @@ Sections dated before 2026-09-19 predate the cycle and stay as they are. Named m
19
19
20
20
## Unreleased
21
21
22
-
- fix(close-task): **`close-task.sh` resolves `checkpoint.sh` instead of printing it bare.** The script ships at `claude-hooks/bin/checkpoint.sh` and reaches `~/.claude/bin` only via the opt-in `bin/install-claude-hooks.sh --basic`, so a project without the hooks got a `checkpoint.sh --write` step it could not run. `close-task.sh` now looks in PATH, then `~/.claude/bin`, then `$MXTK_ROOT/claude-hooks/bin`, and prints the full path it found. If none is found it prints `checkpoint.sh not installed — run <toolkit>/bin/install-claude-hooks.sh --basic, or skip: RESUME.md is the resume source` and carries on; the exit code still means only "writes owed". `close-the-loop.md` step 4 says the same. Fixture `tests/wave2/test-close-task-checkpoint.sh` (10 cases; 7 fail on master). Field evidence: the reporter's existing-app run, where the closing agent had to skip the step with no pointer. — joshuamoesa (#358)
22
+
- fix(close-task): **`close-task.sh` resolves `checkpoint.sh` instead of printing it bare.** The script ships at `claude-hooks/bin/checkpoint.sh` and reaches `~/.claude/bin` only via the opt-in `bin/install-claude-hooks.sh --basic`, so a project without the hooks got a `checkpoint.sh --write` step it could not run. `close-task.sh` now looks in PATH, then `~/.claude/bin`, then `$MXTK_ROOT/claude-hooks/bin`, and prints the full path it found, single-quoted so a path with spaces survives copy-paste. If none is found it prints `checkpoint.sh not installed — run <toolkit>/bin/install-claude-hooks.sh --basic, or skip: RESUME.md is the resume source` and carries on; the exit code still means only "writes owed". `close-the-loop.md` step 4 says the same. The `~/.claude/bin` copy (`claude-hooks/bin/close-task.sh`) now prints its sibling `checkpoint.sh` by full quoted path, because `~/.claude/bin` is usually not on PATH. Fixture `tests/wave2/test-close-task-checkpoint.sh` (14 cases, including a space and `'` in HOME and the toolkit path; 11 fail on master). Field evidence: the reporter's existing-app run, where the closing agent had to skip the step with no pointer. — joshuamoesa (#358)
23
23
- process(build): **Stage 5 drafts the ready set in parallel and applies serially.** The runbook dispatch row said "sequential within a module", which serialised drafting even for independent scripts; it now points to `iterative-build-loop.md` → Gate cost, the single statement of the rule. The unit is the build-plan row: every `BUILD` row whose "Depends on" rows are all applied, minus overlapping writers (two rows that replace, alter or drop+create the same document never share a ready set, and no row is drafted while it overlaps a queued unapplied one; `brd-to-build-plan.md` has Produces name every document a row writes), runs at once, its scripts in order, one `mdl-agent` per script. Applies stay one at a time through `bin/exec.sh`, and the ready set is recomputed after each. A queued draft made before a sibling apply landed is re-checked with `mxcli diff --format struct` (preflight STOP rule 23); any removal line (checked against `describe` per BUG-146) or STOP rule 21 target means re-draft, never patch, because a stale restatement of a shared document is exactly rule 21's silent seed-call loss and passes `check --references`. Report `ready set N, drafted N, applied k`; the `mdl-agent` template says a drafter never applies and never depends on an unapplied draft. Field evidence: none yet. — MendixMau
24
24
- fix(platform-link): **CLI commits now show their changed documents in Studio Pro History.** Studio Pro's History → Model changes pane reads a `ModelChanges` array from the commit's `refs/notes/mx_metadata` note. Trap 6c's hand-written template set it to `[]`, so every mxcli/agent commit showed "Model changes 0" (field project: 270 of 270 notes empty). New `project-bin/mx-metadata-note.py` (stdlib only) computes the array from the commit's changed `.mxunit` files, in Studio Pro's entry shape: Status, UnitID, UnitType, UnitName and Module (walked up the `.mpr` Unit tree). It has `changes` / `write` / `backfill` / `sync <remote>` subcommands. `install-project-hooks.sh` now also installs post-commit and post-rewrite hooks that write the note and never block, and `--check` covers them, so `sync-project.sh` rolls them out to wired projects. Notes are published with `mx-metadata-note.py sync <remote>` after the branch push. Push config is never touched. With mxcli v0.26+ in the project root the hooks call `mxcli git note --write` instead (mendixlabs/mxcli#1337); the Python script is the fallback for older pins, and on 160 field commits both wrote the same 3,594 entries. Trap 6c rewritten. Measured against Studio Pro's own notes, 51 commits in 5 apps: 3387/3389 entries exact on all five fields. Field run on a 357-commit Mendix 11.15.0 app: 158 notes backfilled and pushed, and Studio Pro History lists the documents per revision. Review fixes: an earlier revision added `HEAD` + the notes ref to `remote.<r>.push`. It was dropped because any push refspec replaces `push.default`. A branch tracking a differently named upstream got a new same-named branch on Team Server where `simple` refuses, a missing local notes ref failed the whole push, and nobody knows whether Studio Pro's own push reads that config. The installer now only fetches the remote's notes (non-forced). It removes that exact `HEAD` + notes pair if present, and leaves and reports any other entry. `sync` handles a remote with no notes ref (it used to exit 1) and retries a rejected push once after re-merging. A note that already lists changes (Studio Pro's) is never overwritten by `write`/`backfill` without `--force`, and `sync` keeps a colleague's non-empty note over ours. The mxcli probe greps `git note --help` for `--write`. Hooks and docs call the script through `resolve_py`. Fixture `tests/wave2/test-mx-metadata-note.sh` (40 cases, over real captured template units; single- and two-tree layouts, amend, backfill and `--force`, push exit codes identical to a no-hooks clone, leftover-refspec cleanup, sync to an empty remote and its retry, notes fetch at install, a diverged notes merge; green under `init.defaultBranch` master and main). — field project (Mendix 11.15 app), MendixMau
25
25
- learn(fixture-seeding): **explore the data structure first, choose rows by use case, scan actions for resets before any run.** Two seeding runs on public template apps: seeding raised journey passes 33 -> 58 and 20 -> 51 of the same sets (FAIL 93 -> 68, 163 -> 132; INVALID unchanged), and a "Reset all demodata" journey wiped accounts so 104 of 127 journeys reported `The username or password you entered is incorrect`, identical on empty and seeded databases. Skill gains three questions a seed must answer, a use-case checklist, a destructive-action scan, a generic traps table with symptoms, measured expectations and a denominator checklist; routing trigger now fires on seed/test/demo data and empty pages. Independent review fixes: object ids follow the Mendix bigint pattern with a business-key guard (no uuids), associations are seeded where the page's path stores them, four new traps (enum names, inheritance chain, calculated attributes, view/external entities), and the port-offset and container-label traps moved to `harness-architecture.md`. — MendixMau
grep -qF "$TMP/pathbin/checkpoint.sh --write"<<<"$out"&& ok "T1 prints PATH hit"|| bad "T1 prints PATH hit""$(grep -n -A2 '### Then'<<<"$out")"
56
+
grep -qF "'$TMP/pathbin/checkpoint.sh' --write"<<<"$out"&& ok "T1 prints PATH hit"|| bad "T1 prints PATH hit""$(grep -n -A2 '### Then'<<<"$out")"
54
57
55
58
echo"T2 found in ~/.claude/bin"
56
59
H2="$TMP/home2"; mk_ckpt "$H2/.claude/bin"
57
60
out=$(run "$H2""$SYSPATH""$NOTK")
58
-
grep -qF "$H2/.claude/bin/checkpoint.sh --write"<<<"$out"&& ok "T2 prints ~/.claude/bin hit"|| bad "T2 prints ~/.claude/bin hit""$(grep -n -A2 '### Then'<<<"$out")"
61
+
grep -qF "'$H2/.claude/bin/checkpoint.sh' --write"<<<"$out"&& ok "T2 prints ~/.claude/bin hit"|| bad "T2 prints ~/.claude/bin hit""$(grep -n -A2 '### Then'<<<"$out")"
59
62
60
63
echo"T3 found in toolkit claude-hooks/bin"
61
64
TK="$TMP/toolkit"; mk_ckpt "$TK/claude-hooks/bin"
62
65
out=$(run "$EMPTYHOME""$SYSPATH""$TK")
63
-
grep -qF "$TK/claude-hooks/bin/checkpoint.sh --write"<<<"$out"&& ok "T3 prints toolkit hit"|| bad "T3 prints toolkit hit""$(grep -n -A2 '### Then'<<<"$out")"
66
+
grep -qF "'$TK/claude-hooks/bin/checkpoint.sh' --write"<<<"$out"&& ok "T3 prints toolkit hit"|| bad "T3 prints toolkit hit""$(grep -n -A2 '### Then'<<<"$out")"
64
67
65
68
echo"T4 lookup order"
66
69
out=$(run "$H2""$TMP/pathbin:$SYSPATH""$TK")
67
-
grep -qF "$TMP/pathbin/checkpoint.sh --write"<<<"$out"&& ok "T4a PATH wins"|| bad "T4a PATH wins""$(grep -n -A2 '### Then'<<<"$out")"
70
+
grep -qF "'$TMP/pathbin/checkpoint.sh' --write"<<<"$out"&& ok "T4a PATH wins"|| bad "T4a PATH wins""$(grep -n -A2 '### Then'<<<"$out")"
68
71
out=$(run "$H2""$SYSPATH""$TK")
69
-
grep -qF "$H2/.claude/bin/checkpoint.sh --write"<<<"$out"&& ok "T4b ~/.claude/bin beats toolkit"|| bad "T4b ~/.claude/bin beats toolkit""$(grep -n -A2 '### Then'<<<"$out")"
72
+
grep -qF "'$H2/.claude/bin/checkpoint.sh' --write"<<<"$out"&& ok "T4b ~/.claude/bin beats toolkit"|| bad "T4b ~/.claude/bin beats toolkit""$(grep -n -A2 '### Then'<<<"$out")"
70
73
71
74
echo"T5 not found"
72
75
out=$(run "$EMPTYHOME""$SYSPATH""$NOTK"); rc=$?
73
-
grep -qF "checkpoint.sh not installed — run $NOTK/bin/install-claude-hooks.sh --basic, or skip: RESUME.md is the resume source"<<<"$out" \
76
+
grep -qF "checkpoint.sh not installed — run '$NOTK/bin/install-claude-hooks.sh' --basic, or skip: RESUME.md is the resume source"<<<"$out" \
74
77
&& ok "T5a install pointer printed"|| bad "T5a install pointer printed""$(grep -n -A2 '### Then'<<<"$out")"
75
78
grep -qE '^ +checkpoint\.sh --write'<<<"$out"&& bad "T5b no bare checkpoint.sh line""$(grep -n 'checkpoint.sh --write'<<<"$out")"|| ok "T5b no bare checkpoint.sh line"
&& ok "T7b space and ' in toolkit path: quoted and runnable"|| bad "T7b space and ' in toolkit path: quoted and runnable""$(grep -n -A1 '### Then'<<<"$out")"
0 commit comments