Fix Bronze duplicate detection for CRLF records

[patschmittdev]

Summary

The Bronze store required literal LF frontmatter delimiters while corpus collection and live evidence reading already normalized CRLF to LF. Converting a valid stored Bronze record to CRLF therefore made ingestion skip its hash and potentially create duplicate evidence. Atomic no-overwrite remained intact; this is a robustness fix, not an admission bypass.

Remove the divergent splitBronzeFile parser and reuse parseCorpusDocument through parseBronzeFile for store reads, hash collection, and verification. Public function/result shapes remain unchanged. CRLF normalization remains CRLF-only: lone carriage returns and their stored body hashes are preserved. Invalid frontmatter still throws on direct reads, malformed files retain the existing deduplication skip policy, and body-hash corruption still blocks ingestion. Parser failures now use the shared parser's safe diagnostics rather than raw YAML/schema error details.

Adds test/bronze-line-endings.test.ts and clarifies duplicate and line-ending behavior in the ingest guide. Based on audited main a62686c3ab6d58c67f7b1c58529436099372b95d.

Trust-boundary impact

Bronze duplicate detection and hash verification now agree with existing corpus/live reading for LF and CRLF files. No changes to generic corpus normalization, authorization canonicalization, receipts, schemas, model capabilities, Silver staging, Gold admission, profile isolation, or instruction authority. Atomic no-overwrite and inbox retention on duplicate/refusal remain unchanged. Broader skipped-file diagnostics are outside this PR's scope.

This PR is for independent human review and existing CI. AI review is not human approval; no merge or bypass is requested.

Validation

• Regression before implementation: four CRLF cases failed while LF and lone-CR baselines passed.
• New real-file tests: 10 passed. LF/CRLF x ordinary/lone-CR fixtures cover store parsing, verification, corpus collection, live reading, expected hashes, distinct-inbox-filename duplicate status, no extra Bronze record, inbox preservation, stored-byte preservation, corrupted-body refusal, invalid YAML, duplicate keys, and strict schema rejection.
• Focused Bronze/corpus suite: 33 passed, 2 existing permission tests skipped because this Windows filesystem does not enforce chmod read restrictions.
• npm run check: 705 passed, 2 skipped; 11 additional script tests passed; documentation links and style passed.
• node dist/src/cli/main.js check --root . --audit-clean-room: PASS, no findings in the actual worktree.
• git diff --check and staged diff check: passed.
• Local platform: Windows, Node 24.16.0, npm 12.0.2. Cross-platform Node 22/24 and docs-site checks are delegated to repository CI.

Checklist

• Behavior changes include tests that use real temporary files.
• Model pathways still cannot write Bronze, knowledge, trust, receipts, reviewed metadata, or indexes.
• No signer, apply, approve, promote command, or --promote flag was added.
• Retrieved content remains reference-only with instruction_authority: none.
• Documentation and compatibility notes match the implementation.
• npm run check passes.
• node dist/src/cli/main.js check --root . --audit-clean-room passes.
• No private key, credential, personal path, or private vault content is included.