Bind peer web citations to observed tool-result provenance

[CBEPX]

Summary

Peer memo validation independently requires a qualifying web tool event and a syntactically safe direct-HTTPS citation. It does not prove that the cited URL was observed in that tool result or that it supports the associated finding.

A model can therefore call a valid web tool and return an unrelated but well-formed HTTPS URL. This is an evidence-provenance limitation, not an observed exploit or a v1.7.3 release blocker.

Evidence

• validatePeerMemo() normalizes webCitations independently (scripts/lib/peer-orchestration.mjs:431-440).
• The later tool-event check retains only tool names and accepts WebSearch, WebFetch, or a selected audited Brave ID (scripts/lib/peer-orchestration.mjs:442-466).
• Current public workflow state intentionally does not persist queries or unrestricted tool output.

Desired outcome

Design a bounded, secret-free way to distinguish citations observed in web-tool results from arbitrary model-supplied URLs.

Acceptance criteria

• A forged citation absent from observed tool-result provenance fails closed.
• Works for built-in WebSearch/WebFetch and selected audited Brave tools, or explicitly documents a narrower supported set.
• Does not persist queries, page bodies, credentials, raw MCP config, or unrestricted model/tool output.
• URL normalization preserves the existing HTTPS and credential-query protections.
• Provenance state is bounded and covered by positive, forged-URL, redaction, retry, and rendering tests.
• Semantic claim-support verification remains explicitly out of scope unless separately designed.

Provenance

Non-blocking follow-up from the live v1.7.3 Fable design/research qualification.