# Fleet handoff — agent-lib v2 rollout What az-fleet must roll out, and why. This document is written so the fleet team can implement their role from this file alone. ## What the binary does (and does not do) `agent-lib` is one static Go binary with two roles: - **Curator** (maintainer machine): `vendor add/update/diff/remove/list/inspect` plus `validate` — manages external content inside the company work repository. Publication = `git commit && git push` by the maintainer. - **Client** (employee machine): `sync` + `status` — pulls the work repository and deploys skills/commands/agents into the OpenCode paths. Deploys with three-state protection: user-modified managed items are skipped with a warning (never steamrolled), self-created items are never touched, unmodified items update/remove silently. The binary handles all content transport itself. It never deploys or merges MCP fragments — `mcp/` and `external/*/mcp/` stay under controller-side merge and vault substitution (clone the work repository as before, now including the external areas). ## Rollout components ### 1. Binary via pinned GitHub release - Source of truth: GitHub releases of `m3tam3re/agent-lib`. - Artifacts: `agent-lib_{windows_amd64,linux_amd64,linux_arm64,darwin_amd64,darwin_arm64}` plus `checksums.txt` (tar.gz archives; windows is a zip containing `agent-lib.exe` and the windowless `agent-libw.exe`). - Fleet pins an exact release tag (installer-pin pattern already used for other tools). **No self-update exists in the binary** — binary updates are exclusively fleet rollouts. Content updates are pulled by the binary itself. - Verify the checksum during rollout; install to a fixed path (e.g. `C:\Program Files\agent-lib\agent-lib.exe` / `/usr/local/bin/agent-lib`). ### 2. Admin-protected client config Path: `C:\ProgramData\agent-lib\config.json` (Windows, ACL restricted to Administrators + read for Users) or `/etc/agent-lib/config.json` (Linux, root-owned, mode 0644). ```json { "repo_url": "https://git.example.com/company/agent-content.git", "ref": "main", "token": "", "token_user": "oauth2" } ``` - The token is a **shared read-only** deploy token scoped to the work repository. It is used for HTTP basic auth only and never appears in the lockfile, the manifest, logs, or error output. - Employees must be able to read the config (sync runs in their context) but must not be able to alter it. - Per-run overrides for testing: `--config ` or `AGENT_LIB_CONFIG`. - Optional `"labels": ["