Review your agents’ work in minutes, not hours.

linkcheck-build-plan.md

Decisions and review notes, as agents wrote them

• coder-b · decisionc_8f83 review fix: headings.js now uses extract.js's `FENCE_OPEN`/`FENCE_CLOSE` regexes verbatim (fences after list markers and `>`, at any indentation), so both modules agree on what is code. Whoever changes the fence rule in one file must change it in the other. The two files still differ in two edge cases: headings.js also treats a lone ` ` as a line break (CommonMark), and it skips leading YAML front matter before looking for fences.
• coder-c · decisionShared fence rule for extract.js (c_6da9) and headings.js (c_8f83); it replaces my earlier fence line and is what extract.js now does. Opener: `/^[ \t]*(?:(?:>|(?:[-*+]|\d{1,9}[.)])(?=[ \t]))[ \t]*)*(`{3,}|~{3,})(.*)$/`, meaning any indentation, then any mix of `>` and list markers (`-` `*` `+` `1.` `1)`, each followed by a space or tab), then 3+ backticks or tildes; a backtick fence's info string (group 2) can't contain a backtick. Closer: `/^[ \t]*(?:>[ \t]*)*(`{3,}|~{3,})[ \t]*$/`, the same char at least as long as the opener, with any indentation and `>` allowed but no list mar…
• reviewer · reviewc_8f83: same fence bug as c_6da9. A fence opened on a list-item marker line is not recognised, and the indented closing fence then opens a fence that runs to end of file. Repro: `headingAnchors('- ```sh\n # install deps\n npm i\n ```\n# Real')` returns `['install-deps']`: the shell comment becomes an anchor and `real` (and every later heading) is lost, so valid `#real` links would be reported as broken. Fix: let `FENCE_OPEN` accept an optional list marker (`[-*+]` or 1-9 digits plus `.` or `)`, then a space) before the fence, and add a test for it. Please agree the fence rule w…
• coder-c · decisionREADME.md documents cli.js as it stands: `--json`, `-h`/`--help`, exit codes 0/1/2, and the stderr usage line. Its text example is the `test/fixtures/cli` run, identical to `EXPECTED_TEXT` in test/cli.test.js. If the cli card changes flags, exit codes or that fixture during review, the README card has to follow.
• reviewer · reviewc_6da9: a fence opened on a list-item marker line is not recognised, so the fence state inverts for the rest of the file. Repro: `extractLinks('1. ```sh\n [no](1.md)\n ```\n[yes](2.md)')` returns only `1.md` (code content reported as a link) and drops `2.md`; same with `- ```` and `* ````. The indented closing fence is then read as an opener and hides every later link in the file. Fix: let `FENCE` accept an optional list marker (`[-*+]` or 1-9 digits plus `.` or `)`, then a space) before the backticks/tildes, and add a test for it. Everything else checks out (27/27 pass).