mosaicstack/stack
21
0
Fork 1
Code Issues 339 Pull Requests 13 Actions Packages Projects Releases 15 Wiki Activity

Record owner rulings resolving registry review gates

Browse Source
This commit is contained in:
jason.woltje
2026-09-10 14:42:31 -05:00
parent d5307d2b0a
commit 224147eccc
2 changed files with 41 additions and 29 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/plans/2026-09-03_auth-provider-harness-registry.md
+39 -29
View File
@@ -470,34 +470,44 @@ No named accounts currently exist, so migration is state-free:
1. **RESOLVED (owner, #50):** canonical harness IDs are executable names:
`pi`, `claude`, `codex`, `opencode`; validation is registry/manifest-driven,
not a schema enum. `mosaic harness detect/install/list/rm/status` owns the
lifecycle. Remaining seam to approve: detected host executables are
available but not launch-ready under the container boundary until
imported/installed into a managed runtime (unless host execution receives a
separate reviewed adapter).
2. Confirm `agentVersion: 2` migration and whether `settingsProfile` becomes
mandatory for defined seats.
3. Confirm registry path/schema split (`account.json` metadata +
`credential.json` secret) versus one encrypted/combined file.
4. Decide encryption-at-rest requirement. Filesystem 0600 is specified now;
external keyring/envelope encryption would change login/refresh design.
5. **RESOLVED (owner, 2026-09-10):** named launch profiles are deferred. Per-execution
selection recorded in execution records/context manifests (per the Gate 7
reconciliation and #53 model) covers the need; a named-profile layer would be
a separate future decision if a use case emerges.
6. **RESOLVED (owner, 2026-09-10):** forked sessions pin the original account in
immutable session metadata. Ordinary relaunches of an unpinned session
materialize the current profile default. Selection changes apply between
executions, never mid-session.
7. Determine pi's supported host-side noninteractive OAuth refresh trigger;
implementation must prove refresh without exposing or duplicating tokens.
8. Confirm local Ollama container routing (`host-gateway`) and remote Ollama
transport/auth requirements.
9. Decide whether M20 `packages/mosaic` begins with this auth/provider/harness
domain or whether scripts prototype it first. Confirm managed harness
packaging: harness-specific container image/bundle survives dataRoot reset;
lifecycle. Detected host executables are available but not launch-ready
under the container boundary until imported/installed into a managed
runtime (unless host execution receives a separate reviewed adapter).
2. **RESOLVED (owner, 2026-09-10):** one-time reviewed cutover to
`agentVersion: 2`; `settingsProfile` is mandatory for defined seats. v1
seats resolve to `pi` with a loud deprecation warning until migrated.
3. **RESOLVED (owner, 2026-09-10):** keep the split — `account.json` non-secret
metadata + `credential.json` secret, both 0600.
4. **RESOLVED (owner, 2026-09-10):** filesystem 0600 now. OpenBao is the
intended eventual secret backend; the credential-type field and materializer
interface are the design seam. No OpenBao work is authorized yet.
5. **RESOLVED (owner, 2026-09-10):** named launch profiles are deferred.
Per-execution selection recorded in execution records/context manifests
(per the Gate 7 reconciliation and #53 model) covers the need; a named-profile
layer would be a separate future decision if a use case emerges.
6. **RESOLVED (owner, 2026-09-10):** forked sessions pin the original account
in immutable session metadata; unpinned relaunches materialize the current
profile default; selection applies between executions, never mid-session.
7. **PARTIALLY RESOLVED (owner, 2026-09-10):** the pin moves to pi 0.85.1
(exact). A bounded read-only investigation of the 0.85.1 package will
determine the supported noninteractive OAuth refresh path; owner approves
the mechanism from those findings before implementation. Refresh stays
host-side, fail-closed, no token exposure or duplication.
8. **RESOLVED (owner, 2026-09-10):** local Ollama routes via `host-gateway`
(`http://host.docker.internal:11434/v1`). Remote Ollama supports http and
https; plain http requires an explicit per-provider `allowInsecureTransport:
true` flag (loud, opt-in, audited). Ollama is not currently installed on the
workstation; suites use fixtures/mocks, and the owner may install Ollama
with a small model for real-endpoint testing later.
9. **RESOLVED (owner, 2026-09-10):** M20 `packages/mosaic` begins with the
auth/provider/harness domain. `scripts/auth.sh` becomes a thin compatibility
shim over it, removed at the version-2 cutover. Harness runtime bundles
package beside the active release image so `reset.sh` does not destroy them;
registry state and receipts remain under dataRoot.
10. Define backup/reset semantics for the central registry. Current reset wipes
the data root; OAuth re-login cost may justify a separately protected
registry root, but that would require an explicit canon change.
10. **RESOLVED (owner, 2026-09-10):** registry stays inside the data root;
`reset.sh` keeps wiping it but prints a loud warning about OAuth re-login
cost. Revisit a separate protected registry root only if re-login pain
proves real (would be a canon change).
Implementation is blocked until these gates are reviewed and owner-approved.
Remaining open item before implementation: gate 7's 0.85.1 refresh investigation
findings and the owner's approval of the refresh mechanism it proposes.