@pennixrv/trellis 0.7.0-beta.9 → 0.7.1

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

@@ -1,295 +0,0 @@
-# Workers And Agent Cards
-
-Use workers when a peer agent should execute independently and report back
-through the channel event log. A worker is a registered child process (claude
-or codex) attached to a channel; the supervisor forwards inbox messages to it
-and translates its output back into channel events.
-
-## Spawn
-
-```bash
-trellis channel create impl-task --by dispatcher --cwd /path/to/repo
-trellis channel spawn impl-task --provider codex --as codex-impl --timeout 30m
-
-echo "Implement the schema for table X per .trellis/.../prd.md" \
-  | trellis channel send impl-task --as dispatcher --to codex-impl --stdin
-
-trellis channel wait impl-task --as dispatcher --from codex-impl --kind done --timeout 30m
-```
-
-`spawn` forks a `channel __supervisor` worker that emits `spawned`, streams
-`progress`, and should end with `done`, `error`, or `killed`. Workers stay
-inbox-idle until a `send --to <worker>` (or a broadcast when
-`--inbox-policy broadcastAndExplicit` is set) wakes them.
-
-Key `spawn` flags:
-
-- `--agent <name>` — load `.trellis/agents/<name>.md` (provider/model/as/system prompt defaults).
-- `--provider <claude|codex>` — overrides the agent card; validated against the adapter registry.
-- `--as <name>` — channel worker handle; defaults to the agent name.
-- `--cwd <path>` — worker working directory (also the jail root for `--file`/`--jsonl`).
-- `--model <id>` — model override.
-- `--resume <id>` — resume an existing claude session / codex thread.
-- `--timeout <duration>` — auto-kill after `30s` / `2m` / `1h`.
-- `--warn-before <duration>` — supervisor_warning lead time (default `5m`; `0ms` disables).
-- `--file <path>` (repeatable, glob-supported) — inject file content into the system prompt.
-- `--jsonl <path>` (repeatable) — Trellis jsonl manifest (`{file, reason}` per line).
-- `--by <agent>` — author of the `spawned` event (defaults to `$TRELLIS_CHANNEL_AS` or `main`).
-- `--inbox-policy <explicitOnly|broadcastAndExplicit>` — default `explicitOnly`.
-- `--idle-timeout <duration>` — OOM guard idle TTL (default `5m`; `0` disables).
-- `--max-live-workers <n>` — spawn-time live-worker budget (default `6`; `0` disables).
-
-An agent card may declare `env_file: <file>`; the channel runtime loads that
-relative sibling file automatically for the provider child. Use this for
-stable role settings so every spawn of that role gets the same environment.
-The file contains plain `KEY=VALUE` lines only; it is not shell code and does
-not perform expansion or interpolation. Do not put credentials in a bundled
-role file. The bundled `subnode` role uses this mechanism to disable
-OpenViking's automatic recall, capture, and fixed background injection in the
-evidence worker process.
-
-The success event `spawned` records `pid`, `provider`, `agent`, the injected
-`files`, and the resolved `manifests` so later spectators can audit context.
-
-## Agent Cards
-
-`--agent <name>` resolves to `.trellis/agents/<name>.md`. The card name must
-match `[A-Za-z0-9._-]+`. The default Trellis install ships three cards:
-
-- `.trellis/agents/check.md` — code-quality reviewer.
-- `.trellis/agents/implement.md` — coding worker for implementation runs.
-- `.trellis/agents/subnode.md` — bounded independent-evidence worker; its
-  `subnode.env` sibling is loaded automatically.
-
-```yaml
----
-name: check
-description: Code quality check expert.
-provider: claude
----
-```
-
-Frontmatter fields populate `spawn` defaults (provider, model, `as`); the
-markdown body becomes the worker's system-prompt role. Cards do **not**
-auto-attach task files — context must be injected explicitly per spawn (see
-below).
-
-Always inspect project cards before spawning a named agent:
-
-```bash
-ls .trellis/agents
-sed -n '1,100p' .trellis/agents/check.md
-```
-
-## Context Injection
-
-Two flags inject content into the worker's system prompt under a
-`# CONTEXT FILES` block, assembled by `context-loader`:
-
-- `--file <path>` — repeatable, glob-supported (`*`, `**`). Each match is
-  read and concatenated.
-- `--jsonl <path>` — repeatable Trellis manifest where every line is
-  `{"file":"<path>","reason":"<why>"}`. The reason is preserved as a header
-  comment above each file's content.
-
-Limits enforced by the loader:
-
-- 1 MB hard cap per file (oversize → error).
-- 200 KB per-file warning to stderr.
-- 500 KB total assembled-context warning to stderr.
-- Path-traversal jail: all resolved paths must stay under `--cwd`.
-
-Example spawning a check agent against a task directory:
-
-```bash
-TASK=.trellis/tasks/05-13-example
-trellis channel spawn cr-example --agent check --provider codex --as check-cx \
-  --file "$TASK/prd.md" \
-  --file "$TASK/design.md" \
-  --file "$TASK/implement.md" \
-  --jsonl "$TASK/check.jsonl" \
-  --cwd "$PWD" --timeout 30m
-```
-
-The `spawned` event records both the literal `files` array and any `manifests`
-expanded from `--jsonl`, so the audit trail captures whatever the worker was
-actually shown.
-
-## Names And Routing
-
-`--as` has two meanings:
-
-- `send` / `wait` / `interrupt`: speaker identity (author of the resulting event).
-- `spawn`: the worker handle that other agents address with `--to`.
-
-Use explicit names when multiple workers or providers participate in one
-channel:
-
-```bash
-trellis channel spawn cr-feature --agent check --as check-claude
-trellis channel spawn cr-feature --agent check --provider codex --as check-cx
-
-trellis channel wait cr-feature --as main \
-  --from check-claude,check-cx --kind done --all --timeout 15m
-```
-
-`--all` requires `--from` and blocks until every listed worker has produced a
-matching event; timeout exits with code **124** and prints
-`timeout: still waiting on ...` to stderr.
-
-## Soft Interrupt — `interrupt`
-
-`channel interrupt` is the cooperative redirect: it appends an `interrupt`
-event (reason `"user"`) and, where the adapter supports it, issues a
-provider-level turn interrupt with a replacement instruction. Use it when the
-worker should drop its current turn and act on new input immediately, without
-losing its session.
-
-```bash
-echo "Stop refactoring the parser — switch to fixing the failing test in src/foo.ts" \
-  | trellis channel interrupt impl-task --as dispatcher --to codex-impl --stdin
-```
-
-Flags:
-
-- `--as <agent>` **(required)** — caller identity.
-- `--to <agent>` **(required)** — target worker.
-- `--scope <project|global>` — channel scope.
-- `--stdin` / `--text-file <path>` / `[text]` — replacement instruction body.
-
-The appended event has `kind: "interrupt"` — downstream `wait` / `messages`
-filters can subscribe with `--kind interrupt` to react to redirections (e.g.
-to log the rerouting, or to gate other workers behind a coordinator's
-correction).
-
-For low-priority hints that should wait for the worker's next turn, send a
-plain tagged message instead:
-
-```bash
-echo "Check this when you reach the next turn." \
-  | trellis channel send impl-task --as dispatcher --to codex-impl \
-      --stdin --tag question
-```
-
-## Hard Interrupt — `kill` + `--resume`
-
-Use `kill` when the worker must stop **now** (e.g. runaway loop, bad
-instructions already in flight, or `interrupt` is not honored by the
-adapter). The supervisor escalates SIGTERM → 8 s grace → SIGKILL; the CLI
-writes a `killed` event when SIGKILL is needed so the event log stays
-truthful.
-
-```bash
-trellis channel kill impl-task --as codex-impl
-trellis channel spawn impl-task --as codex-impl --provider codex \
-  --resume "$(cat ~/.trellis/channels/<bucket>/impl-task/worker.session-id)"
-
-echo "STOP — new instructions: ..." \
-  | trellis channel send impl-task --as dispatcher --to codex-impl --stdin
-```
-
-`kill` flags:
-
-- `--as <agent>` **(required)** — names the worker (positional `<name>` is the channel).
-- `--scope <project|global>`.
-- `--force` — SIGKILL immediately (also kills the inner worker pid).
-
-Side effects: cleans `pid`, `worker-pid`, `config`, `spawnlock` sidecar
-files; keeps `log`, `session-id`, `thread-id` for forensics and resume.
-
-When `interrupt` will not converge, kill + `--resume` is the guaranteed
-redirection path.
-
-## Worker OOM Guard
-
-The OOM guard prevents orphaned/idle workers from accumulating and exhausting
-host resources. It runs at every `spawn` and enforces two policies per
-project bucket:
-
-- **Idle TTL** — sweep workers whose last activity is older than the
-  configured threshold (default `5m`; `0` disables).
-- **Live-worker budget** — refuse the new spawn if more than N workers are
-  already alive in the same project bucket (default `6`; `0` disables).
-
-Precedence (highest first):
-
-1. CLI flags: `--idle-timeout`, `--max-live-workers` on `spawn`.
-2. Environment variables: `TRELLIS_CHANNEL_WORKER_IDLE_TIMEOUT`,
-   `TRELLIS_CHANNEL_MAX_LIVE_WORKERS`.
-3. For `--agent subnode`, `channel.subnode` in `.trellis/config.yaml`.
-4. `.trellis/config.yaml` under `channel.worker_guard`.
-5. Built-in defaults (`5m`, `6`) for ordinary workers.
-
-Cleanup notices are written to stderr at spawn time so operators can see which
-idle workers were swept and why a new spawn was rejected. The guard does not
-touch ephemeral / `channel run` workers any differently — they are subject to
-the same idle TTL and budget.
-
-To audit durable state, use `trellis channel workers <name> --include-terminal
---json`. This is the canonical worker projection. Inspect per-channel `pid` /
-`worker-pid` sidecar files under `~/.trellis/channels/<bucket>/<channel>/` only
-when diagnosing host-local process liveness; they are not lifecycle truth.
-
-For bounded evidence workers, `channel.subnode` is a separate role-default
-section. It configures `idle_timeout`, `max_live_workers` (generated default
-`8`), `timeout`, and `warn_before` only for `spawn --agent subnode`. Explicit
-spawn flags remain one-dispatch overrides; ordinary workers retain the generic
-`worker_guard` defaults.
-
-## Worker Inbox APIs
-
-The inbox is the channel surface workers wake on. Routing is controlled by
-two knobs:
-
-- **Inbox policy** (`spawn --inbox-policy`):
-  - `explicitOnly` (default) — worker only wakes on `send --to <worker>` or
-    `interrupt --to <worker>`.
-  - `broadcastAndExplicit` — also wakes on broadcasts (`send` with no `--to`).
-- **Delivery mode** (`send --delivery-mode`):
-  - `appendOnly` — append the event regardless of worker state.
-  - `requireKnownWorker` — fail if no worker named in `--to` was ever spawned.
-  - `requireRunningWorker` — fail if the named worker is not currently alive.
-
-Stricter delivery modes prevent silent message loss when callers expect a
-running peer.
-
-Inbox-relevant subcommands:
-
-- `send <channel> [text]` — append a `message` event.
-  - `--as <agent>` **(required)** — author.
-  - `--to <agents>` — CSV; one → string, many → array; broadcast if omitted.
-  - `--stdin` / `--text-file <path>` / `[text]` — body source.
-  - `--delivery-mode <appendOnly|requireKnownWorker|requireRunningWorker>`.
-- `interrupt <channel> [text]` — soft-interrupt redirect (see above).
-- `wait <channel>` — block until matching events arrive.
-  - `--as <agent>` **(required)** — `self` for filter context.
-  - `--from <agents>` — CSV authors.
-  - `--kind <kind[,kind...]>` — CSV (OR semantics); supports `interrupt`,
-    `done`, `progress`, etc.
-  - `--to <target>` — defaults to own agent (broadcast + explicit-to-me).
-  - `--include-progress` — also wake on progress events.
-  - `--all` — require every `--from` agent to match (timeout → exit **124**).
-  - `--timeout <duration>` — `30s` / `2m` / `1h` / `1000ms`.
-- `messages <channel>` — view / filter / follow the event stream.
-  - `--follow` to tail, `--kind` / `--from` / `--to` to filter, `--raw` for
-    JSON-per-line, `--no-progress` to hide progress noise.
-
-A typical dispatcher loop:
-
-```bash
-# 1. Wake the worker.
-echo "Run the failing test and report." \
-  | trellis channel send impl-task --as dispatcher --to codex-impl --stdin \
-      --delivery-mode requireRunningWorker
-
-# 2. Block until it finishes.
-trellis channel wait impl-task --as dispatcher \
-  --from codex-impl --kind done,error --timeout 30m
-
-# 3. Read the final answer.
-trellis channel messages impl-task --from codex-impl --last 1 --raw
-```
-
-All event-emitting subcommands (`send`, `interrupt`, `post`, `context add` /
-`delete`, `title set` / `clear`, `thread rename`) print the appended event as
-a single JSON line on stdout, making the inbox layer easy to script against.

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

