[daveh-beep]

What observed experience does this improve?

An integration using the existing index or search output cannot read the complete reference, including inline must rules, exceptions, exact wording, and approval scope.

Learning check

This is an optional deterministic tooling change; setup, reference contracts, and drafting behavior are unchanged. On Python 3.9.6, python3 -B -m unittest discover -s tests -v passes all 48 tests. The fresh independent reviewer also reran the 30 corpus tests.

test_export_preserves_complete_original_bytes_and_leaves_index_unchanged uses a synthetic UTF-8 reference with CRLF, comments, inline enforcement, scoped exact wording, and trailing whitespace. The failure criterion is any difference between decoded exported text and original bytes/hash/length; index and search outputs are unchanged controls. Other executed cases cover malformed input, missing or invalid revisions, ingestion limits, excluded calibration and instruction files, empty coverage, and refusing to overwrite output. These tests establish transport and structural behavior, not model adherence or writing quality.

Changes

• Add corpus.py export --reported-revision <full Git object ID> with complete original source text, existing metadata, byte counts, and SHA-256 hashes.
• Label the caller-reported revision explicitly unverified. The command does not inspect Git or attest source identity, cleanliness, approval, or safe prose.
• Keep the existing bounded corpus loader and check/index/search outputs unchanged.
• Document candidate review, conversational-only vocabulary, excluded calibration, and the separate cross-repository snapshot contract. No Ghost dependency, automatic adapter, service, or additional setup step is introduced.

Related groundwork: Ghost scoped language references. Each change works independently.

Additional validation: bash checks/adversarial-contract.sh, template/Meridian/Harbor corpus checks, export help, and git diff --check pass. A synthetic transport check selected the fictional Meridian terminology reference from the real export and delivered it through Ghost's JSON and Markdown pull commands, preserving full text and scope. This does not establish an approved consumer integration.

Safety and verification

• I used only fictional, redacted, or explicitly publishable material.
• I did not include secrets, personal or customer data, confidential material, or private links.
• Examples preserve supplied facts and do not invent product state, causes, dates, deadlines, guarantees, names, amounts, eligibility, or actions.
• Executed deterministic reproduction and unchanged controls are recorded above; no agent behavior change or model-effectiveness claim is made.
• My commits include a DCO sign-off (git commit -s).