Reviewed source-contract reference. CLI 0.13.4 is released. Hosted pack contracts below are taken from Agent source 573c9a11b1b6674b163ce21273a162a4ed453282; their activation and deployed worked responses remain pending. This draft does not establish settings, shared context or intake acceptance for the existing 70 Codex and 70 Claude agents.
Start from the existing pack
Use the existing pack name and preserve its native IDs, role files and conversations. Pack installation, native adoption, effective settings, hosted connection and model use are separate states. A successful package installation proves only installation.
topolo agent-packs status --harness codex
topolo agent-packs status --harness claude
topolo agent-packs policy <existing-pack> --harness codex --output /absolute/review-codex.json
topolo agent-packs policy <existing-pack> --harness claude --output /absolute/review-claude.json
These source-based command templates inspect status or render reviewed policy; they are not captured runtime responses. Use the selected adapter's --adapter-help to inspect its options. Keep the explicit environment and organization context on cloud operations.
Interpret the result
Record the installed CLI version and source provenance, the exact selected roster, existing IDs/workspaces, requested policy, native settings readback and pending journal separately. Missing native readback is not an effective-settings PASS. A zero-turn import is not a model or memory acceptance result.
Codex's managed adapter qualifies the native protocol and account model catalog, then checks resume settings before later model work. Claude import is separate from native configuration. Its compatibility adapter requires the exact qualified host/module version and an already authorized local control endpoint. This guide does not authorize enabling debugging or restarting an application.
Preserve interrupted work
An uncertain native response can leave partial effects. Retain the operation journal and use supported read-only reconciliation before another apply. Do not recreate the roster, edit cached native records, clear a pending operation by age/PID alone, or retry a lost acknowledgement as if nothing happened. Keep charter and transcript before/after proofs.
Evidence still required
Attach the original owner's current native adoption and effective-policy receipts for each selected role. Actual shared Agent/Bytes and intake decision checks follow the qualified hosted release. Older README passages saying the public CLI dispatch was unpublished describe an earlier checkpoint; the exact 0.13.4 publication/install proof governs package status, not runtime acceptance.