Skip to content
Open
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
1 change: 1 addition & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,6 +18,7 @@ Sections dated before 2026-09-19 predate the cycle and stay as they are. Named m
`docs/RELEASE-PROCESS.md` §8.

## Unreleased
- new(exec, metrics): **refusal rows name the guard that refused**: every 🚫 / ✗ refused / ❌ / ↩ row `bin/exec.sh` writes to `docs/BUILD-LOG.md` (27 call sites) now carries a stable token ` · guard=<id>` right after its detail text (`plan-rule`, `stop-row-scan`, `row-group-gate`, `lock-studio-pro`, `commit-first`, `uncommitted-model`, `marketplace-gate`, `mxcli-check`, `mxbuild-missing` (toolchain absent), `pre-existing-errors` (model already broken), `mxbuild-crash` (gate could not run, including a `--patch` rolled back after a crash or unverified gate), `mxbuild-gate` (errors the script introduced — the real catches), `hash-verify`; `patch-exit` marks a `--patch` script that exited non-zero and is not a guard), inside the detail cell so every column reader is unchanged; `bin/metrics-trend.sh` (and so the harvested metrics inbox file) adds a `blocked by guard: mxbuild-gate 15, plan-rule 7, …` line, matched on the ` · guard=` separator only (a bare `guard=` quoted in detail text is not counted), rows from an older exec.sh counted as `unnamed`, and `patch-exit` rows on a separate `script failed` line. Why: a field metrics file had 13 of 136 execs blocked or refused and no way to tell which guard, so no guard's catch rate could be weighed against its false refusals. Same verdicts, exit codes and refusal text; no new process per exec. Fixture `tests/wave2/test-buildlog-guard-name.sh`. — overengineering audit 2026-11-20 (field metrics, #804); mxbuild split and anchoring from independent review of #813
- new(doctor, bug ledger): **a guard for mxcli's silent MxBuild fallback**: when the project's Mendix version is not in `~/.mxcli/mxbuild/` (and no Studio Pro of that version exists), `mxcli docker build` / `docker check` fall back to the newest cached MxBuild and print its path but no version warning (`run --local` is exact-or-refuse); `bin/doctor.sh` now warns, naming the model version, the cached ones and `./mxcli setup mxbuild -p <app>.mpr` (`mxtk_mxbuild_cache_gap`, warning only, never changes a gate). Ledger entry `BUG-DRAFT-mxbuild-silent-version-fallback`; upstream issue not filed. — a four-app Mendix build (field run), independent review
- fix(gate-check): **a fresh clone no longer FAILs Stage 3 as "stale render"**: `blueprint.html` / `process-map.html` freshness used `[ render -ot source ]`, a nanosecond mtime compare, and a checkout stamps files in directory order (`process-map.html` lands before `process-model.json`), so an unedited project read stale on every clone (reproduced: 200-wireframe checkout, 10 of 10 clones). New `bin/lib/render-fresh.sh` keeps `-ot` as the first test (a pass never flips, no git call) and, only where `-ot` would FAIL, asks git once per render (one `log`, one `status`) whether the source was committed after the render's commit; measured 0.19 s for 200 sources all `-ot`-stale on a 300-commit history (a per-source git version cost 12.9 s). Limit: a depth-1 clone cannot see a genuinely stale render. Field run: a four-app Mendix build checked out on a second machine. — a four-app Mendix build (field run), independent review
- fix(test-stack-up, e2e-harness-base): **the app port follows the app's configured port, and a multi-app start is no longer pinned to 8080**: with no `APP_PORTS`, `test-stack-up.sh` puts `RUN_LOCAL_APP_PORT`, then `APP_PORT` from the `.docker/.env` beside the `.mpr` (`apps/<App>/.docker/.env`; the project-root one as fallback) first, ahead of the old fixed `8080 8081 8084` tail. A fresh `run --local` start for a model under `apps/` with no handshake and no configured port used to fall back to 8080 for every app (`--app-port 8080`); it now exits 4 naming `RUN_LOCAL_APP_PORT`. `e2e-harness-base.md` states that a PAD/Docker runtime listens on 8080 *inside* the container only. Fixtures T28–T32 added. Field run: a four-app Mendix build on 8081–8084 whose fresh start failed with every app pinned to 8080. — a four-app Mendix build (field run), independent review
Expand Down
Loading
Loading