@pennixrv/trellis 0.6.18 → 0.6.20

package/dist/templates/common/bundled-skills/trellis-channel/references/command-reference.md

@@ -41,6 +41,7 @@ trellis channel create <name>
 ```
 
 Behavior:
+
 - Appends a `create` event; immutable `type` (cannot mutate forum↔chat after).
 - `--ephemeral` channels are hidden from `channel list` by default and are
   the sweep target for `channel prune --ephemeral`.
@@ -59,6 +60,7 @@ trellis channel list
 ```
 
 Behavior:
+
 - Default scope: current cwd's project. `--all-projects` scans every bucket.
 - Pretty mode prints `NAME WORKERS EVENTS LAST KIND TYPE TASK`, sorted by
   recency, with a footer noting hidden ephemeral count.
@@ -80,6 +82,7 @@ trellis channel send <name> [text]
 ```
 
 Behavior:
+
 - Body precedence: positional `[text]` → `--stdin` → `--text-file`.
 - `--to` with one entry stores a string; multiple stores an array; omitted
   means broadcast.
@@ -110,12 +113,24 @@ trellis channel messages <name>
 ```
 
 Behavior:
+
 - Auto-detects forum channels: with no filters it renders the thread board
   instead of the event stream. `--thread` / `--action` are forum-only and
   error against chat channels.
 - `--kind` is validated against `CHANNEL_EVENT_KINDS` (single value, not
   CSV — that's the `wait` side).
 
+### `barrier <name>`
+
+```bash
+trellis channel barrier <name>
+  [--scope project|global]
+```
+
+Prints the channel's current durable event sequence as one integer. It does not
+append an event. Capture it after `create` and before an operation that can
+emit the event you intend to wait for, then pass it to `wait --after-seq`.
+
 ### `wait <name>`
 
 ```bash
@@ -123,6 +138,7 @@ trellis channel wait <name>
   --as <agent>                            # REQUIRED — self for filter ctx
   [--scope project|global]
   [--timeout <Ns|Nm|Nh|Nms>]              # parsed by parseDuration
+  [--after-seq <integer>]                 # replay only events after barrier
   [--from <a,b>]                          # author CSV
   [--kind <k1,k2>]                        # CSV, OR semantics
   [--thread <key>]                        # forum filter
@@ -133,11 +149,15 @@ trellis channel wait <name>
 ```
 
 Behavior:
+
 - Streams matching events as JSON, one per line.
 - Default `--to` filter is the caller's own agent (broadcast events still
   match — broadcast + explicit-to-me).
 - `--all` requires `--from` and blocks until every listed agent has produced
   a matching event.
+- Without `--after-seq`, the command captures its current event sequence before
+  constructing its watcher and ignores prior events. With `--after-seq`, it
+  replays matching events whose sequence is greater than that supplied barrier.
 - **Timeout exits 124** and prints `timeout: still waiting on ...` to stderr
   when `--all` was in play.
 
@@ -199,6 +219,7 @@ trellis channel interrupt <name> [text]
 ```
 
 Behavior:
+
 - Appends an `interrupt` event with `reason: "user"` and a replacement
   instruction body; supervisor performs provider-level interrupt where
   supported (Claude `/interrupt`, Codex turn cancel).
@@ -235,6 +256,7 @@ trellis channel spawn <name>
 ```
 
 Behavior:
+
 - Provider is validated against the adapter registry
   (`packages/cli/src/commands/channel/adapters/`); current: `claude`,
   `codex`.
@@ -262,6 +284,7 @@ trellis channel run [name?]
 ```
 
 Behavior:
+
 - One-shot. Auto-generates `run-<hex>` if `name` omitted.
 - Creates an ephemeral channel (`createMode=run`), spawns a single worker,
   sends the prompt, waits for `done`, prints the final assistant text to
@@ -281,6 +304,7 @@ trellis channel kill <name>
 ```
 
 Behavior:
+
 - Default path: SIGTERM → 8 s grace → SIGKILL escalation; the CLI writes a
   `killed` event when SIGKILL was needed so the log stays truthful.
 - Cleans `pid`, `worker-pid`, `config`, `spawnlock` sidecar files; keeps
@@ -294,6 +318,7 @@ trellis channel rm <name>
 ```
 
 Behavior:
+
 - Kills any live workers, then deletes the entire channel directory.
 - Prints `Removed channel '<name>'`.
 
@@ -309,6 +334,7 @@ trellis channel prune
 ```
 
 Behavior:
