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

fix(fleet): propagate roster git identity (#1043)

Browse Source
This commit is contained in:
be-coder-06
2026-08-07 01:46:03 -05:00
committed by coder-mos1
parent aa0a7b5fa2
commit ebf518215a
17 changed files with 258 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files
docs/fleet/reference/generated-env-boundary.md
+4 -2
View File
@@ -35,6 +35,7 @@ values, credential material, or command text.
```dotenv
MOSAIC_AGENT_NAME=<roster name>
MOSAIC_GIT_IDENTITY=<roster name>
MOSAIC_AGENT_CLASS=<roster class>
MOSAIC_AGENT_RUNTIME=<roster runtime>
MOSAIC_AGENT_MODEL=<roster model hint>
@@ -44,8 +45,9 @@ MOSAIC_AGENT_WORKDIR=<absolute roster work directory>
MOSAIC_TMUX_SOCKET=<roster socket or empty>
```
The generated launch contract supports only `claude`, `codex`, `opencode`, and `pi`. fleet add
uses that same runtime authority and rejects any other runtime before it writes the roster or changes
`MOSAIC_GIT_IDENTITY` is derived from and must equal `MOSAIC_AGENT_NAME`; it is not a separate
operator-controlled identity authority. The generated launch contract supports only `claude`, `codex`,
`opencode`, and `pi`. fleet add uses that same runtime authority and rejects any other runtime before it writes the roster or changes
projection, local, or quarantine files. The legacy dogfood stub on its separate `mosaic-factory`
socket remains an observability canary; it has no generated-launch adapter and cannot be added through
this projection path.