workspace

name	workspace
description	Inspect or set the active workspace/worktree map for OmA execution lanes.

Run OmA workspace manager.

Input: $ARGUMENTS

Protocol:

1. Parse requested action:
   • status
   • set <root-or-path>
   • add <path> <lane-or-owner>
   • audit
   • clear
2. Track the active execution surface:
   • primary workspace root
   • optional worktree/path lanes
   • owner or lane affinity
   • baseline branch or HEAD anchor when known
   • lane health (clean, dirty, unknown)
   • trust status (trusted, untrusted, unknown)
   • handoff readiness (ready, needs-review, blocked)
   • cross-lane safety notes
3. Keep the structure minimal and cache-stable:
   • use canonical relative paths when possible
   • avoid volatile timestamps, counters, or shell/session metadata
   • record only active lanes and health notes needed for the current task
4. Recommend separate worktrees only when parallel implementation would otherwise conflict, or when dirty/untrusted lanes need isolation before review or automation.
5. When runtime behavior indicates Gemini CLI v0.36.0+ capabilities, prefer native Git worktree lanes for parallel execution; otherwise keep explicit path-lane ownership with stricter collision notes.
6. When a lane maps to a branch/worktree, record the expected baseline branch and a compact baseline commit/HEAD hint when available.
7. During audit, treat these as execution blockers until reconciled:
   • dirty or untrusted lanes selected for review, verification, or autonomous execution
   • missing baseline anchor on an active parallel lane
   • baseline branch/HEAD mismatch between the recorded lane anchor and the current lane state
8. Prefer one concise safety verdict per lane (ready, needs-review, blocked) so follow-up commands can reuse the result without reinterpreting prose.
9. Before mutating shared lane state, read .omg/state/session-lock.json.
   • only the lock-owning orchestration session may write/update .omg/state/workspace.json
   • if another session owns the lock, write .omg/state/sessions/[session-slug]/workspace.json instead and report the ownership conflict
10. Delegated/worker/subagent turns must not write shared workspace state directly.

Suggested workspace.json shape: { "primary_root": ".", "lanes": [ { "id": "main", "path": ".", "owner": "oma-director", "purpose": "merge-ready baseline", "baseline": { "branch": "main", "commit": "abc1234" }, "health": { "cleanliness": "clean", "trusted": "trusted", "handoff": "ready" } } ], "cross_lane_policy": "explicit-handoff", "source": "oma:workspace" }

Response:

• Keep it concise and operator-facing.
• Include Workspace Status, Lane Map, Lane Health, Baseline Anchors, Collision Risks, and Next Command.
• When audit finds blockers, make the blocker lane and the unblock action explicit.