axstack 0.13.0 → 0.13.1

package/README.md

@@ -26,7 +26,9 @@ without changing authority.
    substantial or stacked work needs an approved spec and matching ticket map.
 2. The current chat drives on whatever model runs it; there is no driver
    profile. Bind each ready task to the selected role snapshot and an authoritative Orca
-   Run, Task, and Dispatch. Exactly one writer owns a candidate at a time.
+   Run, Task, and Dispatch. Exactly one writer owns a candidate at a time. All
+   subagent and delegated worker dispatches go through Orca orchestration rather than
+   harness-native subagent tools.
 3. Peer PRs receive both configured independent reviewer roles. Authored PRs
    receive one eligible reviewer from the selected preset's explicit mapping
    and actual author provenance. Every review binds the exact head and base.
@@ -66,8 +68,10 @@ See [installation details](docs/installation.md).
 
 `--instructions` manages one versioned Axstack block in `AGENTS.md`,
 `CLAUDE.md`, or `GEMINI.md`. Harness defaults resolve those files automatically. The block
-points at the installed entry skill and requires delegated work to use visible
-Orca orchestration rather than a harness-native subagent tool. Text and file
+points at the installed entry skill and requires every subagent, delegated worker,
+reviewer, and cross-harness dispatch to use visible Orca orchestration via the `orca` CLI
+rather than a harness-native subagent tool (e.g. Claude/Codex native subagents). OpenCode
+and Antigravity subagents run as Orca-supervised workers. Text and file
 mode outside the markers are preserved; edited, malformed, unowned, or unsafe
 targets are reported without normal-path adoption. Install exits nonzero when
 an instruction conflict is preserved, while clean and idempotent installs exit
@@ -96,9 +100,9 @@ End-to-end compatibility remains unverified without matching runtime receipts.
 
 ## Runtime evidence and holds
 
-Native Orca exercises have returned Codex and Claude worker completions,
-same-terminal follow-up, separate worktree placement, settlement cleanup,
-`user_takeover` retention, and recovery from `consumer_fenced`. These are
+Native Orca exercises have returned Codex, Claude, and OpenCode Muse Spark
+worker completions, same-terminal follow-up, separate worktree placement, settlement
+cleanup, `user_takeover` retention, and recovery from `consumer_fenced`. These are
 bounded runtime facts, not proof that every role or harness is compatible.
 
 Input acceptance is not agent readiness. A trust prompt was observed after an

package/docs/installation.md

@@ -88,8 +88,11 @@ are pruned only when empty, and the target root is never removed.
 
 The deterministic `<!-- axstack:begin v1 -->` / `<!-- axstack:end -->` block
 contains the target-derived Axstack entry path and model-free routing prose. It
-also routes subagents, delegated workers, reviewers, and cross-harness work
-through Orca's `orca` CLI and forbids harness-native subagent delegation.
+also routes every subagent, delegated worker, reviewer, and cross-harness dispatch
+through Orca orchestration via the `orca` CLI (`orca-cli` / `orchestration` guides)
+so the work stays visible. It forbids harness-native subagent tools (e.g. Claude/Codex
+native subagents); workers such as OpenCode and Antigravity subagents
+run as Orca-supervised workers, never via harness-native delegation.
 
 Create, update, repeated install, check, and uninstall preserve every byte and
 the file mode outside the markers. The manifest binds the canonical instruction
@@ -189,6 +192,7 @@ survives.
 | Claude | `~/.claude/skills` | documented upstream |
 | Codex | `$CODEX_HOME/skills` (default `~/.codex/skills`) | documented upstream |
 | OpenCode | `~/.config/opencode/skills` | documented upstream |
+| Antigravity | `~/.gemini/config/skills` | documented upstream |
 | Grok | explicit `--skills-dir` only | auto-discovery unverified |
 
 Prefer explicit paths and current upstream CLI guidance. Installing files does

package/docs/workflows.md

@@ -78,6 +78,12 @@ one Orca executable, loads that binary's version-matched `orchestration` and
 `orca-cli` guides, and follows their advertised schemas. Axstack does not vendor
 the guides or restate a competing command protocol.
 
+All subagent, delegated-worker, reviewer, and cross-harness work goes through Orca
+orchestration via the `orca` CLI (`orca-cli` / `orchestration` guides). Do not use a
+harness-native subagent tool (e.g. Claude/Codex native subagents) for delegated work;
+use Orca runs, tasks, and dispatches instead so the work stays visible. OpenCode
+and Antigravity subagents run as Orca-supervised workers.
+
 Supervised work uses native Run, Task, and Dispatch identity. Preserve actual
 terminal, agent, worktree, requested/effective role, and revision receipts.
 `input_accepted` proves only terminal input; `turn_started` and session

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "axstack",
-  "version": "0.13.0",
+  "version": "0.13.1",
   "description": "Axstack installer and setup CLI: installs owned chat skills and role data, configures supported harness settings, and checks Orca capabilities.",
   "keywords": [
     "claude-code",