Land verifiable security and readiness slices from the north-star plan without widening changes beyond what can be tested.
- Phase 1: Rehydrate state and create planning files
- Phase 2: Research proxy authentication and related tests
- Phase 3: Implement header-only default proxy auth with explicit query compatibility path
- Phase 4: Verify targeted tests and update notes
- Phase 5: Deliver concise readiness report
- Phase 6: Parallel discovery for next foundation slice
- Phase 7: Implement one bounded next slice
- Phase 8: Verify and update readiness notes
- Phase 9: Fix isolated web device-auth blocker
- Phase 10: Add advisory
.phantom.tomlservice-route risk warnings - Phase 11: Fix Rust team API response-envelope parsing
- Phase 12: Align public proxy-auth documentation with header-only defaults
- Phase 13: Quarantine broken GitHub Action docs and workflow examples
- Phase 14: Fix team invite API compatibility with CLI/MCP
github_login - Phase 15: Restore SDK-compatible proxy auth while preserving strict header mode
- Phase 16: Harden device-code duplicates/collisions
- Phase 17: Serialize audit HMAC/head writes and add required mode
- Where are proxy auth URLs generated and consumed?
- Which tests already cover query-token proxy auth?
- What smallest compatibility switch can preserve legacy behavior without making query auth the default?
- Which security-foundation slice has the best ratio of risk reduction to testability after proxy auth?
- First implementation slice: proxy auth hardening, because it is a concrete foundation item with bounded Rust surface area.
- Persistent files will live at repo root per the provided operating loop.
- Query-token proxy auth is controlled by
PHANTOM_PROXY_ALLOW_QUERY_TOKEN=1; default generated base URLs no longer includephantom_token. - Second wave discovery is split across audit integrity, MCP approval gates, config tamper warnings, docs drift, and web/cloud/team blockers.
- Second implementation slice: audit verifier hardening with signed sequence numbers, malformed-line failure, and head checkpointing.
- Third implementation slice: canonicalize device auth user codes across initiate, browser approval, approve route, and database uniqueness.
- Fourth implementation slice: advisory service-route risk analysis in core, surfaced by
doctorand non-blocking stagedcheckwarnings. - Fifth implementation slice: align Rust team client parsing with web API response envelopes for list/create/members.
- Sixth implementation slice: align README, getting-started docs, LLM reference docs, and static site feature/pricing copy with header-authenticated proxy sessions.
- Seventh implementation slice: disable the GitHub Action fail-fast and replace CI docs/examples that referenced unsupported non-interactive cloud auth flags.
- Eighth implementation slice: keep the public team invite contract as GitHub login by accepting
github_loginin the web team-members route and resolving it to the stored user UUID. - Ninth implementation slice: restore generic SDK compatibility by using path-scoped local proxy auth in CLI-generated base URLs by default, while keeping
PHANTOM_PROXY_HEADER_AUTH_ONLY=1for strict header-aware clients. - Tenth implementation slice: make device-code approval/migration resilient to historical duplicate canonical codes and rare generated-code collisions.
- Eleventh implementation slice: add audit file locking around HMAC/head transactions plus
PHANTOM_AUDIT=requiredfail-closed API.
cargo fmt --all -- --checkreported a formatting-only diff incrates/phantom-proxy/src/server.rs; resolved withcargo fmt --all.cargo test -p phantom-proxyused the library crate name instead of package name; rerun with-p phantom-secrets-proxy.cargo check -p phantom-secrets-cliused a nonexistent package name; rerun with-p phantom-secrets.cargo fmtwas required after audit checkpoint edits; finalcargo fmt --all -- --checkpassed.
Complete - Proxy auth, audit integrity/concurrency, device auth canonicalization, service-route warnings, team response-envelope parsing, proxy-auth docs alignment, GitHub Action drift cleanup, and team invite compatibility implemented and verified; next candidate slices recorded in notes.