@@ -1,131 +0,0 @@
-# Workflows
-
-Use these patterns by intent. Prefer durable channels for multi-round work and
-`channel run` for one-shot questions.
-
-## Pattern A: Multi-round Brainstorm
-
-Use when the user says "和 codex/claude 讨论一下", "brainstorm", or "拉一个 agent
-进来一起看".
-
-```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 \
-  --file .trellis/tasks/05-XX-storage-adapter/prd.md \
-  --file .trellis/tasks/05-XX-storage-adapter/design.md \
-  --as cx-arch --timeout 30m
-
-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 --after-seq "$BARRIER" --timeout 10m
-```
-
-Do not stop after one answer. Read the answer, identify vague areas, send a
-new probe, and repeat until the result is executable.
-
-Minimum round structure:
-
-1. Direction split: should this live in an existing mechanism or a new one?
-2. MVP boundary: v1, v2, and what would force v2 back into v1.
-3. Data contract: events, schema, metadata, state source of truth, compatibility.
-4. CLI / UX contract: command names, flags, errors, defaults, ambiguity.
-5. Cross-layer risk and tests: shared helpers, drift points, release-blocking tests.
-
-Optional rounds:
-
-- Operations: logs, debugging, stuck workers, kill/restart, recovery.
-- Migration/release: breaking status, manifest, changelog, docs-site.
-- Opposition review: ask the peer agent to argue against the current plan.
-
-Every probe should request concrete file paths, commands, schema, rejected
-alternatives, and release-blocking issues. Reject hedging when a decision is
-needed.
-
-## Pattern B: Implement / Check Agent
-
-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 \
-  --jsonl "$TASK/check.jsonl" \
-  --file "$TASK/prd.md" \
-  --file "$TASK/design.md" \
-  --file "$TASK/implement.md" \
-  --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 --after-seq "$BARRIER" --timeout 15m
-trellis channel messages cr-foo --kind message --from check --tag final_answer
-```
-
-For implement work, use `--agent implement` and send an implementation brief.
-For check work, include the exact diff scope, relevant specs, and validation
-already run.
-
-## Pattern C: Parallel Reviewers
-
-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" \
-  --timeout 15m
-
-trellis channel spawn cr-feature --agent check --provider codex --as check-cx \
-  --jsonl "$TASK/check.jsonl" --file "$TASK/prd.md" --file "$TASK/design.md" \
-  --timeout 15m
-
-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 --after-seq "$BARRIER" --timeout 15m
-```
-
-`--all` means every listed worker must emit a matching event.
-
-## Pattern D: One-shot Worker
-
-```bash
-trellis channel run --provider codex --message "say hi in 3 words" --timeout 1m
-trellis channel run --agent plan --message-file /tmp/plan-question.md --timeout 10m
-```
-
-On success, `run` removes the ephemeral channel. On error/timeout/killed, it
-keeps the channel and prints the path for inspection.
-
-## Pattern E: Forum Channel
-
-Use for issue forums, topic-style feedback, release todos, agent findings, and
-internal changelogs. Read `forum.md` for the full model.
-
-## Pattern F: Take Over Existing Thread
-
-If the user gives a forum/thread name, restore context yourself:
-
-```bash
-trellis channel forum <board> --scope global
-trellis channel thread <board> <thread> --scope global --raw
-trellis channel context list <board> --scope global --thread <thread>
-trellis channel messages <board> --scope global --raw --thread <thread>
-```
-
-Output a constraint summary, not a transcript dump:
-
-- user-level problem
-- context files that affect this repo
-- current-version versus future-version requirements
-- whether current code/design satisfies it
-- next action or comment to append

