Three capabilities that should not share one promise
Viewing another agent’s history, resuming a provider-owned session and passing reviewed context into a new conversation are different operations. A product can support the first without supporting either of the others. A history importer does not automatically provide a provider-native resume token.
The identity includes the provider, account, project and session. Similar account names or matching project titles do not prove that two credentials can read or resume the same underlying session.
The handoff should be visible
A cross-provider handoff starts a new session using bounded context. The source should be named, exclusions preserved and the payload reviewable before delivery. Stale evidence or a different destination privacy posture can invalidate a previously reviewed plan.
The handoff guide explains the plan, preview, review and current-evidence boundary. Choosing a clean start means no handoff payload. It is not an opaque “resume everything” command.
A graph is not automatically a GNN
Matrix can organize evidence and propose deterministic candidates without an active learned graph model. Calling that a trained GNN would overstate its current state. Human judgments can improve the evaluation corpus, but label count alone is not evidence of a useful model.
A learned ranker needs a defined target, appropriate topology, held-out evaluation and a comparison with the deterministic baseline. Relatedness labels should reflect shared objectives or dependencies, not just matching words. Ambiguous evidence deserves a skip rather than a forced training label.
Provider parity needs receipts too
Provider-specific continuity implementations and privacy guarantees are not interchangeable. The capability matrix identifies supported, limited and unavailable paths. The launch documentation does not erase a known gap by describing an aspirational universal interface.
When a resume fails, preserve the provider/account/session identity and the relevant diagnostic. Do not fix it by copying sensitive context into a different account without reviewing the destination.