+
 - Filter flags are mutually exclusive — error otherwise.
 - Default is dry-run; `--yes` flips to real delete.
 - Without `--scope`, scans **every** project bucket (intentional, repo-wide
@@ -341,6 +367,7 @@ trellis channel post <name> <action>
 ```
 
 Behavior:
+
 - `<action>` is free-form on the CLI surface; conventional values include
   `opened`, `comment`, `status`, `labels`, `assignees`, `summary`,
   `processed`.
@@ -358,6 +385,7 @@ trellis channel forum <name>
 ```
 
 Behavior:
+
 - Lists threads (reduced state). `--status` filters by current thread
   status. `--raw` prints one JSON per thread.
 
@@ -374,6 +402,7 @@ trellis channel thread rename <name> <old-thread> <new-thread>
 ```
 
 Behavior:
+
 - `thread <name> <key>` shows one thread's timeline:
   header `<thread> [<status>] <title>`, then description / labels /
   assignees / summary / timeline lines. `--raw` switches to raw events.
@@ -408,6 +437,7 @@ trellis channel context list <name>
 ```
 
 Behavior:
+
 - `add` / `delete` append a `context` event and print the event JSON.
 - `list` projects current context entries; pretty output is
   `file <path>` / `raw <truncated text>` lines, `(no context)` when empty.
@@ -426,6 +456,7 @@ trellis channel title clear <name>
 ```
 
 Behavior:
+
 - Appends a `title` event projecting a stable display title onto the
   channel. Output: event JSON.
 
@@ -433,10 +464,10 @@ Behavior:
 
 ## Hidden / Internal
 
-| Command | Purpose |
-|---|---|
-| `channel __supervisor <channel> <worker> <config>` | Forked entry point invoked by `spawn`. Do not invoke directly. |
-| `channel __parse-trace <adapter> <file>` | Dev helper — replays a recorded stream-json / wire trace through the matching adapter and prints the resulting channel events. Adapter is validated against the provider registry. |
+| Command                                            | Purpose                                                                                                                                                                            |
+| -------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `channel __supervisor <channel> <worker> <config>` | Forked entry point invoked by `spawn`. Do not invoke directly.                                                                                                                     |
+| `channel __parse-trace <adapter> <file>`           | Dev helper — replays a recorded stream-json / wire trace through the matching adapter and prints the resulting channel events. Adapter is validated against the provider registry. |
 
 ---
 
@@ -477,4 +508,3 @@ Forum channels are event-sourced; use the CLI reducers
   pipe); diagnostic notes go to stderr.
 - **Errors** go through `chalk.red("Error:")` to stderr and `exit 1`.
 - **`wait` timeout** specifically exits **124**.
-

package/dist/templates/common/bundled-skills/trellis-channel/references/progress-debugging.md

@@ -1,7 +1,7 @@
 # Progress And Debugging
 
 Pretty output is for operators. Raw output is the audit log. Subcommands
-(`forum`, `thread`, `messages`, `context`) are the audit *interface* — reach
+(`forum`, `thread`, `messages`, `context`) are the audit _interface_ — reach
 for them before grepping `events.jsonl` by hand.
 
 ## Pretty vs `--raw`
@@ -120,7 +120,18 @@ inspect the worker log for the subprocess.
 
 ## Wait Semantics (Quick Reference)
 
-`channel wait` watches `events.jsonl` from EOF and wakes on:
+Without `--after-seq`, `channel wait` captures the current durable sequence,
+then watches matching later events. For an operation that can finish before the
+wait command starts, capture a barrier before that operation and pass it back:
+
+```bash
+BARRIER="$(trellis channel barrier T)"
+# spawn or trigger work that may emit a terminal event
+trellis channel wait T --as main --from check --kind done,error \
+  --after-seq "$BARRIER" --timeout 15m
+```
+
+It wakes on:
 
 - `message`
 - `done`
@@ -133,7 +144,7 @@ Useful filters:
 ```bash
 trellis channel wait T --as main --from check --kind done --timeout 15m
 trellis channel wait T --as main --from check,check-cx --kind done --all --timeout 15m
-trellis channel wait T --as worker --tag interrupt --timeout 1h
+trellis channel wait T --as worker --kind message --timeout 1h
 trellis channel wait T --as main --thread release-note --action status --timeout 10m
 ```
 
@@ -192,16 +203,16 @@ diffing against `<worker>.inbox-cursor` while debugging the supervisor.
 
 ## Common Failures
 
-| Symptom | Cause | Fix |
-|---|---|---|
-| `trellis: command not found` | CLI not installed globally | `npm install -g @pennixrv/trellis` |
-| `wait` exits immediately | wrong filter or identity collision | use distinct `--as`, inspect raw messages |
-| zsh errors on message text | shell interpreted punctuation | use `--stdin` or `--text-file` |
-| progress line is cut off | pretty output truncation | use `messages --raw --kind progress` |
-| worker never speaks | provider startup / prompt / MCP delay | inspect `<worker>.log`, `ps`, raw events |
-| channel not found in another cwd | project bucket mismatch | `cd` to project, use `--scope global`, or `list --all-projects` |
-| ghost worker in list | supervisor died without cleanup | `trellis channel kill <name> --as <worker> --force` |
-| forum thread looks scrambled | parsed `events.jsonl` directly | use `forum`, `thread`, `messages --thread` |
+| Symptom                          | Cause                                 | Fix                                                             |
+| -------------------------------- | ------------------------------------- | --------------------------------------------------------------- |
+| `trellis: command not found`     | CLI not installed globally            | `npm install -g @pennixrv/trellis`                              |
+| `wait` exits immediately         | wrong filter or identity collision    | use distinct `--as`, inspect raw messages                       |
+| zsh errors on message text       | shell interpreted punctuation         | use `--stdin` or `--text-file`                                  |
+| progress line is cut off         | pretty output truncation              | use `messages --raw --kind progress`                            |
+| worker never speaks              | provider startup / prompt / MCP delay | inspect `<worker>.log`, `ps`, raw events                        |
+| channel not found in another cwd | project bucket mismatch               | `cd` to project, use `--scope global`, or `list --all-projects` |
+| ghost worker in list             | supervisor died without cleanup       | `trellis channel kill <name> --as <worker> --force`             |
+| forum thread looks scrambled     | parsed `events.jsonl` directly        | use `forum`, `thread`, `messages --thread`                      |
 
 ## Storage Layout
 

package/dist/templates/common/bundled-skills/trellis-channel/references/subnode-work.md

@@ -0,0 +1,159 @@
+# Bounded Subnode Work
+
+Use a `subnode` only when the user explicitly needs independently reviewable
+evidence for a bounded analysis, design, audit, review, counterargument, or
+verification question. It is not the normal path for an ordinary static review,
+implementation, memory retrieval, or routine tool call.
+
+The coordinator owns task facts, protected targets, acceptance, Git, worker
+lifecycle, and the final result. A subnode owns one evidence report and its own
+append-only worklog. This is a behavioral contract; do not add `--sandbox` or
+claim that path restrictions enforce it.
+
+## Artifact Setup
+
+Before spawning, the coordinator must use an active task (`planning` or
+`in_progress`), define one stable `work_id` and
+`subnode_id`, then prepare a brief-draft JSON with the question, independence
+reason, scope, protected targets, lens, evidence method, source snapshot,
+dependencies, stop conditions, deadline, `channel_ref`, `retry_of` (null unless
+this is an explicit manual retry), and `counter_of` (null unless this is
+intentional counterwork). A retry names an existing, different subnode in the
+same task and `work_id`; counterwork may be initialized independently. The
+helper supplies the immutable task identity and report path.
+
+```bash
+TASK=.trellis/tasks/09-07-example
+WORK_ID=security-audit
+SUBNODE_ID=dependency-evidence
+
+python3 .trellis/scripts/subnode_artifact.py init \
+  --task "$TASK" \
+  --work-id "$WORK_ID" \
+  --subnode-id "$SUBNODE_ID" \
+  --draft /tmp/subnode-brief.json
+```
+
+This creates exactly:
+
+```text
+$TASK/subnodes/$WORK_ID/$SUBNODE_ID/
+  brief.json     # coordinator-owned and immutable after dispatch
+  worklog.md     # subnode appends material progress and corrections
+  report.json    # subnode-owned final pending-review result
+```
+
+Do not use a terminal Channel message as the report transport. The short final
+message names the already-written `report.json` and its status; the durable
+JSON file carries the reviewable result.
+
+The subnode copies identity, scope, and lens from `brief.json`. The minimal
+complete report is:
+
+```json
+{
+  "schema_version": 1,
+  "task_id": "task-id-from-brief",
+  "work_id": "work-id-from-brief",
+  "subnode_id": "subnode-id-from-brief",
+  "role_id": "subnode",
+  "status": "complete",
+  "scope": ["exact scope copied from brief"],
+  "lens": "exact lens copied from brief",
+  "evidence": [
+    {
+      "id": "stable-evidence-id",
+      "locator": "source path, URL, or command receipt",
+      "summary": "What this independently reviewable evidence establishes."
+    }
+  ],
+  "findings": ["Bounded conclusion."],
+  "uncertainties": [],
+  "corrections": []
+}
+```
+
+For `blocked`, `incomplete`, or `error`, include the same base fields plus a
+non-empty `completed_scope` list and a non-empty `blocker` string. Never use
+`accepted`, `rejected`, or `deferred` as a report status.
+
+## Dispatch And Wait
+
+Inspect the installed role first, then capture a durable event barrier before
+the worker can emit a terminal event. The CLI waits once and replays matching
+events committed after that barrier:
+
+```bash
+trellis channel create subnode-example --by main --cwd "$PWD"
+BARRIER="$(trellis channel barrier subnode-example)"
+trellis channel spawn subnode-example --agent subnode --provider codex \
+  --as "$SUBNODE_ID" --cwd "$PWD" --timeout 30m
+
+printf '%s\n' "Read $TASK/subnodes/$WORK_ID/$SUBNODE_ID/brief.json and perform only that bounded work." \
+  | trellis channel send subnode-example --as main --to "$SUBNODE_ID" \
+      --stdin --delivery-mode requireRunningWorker
+
+trellis channel wait subnode-example --as main --from "$SUBNODE_ID" \
+  --kind done,error --after-seq "$BARRIER" --timeout 30m
+```
+
+Where the host exposes a live wait continuation, capture the same barrier,
+establish one event waiter before triggering the worker, and continue that same
+waiter until terminal state. Do not create a second waiter or treat an empty
+transport slice as completion. `channel messages`, worker inspection, and
+status/list commands remain valid on-demand diagnostics, but do not use
+high-frequency repeated queries as the coordinator's supervision loop.
+
+## Coordinator Review
+
+After a terminal message, independently validate and then record a task-level
+disposition. `complete` means only that the subnode claims it completed its
+assigned work; it is not acceptance.
+
+```bash
+REPORT="$TASK/subnodes/$WORK_ID/$SUBNODE_ID/report.json"
+python3 .trellis/scripts/subnode_artifact.py validate --report "$REPORT"
+```
+
+The coordinator must re-check enough source evidence and protected-target state
+to decide `accepted`, `rejected`, or `deferred`, preserving the reason and named
+checks such as `report_validation`, `source_recheck`, and
+`protected_target_check` in task research or a decision record. The validator
+does not make that decision and does not modify `task.json`.
+
+Use the separate coordinator work-record helper only for a durable cross-task
+observation, decision, open question, or blocker. It does not substitute for a
+task artifact or subnode worklog.
+
+```bash
+python3 .trellis/scripts/workspace_note.py \
+  --kind decision \
+  --summary "Accepted independent dependency evidence for the release gate." \
+  --source "$REPORT"
+```
+
+## Counterwork
+
+Counterwork is a new, independently scoped subnode, not a retry. It must use a
+different `subnode_id`, lens, and evidence identities, and its brief sets
+`counter_of` to the primary subnode ID. After both reports are complete:
+
+```bash
+python3 .trellis/scripts/subnode_artifact.py validate-counter \
+  --primary "$TASK/subnodes/$WORK_ID/primary" \
+  --counter "$TASK/subnodes/$WORK_ID/counter"
+```
+
+The coordinator compares the two reports and retains the comparison as part of
+its own disposition.
+
+## Manual Retry
+
+A retry is a fresh, explicitly approved subnode after a recorded failed or
+incomplete attempt. It uses a new `subnode_id`, preserves the old artifacts,
+and sets `retry_of` to that prior subnode ID in its brief. The coordinator must
+record why it is retrying and check the new report independently; neither the
+helper nor Channel decides when to retry.
+
+No scheduler, high-frequency polling loop, automatic retry, worktree, global
+ledger, or provider-specific transport is introduced by this workflow.

package/dist/templates/common/bundled-skills/trellis-channel/references/workflows.md

@@ -11,6 +11,7 @@ Use when the user says "和 codex/claude 讨论一下", "brainstorm", or "拉一
 ```bash
 trellis channel create brainstorm-storage-layer --by main \
   --task .trellis/tasks/05-XX-storage-adapter
+BARRIER="$(trellis channel barrier brainstorm-storage-layer)"
 
 trellis channel spawn brainstorm-storage-layer \
   --agent architect --provider codex \
@@ -22,7 +23,7 @@ trellis channel send brainstorm-storage-layer \
   --as main --to cx-arch --text-file /tmp/brainstorm-r1.md
 
 trellis channel wait brainstorm-storage-layer \
-  --as main --kind done --from cx-arch --timeout 10m
+  --as main --kind done --from cx-arch --after-seq "$BARRIER" --timeout 10m
 ```
 
 Do not stop after one answer. Read the answer, identify vague areas, send a
@@ -53,6 +54,7 @@ Use when the user asks to dispatch implementation or review work.
 ```bash
 TASK=.trellis/tasks/05-12-foo
 trellis channel create cr-foo --task "$TASK" --by main
+BARRIER="$(trellis channel barrier cr-foo)"
 
 trellis channel spawn cr-foo \
   --agent check \
@@ -63,7 +65,7 @@ trellis channel spawn cr-foo \
   --cwd "$PWD" --timeout 15m
 
 trellis channel send cr-foo --as main --to check --text-file /tmp/cr-brief.md
-trellis channel wait cr-foo --as main --kind done --from check --timeout 15m
+trellis channel wait cr-foo --as main --kind done --from check --after-seq "$BARRIER" --timeout 15m
 trellis channel messages cr-foo --kind message --from check --tag final_answer
 ```
 
@@ -77,6 +79,7 @@ Use one channel and distinct worker names.
 
 ```bash
 trellis channel create cr-feature --by main --ephemeral
+BARRIER="$(trellis channel barrier cr-feature)"
 
 trellis channel spawn cr-feature --agent check \
   --jsonl "$TASK/check.jsonl" --file "$TASK/prd.md" --file "$TASK/design.md" \
@@ -88,7 +91,7 @@ trellis channel spawn cr-feature --agent check --provider codex --as check-cx \
 
 trellis channel send cr-feature --as main --to check --text-file /tmp/cr-brief.md
 trellis channel send cr-feature --as main --to check-cx --text-file /tmp/cr-brief.md
-trellis channel wait cr-feature --as main --kind done --from check,check-cx --all --timeout 15m
+trellis channel wait cr-feature --as main --kind done --from check,check-cx --all --after-seq "$BARRIER" --timeout 15m
 ```
 
 `--all` means every listed worker must emit a matching event.

package/dist/templates/shared-hooks/inject-workflow-state.py

@@ -286,13 +286,14 @@ def prompt_has_skip_keyword(prompt: str, keyword: str) -> bool:
 def _resolve_codex_dispatch_mode(config: dict) -> str:
     """Normalize `codex.dispatch_mode` from .trellis/config.yaml to "auto" or "inline".
 
-    Defaults to `auto`. The legacy `sub-agent` value is an alias for `auto`.
-    Any other explicit value (including invalid ones) falls back to `inline`
+    Defaults to `inline`. `auto` explicitly enables native dispatch; the
+    legacy `sub-agent` value is an alias for `auto`. Any other explicit value
+    (including invalid ones) falls back to `inline`
     without per-turn warnings. Shared by `_codex_mode_banner` (the per-turn
     banner) and `resolve_breadcrumb_key` (the breadcrumb tag key) so the two
     stay in lockstep.
     """
-    mode = "auto"
+    mode = "inline"
     if isinstance(config, dict):
         codex_cfg = config.get("codex")
         if isinstance(codex_cfg, dict):
@@ -310,16 +311,16 @@ def _codex_mode_banner(config: dict) -> str:
     """Emit a `<codex-mode>` banner for the additionalContext payload.
 
     Reads `codex.dispatch_mode` from .trellis/config.yaml; defaults to
-    `auto`, which dispatches Trellis sub-agents using native Codex context
+    `inline`, so the main session implements and checks directly. `auto`
+    explicitly dispatches Trellis sub-agents using native Codex context
     injection with a child-side fallback. This does not rely on inherited
     parent transcripts: `fork_turns` remains caller-controlled, and
     fresh-history sub-agents still receive their explicit delegated task and
-    inherited session configuration. `inline` is an explicit opt-out; the
-    legacy `sub-agent` value is an alias for `auto`. Invalid explicit values
-    fall back to `inline` without per-turn warnings. The banner makes the
-    active mode explicit to Codex AI per turn, complementing the workflow-state
-    body which is per-status. Mode tells AI which dispatch protocol to follow;
-    workflow-state tells AI what step it's at.
+    inherited session configuration. The legacy `sub-agent` value is an alias
+    for `auto`. Invalid explicit values fall back to `inline` without per-turn
+    warnings. The banner makes the active mode explicit to Codex AI per turn,
+    complementing the workflow-state body which is per-status. Mode tells AI
+    which dispatch protocol to follow; workflow-state tells AI what step it's at.
     """
     mode = _resolve_codex_dispatch_mode(config)
     if mode == "auto":
@@ -341,12 +342,12 @@ def resolve_breadcrumb_key(
 ) -> str:
     """Pick the breadcrumb tag key based on Codex dispatch_mode.
 
-    Codex defaults to ``auto`` and therefore uses the ordinary ``<status>``
-    breadcrumb for native SubagentStart dispatch with child-side fallback;
-    it does not depend on an inherited parent transcript. ``inline`` selects
-    the parallel ``<status>-inline`` tag; ``sub-agent`` remains an alias for
-    ``auto``. Invalid explicit values fall back to inline without per-turn
-    warnings.
+    Codex defaults to ``inline`` and therefore uses the parallel
+    ``<status>-inline`` breadcrumb for main-session execution. Explicit
+    ``auto`` uses the ordinary ``<status>`` breadcrumb for native
+    SubagentStart dispatch with child-side fallback; ``sub-agent`` remains an
+    alias for ``auto``. Invalid explicit values fall back to inline without
+    per-turn warnings.
 
     Non-codex platforms return the plain status unchanged.
     """

package/dist/templates/trellis/agents/subnode.md

@@ -0,0 +1,62 @@
+---
+name: subnode
+description: |
+  Bounded independent-evidence worker. It preserves its assigned task artifacts,
+  never changes protected target files, and leaves acceptance to the coordinator.
+provider: codex
+labels: [trellis, subnode]
+---
+
+# Subnode (channel runtime)
+
+You are a bounded Trellis subnode spawned through `trellis channel`. Your job is
+to produce independently reviewable evidence for one assigned question. You are
+not an implementation worker, task owner, reviewer-of-record, or Git operator.
+
+## Required Context
+
+Before starting, read the `brief.json` path named in the coordinator message.
+It fixes your task identity, scope, protected targets, evidence method, source
+snapshot, deadline, stop conditions, channel handle, and final `report_path`.
+Read the necessary current project and external sources needed to answer that
+brief. A source snapshot records evidence; it is not a filesystem allowlist.
+
+## Ownership And Write Boundary
+
+You may write only within the artifact directory named by the brief:
+
+- `worklog.md` — append substantive observations, corrections, blockers, and
+  completion notes as they occur.
+- `report.json` — write your one final pending-review report at the exact path
+  in `brief.json`.
+
+Do not modify `brief.json`. Do not edit any protected target, business source,
+test, task artifact, project rule, coordinator workspace note, or unrelated
+file. Do not run Git commands that change state (`commit`, `push`, `merge`,
+`rebase`, `reset`, `checkout`, `stash`, or branch/worktree operations). Do not
+spawn or control another worker. These are behavioral requirements, not a
+sandbox claim.
+
+## Work Method
+
+1. Confirm the brief identity and artifact paths before doing substantive work.
+2. Inspect evidence using the stated lens and method. Keep the assigned scope
+   narrow; stop when a stop condition is met or the evidence is sufficient.
+3. Append a concise worklog entry when you make a material discovery, retract a
+   conclusion, encounter a blocker, or finish. Preserve corrections rather
+   than silently rewriting the historical trail.
+4. Write `report.json` only when you are ready to stop. Its status is one of
+   `complete`, `blocked`, `incomplete`, or `error`; it is always
+   **pending coordinator review**, never accepted/rejected/deferred.
+5. A complete report includes independently checkable evidence. A non-complete
+   report explains completed scope and the blocker or error. Include the exact
+   identity, scope, and lens required by the artifact helper.
+6. Send one short terminal Channel message with the status and report path.
+   Do not place the report JSON in Channel text.
+
+## Report Boundary
+
+The coordinator independently runs the artifact validator and then records the
+task disposition (`accepted`, `rejected`, or `deferred`) with its own source and
+protected-target checks. Do not claim that a report has been accepted, and do
+not infer a disposition from a successful Channel delivery.

package/dist/templates/trellis/config.yaml

@@ -110,14 +110,14 @@ channel:
 #-------------------------------------------------------------------------------
 # Codex (dispatch behavior)
 #-------------------------------------------------------------------------------
-# Codex-only knob; other platforms ignore it. Default ("auto") dispatches
-# trellis-implement / trellis-check / trellis-research sub-agents. This does
-# not rely on inherited parent transcripts: `fork_turns` remains
-# caller-controlled, while Codex's native SubagentStart hook injects task
-# context when trusted and child-side loading remains the fallback when it is
-# unavailable. Set to "inline" only to keep implementation and checks in the
-# main session. "sub-agent" remains a backwards-compatible alias for "auto".
-# Invalid explicit values safely use inline mode.
+# Codex-only knob; other platforms ignore it. The default is "inline": the
+# main session performs implementation and checks directly. Set "auto" only
+# to opt in to trellis-implement / trellis-check / trellis-research native
+# sub-agents. Their task context does not rely on inherited parent transcripts:
+# `fork_turns` remains caller-controlled, while Codex's native SubagentStart
+# hook injects context when trusted and child-side loading remains the fallback
+# when it is unavailable. "sub-agent" remains a backwards-compatible alias
+# for "auto". Invalid explicit values safely use inline mode.
 #
 # In "auto" mode, dispatched sub-agents inherit the main session's model
 # unless you pin one. To use a cheaper/faster model for implement/check/
@@ -127,7 +127,7 @@ channel:
 # `trellis update` preserves your edits across regeneration.
 #
 # codex:
-#   dispatch_mode: auto  # or "inline"; legacy alias: "sub-agent"
+#   dispatch_mode: auto  # opt in to native sub-agents; default: "inline"; legacy alias: "sub-agent"
 
 #-------------------------------------------------------------------------------
 # Sub-agent context injection limits

package/dist/templates/trellis/index.d.ts

@@ -45,12 +45,15 @@ export declare const initDeveloperScript: string;
 export declare const taskScript: string;
 export declare const getContextScript: string;
 export declare const addSessionScript: string;
+export declare const subnodeArtifactScript: string;
+export declare const workspaceNoteScript: string;
 export declare const workflowMdTemplate: string;
 export declare const configYamlTemplate: string;
 export declare const gitignoreTemplate: string;
 export declare const gitattributesTemplate: string;
 export declare const implementAgentTemplate: string;
 export declare const checkAgentTemplate: string;
+export declare const subnodeAgentTemplate: string;
 /**
  * Get all script templates as a map of relative path to content
  */

package/dist/templates/trellis/index.d.ts.map

@@ -1 +1 @@
-{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/templates/trellis/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AAcH,eAAO,MAAM,WAAW,QAAsC,CAAC;AAG/D,eAAO,MAAM,UAAU,QAA6C,CAAC;AACrE,eAAO,MAAM,WAAW,QAA0C,CAAC;AACnE,eAAO,MAAM,eAAe,QAA8C,CAAC;AAC3E,eAAO,MAAM,gBAAgB,QAAgD,CAAC;AAC9E,eAAO,MAAM,eAAe,QAA+C,CAAC;AAC5E,eAAO,MAAM,eAAe,QAA+C,CAAC;AAC5E,eAAO,MAAM,gBAAgB,QAAgD,CAAC;AAC9E,eAAO,MAAM,gBAAgB,QAAgD,CAAC;AAC9E,eAAO,MAAM,YAAY,QAA2C,CAAC;AACrE,eAAO,MAAM,QAAQ,QAAuC,CAAC;AAC7D,eAAO,MAAM,SAAS,QAAwC,CAAC;AAC/D,eAAO,MAAM,SAAS,QAAwC,CAAC;AAC/D,eAAO,MAAM,WAAW,QAA0C,CAAC;AACnE,eAAO,MAAM,WAAW,QAA0C,CAAC;AACnE,eAAO,MAAM,iBAAiB,QAAiD,CAAC;AAChF,eAAO,MAAM,eAAe,QAA+C,CAAC;AAC5E,eAAO,MAAM,oBAAoB,QAEhC,CAAC;AACF,eAAO,MAAM,qBAAqB,QAEjC,CAAC;AACF,eAAO,MAAM,mBAAmB,QAE/B,CAAC;AACF,eAAO,MAAM,mBAAmB,QAE/B,CAAC;AACF,eAAO,MAAM,gBAAgB,QAAgD,CAAC;AAG9E,eAAO,MAAM,kBAAkB,QAA2C,CAAC;AAC3E,eAAO,MAAM,mBAAmB,QAA4C,CAAC;AAC7E,eAAO,MAAM,UAAU,QAAkC,CAAC;AAC1D,eAAO,MAAM,gBAAgB,QAAyC,CAAC;AACvE,eAAO,MAAM,gBAAgB,QAAyC,CAAC;AAGvE,eAAO,MAAM,kBAAkB,QAA8B,CAAC;AAC9D,eAAO,MAAM,kBAAkB,QAA8B,CAAC;AAC9D,eAAO,MAAM,iBAAiB,QAAgC,CAAC;AAC/D,eAAO,MAAM,qBAAqB,QAAoC,CAAC;AAMvE,eAAO,MAAM,sBAAsB,QAAsC,CAAC;AAC1E,eAAO,MAAM,kBAAkB,QAAkC,CAAC;AAElE;;GAEG;AACH,wBAAgB,aAAa,IAAI,GAAG,CAAC,MAAM,EAAE,MAAM,CAAC,CAqCnD;AAED;;;;;;;GAOG;AACH,wBAAgB,YAAY,IAAI,GAAG,CAAC,MAAM,EAAE,MAAM,CAAC,CAKlD"}
+{"version":3,"file":"index.d.ts","sourceRoot":"","sources":["../../../src/templates/trellis/index.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;;;GAmBG;AAcH,eAAO,MAAM,WAAW,QAAsC,CAAC;AAG/D,eAAO,MAAM,UAAU,QAA6C,CAAC;AACrE,eAAO,MAAM,WAAW,QAA0C,CAAC;AACnE,eAAO,MAAM,eAAe,QAA8C,CAAC;AAC3E,eAAO,MAAM,gBAAgB,QAAgD,CAAC;AAC9E,eAAO,MAAM,eAAe,QAA+C,CAAC;AAC5E,eAAO,MAAM,eAAe,QAA+C,CAAC;AAC5E,eAAO,MAAM,gBAAgB,QAAgD,CAAC;AAC9E,eAAO,MAAM,gBAAgB,QAAgD,CAAC;AAC9E,eAAO,MAAM,YAAY,QAA2C,CAAC;AACrE,eAAO,MAAM,QAAQ,QAAuC,CAAC;AAC7D,eAAO,MAAM,SAAS,QAAwC,CAAC;AAC/D,eAAO,MAAM,SAAS,QAAwC,CAAC;AAC/D,eAAO,MAAM,WAAW,QAA0C,CAAC;AACnE,eAAO,MAAM,WAAW,QAA0C,CAAC;AACnE,eAAO,MAAM,iBAAiB,QAAiD,CAAC;AAChF,eAAO,MAAM,eAAe,QAA+C,CAAC;AAC5E,eAAO,MAAM,oBAAoB,QAEhC,CAAC;AACF,eAAO,MAAM,qBAAqB,QAEjC,CAAC;AACF,eAAO,MAAM,mBAAmB,QAE/B,CAAC;AACF,eAAO,MAAM,mBAAmB,QAE/B,CAAC;AACF,eAAO,MAAM,gBAAgB,QAAgD,CAAC;AAG9E,eAAO,MAAM,kBAAkB,QAA2C,CAAC;AAC3E,eAAO,MAAM,mBAAmB,QAA4C,CAAC;AAC7E,eAAO,MAAM,UAAU,QAAkC,CAAC;AAC1D,eAAO,MAAM,gBAAgB,QAAyC,CAAC;AACvE,eAAO,MAAM,gBAAgB,QAAyC,CAAC;AACvE,eAAO,MAAM,qBAAqB,QAEjC,CAAC;AACF,eAAO,MAAM,mBAAmB,QAA4C,CAAC;AAG7E,eAAO,MAAM,kBAAkB,QAA8B,CAAC;AAC9D,eAAO,MAAM,kBAAkB,QAA8B,CAAC;AAC9D,eAAO,MAAM,iBAAiB,QAAgC,CAAC;AAC/D,eAAO,MAAM,qBAAqB,QAAoC,CAAC;AAMvE,eAAO,MAAM,sBAAsB,QAAsC,CAAC;AAC1E,eAAO,MAAM,kBAAkB,QAAkC,CAAC;AAClE,eAAO,MAAM,oBAAoB,QAAoC,CAAC;AAEtE;;GAEG;AACH,wBAAgB,aAAa,IAAI,GAAG,CAAC,MAAM,EAAE,MAAM,CAAC,CAuCnD;AAED;;;;;;;GAOG;AACH,wBAAgB,YAAY,IAAI,GAAG,CAAC,MAAM,EAAE,MAAM,CAAC,CAMlD"}