docs(plan): specify harness declaration + centralized auth/provider registry (#49)
Design only; implementation blocked pending owner review.
- agent.json: one harness identifier (pi first), resolved through a
versioned adapter/harness manifest; reusable settingsProfile reference
- central data-root registry: providers, accounts (metadata + secret
credential split), reusable settings profiles, audited runtime selection
- per-seat pi auth.json/models.json mechanically generated and atomically
activated; no seat/provider registration ceremony
- mixed oauth/api-key accounts supported centrally; one active account per
provider per pi materialization
- host-side centralized OAuth login/refresh; agents never authenticate
- local/remote Ollama modeled as endpoint providers, not accounts
- target mosaic auth/provider/agent settings CLI; secrets never on argv
- migration, fail-closed acceptance suites, and ten explicit review gates
CURRENT.md points only to spec review. Suites 24/15/90/14/17 + verify
green; unslop clean.
jason.woltje
d9a94f51ba