Repository navigation
Description
Verified gap
Source audit on 2026-10-29: TS main 90481b148584926ea328ed956327f3050d9be9cb selects exactly one Claude registry, from CLAUDE_CONFIG_DIR, ANTHROPIC_CONFIG_DIR or ~/.claude. Consequently sessions present only in Orca's macOS profiles are not enumerated by the default list/selection path. Python main f5e7c49554ff02771990a151e00b52f2abf3df0a has a bounded additional inventory when neither override is set.
- TS single directory and row construction
- TS selection and revalidation; handoff binding currently reconstructs the single default registry path
- Python bounded profile inventory; duplicate/endpoint conflict classification
Scope and acceptance
- Decide and document the supported macOS profile contract; enumerate only the known Orca profile location with bounded profile/record counts. Explicit environment overrides remain isolated; Linux/Windows must not silently scan the macOS convention.
- Preserve bounded regular-file reads, deterministic ordering and successful rows with explicit incomplete-inventory diagnostics; incomplete or conflicting evidence must not authorize a send.
- Carry original registry provenance through selection and handoff continuity checks instead of reconstructing ~/.claude paths.
- Distinguish exact aliases from conflicting PID, socket-string and underlying endpoint claims; never choose by inventory order. Keep ordinary name ambiguity refusal.
- Test default-only/profile-only/multiple profiles, explicit overrides, absent/unreadable/unsafe directories, enumeration limits, duplicate records and socket aliases, and changes between discovery and dispatch. Listing/dry-run fixtures must establish zero inbox writes.
- Update parity/help documentation with supported scope and actual platform qualification limits.
Evidence limits and related work
Static source verification only: no current Mac profile inventory, CLI test, native send or ACK was executed. The review report's two-session observation and Python test count are not independent TS evidence. No exploit or privilege escalation is claimed. Closed #16/#99 cover earlier unified Codex listing and bounded Claude record reads; neither implements this macOS Claude profile extension. All existing issues and PRs were checked for overlap; no current implementation PR for this extension was found. No release or live-session test is authorized by this tracking issue.
Activity
abruption commentedon Oct 29, 2026
Milestone triage — 2026-10-29: assigned to 0.6.0 because bounded Orca Claude profile discovery/selection adds a supported capability. The milestone scope now names this feature alongside the existing receipt/research work. Keep registry provenance and conflict refusal through discovery, selection and handoff as acceptance gates. This can proceed independently of #166; it does not complete existing 0.5.0 platform qualification.
fix(claude): reject unsafe automatic registries and invalid process p…
fix(claude): fence all registration evidence and retain confirmed sta…
fix(claude): reject extended ACLs on automatic profile registrations