[jeremi]

Project checks can retain a deliberate acceptance of one warning, identified by its exact code and source scope, with a required reason. Accepted warnings remain visible in human and JSON output and do not fail --deny-warnings; errors remain blocking.

The shared format covers BReg, Evidence, Casework, Scheduling, Messaging, Coordinator, Document Store, Discovery, Manifest and Render. It includes strict schemas, editor bindings, configuration guidance and source-boundary tests. Acceptances persist until edited or removed.

Preserve accepted warnings alongside mixed project/runtime findings and later target or provider domain refusals. Existing diagnostic codes, scalar redaction and operational exit classes are retained. The API connection-report schema and identifier catalog are regenerated together, with the connections configuration contract unchanged.

Validation:

• Shared API: 24 tests; Messaging CLI: 127 tests; BReg CLI: 181 command tests and 28 explanation tests.
• Evidence and Casework: targeted pre-fix failures, post-fix regressions and package checks, including real late-validation paths. Evidence: 866 passed, 12 existing ignores. Casework: eight focused project tests passed, including namespace and contract refusal cases plus typed-report deduplication and operational-error preservation.
• Identifier tests and full reproduction, 31 editor tests, strict Clippy, Cargo formatting and secret scanning passed.
• Evidence production tutorial: the exact offline production-assurance refusal matches the maintained transcript. Content, Markdown, style, tutorial dry-run and three production-doc tests passed. Full issuer-backed journeys require fresh CI.
• Fresh protected CI and merge-queue validation are required before landing. Local checks did not repeat PostgreSQL or running-service journeys for these offline reporting changes.

Supersedes #2434 on a linear branch based on current main. The original published branch remains intact.

DCO

• Every commit includes a Signed-off-by trailer.
• I reviewed the submitted changes and am responsible for the contribution.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-26T00:47:28.889964Z	7bff819	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.