[Riverbraid]

Scope

Document the observation frames that can make a configured PASS seem broader than its evidence. Add a focused guide, clarify the Evaluation Kit verification-depth page, add the source-confirmed limitations, and link the guide from README.

Evidence

• Public Core at b5c8cde0ebb56ac98bc738545a8e80c10c67b191: byte-audit.mjs swallows Git observation failures. An isolated non-Git fixture returned BYTE_GATE_PASS_VERIFIED with null branch/commit and zero tracked files. This reproduces a false-positive route in the public script, not a Riverbraid production result.
• Public Evaluation Kit at cd814ac415d7952e524c8edd5c595d77189ed24d: four of 30 commands check README presence; external_reproduction derives only from zero failing commands; setup can exit before final JSON. The latter is source-path review, not an executed failure case.
• Same-day Core correction draft #9 passed six focused CI cases. Its Ring 2 run #185 found 8/8 constellation verification but only 2/8 byte verification: six BOM findings and three repositories with previously skipped symlink/gitlink paths. The guide records the exact claim limit; the Core branch remains draft.
• Public Documentation base 541d3f62f9e70e38f5ea4338d9799540f148469c; branch text was fetched and matched after the update.

Boundary

• Documentation only
• No code, runner, registry, expected-result, workflow, or authority-state change
• No new 30-repository, native, or founder-local execution claim

The Core script repair is separately proposed in draft PR #9. Kit runner changes would need their own selected code change and evidence. This draft is for review; it does not assert adoption or qualification.