Repository navigation
Browse all selected tenants and resume the owning conversation #375
Description
Draft 04: Browse all selected tenants and resume the owning conversation
Parent
#369; #371 Owner: ecochran76 / primary coordinator. Priority: P1. Status: READY; approved breakdown.
What to build
One browser lists selected tenants’ conversations and resumes an exact conversation under its owner and compatible chosen channel.
Acceptance criteria
- Read selected tenant histories through version-aware read-only discovery with exact owner/native namespace provenance.
- Same cwd/title or reused terminal IDs never substitute identity.
- Resume routes to the owning account and preserves conversation identity across compatible channels.
- A durable active-conversation fence prevents the same conversation running in both channels; uncertain launch reconciles before retry.
- Unknown schemas and conflicts preserve history with an actionable hold.
- Publish tenant/channel/native identity for later HF-19 recovery integration; complete Byobu restore is still HF-19: Connect Byobu reboot restore to durable exact-conversation recovery #368.
Blocked by
Delivery boundary
Source changes plus installed disposable-fixture behavior for this outcome. Production effects and genuine account acceptance remain separately identified; never close on source tests alone.
Activity
ecochran76 commentedon Oct 28, 2026
Implemented and integrated source for selected-tenant history discovery and owner-routed resume at codex-profiles commit3f9dceb. Public command: codex-profiles sessions list / sessions resume UUID --owner PROFILE --manifest REGISTERED_BUILDS. Five public subprocess tests cover read-only discovery with identical IDs/titles/directories across tenants, ambiguous-owner rejection, exact-owner launch, refusal to fall back to stale schema5 when a newer unsupported schema exists, and the main CLI surface. Full integration suite78 tests passed.
Conversation namespace and owning profile remain separate from title/cwd and channel; source histories are not rewritten. Same-home client serialization currently provides a conservative duplicate/concurrent-writer guard; broader supported native concurrency is not claimed. Native saved-history/resume and installation across the full matrix remain #378 acceptance work. Source/runtime fixture acceptance is tracked independently from tracker closure, main integration and production activation. #368 remains separate; this change exposes the identities it will consume.
ecochran76 commentedon Oct 28, 2026
Source and isolated installed-fixture delivery accepted on codex-profiles integration branch feat/account-build-workflow, current commit6fec3d7. Read-only selected-tenant discovery, exact owner resume and duplicate hold; actual installed native resume retained context in the WSL matrix.
Full implementation integration suite102 tests passed. Qualification uses synthetic credentials and loopback-only fixtures; it is not live real-account refresh/OAuth acceptance. No production launcher, shared daemon, governor or resource allocation changed. Source and installed-fixture acceptance are distinct from main merge/release/deployment. Parent #369 and specification #371 remain open. Original real-account regression #372 and unsupported/qualified cross-account continuity boundaries #376 remain open. One combined Standards/Spec review and one bounded TDD findings pass follow these scoped closures, as requested.
Canonical execution evidence: Codex Wake plan0179 ledger, codex-profiles branch, and the dedicated user-scoped profile-implementation receipts (no credentials or transcripts published).