code-be-02
87c08d25d4
Spec of record: docs/plans/2026-08-23_repo-structure-declaration.md (brain repo) sections 4 (consumption contract), 5.1/5.3/5.4, 1.2a. New shared lib repo-decl.sh: one consumption surface for the wrappers. Loads .mosaic/repo.json, classifies absent/invalid/valid via the WP1 validator (5.1: ALL consumers invoke the same script; 5.4 point 1: invalid = ABSENT + loud error naming file/key/reason), extracts the consumed fields, normalizes origin for 5.3 comparisons, validates transitions per 4.2 (a CLI flag is input, not authority), and resolves host:/ paths FAIL-CLOSED while MOSAIC_HOST_ROOT is unset (1.2a — no WP5b consumer resolves a path today; the helper exists so the first that needs one cannot guess). v1 declarations validate but carry no consumable fields: legacy behavior with a note. pr-create.sh: base precedence -B (validated as an allowed transition) -> declared integration_trunk -> legacy WP5a forge-default floor (unmanaged/absent/v1 per 4.3 reversible class, warn + legacy). Remote mismatch vs canonical_remote refuses (write path, 5.3). pr-merge.sh: transition validation per declared flow; the hardcoded main/next target check survives only for undeclared repos during the rollout window (4.3 irreversible class, loud warning). Remote mismatch refuses. ci-queue-wait.sh: ROUTE CONTEXT only (4.1, C4/jarvis F8/DR2 R9) — branch-selection semantics untouched, absence silent, invalid reported per 5.4. mosaic-worktree.sh: staged rule 4.4 — invalid declaration fails branch-creation loud, absent warns and proceeds, valid contributes policy ADVICE only (4.5: placement stays derived; the advisory worktree_root comparison runs only when MOSAIC_HOST_ROOT is set, per 1.2a warn-and-omit). Consuming via a self-located source line and set -u-safe env access. mutate-push-guard.sh: NO change — spec 4.1 names it for push-to-trunk protection, but the tool as shipped is a mutation-coverage meta-tool for push-guard.sh with no trunk-protection logic to consult; the disposition is documented in #1413 rather than force-feeding a fake consumption. All wrappers degrade SILENTLY to legacy behavior when repo-decl.sh is absent from a copied tool subset (a legal deployment shape; a note there broke single-line diagnostic contracts in test-pr-merge-message-field). test-repo-decl-consumption.sh: 67 assertions, green x2, hermetic; runs RED against pre-change tools via WP5B_TOOLS (49 red there — red-first evidence). Covers every 5.4 hostile-input class applicable to consumed fields (missing, malformed, unknown schema_version, v1, unknown key, bad refs, cross-field, userinfo URL, remote mismatch) plus transition validation, base precedence, absence policies, staged worktree rule, route context, and 1.2a fail-closed. Enumerated on the S1 surface (enumeration guard green: population 71, enumerated 57). Neighbor suites green: WP5a fallback suite, all six pr-merge suites, worktree large-repo, help/login/interactive suites. S1 chain failures (fleet-units systemd bus, invariant_r host Pi version, pr-edit credential-helper env) reproduce identically at origin/next — environmental, untouched by this diff. No TS/vitest lane touched (shell tools only).
@mosaicstack/mosaic
CLI package for the Mosaic self-hosted AI agent platform.
Usage
mosaic wizard # First-run setup wizard
mosaic gateway install # Install the gateway daemon
mosaic config show # View current configuration
mosaic config hooks list # Manage Claude hooks
Headless / CI Installation
Set MOSAIC_ASSUME_YES=1 (or ensure stdin is not a TTY) to skip all interactive prompts. The following environment variables control the install:
Gateway configuration (mosaic gateway install)
| Variable | Default | Required |
|---|---|---|
MOSAIC_STORAGE_TIER |
local |
No |
MOSAIC_GATEWAY_PORT |
14242 |
No |
MOSAIC_DATABASE_URL |
(none) | Yes if tier=team |
MOSAIC_VALKEY_URL |
(none) | Yes if tier=team |
MOSAIC_ANTHROPIC_API_KEY |
(none) | No |
MOSAIC_CORS_ORIGIN |
http://localhost:3000 |
No |
Admin user bootstrap
| Variable | Default | Required |
|---|---|---|
MOSAIC_ADMIN_NAME |
(none) | Yes (headless) |
MOSAIC_ADMIN_EMAIL |
(none) | Yes (headless) |
MOSAIC_ADMIN_PASSWORD |
(none) | Yes (headless) |
MOSAIC_ADMIN_PASSWORD must be at least 8 characters. In headless mode a missing or too-short password causes a non-zero exit.
Example: Docker / CI install
export MOSAIC_ASSUME_YES=1
export MOSAIC_ADMIN_NAME="Admin"
export MOSAIC_ADMIN_EMAIL="[email protected]"
export MOSAIC_ADMIN_PASSWORD="securepass123"
mosaic gateway install
Runtime launchers
mosaic claude # Launch Claude Code with Mosaic injection
mosaic yolo claude # …with --dangerously-skip-permissions
mosaic codex | opencode | pi
mosaic claudex (EXPERIMENTAL)
Runs GPT models inside the Claude Code harness by pointing Claude Code at a
local claude-code-proxy that
translates the Anthropic Messages API to a ChatGPT-subscription (Codex OAuth)
backend. This is not Anthropic Claude — model behavior, tool use, and output
quality may differ. Intended for evaluation, not production delivery.
mosaic claudex # launch (prompts through the proxy readiness gate)
mosaic yolo claudex # …with --dangerously-skip-permissions
mosaic claudex --print "hello" # trailing args are forwarded to Claude Code
Prerequisite: the claude-code-proxy binary must be installed and
authenticated (claude-code-proxy codex auth …). mosaic claudex runs a
preflight that verifies the binary, the OAuth state (triggering a device re-auth
if needed), and a trusted local listener before launching; it fails closed
if the proxy cannot be brought up with a verified identity.
Isolation (never touches your real Claude state). claudex always launches
against an isolated CLAUDE_CONFIG_DIR (default ~/.config/mosaic/claudex/home).
The ambient CLAUDE_CONFIG_DIR is deliberately ignored, and a guard proves the
resolved dir can never be — or live under — the real ~/.claude. A claudex
session therefore cannot mutate your normal Claude Code config.
No token leakage. claudex never reads the proxy's credential file. Claude
Code is handed only ANTHROPIC_AUTH_TOKEN=unused pointed at the loopback proxy;
the entire credential-bearing env family (ANTHROPIC_*, AWS_*, GOOGLE_CLOUD_*,
GOOGLE_APPLICATION_CREDENTIALS, *_TOKEN, *_KEY, *_SECRET, …) is stripped
from the composed environment. The Bedrock/Vertex routing switches
(CLAUDE_CODE_USE_BEDROCK, CLAUDE_CODE_USE_VERTEX, and the _SKIP_*_AUTH
pair) are force-removed regardless of value — otherwise their mere presence
would route Claude Code to the real Anthropic API via AWS/GCP and bypass the
proxy. The proxy holds the real OAuth credential.
Model tiers (override via env).
| Tier | Env var | Default |
|---|---|---|
| primary (opus/sonnet) | ANTHROPIC_MODEL |
gpt-5.6-sol |
| small/fast (haiku) | ANTHROPIC_SMALL_FAST_MODEL |
gpt-5.6-luna |
Operator-provided values win over the defaults. Additional overrides:
MOSAIC_CLAUDEX_CONFIG_DIR (isolated config dir), ANTHROPIC_BASE_URL (proxy
endpoint).
Hooks management
After running mosaic wizard, Claude hooks are installed in ~/.claude/hooks-config.json.
mosaic config hooks list # Show all hooks and enabled/disabled status
mosaic config hooks disable PostToolUse # Disable a hook (reversible)
mosaic config hooks enable PostToolUse # Re-enable a disabled hook
Set CLAUDE_HOME to override the default ~/.claude directory.