Keep presentation evidence observed and retain current gates

[HomenShum]

A developer preparing a Change Story or deck needs to reuse media without implying that its depicted workflow passed. The original bridge promoted a tracked schema-only receipt reference to verified. This current-main port keeps every projected asset observed, counts receipt references without certifying their outcomes, and requires productWorkflowProof: not-certified and releaseReady: false.

Both fixed output paths reject directory/file redirects before read or write. The explicit project command generates the two committed outputs; read-only proof rejects missing or stale outputs without rewriting them. Current source, citation and render-record checks, dependency lock, Remotion wrapper, media and capture/render drivers are retained.

Validation:

• Unchanged main: 43 JavaScript parses, 36 tour steps, 34 prose citations and 3 render-record bindings passed.
• Preserved original module: 13 original scenarios passed while accepting the unsupported schema-only verified result.
• Candidate: 20 scenarios passed with no failures or skips; schema-only, failed and unbound receipt references remain observed. Redirected directory/file outputs reject project/proof with foreign files unchanged; eight deterministic rounds and two simultaneous disjoint fixture jobs passed.
• Final source/citation check: 45 parses (two protocol files added), the same 36/34/3 assertions passed; native whitespace check passed. Natural CI is separate from these local results.

The corrected branch-only v1 counter is workflowReceiptReferences, with no compatibility alias. Three historical media assets and unchanged supporting-file byte guards are retained; old README/NODE-LOOPS digests remain historical limitations rather than being rebound to current docs. This ports the useful intent of #4, which remains open until adoption is verified.

Before/after update log and boundaries

These are different scenario suites, not a performance score. This trusted local single-writer bridge does not certify workflow outcomes, capture provenance, pixels, fresh rendering, provider behavior, release readiness, security findings or production.