Sharing #15313

Individual share, unshare and fork-from-share, a public viewer that renders v2 messages, fail-closed team upload, and scrubbed background session ingest. Team and incremental sharing are in the post-cutover backlog.

Milestone: v2 M2: Public CLI preview
Priority: P2
Owner: unassigned

v1 reference

Progress-map features: session-fork, session-export, archive-security. The v1 changes for a feature are listed by bun script/upstream/progress.ts --list <feature>. v1 main (pinned in migration-context.md) is the behavioral reference; acceptance is written against it.

Slices (migration plan units)

The plan's units for this epic. Child issues of this epic are the live work items; a slice without an issue is created when its work starts. Status here is a snapshot from the plan.

• U-E5-01 Share transport normalization; share/unshare/fork client operations (Normalize share transport and port share client operations onto v2 #14396)
• U-E5-02 v2 share payload contract (self-contained messages, metadata-first upload) (Settle the v2 share payload contract (self-contained messages, metadata-first upload) #14397)
• U-E5-03 Public viewer for v2 messages (cloud repository) (Implement public shared-transcript viewer support for v2 messages #14398)
• U-E5-04 Team upload stays refused (fail-closed) (Settle team sharing ownership authorization and keep fail-closed gating #14399 (part))
• U-E5-05 Deployed share contract verification (external-gated) (Verify deployed share contracts end-to-end (external-gated) #14401)
• U-E5-06 Background session export/ingest to Kilo cloud (scrubbed), opt-out

Notes

The public viewer lives in another repository (cloud) with another owner.

References

• Migration plan (epics, units, acceptance) and migration-tracking/plans/migration-context.md (decisions, pinned refs)
• chore(migration): plan by feature, decide now, prioritize code #15294 (how the work is organized) and docs(migration): record the client, identity and sync-gate decisions of 2026-10-20 #15290 (client, identity and sync decisions)
• Placement: plugin first, then the Kilo host; see migration-tracking/plans/v2-host-strategy.md section 5