2 Commits

Include renames

Author	SHA1	Message	Date
jason.woltje	69d1bb3aa4	docs(plan): resolve harness IDs + lifecycle review gate (#50) ... Owner adjudication: - canonical harness IDs match executables: pi, claude, codex, opencode - agent.json uses one scalar harness ID; registry/manifest resolution, no hard-coded schema enum - target mosaic harness list/detect/install/rm/status lifecycle - detection recognizes reviewed executables and records compatibility without reading/copying harness homes - installs are exact-version/verified, Mosaic-managed, never global - detected external harness is available but not container-ready until imported/installed, absent a separately reviewed host adapter Gate 1 resolved. Remaining P0/review gates stay open; no implementation authorized. Suites 24/15/90/14/17 + verify green; unslop clean.	2026-09-04 12:26:57 -05:00
jason.woltje	d9a94f51ba	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.	2026-09-04 11:57:40 -05:00