Reconcile portable clone issues with current Snapshot v2 behavior

[valiantone]

Context

HotMem issues #67 and #69 describe an interchange contract and a verified dump/hydrate workflow. The current Snapshot v2 implementation already covers parts of those descriptions, while the remaining work overlaps the foundation issues for record fidelity, identity, and replay. Issue #67 also references docs/okf/company-brain-interchange.md, which is absent from the reviewed checkout.

What needs to be done

• Verify every scope item and acceptance criterion in Define HotMem interchange and company-brain clone package v1 #67 and Ship verified portable company-brain dump and hydrate workflow #69 against the current default branch, tests, and documentation.
• Produce a disposition matrix marking each item verified-current, remaining-gap, superseded, or separately deferred.
• Replace the absent documentation reference with a current canonical public-neutral link, or remove it if no longer applicable.
• Recommend whether each issue should be retained with edits, split and linked to the foundation issues, or closed as superseded/partially delivered.
• Preserve historical context through explicit comments and cross-links rather than silently rewriting it.
• Remove private-direction wording from any approved replacement title, body, dependency, label description, milestone, or comment.

Acceptance criteria

• Every Define HotMem interchange and company-brain clone package v1 #67 and Ship verified portable company-brain dump and hydrate workflow #69 requirement has an evidence link and one unambiguous disposition.
• No remaining issue claims that already-shipped behavior is wholly absent.
• No active issue references a missing documentation path.
• Remaining work links one-to-one to the relevant foundation issue without duplicate acceptance criteria.
• Historical context is preserved through a reconciliation comment or successor links.
• Any GitHub edit, label change, milestone change, or closure receives review before publication.

Constraints and non-goals

This is a tracker/documentation reconciliation issue. It does not implement Snapshot changes, delete issue history, assign owners, set dates, or make release commitments.