[blafourcade]

🎯 What & why

A cli test reads plugin markdown that no gate watches, so a change confined to those plugin files could land it red on next. The structural assertions move to the guard whose glob already covers plugins/**.

🛠️ How it works

a-backlog-link-the-reader-can-read.test.js checked that the three field names appeared as substrings. It parses the taught example now, and requires each field as a non-empty string — the same predicate the reader applies at task-backlog-adapter.ts:12. A taught value that is not a plain object is refused by the predicate json-file.ts:5 uses, so nothing the reader accepts is rejected here.

The fence rule took three attempts, and the history is worth one line. Requiring exactly one json fence failed a case nobody has produced. Selecting the fence by content then left this guard green on a decoy above the example while its cli/ sibling went red — reopening the very harm this issue names, since no gate runs that sibling on plugins/**. What ships copies the sibling's own pattern, g added for matchAll, so the two cannot disagree about which fence they read.

One case stays green on both, knowingly. A valid decoy carrying backlog at line start, above a broken taught example, is read as the example by both guards. They agree, so nothing lands red on next, and closing it here alone would make this guard red where the sibling is green. Recorded in the plan's Decisions.

🧪 How to verify

• Empty written_by in plugins/aidd-dev/skills/01-plan/actions/04-plan.md, stage that file alone, and run pnpm exec lefthook run pre-commit: scripts-tests exits 1. Do not pass --all-files --force, which bypasses the globs and so proves nothing about the local gate.
• Mutations, each verified against both guards: a line-start fence above the example fails on both; a fence opened after text on the same line is ignored by both; the fence markers stripped, null, [1], and an emptied field each fail naming the file, the shape or the field.
• node scripts/check-tests-leave-git-alone.js -- node --test 'scripts/__tests__/**/*.test.js' → 550 pass.

⚠️ Heads-up

• The deferred gap is fix(cli): the taught backlog example is pinned harder than the reader requires #973: the sibling pins the placeholder value and demands key-set equality, both stronger than the reader, and a plugins-only edit to either still lands it red on next.
• review.md in the task folder is round 1's record and reads changes-requested against a head three rounds old. Rounds 2 to 4 each found one item, each fixed here; the last returned no contract violation.
• Four commit bodies on this branch assert rules the tree no longer has — the one-fence rule, content selection, a renamed-asset mutation that proved another test, and "no number exists to declare yet". This description is the squash message; do not let GitHub concatenate them.

🔗 Linked issue

Closes #972

✅ I certify

• I DO CERTIFY I READ EACH LINE OF THE PULL REQUEST BECAUSE I AM A SOFTWARE ENGINEER, NOT A AI PUPPY.

🤖 Generated with Claude Code

https://claude.ai/code/session_01VE16AxC1V9wAMGmGgefe4z