Lint receipt does not cover a project's edits to bundled rules, so mxcli's per-session refresh is charged to the next exec as a lint rise #524

Activity

1. MendixMau commented on Oct 24, 2026

   

   MendixMau

   on Oct 24, 2026

   Owner

   More actions

   Field evidence 2026-10-24 (a Quality demo project, mxcli v0.26.0, three back-to-back headless sessions):

   • The session-start hook .claude/bootstrap-mxcli.sh runs ./mxcli init --sync-skills . || true on every start and every context compaction. Each time it prints "Refreshed 4 bundled lint rule(s) in .claude/lint-rules/ to match this mxcli". The files it overwrites are conv009_max_microflow_objects, conv010_act_microflow_content, data_change_microflows and entity_business_key (.star).
   • Those four rules are committed with project edits. After the refresh the lint ratchet no longer matches its baseline. The agent had to git checkout -- .claude/lint-rules/ twice in one session before the gate read 1617/1617 PASS again.
   • Each agent finds this on its own, and rounds 2 and 3 both spent time on it.

   Suggested fix, same as above: --sync-skills should skip rule files the project has committed and changed (or warn and keep them), or the toolkit should ship its edited variants under its own names so the stock files can refresh safely.

   🤖 Generated with Claude Code
2. MendixMau commented on Oct 24, 2026

   

   MendixMau

   on Oct 24, 2026

   Owner

   More actions

   Triage: DISCUSS track. Every fix either changes a gate verdict (a new BLIND / exit 1 where today the gate reports a rise) or how lint rules are named and installed (re-architecture). It affects every entry mode that runs the lint gate at Stage 5, plus à-la-carte assurance. The receipt gap is verified against the code. The revert mechanism was reproduced by the reporter on v0.27.0, and the maintainer's 2026-10-24 field note confirms it on v0.26.0.
   Problem:

   • The gap: project-bin/lint-gate.sh:200-252 checks only the rows in .claude/.mxtk-lint-receipt. bin/lib/install-lint-rules.sh:29 writes that receipt for rules the toolkit installed. A project's own edit to a bundled example (example_microflow.star, CUSTOM002) has no receipt row. So when mxcli's SessionStart init --sync-skills restores the stock file, the gate sees a CUSTOM002 rise and charges it to the next script.
   • The maintainer's note widens it: four committed rules with project edits (conv009…, conv010…, data_change_microflows, entity_business_key) are restored at every session start and compaction. Agents rediscover this independently each round (git checkout -- .claude/lint-rules/ twice in one session).

   Value: High. It costs time in every multi-session project with edited rules, and a false rise blamed on a script is the kind of false red that sends people debugging the wrong thing.
   Options:

   1. Receipt every edited bundled-name rule. When --update-baseline runs, record md5 + kind project for every .claude/lint-rules/*.star that differs from mxcli stock. A later revert then reads BLIND — reverted, not a rise. That's a new BLIND (exit 1) for projects with edits, an honest verdict but a flip. No extra mxcli calls. S–M.
   2. Option 1, plus self-restore from git. If a receipt row reverted and the committed (HEAD) version matches the receipt md5, git checkout -- <file> it, print one warning line, and lint normally. Under guard rule 7 the gate unblocks itself. Risk: the gate writes to the working tree. One git call per reverted file. M.
   3. Rename instead of edit. The toolkit ships its edited variants under its own names (mxtk_*.star) and lists the stock names in .claude/lint-rules-disabled.txt. The lint skill tells projects to copy-and-rename rather than edit a bundled file. The refresh can then restore stock files safely, because they are disabled. This changes the install layout and needs a sync-project.sh migration for existing projects. It is durable whatever mxcli does. M–L.
   4. Wait for upstream (init and init --sync-skills overwrite an edited bundled lint rule (example_microflow.star / CUSTOM002) and recreate it when renamed mendixlabs/mxcli#1615: keep edited bundled rules), with docs only. Zero risk, but the problem stays until mxcli ships.

   Recommendation: Option 3 for the toolkit's own four rules, which removes the cause. Option 2 as a safety net for project-edited examples until #1615 lands. Add one skill line now in lint-that-actually-runs.md, "an edit to a bundled rule is not durable; copy under a new name", whichever option is chosen.
   Decision needed from you: Should edited lint rules be protected by renaming (3), by the gate detecting and restoring them (1 or 2), or should we wait for mxcli (4)? Reply "go option N" to build it.

   ---

   Generated by Claude Code
3. MendixMau

   added 3 commits that reference this issue on Oct 26, 2026

   fix(lint-gate): a project-edited bundled rule lost to mxcli's session…

   ...

   c5c51cc

   fix(lint-gate): #524 project rows ignore CRs, cover seeded rules only…

   ...

   ef204de

   Bug sweep 2026-10-26: gates, runners, doctor, lint receipt, git hooks…

   ...

   a088b4e
4. MendixMau commented on Oct 26, 2026

   

   MendixMau

   on Oct 26, 2026

   Owner

   More actions

   Option 1 shipped in #578 (squash a088b4e). --update-baseline receipts edited seeded rules, and a later revert by init --sync-skills reads BLIND — reverted with the git checkout remedy. The receipt:

   • ignores CRs;
   • covers only seeded rule names;
   • is written only on captured mxcli versions.

   Field-checked: v0.27 overwrote an edit → BLIND, checkout → PASS; v0.28 keeps edited rules → no alarm. Option 3 (rename) is on the roadmap #579.

   ---

   Generated by Claude Code
5. MendixMau

   closed this as completedon Oct 26, 2026