Cross-device continuity
A developer can keep local signed KBD work independent of networking, then optionally synchronize an authorized project through Companion. Choose one socket host, enroll each project/replica and configure authorized network peers. Before a push, record the source frontier and exact signed intent; after it, inspect the original host's receipt and destination application evidence.
If the response is lost, recover its durable intent and query the original ID rather than creating another operation. If peers are unavailable, retain local state, outbox and receipt evidence; transport recovery does not by itself settle application outcomes.
This is a supported source workflow, not an observed cross-device acceptance result. It does not replicate local-only memory, move credentials or activate an agent team on the destination. See installation and push recovery.
Ownership and evidence
These routes remain useful after relocation. The current recovered Companion
source (docs/installation.md, docs/control-api.md) has no public remote or
certified release yet. Source inspection is not installed or peer acceptance;
final source/artifact identities and publication links remain release-owned.
Use local KBD without the optional extension, and the service operations guide for pack/Companion ownership. The integration contract is a one-way seam. Relocation history is a decision record, not a Companion repository URL.