Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,6 +28,8 @@ Sections dated before 2026-09-19 predate the cycle and stay as they are. Named m
- learn(security): **MxAdmin no longer "ships with password `1`" in the rules (#662)**: `learned-mdl-preflight.md` (baseline), `brd-to-build-plan.md` Step 7 and the rendered `generated/rules-access.md` now say MxAdmin exists only where the runtime host created it (Studio Pro's own run, or the buildpack's `ADMIN_PASSWORD`); `mxcli run --local` never creates it (`MxAdmin user ... does not exist!`) and `mxcli docker build` seeds `admin` / `Admin123!` instead, so sign in as a demo user. The "never touch MxAdmin" rule stays — field run, 2026-11
- fix(build-tree): **`bin/build-tree.py` excludes `node_modules` at any depth, not only at the project root (#764)**: `skip()` ran only for top-level names, so a custom widget's nested `widgets/<W>/node_modules` (1.2 GB in the field) was copied into `.mxtk/build/model/` on every full build, and one exec stalled for 13+ minutes. A nested `node_modules` already in an existing copy is removed on the next sync; the other excluded names (`deployment`, `docs`, `.mxcli`, `.mxtk`, ...) stay top-level only, since a widget may hold its own. The one exception is the top-level `javascriptsource/` tree, whose `node_modules` hold JavaScript actions' npm dependencies that mxbuild bundles: those are still copied. `test-build-tree.sh` B4c covers both. — a Greenfield field run (2026-11-13)

- fix(tests): **`tests/wave2/run-all.sh` exports `MXTK_NO_GUIDE=1`**: every fixture that scaffolds a fresh project through `bin/init-project.sh` opened `toolkit-guide.html` in the developer's real browser, one tab per fixture for the whole run; `test-guide-reopen.sh` unsets it, since it tests the opening with a fake `open` — Maurits Visser, from a local full-suite run

## v2026.11.16
- fix(gitignore): **`bin/doctor.sh` appends its machine-local entries (`.doctor-receipt`, `toolkit.env`, `progress-report-sessions.txt`, `.property-sets-receipt`) through `mxtk_gitignore_ensure`**: a CRLF `.gitignore` got LF lines (mixed endings) and could get an entry it already had added again; LF files get the same bytes as before, and the "(added … to the project's .gitignore)" note now prints only when a line was actually written — follow-up to the .gitignore line-ending fixes, 2026-11
- fix(journey-runner): **The HTML report now shows resolved seed values in step names, check labels, the journey title and the page-says expectations instead of `{{seed}}` (#668, the report half).** `report-render.js` resolves them for display only, on a copy, from the seeds the walk already records (`walks[].seeds`); stored names, `report.json`, ids, anchors and every join key stay raw (`report-normalize.js` still matches rows to the contract by the raw string), a placeholder with no seed stays visible as written, and a walk with no recorded seeds renders as before. `journey-runner.js` also exports `walks` (for fixtures; no behaviour change). New `tests/wave2/test-report-seeds-668.sh` on a capture from the real runner — field run, 2026-11
Expand Down
4 changes: 4 additions & 0 deletions tests/wave2/run-all.sh
Original file line number Diff line number Diff line change
Expand Up @@ -23,6 +23,10 @@ FAILED=0; RAN=0; SKIPPED=0
# registers the project name in the toolkit's gitignored denylist unless told otherwise. Send it
# to scratch here for every fixture, and refuse at the end if the real one appeared anyway.
export MXTK_LEAKGUARD_DENYFILE="${TMPDIR:-/tmp}/mxtk-runall-denylist.$$"
# Same idea for the browser: every fixture that scaffolds a fresh project through init-project.sh
# would open toolkit-guide.html in the developer's real browser, one tab per fixture, all run long.
# test-guide-reopen.sh unsets this and uses a fake `open` to test the opening itself.
export MXTK_NO_GUIDE=1
ROOT_DENY="$TOOLKIT/.leakguard-deny"; ROOT_DENY_BEFORE=0; [ -f "$ROOT_DENY" ] && ROOT_DENY_BEFORE=1

echo "### SYNTAX — every shell script in the toolkit"
Expand Down
2 changes: 2 additions & 0 deletions tests/wave2/test-guide-reopen.sh
Original file line number Diff line number Diff line change
Expand Up @@ -17,6 +17,8 @@
# toolkit leak-guard denylist; send that to scratch, never to the developer's real list.
export MXTK_LEAKGUARD_DENYFILE="${TMPDIR:-/tmp}/mxtk-fixture-denylist.$$"
trap 'rm -f "$MXTK_LEAKGUARD_DENYFILE"' EXIT
# run-all.sh exports MXTK_NO_GUIDE=1 so the suite opens no tabs; this test needs the opening.
unset MXTK_NO_GUIDE

SUBJECT="${1:-$(cd "$(dirname "${BASH_SOURCE[0]}")/../../bin" && pwd)/init-project.sh}"
TOOLKIT="$(cd "$(dirname "${BASH_SOURCE[0]}")/../.." && pwd)"
Expand Down
Loading