package/dist/templates/common/bundled-skills/trellis-meta/references/local-architecture/multi-agent-channel.md

@@ -1,70 +0,0 @@
-# Local Multi-Agent Channel Runtime
-
-`trellis channel` is the local multi-agent collaboration runtime shipped with the Trellis CLI. It lets the main AI session spawn peer workers (Claude Code, Codex, or any agent definition under `.trellis/agents/`), exchange durable messages through an event log, and coordinate review or brainstorm loops without hand-stitching shell pipelines.
-
-This reference covers how channels are wired into the user project so an AI customizing the project knows what to edit. For runtime usage (commands, forum/thread patterns, worker spawn flags), defer to the bundled `trellis-channel` capability skill.
-
-## Local System Model
-
-The channel runtime spans three local surfaces:
-
-1. **Storage layer** in the user's home directory: durable event logs and worker state files.
-2. **Agent definitions** inside the project at `.trellis/agents/`: platform-agnostic role cards consumed by `trellis channel spawn --agent <name>`.
-3. **Project configuration** in `.trellis/config.yaml`: worker guard thresholds and other channel knobs.
-
-## Core Paths
-
-| Path | Purpose |
-| --- | --- |
-| `~/.trellis/channels/<project>/<channel>/events.jsonl` | Per-channel append-only event log. Sequence-locked, replay-safe. |
-| `~/.trellis/channels/<project>/<channel>/<channel>.lock` | Channel-level write lock. |
-| `~/.trellis/channels/<project>/<channel>/<worker>.spawnlock` | Per-worker spawn lock used by the OOM guard. |
-| `~/.trellis/channels/<project>/<channel>/.seq` | Sequence sidecar for ordered event assignment. |
-| `~/.trellis/channels/_global/<channel>/...` | Channels created with `--scope global`. The project bucket is replaced by a shared key. |
-| `.trellis/agents/check.md` | Default Check Agent role definition consumed by `--agent check`. |
-| `.trellis/agents/implement.md` | Default Implement Agent role definition consumed by `--agent implement`. |
-| `.trellis/config.yaml` (`channel.*` block) | Worker guard thresholds and channel defaults. |
-
-The project bucket name is derived from the absolute project path (slashes flattened, non-alphanumerics replaced with `-`), matching Claude Code's `~/.claude/projects/<sanitized-cwd>/` convention. Override with `TRELLIS_CHANNEL_ROOT` (root directory) or `TRELLIS_CHANNEL_PROJECT` (bucket name) for testing or sandboxing.
-
-## When To Reach For The Channel Runtime
-
-Channels are heavier than a single Bash call or a one-shot sub-agent dispatch. Use them only when at least one of these conditions holds:
-
-- The work needs **two or more agents to converse** through more than one turn (cross-AI brainstorm, peer review, dispatcher + worker).
-- A worker should run as a **peer process** that the main session can interrupt, watch progress on, or wait for asynchronously.
-- The conversation must be **durable and inspectable** later (forum/thread channels, issue boards, decision trails).
-- Multiple workers must **share an event log** so each can see what the others reported.
-
-Prefer cheaper primitives when:
-
-- A single-shot Bash command or single Agent tool call is enough -> do that directly.
-- The user just needs a static review against a file -> read the file and reply inline.
-- The need is "remember what we discussed last week" -> use `trellis mem` instead of a channel.
-
-## Customization Points
-
-| Need | Edit location |
-| --- | --- |
-| Change default channel worker idle timeout | `channel.worker_guard.idle_timeout` in `.trellis/config.yaml`. Accepts `5m`, `30s`, etc. Set `0` to disable idle cleanup. |
-| Change live worker budget | `channel.worker_guard.max_live_workers` in `.trellis/config.yaml`. Set `0` to disable the spawn-time budget check. |
-| Override worker guard per spawn | Pass `--idle-timeout` / `--max-live-workers` on `trellis channel spawn`, or set `TRELLIS_CHANNEL_WORKER_IDLE_TIMEOUT` / `TRELLIS_CHANNEL_MAX_LIVE_WORKERS` in the environment. |
-| Tune bounded subnode dispatch defaults | Set `channel.subnode.max_live_workers`, `idle_timeout`, `timeout`, or `warn_before`. Generated defaults are `8`, `5m`, `30m`, and `5m`; explicit spawn flags and existing guard environment overrides still win. |
-| Change what the default Check or Implement worker does | Edit `.trellis/agents/check.md` or `.trellis/agents/implement.md`. These are platform-agnostic role cards; the channel runtime injects them when `--agent check|implement` is passed. |
-| Add a new role card | Drop `<name>.md` into `.trellis/agents/`. `trellis channel spawn --agent <name>` will pick it up. |
-| Relocate channel storage (CI sandbox, ephemeral runs) | Set `TRELLIS_CHANNEL_ROOT=/path/to/dir`. Channel events move with it; existing channels stay at the old root. |
-| Switch storage scope | Pass `--scope project` (default) or `--scope global` on every channel subcommand. The bucket directory changes; nothing else does. |
-
-Worker guard precedence is: CLI flag > environment variable > `channel.subnode` for `--agent subnode` > `channel.worker_guard` > built-in default. Ordinary worker defaults remain `idle_timeout: 5m` and `max_live_workers: 6`.
-
-## Relationship To Other Local Layers
-
-- **Workflow layer**: workflows that use channel dispatch (such as `channel-driven-subagent-dispatch`) instruct the main agent to call `trellis channel spawn --agent check` or `--agent implement` instead of a platform sub-agent. If `.trellis/agents/check.md` or `implement.md` is missing, `trellis workflow --template <id>` prints a non-blocking warning at install time. Restore them with `trellis update` if they are deleted by accident.
-- **Task layer**: channel workers do not own task state. The supervising main session passes the active task path through the worker inbox; the worker resolves task artifacts from disk.
-- **Spec layer**: workers read `.trellis/spec/` the same way the main session does. Channel runtime does not bypass spec context loading.
-- **Platform integration layer**: channel runtime is platform-neutral. It does not depend on `.claude/`, `.codex/`, or any other platform directory. The adapters that normalize provider output (Claude `stream-json`, Codex `app-server`) live inside the Trellis CLI binary, not in the project.
-- **Platform sub-agent files vs. channel workers**: editing `.claude/agents/trellis-implement.md` (and its peers in other platform `.X/agents/` directories) does NOT change channel-runtime worker behavior — channel workers load `.trellis/agents/<name>.md`. The platform-specific agent files are for direct sub-agent dispatch from the main AI session, not for channel-spawned workers. See `platform-files/agents.md` for the per-platform agent surface, and the `trellis-meta/SKILL.md` rule that codifies this split.
-
-## Runtime Usage
-
-For command syntax, forum/thread patterns, worker handles, progress inspection, and the `--kind done` / `--kind turn_finished` dispatcher wait pattern, load the bundled `trellis-channel` skill (auto-installed under each platform's skills directory after `trellis init` / `trellis update`). This reference only covers the local file layout and customization knobs; it does not duplicate command syntax that may change between releases.

package/dist/templates/common/bundled-skills/trellis-research-record/SKILL.md

@@ -1,14 +0,0 @@
----
-name: trellis-research-record
-description: Record task-relevant verified research, audit, or review findings in active Trellis task artifacts. Use when material facts, candidates, uncertainty, or a decision basis should persist; do not use for routine navigation or transient observations.
----
-
-# Trellis Research Record
-
-Keep task-relevant evidence in the active task rather than only in session context.
-
-1. Confirm the active task, actual modification target, and authoritative source.
-2. Before changing scope or ending the work, record verified facts with evidence locators in that task's `research/` directory or another appropriate task artifact. Keep candidates and uncertainty separate from facts, and state one bounded next action when needed.
-3. A subnode report is a candidate artifact. The coordinator verifies it and records the resulting conclusion; this Skill does not accept reports, alter task lifecycle, create a handoff, or create a second ledger.
-
-Do not create a record for routine navigation, temporary tool output, waits, compaction, or observations with no task value.