[DanielNetzer]

Implements issue #389.

Molecule: mol-389-04efa720ecc7d7e991697116
Formula: forgecell-github-issue
Base: 1797a27a5792f7de82d111e69abe91b5641175b4
Delivery: 6ba2c6a2cc8aede57ffb7e5b7c065dd3d95358f7

Awaiting exact-commit CI and human review. Harness-reported checks are not independent CI evidence. No merge, deployment or issue closure is authorized.

[DanielNetzer]

Protocol bump. AdapterProtocolVersion goes from 6 to 7, because the pinned contract digest covers the analysis prompt. Every binding fingerprint changes: saved bindings need a reviewed rebind (init --rebind) after upgrading, and in-flight plans need a fresh intake.

Protected failures. The protected regression run failed 10 tests (27 entries with subtests) by design. All of them are exact-message or protocol-pin assertions in the 7 test files this change edits, and they were accepted with amend --accept-protected-failures.

LOWs (not fixed in this slice):

• labellingViolation cuts the check ID at 128 bytes, which can split a multibyte character. %q escapes it, so the output is harmless.
• There's no blank line between labellingViolation and uniqueJSON in plan.go.