CODE-053: mint rewrites refs inside URLs and string literals — the hook ships them

Now: OPEN
Sev: HIGH
Rep: ///bee
Ask: gritzko
Rev: ///bee#8cb69a0
See: BEE-070
See: DOG-034

Input

Context

index/mint.js:23:PA with index/hook.js:163:bn mints any F token the lexer fuses, with no look at what precedes it. Confirmed: https://example.com/target.c:12:ZF becomes https://example.com/target.c:12:RW both under bee mint and under the pre-commit hook, where the STAGED BLOB is rewritten, so a commit silently ships a broken URL; "target.c:12:ZF" inside a string literal is rewritten too. meta/link.mkd separates a link from a URI on purpose. Also index/mint.js:156:PA keys the dry-run report on ref text, so a repeated ref reports once per occurrence, and :72 whyLeft claims "answers no line N" for any foreign target without checking. Found in the 2026-09-18 index review.

Goals

Refuse a token whose preceding bytes form a scheme or authority, and one inside a string literal the lexer already tagged. Repro through the hook, not only bee mint.

WIP

Design decisions

CONTEXT, not recognition: the DOG-034 lexer still owns what an F token is (the INDEXES.mkd ruling), and hook.js inUri only asks what PRECEDES the token. It lives in index/hook.js, the one scanner's file, and mint.js calls it — no second recogniser.
A scheme is required, or a // with a DOTTED authority. So //src/A.c:20 opening a C comment still mints, while //example.com/src/A.c:20 does not. The walk back stops at whitespace and at the bracket family, so a backticked ref — how this journal spells a link — keeps minting.
The string-literal half needed NO code: a grammar that has string literals tags one as a single G token, so no F token is ever inside one (checked for js, c, go, rs, h, sh and yaml). A quote in a .mkd is punctuation and a quoted ref there is a link, so it still mints. Both are pinned by test/mint/mint.js.
The dry run reports off ref.to, what THAT occurrence became, instead of looking the ref TEXT up in subs.
whyLeft opens a foreign target read-only and asks its HEAD blob the two questions a local target is asked.

TODOs

[v] repro: URL and string-literal refs survive bee mint and the hook
[v] recogniser rejects scheme/authority context
[v] dry-run report per occurrence, whyLeft checked

Blockers and bummers

bee lindex still mints a LINK row for a URL's tail: fTokens is shared and this fix is scoped to the minter. LINK rows are SUSPECTS by the INDEXES ruling, so it costs nothing today; a URI tag in the lexer (libdog, DOG-034's grammars) would settle both at once — gritzko's call.
No fixture covers the foreign whyLeft leg (it would need two repos inside the mint suite); verified by hand on a scratch pair.