trellis-herbivore 0.1.0

package/dist/migrations/manifests/0.5.0-beta.1.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.1",
+  "description": "First published 0.5 beta — same code as the beta.0 dev cut, bumped at release time",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Release:**\n- First @beta-tagged release of the 0.5 skill-first architecture. Code is identical to the 0.5.0-beta.0 dev cut; the bump happens automatically via `pnpm version prerelease --preid beta` inside `pnpm release:beta`, so beta.0 was never published to npm.\n\nAll migration work (command→skill for 5 skills, safe-file-delete for 6 legacy commands + multi-agent + iFlow + Ralph Loop, breaking-change gate, worktree backup exclusion) is defined in the 0.5.0-beta.0 manifest and applies when upgrading from 0.4.x.",
+  "migrations": [],
+  "notes": "If upgrading from 0.4.x: run `trellis update --migrate` — the gate in the 0.5.0-beta.0 manifest requires the flag. See the 0.5.0-beta.0 changelog for the full migration story."
+}

package/dist/migrations/manifests/0.5.0-beta.10.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.10",
+  "description": "Hotfix: three bugs in `trellis update --migrate` / `init-context` (codex/kiro skill `trellis-` prefix, `.agents/` detection, `--platform` threading) + migrationGuide back-fill on 0.5.0-beta.0 / 0.5.0-beta.5 + docs-site changelog pre-release gate.",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Bug fixes (no --migrate required):**\n- fix(cli_adapter): codex/kiro branches of `get_trellis_command_path` now emit the `trellis-` prefix introduced by 0.5.0-beta.0 — previously `init-context` wrote `check.jsonl` paths that 404'd on codex/kiro projects.\n- fix(detect_platform): removed `.agents/` from the config-dir enumeration (it's a shared cross-platform skills layer consumed by Codex / Amp / Cline / Kimi / Warp, not a platform directory). Added a guarded codex fallback so repos whose only signal is `.agents/skills/trellis-*` still identify as codex.\n- feat(init-context): `task.py init-context` accepts `--platform`; skill/command templates thread it end-to-end via `{{CLI_FLAG}}` instead of re-detecting from the filesystem at runtime.\n- fix(migrations): back-filled `migrationGuide` + `aiInstructions` on 0.5.0-beta.0 (0.4→0.5 narrative: skill renames, retired commands, multi-agent-pipeline removal, iFlow drop, task.json schema cleanup) and 0.5.0-beta.5 (sub-agent rename). Both breaking releases previously shipped with no guide, so `update --migrate` PRDs fell back to 0.3/0.4 historical content.\n- feat(release): `create-manifest.js` now rejects `breaking && recommendMigrate && !migrationGuide`; `release:beta` / `release:rc` / `release:promote` pre-flight `check-docs-changelog.js` to catch missing docs-site changelog pages before tagging.",
+  "migrations": [],
+  "notes": "Pure runtime/tooling bug fix; no user file operations. Upgrading from beta.9: if you ran `trellis update --migrate` before beta.10 on a codex/kiro project, the `check.jsonl` generated then points at pre-prefix skill paths — re-run `task.py init-context <task-dir> <type> --platform <platform>` or recreate the task. If on 0.4.x, the migration task PRD now contains the real 0.4→0.5 guide."
+}

package/dist/migrations/manifests/0.5.0-beta.11.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.11",
+  "description": "Hotfix: SessionStart hook crashed on PEP 604 annotations when the AI CLI spawned python3 as system 3.9 even though the user's shell had 3.11. Also relaxes declared Python floor from 3.10 to 3.9. Not breaking; no --migrate required.",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Bug Fixes:**\n- fix(hooks): `shared-hooks/session-start.py` and `shared-hooks/inject-subagent-context.py` now declare `from __future__ import annotations`. Without it, PEP 604 union annotations (`str | None`, `dict | None`) were evaluated at function-def time and crashed on `python3` < 3.10 with `TypeError: unsupported operand type(s) for |: 'type' and 'NoneType'`. Observed in the field on macOS where the user's shell `python3` was 3.11 (homebrew) but the AI CLI host resolved the hook subprocess `python3` via a minimal PATH, falling back to `/usr/bin/python3` → system 3.9. `statusline.py` and the copilot/codex copies of session-start already had the future import; the two canonical `shared-hooks/*.py` files were the outliers.\n\n**Improvements:**\n- feat(cli): Python version floor relaxed from 3.10 to 3.9. `packages/cli/src/commands/init.ts` now sets `MIN_MINOR = 9` — matches macOS Ventura/Sonoma/Sequoia system `python3` (3.9.6). Trellis-distributed Python templates were verified via full package-import matrix on CPython 3.8–3.13 (30/30 pass). Python 3.8 is not supported (EOL 2024-10; declaring support would incur CVE backport obligations).\n- docs: `README.md`, `docs-site/quickstart.mdx` (+ zh), `docs-site/start/install-and-first-task.mdx` (+ zh), `docs-site/advanced/multi-platform.mdx` (+ zh), and `docs-site/advanced/appendix-f.mdx` (+ zh) all updated to `Python 3.9+`. New Prerequisites table on the Quickstart page lists Node / Python / git floors up front (previously undocumented on the docs site).",
+  "migrations": [],
+  "notes": "Existing projects: run `trellis update` to pick up the two patched hook files. Hashes match pristine installs; locally-modified copies land on the standard confirm prompt. If you're on Python 3.9 and saw the `Python ≥ 3.10` warning during past `trellis init` runs, the warning is gone — no action needed."
+}

package/dist/migrations/manifests/0.5.0-beta.12.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.12",
+  "description": "Phase 1.3 is now agent-curated. `task.py init-context` removed; `task.py create` seeds `implement.jsonl` / `check.jsonl` with a self-describing `_example` line on sub-agent-capable platforms, and the AI fills real spec + research entries per workflow.md Phase 1.3. Session-start READY gate across 4 implementations now requires at least one curated entry, not just file existence. Skill Routing tables split per-platform — sub-agent platforms no longer see `trellis-before-dev`. Fixes `trellis update` backup-phase stack-overflow on repos with nested `.backup-*/.opencode/node_modules`. Release pipeline hardened with manifest-continuity guard + guards against overwriting published manifests. Restored the missing `0.5.0-beta.10.json` manifest. Not breaking; existing tasks keep working.",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Behavioral changes:**\n- feat(workflow): Phase 1.3 rewritten from \"run `task.py init-context`\" to \"AI curates jsonl directly\". New rule — `implement.jsonl` / `check.jsonl` hold spec + research paths only, never code paths. `task.py create` seeds each jsonl with one self-describing `{\"_example\": \"...\"}` line on sub-agent-capable platforms (Claude / Cursor / Codex / Kiro / Gemini / OpenCode / Qoder / CodeBuddy / Droid / Copilot). Agent-less platforms (Kilo / Antigravity / Windsurf) skip seeding and load specs via the `trellis-before-dev` skill as before.\n- fix(task.py): `init-context` subcommand removed. Invoking it exits 2 with a deprecation message pointing at workflow.md Phase 1.3 and `task.py add-context` for ergonomic editing. `cmd_init_context`, `get_implement_backend`, `get_implement_frontend`, `get_check_context` deleted from `common/task_context.py`.\n- fix(session-start): READY detection requires at least one jsonl row with a `file` key. Seed-only jsonl now surfaces as `Status: PLANNING (Phase 1.3)` with Next-Action pointing at the curate step. Applied across all four implementations: `shared-hooks/session-start.py` (Claude / Cursor / Kiro / CodeBuddy / Droid / Gemini / Qoder), `codex/hooks/session-start.py`, `copilot/hooks/session-start.py`, `opencode/plugins/session-start.js`.\n- feat(workflow.md): Skill Routing and DO-NOT-skip tables split into `[Claude Code, Cursor, OpenCode, Codex, Kiro, Gemini, Qoder, CodeBuddy, Copilot, Droid]` and `[Kilo, Antigravity, Windsurf]` variants. Sub-agent platforms no longer surface `trellis-before-dev` in the routing table — the main-thread job on those platforms is to dispatch `trellis-implement`, not load spec skills.\n- feat(shared-hooks): `inject-subagent-context.py:read_jsonl_entries` emits a single stderr warning when the jsonl is missing or contains only seed rows, so Class-1 platforms have a clear debug signal instead of silent empty injection.\n- feat(configurators/shared.ts): Class-2 pull-based prelude (Codex / Copilot / Gemini / Qoder) now teaches sub-agents to skip rows without a `file` field and fall back to prd.md + self-discovered specs when the jsonl has only a seed row.\n\n**Bug fixes:**\n- fix(update): `trellis update` no longer crashes with `Maximum call stack size exceeded` during the backup phase. Root cause: `createFullBackup` descended into old `.trellis/.backup-*/` directories (which could contain nested `.opencode/node_modules` — tens of thousands of files), and `collectAllFiles` combined recursion with `files.push(...largeArray)` spread. Rewritten as iterative stack traversal. Exclude dirs (`node_modules`, `.backup-*`, etc.) are now skipped at scan time instead of copy time. Symlinks and Windows NTFS junctions are skipped to avoid cyclic scans. `BACKUP_EXCLUDE_PATTERNS` matching normalizes backslashes to forward slashes so Windows paths like `.claude\\worktrees\\...` match. `DEBUG=1` / `TRELLIS_DEBUG=1` env now prints full stack traces for easier triage. See `update.ts:683-790`, `cli/index.ts:130`.\n\n**Release tooling:**\n- feat(release): new `packages/cli/scripts/check-manifest-continuity.js` — pre-release gate that queries npm for published versions and fails non-zero if any lacks a local manifest. Hooked into `release` / `release:minor` / `release:major` / `release:beta` / `release:rc` / `release:promote` before `pnpm test`. Historical gaps (0.1.x pre-manifest era, 0.2.1–0.2.11 old monolith, 0.3.10-beta.0 first public prerelease) whitelisted in `KNOWN_GAPS`; the list documents that it should not be extended.\n- feat(create-manifest): `create-manifest.js` now refuses to (re)write a manifest whose version is already on npm — even with `force: true`. Interactive mode also checks npm before the existing local-file overwrite prompt.\n- fix(migrations): restored `packages/cli/src/migrations/manifests/0.5.0-beta.10.json`. Reconstructed from the actual tarball content (three bug fixes + migrationGuide back-fills + docs-site changelog pre-release gate), not the earlier Qoder-split draft that was consolidated into beta.9 before publish. `KNOWN_GAPS` shrinks from 22 to 21.\n\n**Test fixes:**\n- fix(test): `update.integration.test.ts` and `init-joiner.integration.test.ts` `vi.mock(\"node:child_process\")` now conditionally returns `\"Python 3.11.12\"` on `python3 --version` calls instead of blanket `\"\"`. Resolves 36 pre-existing failures caused by `requireSupportedPython` throwing `Python command not found` in vitest child processes. Full suite now 664/664 green.\n- test(update): regression coverage for the backup-phase crash added in `test/commands/update-internals.test.ts` and `test/commands/update.integration.test.ts`.",
+  "migrations": [],
+  "notes": "**Existing tasks**: keep working. Consumers (hook, prelude, validate, list-context) all skip rows without a `file` key, so old `_example` seed rows are naturally ignored. If your existing `implement.jsonl` / `check.jsonl` were generated by 0.5.0-beta.11-and-earlier `init-context` and point at paths that don't exist in your monorepo spec layout (typical when `package = backend | frontend` instead of `package = business-domain`), re-curate per workflow.md Phase 1.3 — or leave them alone and the sub-agent falls back to prd.md + stderr warning.\n\n**AI instructions (for an agent helping a user through this change)**:\n\n1. Do NOT run `task.py init-context` — it's gone. If you see the deprecation error (exit 2), read `.trellis/workflow.md` Phase 1.3 and curate jsonl directly.\n2. When creating a new task, `task.py create` already seeds empty-but-valid jsonl on sub-agent platforms. Your Phase 1.3 job: open `implement.jsonl` / `check.jsonl`, replace the `_example` line with real `{\"file\": ..., \"reason\": ...}` entries pointing at `.trellis/spec/**/*.md` and `{TASK_DIR}/research/**/*.md` that apply to the task. Never list code files — those are read during Phase 2 implement, not pre-registered.\n3. Run `python3 ./.trellis/scripts/get_context.py --mode packages` to discover which spec layers are available in the current project.\n4. If the session-start breadcrumb shows `Status: PLANNING (Phase 1.3)` right after task.py create, that is correct — it means curation hasn't happened yet. Proceed with Phase 1.3 per workflow.md. The READY status only appears after at least one curated entry is written.\n5. If a user's old task was created under 0.5.0-beta.11 with `init-context` output pointing at `.trellis/spec/<pkg>/backend/index.md` and those paths don't exist on their monorepo, don't try to 'fix' the old script — re-curate the jsonl to the paths that actually exist. Use the `add-context` command or edit the file directly.\n\n**Workaround for users still on a pre-beta.12 published CLI who hit the `Maximum call stack size exceeded` crash during `trellis update`**: `rm -rf .trellis/.backup-*` drops the nested-node_modules source of the overflow, then re-run `trellis update` (still on the old CLI) to complete the upgrade, OR upgrade to beta.12 first via `npm i -g @mindfoldhq/trellis@0.5.0-beta.12` and run update from there."
+}

package/dist/migrations/manifests/0.5.0-beta.13.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.13",
+  "description": "Patch follow-up to beta.12: `task.py start` now transitions `task.json` status planning → in_progress (previously stuck at planning even after the user explicitly started work). Codex sub-agent instructions for seed-row handling — written into the dogfood root during beta.11's init-context-removal but never backported into `packages/cli/src/templates/codex/agents/` — are now in the packaged templates, so fresh `trellis init` / `trellis update` finally ship Phase 1.3 fallback guidance to Codex users. `.codex/config.toml` documents the `features.codex_hooks` user-level opt-in. No src/ changes; `trellis update` is a straight content refresh.",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Bug Fixes:**\n- fix(task.py): `task.py start <task>` transitions `task.json` status `planning` → `in_progress`. Previously `cmd_start` only wrote `.current-task` and ran `after_start` hooks — user explicitly started work but status stayed at `planning`. Non-`planning` statuses (`in_progress`, `review`, `completed`) are preserved on resume so replays don't clobber progress. See `packages/cli/src/templates/trellis/scripts/task.py:cmd_start`.\n- fix(templates/codex): backport the \"Required: Load Trellis Context First\" preamble into packaged `codex/agents/trellis-check.toml` and `codex/agents/trellis-implement.toml`. The block teaches Codex sub-agents to (1) skip `{\"_example\": ...}` seed rows and (2) fall back to prd-only context plus self-discovered specs via `get_context.py --mode packages` when the jsonl has no curated entries. It was edited into the dogfood root during beta.11 init-context-removal but never propagated into `packages/cli/src/templates/codex/agents/`, so up through beta.12 Codex users on fresh `trellis init` / `trellis update` got agent prompts missing the Phase 1.3 fallback path and the agents blocked on seed-only jsonl instead of proceeding with prd.md + spec judgment.\n\n**Docs:**\n- docs(codex): `.codex/config.toml` documents the `[features] codex_hooks = true` user-level opt-in. Project-scoped config cannot enable `features.*`; without the flag, `hooks.json` is silently ignored and Trellis context injection never runs — previously this looked like a bug. The old `shell_environment_policy` stub (dead config unrelated to Trellis) is removed in favor of the opt-in hint.",
+  "migrations": [],
+  "notes": "Pure content refresh. Existing tasks and jsonl files keep working untouched. After `trellis update`, `task.py start <existing-task-in-planning>` will now write `in_progress` on the first invocation — no action needed from you. Codex users who manually edited their `.codex/agents/trellis-*.toml` will see the Required-Context preamble added on update; `trellis update` prompts per-file when hashes drift."
+}

package/dist/migrations/manifests/0.5.0-beta.14.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.14",
+  "description": "Patch follow-up to beta.13: SessionStart hooks now emit a one-shot `<first-reply-notice>` block so the first visible assistant reply announces that Trellis context has been injected (proof-of-load for noisy or summarized hosts). READY-state breadcrumbs across shared/opencode/codex/copilot hooks + `trellis/workflow.md` replace the soft \"Continue with implement or check\" wording with an explicit \"Next required action: dispatch `trellis-implement` … do NOT edit code in the main session\" directive, closing a loophole where agent-capable sessions would still hand-edit code in the main thread. Windows statusline no longer crashes on typed stdout/stderr streams: `sys.stdout.detach() + TextIOWrapper(...)` is replaced with `reconfigure(encoding='utf-8', errors='replace')`. No src/ runtime-code changes outside templates; `trellis update` is a straight content refresh.",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Enhancements:**\n- feat(hooks): SessionStart emits a one-shot `<first-reply-notice>` block instructing the model to open its first visible reply with one short Chinese sentence confirming Trellis context has been injected (workflow, task status, developer identity, git status, active tasks, spec index). Applied to `shared-hooks/session-start.py`, `codex/hooks/session-start.py`, `opencode/plugins/session-start.js`. Notice is explicitly one-shot — not repeated on later turns in the same session. Closes the visibility gap on hosts that collapse or summarize hook output.\n- feat(hooks): READY-state breadcrumbs now say \"Next required action: dispatch `trellis-implement` per Phase 2.1. For agent-capable platforms, do NOT edit code in the main session. After implementation, dispatch `trellis-check` per Phase 2.2 before reporting completion.\" Replaces the old \"Next: Continue with implement or check\" wording that let the main thread silently hand-edit code. Applied uniformly across `shared-hooks/session-start.py` + `inject-workflow-state.py`, `opencode/plugins/session-start.js` + `inject-workflow-state.js`, `codex/hooks/session-start.py`, `copilot/hooks/session-start.py`, and the `[workflow-state:in_progress]` block in `trellis/workflow.md`. `<ready>` directive also drops the \"ask whether to continue\" prompt in favor of \"execute its Next required action\".\n\n**Bug Fixes:**\n- fix(statusline): Windows UTF-8 setup replaces `sys.stdout = io.TextIOWrapper(sys.stdout.detach(), encoding='utf-8')` with `stream.reconfigure(encoding='utf-8', errors='replace')`. The old pattern crashed on hosts that wrap stdout/stderr with typed streams (Copilot / certain Codex environments) because `detach()` is not available on typed wrappers. `reconfigure` is the supported API on Python 3.7+ text streams and is a no-op when unavailable. Fix applied to `shared-hooks/statusline.py`.\n- fix(hooks): Codex and Copilot SessionStart hooks now invoke a shared `configure_project_encoding(project_dir)` helper before emitting JSON, loading `.trellis/scripts/common.configure_encoding()` when present. Prevents stray mojibake in hook stdout on Windows Codex/Copilot runs that haven't already wrapped stdout.\n- docs(copilot): `copilot/hooks/session-start.py` docstring + `systemMessage` text now state plainly that GitHub Copilot currently ignores `sessionStart` hook output. The JSON shape is kept for protocol parity and future host support, but users should rely on `UserPromptSubmit` breadcrumbs and hook logs for Copilot today.",
+  "migrations": [],
+  "notes": "Pure content refresh. Existing tasks, jsonl files, and `.current-task` are preserved. After `trellis update`, fresh sessions across Claude Code / Codex / Copilot / OpenCode will prepend a one-line Chinese confirmation of SessionStart context on the first assistant reply, and the main thread will no longer be nudged to hand-edit code when a task is READY. Windows statusline stops crashing on Copilot/Codex typed stdout. No action needed beyond `trellis update`."
+}

package/dist/migrations/manifests/0.5.0-beta.15.json

@@ -0,0 +1,116 @@
+{
+  "version": "0.5.0-beta.15",
+  "description": "Task runtime and platform compatibility update. `task.py start/current/finish` now use `.trellis/.runtime/sessions/<context-key>.json`; `.trellis/.current-task` is no longer the active-task fallback. `workflow.md` and hook breadcrumbs now allow trivial turns and explicit current-turn overrides to skip Trellis task creation or sub-agent dispatch. Claude Code, Codex, Cursor, OpenCode, and Pi handle shell session identity for `task.py`: Codex uses native `CODEX_SESSION_ID` / `CODEX_THREAD_ID`, while the other hosts propagate `TRELLIS_CONTEXT_ID` through host-specific bridges. Cursor matches `Task|Subagent` and parses native custom-agent payloads. Pi resolves context keys from session manager, environment, transcript path, or process fallback. Template registry downloads support private Git-backed registries through local Git credentials. Claude Code statusLine is no longer installed by default for new projects, while existing Claude Code statusLine files and settings are preserved on update. The manifest also includes 10 hash-verified `safe-file-delete` entries for orphan shared hooks.",
+  "breaking": true,
+  "recommendMigrate": false,
+  "changelog": "**Behavior Changes:**\n- feat(task): `task.py start/current/finish` read and write `.trellis/.runtime/sessions/<context-key>.json`. `.trellis/.current-task` is no longer used as the active-task fallback. `task.py start` exits with a clear error when no session identity is available. `task.py finish` deletes the resolved session file. `task.py archive` deletes session files that still point at the archived task before moving it.\n- feat(init): bootstrap and joiner onboarding tasks no longer write `.trellis/.current-task`; generated PRDs tell the AI to start the task from a session that provides Trellis session identity.\n- feat(workflow): `workflow.md` and hook fallback breadcrumbs now treat no-task trigger words as task-creation signals instead of mandatory creation. Task creation is not required for trivial turns when all three hold: zero file writes, one-reply answer, and no research beyond reading 1-2 repo files. Explicit current-turn phrases such as `skip trellis`, `no task`, `just do it`, `跳过 trellis`, `别走流程`, and `先别建任务` skip task creation for that turn.\n- feat(workflow): `in_progress` breadcrumbs keep `trellis-implement` / `trellis-check` as the default, but explicit current-turn requests such as `do it inline`, `main session 写就行`, and `不用 sub-agent` allow main-session implementation.\n\n**Platform Integration:**\n- feat(hooks): Claude Code writes `TRELLIS_CONTEXT_ID` through `CLAUDE_ENV_FILE`; Codex command environments are supported through `CODEX_SESSION_ID` / Codex Desktop `CODEX_THREAD_ID`; Cursor adds `beforeShellExecution` tickets under `.trellis/.runtime/cursor-shell/`; OpenCode prefixes Bash commands with `TRELLIS_CONTEXT_ID`; Pi injects the same value into Bash and nested `pi --mode json` runs.\n- docs(platforms): GitHub Copilot uses a platform-specific SessionStart hook; Gemini/Qoder/CodeBuddy/Droid/Kiro use shared hook input or platform env; Kilo/Antigravity/Windsurf have no hook integration; `.agents/skills` consumers rely on host-provided prelude/env. All groups share `.trellis/.runtime/sessions/`, while beta.15 adds shell-command handling for Claude Code, Codex, Cursor, OpenCode, and Pi.\n- feat(cursor): Cursor `hooks.json` matches `Task|Subagent`. `inject-subagent-context.py` parses native custom-agent payloads including `{ custom: { name } }` and `{ type: { case: \"custom\", value: { name } } }`.\n- feat(pi): Pi Agent resolves context keys from `TRELLIS_CONTEXT_ID`, `sessionManager.getSessionId()`, `PI_SESSION_ID` / `PI_SESSIONID`, transcript path, or process fallback, then reads active tasks from `.trellis/.runtime/sessions/`.\n- feat(workflow): `workflow-state` breadcrumbs use exact agent names (`trellis-implement`, `trellis-check`, `trellis-research`) and document explicit per-turn override phrases.\n\n**Bug Fixes:**\n- fix(registry): Template registry downloads support private Git-backed registries through local Git credentials. Self-hosted GitLab / GitHub Enterprise and SSH registry sources use Git to read `index.json` and copy template directories, and classify auth, missing-ref, missing-path, invalid-json, and network failures separately instead of falling through to direct-download mode.\n- fix(opencode): OpenCode recognizes `OPENCODE_RUN_ID` and strips the `trellis-` prefix before matching sub-agent names, preserving `implement.jsonl` / `check.jsonl` injection for renamed agents.\n- fix(claude): Claude Code statusLine is no longer installed by default for new projects. Existing `.claude/hooks/statusline.py` files are preserved on update, and an existing `.claude/settings.json` `statusLine` entry is carried forward instead of being forced out.\n- fix(cli): `writeSharedHooks` and `collectSharedHooks` use `SHARED_HOOKS_BY_PLATFORM`. The manifest removes 10 orphan shared-hook files through hash-verified `safe-file-delete` entries; locally modified files are preserved.\n\n**Docs:**\n- docs(beta): docs-site beta pages and `v0.5.0-beta.15` changelog document session-scoped task state, workflow policy relaxation, per-platform session identity behavior, Pi Agent, Cursor hook behavior, native Git worktrees, private Git-backed template registries, Claude Code statusLine defaults, existing statusLine preservation, and the current `continue` / `finish-work` command flow.",
+  "migrations": [
+    {
+      "type": "safe-file-delete",
+      "from": ".cursor/hooks/statusline.py",
+      "description": "Removed: Cursor has no statusLine event; shared-hooks/statusline.py was never invoked.",
+      "allowed_hashes": [
+        "87c01ee786ca9e1f25b591f0ed67564cd430586d57516d5b6fc57c34b6e7a3ec",
+        "c92c0020a0c60308437b66f024a244303e708519c97089cf654ceddc144f7435",
+        "b9b0a39a486643f2b78ecb3c757459182a6326ea070ba34a49887e23adc40bbb"
+      ]
+    },
+    {
+      "type": "safe-file-delete",
+      "from": ".codex/hooks/statusline.py",
+      "description": "Removed: Codex has no statusLine event; shared-hooks/statusline.py was never invoked.",
+      "allowed_hashes": [
+        "87c01ee786ca9e1f25b591f0ed67564cd430586d57516d5b6fc57c34b6e7a3ec",
+        "c92c0020a0c60308437b66f024a244303e708519c97089cf654ceddc144f7435",
+        "b9b0a39a486643f2b78ecb3c757459182a6326ea070ba34a49887e23adc40bbb"
+      ]
+    },
+    {
+      "type": "safe-file-delete",
+      "from": ".gemini/hooks/statusline.py",
+      "description": "Removed: Gemini CLI has no statusLine event; shared-hooks/statusline.py was never invoked.",
+      "allowed_hashes": [
+        "87c01ee786ca9e1f25b591f0ed67564cd430586d57516d5b6fc57c34b6e7a3ec",
+        "c92c0020a0c60308437b66f024a244303e708519c97089cf654ceddc144f7435",
+        "b9b0a39a486643f2b78ecb3c757459182a6326ea070ba34a49887e23adc40bbb"
+      ]
+    },
+    {
+      "type": "safe-file-delete",
+      "from": ".qoder/hooks/statusline.py",
+      "description": "Removed: Qoder has no statusLine event; shared-hooks/statusline.py was never invoked.",
+      "allowed_hashes": [
+        "87c01ee786ca9e1f25b591f0ed67564cd430586d57516d5b6fc57c34b6e7a3ec",
+        "c92c0020a0c60308437b66f024a244303e708519c97089cf654ceddc144f7435",
+        "b9b0a39a486643f2b78ecb3c757459182a6326ea070ba34a49887e23adc40bbb"
+      ]
+    },
+    {
+      "type": "safe-file-delete",
+      "from": ".github/copilot/hooks/statusline.py",
+      "description": "Removed: GitHub Copilot has no statusLine event; shared-hooks/statusline.py was never invoked.",
+      "allowed_hashes": [
+        "87c01ee786ca9e1f25b591f0ed67564cd430586d57516d5b6fc57c34b6e7a3ec",
+        "c92c0020a0c60308437b66f024a244303e708519c97089cf654ceddc144f7435",
+        "b9b0a39a486643f2b78ecb3c757459182a6326ea070ba34a49887e23adc40bbb"
+      ]
+    },
+    {
+      "type": "safe-file-delete",
+      "from": ".codebuddy/hooks/statusline.py",
+      "description": "Removed: CodeBuddy has no statusLine event; shared-hooks/statusline.py was never invoked.",
+      "allowed_hashes": [
+        "87c01ee786ca9e1f25b591f0ed67564cd430586d57516d5b6fc57c34b6e7a3ec",
+        "c92c0020a0c60308437b66f024a244303e708519c97089cf654ceddc144f7435",
+        "b9b0a39a486643f2b78ecb3c757459182a6326ea070ba34a49887e23adc40bbb"
+      ]
+    },
+    {
+      "type": "safe-file-delete",
+      "from": ".factory/hooks/statusline.py",
+      "description": "Removed: Factory Droid has no statusLine event; shared-hooks/statusline.py was never invoked.",
+      "allowed_hashes": [
+        "87c01ee786ca9e1f25b591f0ed67564cd430586d57516d5b6fc57c34b6e7a3ec",
+        "c92c0020a0c60308437b66f024a244303e708519c97089cf654ceddc144f7435",
+        "b9b0a39a486643f2b78ecb3c757459182a6326ea070ba34a49887e23adc40bbb"
+      ]
+    },
+    {
+      "type": "safe-file-delete",
+      "from": ".kiro/hooks/statusline.py",
+      "description": "Removed: Kiro has no statusLine event; shared-hooks/statusline.py was never invoked.",
+      "allowed_hashes": [
+        "87c01ee786ca9e1f25b591f0ed67564cd430586d57516d5b6fc57c34b6e7a3ec",
+        "c92c0020a0c60308437b66f024a244303e708519c97089cf654ceddc144f7435",
+        "b9b0a39a486643f2b78ecb3c757459182a6326ea070ba34a49887e23adc40bbb"
+      ]
+    },
+    {
+      "type": "safe-file-delete",
+      "from": ".kiro/hooks/session-start.py",
+      "description": "Removed: Kiro supports only `agentSpawn`; there is no SessionStart event to trigger this script.",
+      "allowed_hashes": [
+        "26b52ad72259316aa5adc8068d0df2a002273d5eda659ac3c71f3f5ecd9ebd08",
+        "ddd59c6fc5e6fa8c8535d6ac375ecaad60f15b87abc6dfc279007e610c636dd8",
+        "597409062bed8f9977750fa6262bb997facce7d8377d3482d4bcb2054e19c491",
+        "6cf36cffba3cf4a3caff99606d9fc9dde07fa4f74b7227aeb08d3de00ced7ca2",
+        "373f2f41c5506982cef1049f0203ca9e442c8074f54880aa021f037c0b9300b0",
+        "bc2026f6b1c195432e1126e1388d11fccec2df7a72010d0daa9fb6af76f683dd",
+        "cf355e44ace5e9b7c7d9a416462d4057a6cff9d5905b8db1839e6e4c892cfd13",
+        "a1b0db7c264da8e7abeb378a16ba8132b99b9918c9546627137d69427108f4b6",
+        "a0256292a2ade20728d71d2ea9a7ce866f6955efe034934eaecbf820244e9ad8"
+      ]
+    },
+    {
+      "type": "safe-file-delete",
+      "from": ".kiro/hooks/inject-workflow-state.py",
+      "description": "Removed: Kiro supports only `agentSpawn`; there is no UserPromptSubmit event to trigger this script.",
+      "allowed_hashes": [
+        "281939a51a62467a5dd73947fdec7143d0e936b4b64b5224ce0484186eb5b018",
+        "4231e4e0d52c9b05d66a215c870db30a876201a51350e5191953418ca4ec4637",
+        "50bd086d40654b9fe8cb902d2f321ce06e39b6d4020a6e9aa49154cc371bdb16"
+      ]
+    }
+  ],
+  "notes": "Behavior change: `.trellis/.current-task` is preserved but ignored by active-task resolution. Existing task directories and jsonl files remain valid. `task.py start` now requires session identity from the host or `TRELLIS_CONTEXT_ID`. Run `trellis update` to refresh hooks and templates. The 10 shared-hook cleanup migrations are hash-verified; locally modified hook files are preserved with a warning. Claude Code statusLine is not installed by default for new projects, and existing Claude Code statusLine files/settings are preserved on update."
+}

package/dist/migrations/manifests/0.5.0-beta.16.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.16",
+  "description": "Compatibility patch for template hash portability, task archive inputs, and Claude Code statusLine upgrades. Template hashes now use POSIX keys and LF-normalized content, `task.py archive` accepts the same task directory inputs as the other task commands, and existing Claude Code statusLine installs are preserved during `trellis update`. No migration actions are required.",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Bug Fixes:**\n- fix(cli): Normalize `.trellis/.template-hashes.json` keys to POSIX paths and compute template hashes from LF-normalized content. The hash file now uses a `{ \"__version\": 2, \"hashes\": { ... } }` envelope; legacy flat-format hash files are discarded and regenerated from installed templates.\n- fix(scripts): Align `task.py archive` with other task-directory subcommands. `archive` now accepts a bare task name, `.trellis/tasks/<slug>` relative path, or absolute task path.\n- fix(claude): Preserve existing Claude Code statusLine installs during update. `trellis update` no longer safe-deletes `.claude/hooks/statusline.py`, and if `.claude/settings.json` already has a top-level `statusLine` entry, the updated settings template carries that entry forward.\n\n**Behavior:**\n- New Trellis installs still do not create `.claude/hooks/statusline.py` and do not add `statusLine` to `.claude/settings.json`.\n- Non-Claude orphan `statusline.py` files remain hash-verified safe-delete cleanup targets because those platforms have no `statusLine` event.\n- No `--migrate` gate is required for this patch; the hash file is derived state and is regenerated by normal init/update hashing.",
+  "migrations": [],
+  "notes": "Run `trellis update` to receive the compatibility fixes. Legacy `.trellis/.template-hashes.json` files are regenerated under schema v2, `task.py archive` accepts task names or task paths, and existing Claude Code statusLine files/settings are preserved. No manual migration is required."
+}

package/dist/migrations/manifests/0.5.0-beta.17.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.17",
+  "description": "Beta.17 installs trellis-meta as a bundled built-in skill, hardens Pi subagent launch/configuration, removes promotional init completion output, and improves subagent context wiring. No migration actions are required.",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Enhancements:**\n- feat(cli): Install `trellis-meta` as a bundled multi-file built-in skill under every platform skill root. The shared template pipeline now supports `packages/cli/src/templates/common/bundled-skills/<skill>/` through `getBundledSkillTemplates()`, `resolveBundledSkills()`, `collectSkillTemplates()`, and `writeSkills()`.\n- feat(pi): Harden the Trellis Pi `subagent` launcher. The generated extension resolves `@mariozechner/pi-coding-agent/dist/cli.js` when possible, runs child Pi with `--mode text -p --no-session`, sends delegated prompts through stdin, bounds stdout/stderr buffers, forwards `TRELLIS_CONTEXT_ID`, and wires `AbortSignal` cancellation.\n- feat(pi): Add Pi subagent model/thinking configuration. `.pi/agents/*.md` frontmatter may provide `model`, `thinking`, and `fallbackModels`, while the `subagent` tool accepts per-call `model` and `thinking` overrides and maps them to `--model <model[:thinking]>` or `--thinking <level>`.\n- docs(workflow): Clarify that `task.py create --slug <auto>` receives a slug without a date prefix because the script adds the `MM-DD-` directory prefix automatically.\n\n**Behavior Changes:**\n- chore(init): Remove promotional completion output from `trellis init`; completion output now stays focused on generated files and next actions.\n\n**Bug Fixes:**\n- fix(trellis): Improve subagent context wiring across local platform files. Cursor native custom-agent payloads are parsed from `Task`/`Subagent` tool input, workflow-state breadcrumbs require exact `trellis-implement` / `trellis-check` / `trellis-research` agent names, and Claude/Cursor/Codex hook paths preserve session identity for later shell or subagent context loading.",
+  "migrations": [],
+  "notes": "Run `trellis update` to receive the bundled `trellis-meta` skill, Pi subagent launcher/config updates, init output cleanup, and subagent context wiring fixes. No `--migrate` flag is required."
+}

package/dist/migrations/manifests/0.5.0-beta.18.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.18",
+  "description": "Beta.18 redesigns the Phase 3 workflow: Phase 3.4 adds an AI-driven batched commit step, and `/trellis:finish-work` becomes a 4-step survey + archive + journal flow that refuses to run on a dirty working tree. Also fixes parent-task progress regression on child archive, hash-tracks AGENTS.md during update, and supports OpenCode PowerShell context injection on Windows. No migration actions are required.",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Enhancements:**\n- feat(workflow): Add `Phase 3.4 Commit changes` to `workflow.md`. The AI inspects `git status --porcelain`, learns commit-message style from `git log --oneline -5`, classifies dirty files into AI-edited-this-session vs unrecognized groups, drafts a batched commit plan, and commits per batch only after one-shot user confirmation. Rejecting the plan exits to manual mode without a flag. Wrap-up reminder renumbers from 3.4 to 3.5. The `[workflow-state:completed]` breadcrumb (and the four hook fallbacks in `inject-workflow-state.py`/`.js`) now direct users at `/trellis:finish-work` instead of the legacy `task.py finish` + `task.py archive` sequence.\n- feat(skills): Rewrite `/trellis:finish-work` as a 4-step survey + archive + journal flow. Step 1 runs `get_context.py --mode record` to print active tasks, git status, and recent commits — when other completed-but-unarchived tasks surface, the AI prompts once for one-shot batch cleanup. Step 2 runs `git status --porcelain` (excluding `.trellis/workspace/` and `.trellis/tasks/`) and bails out if anything else is dirty. Step 3 archives the active task plus any cleanup tasks the user confirmed in Step 1. Step 4 records the session journal using hashes from Step 1's recent-commits output. Code commits belong in Phase 3.4, not here. The common skill template uses `{{CMD_REF:finish-work}}` so `cmdRefPrefix` resolves correctly per platform (`/trellis:` for Claude/OpenCode, `$` for Codex, `/trellis-` for Cursor).\n\n**Bug Fixes:**\n- fix(scripts): Stop pruning archived children from a parent task's `children` list. `cmd_archive` previously removed the child name on archive, which made `children_progress` shrink both numerator and denominator (e.g. `[1/6 done]` → `[0/5 done]`, hiding completed work). The list now stays intact; `children_progress` treats children missing from active statuses as completed (cmd_archive sets `status=completed` before moving the dir).\n- fix(update): Hash-track `AGENTS.md` during `trellis update`. Pre-0.5.0-beta.18 projects wrote `AGENTS.md` without recording its template hash, which would surface as a false \"modified by you\" conflict on update. The new `<!-- TRELLIS:START -->` / `<!-- TRELLIS:END -->` managed-block replacement plus a legacy pristine-hash allowlist (`LEGACY_UNTRACKED_AGENTS_MD_BLOCK_HASHES`) lets old untouched projects update cleanly while still preserving any user customizations outside the block.\n- fix(opencode): Support PowerShell context injection in OpenCode on Windows. `inject-subagent-context.js` now emits `$env:TRELLIS_CONTEXT_ID = '...'; ` instead of the POSIX `export` form when the host platform is `win32`, and the explicit-assignment dedup detector matches both POSIX and PowerShell forms.\n\n**Internal:**\n- test: Add `test/setup.ts` registered via `setupFiles` in `vitest.config.ts`. It deletes `process.env.TRELLIS_CONTEXT_ID` and `process.env.OPENCODE_RUN_ID` at vitest process start so the OpenCode resolver tests no longer pick up a Claude/OpenCode host-session env that would hijack the platform-input-derived contextKey.\n- docs(spec): Document the parent-child `children` list invariant in `script-conventions.md` and the host-shell env-leak isolation pattern in `unit-test/conventions.md`.",
+  "migrations": [],
+  "notes": "Run `trellis update` to receive the Phase 3.4 commit step, the rewritten `/trellis:finish-work` skill, the parent-child progress fix, AGENTS.md hash tracking, and OpenCode PowerShell support. No `--migrate` flag is required."
+}

package/dist/migrations/manifests/0.5.0-beta.19.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.19",
+  "description": "Beta.19 hot-fixes a regression introduced in beta.18: when an AGENTS.md exists without `<!-- TRELLIS:START -->` / `<!-- TRELLIS:END -->` markers (pre-beta.18 projects, or hand-authored files), `trellis update` was clobbering the user's content with the bare Trellis template. The managed block now appends to the existing file instead of overwriting it. No migration actions are required.",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Bug Fixes:**\n- fix(update): Preserve user content in `AGENTS.md` when the file has no `<!-- TRELLIS:START -->` / `<!-- TRELLIS:END -->` markers. Beta.18's managed-block replacement returned the bare template as a fallback when no markers were found, which silently replaced the user's hand-written `AGENTS.md` content during `trellis update`. The fallback now appends the canonical managed block to the existing content instead, so user-authored sections are preserved verbatim. Existing tests cover the legacy-pristine and modified-managed-block cases; the new `#4d preserves user AGENTS.md without TRELLIS markers by appending the managed block` case covers the hand-authored-without-markers path.",
+  "migrations": [],
+  "notes": "Run `trellis update` to receive the AGENTS.md preservation fix. No `--migrate` flag is required. If beta.18 already overwrote your `AGENTS.md`, restore the file from git history and re-run `trellis update` on beta.19 to merge in the managed block while keeping your content."
+}

package/dist/migrations/manifests/0.5.0-beta.2.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.2",
+  "description": "Bug fix: [b] Backup-rename in the migration confirm prompt now writes an inline .backup copy instead of silently behaving identically to [r] Rename anyway",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Bug Fixes:**\n- fix(update): `backup-rename` actually writes inline `.backup` copy (25a3337) — previously `[b] Backup original, then proceed` and `[r] Rename anyway` executed the exact same code path. Both relied on the full project snapshot at `.trellis/.backup-<timestamp>/`, making the prompt's promise of \"keeps a .backup copy\" misleading. Now `backup-rename` writes `<new-path>.backup` (for rename) or `<from>.backup` (for delete) alongside the normal operation so users can diff/merge their customizations against the new template without digging through the full snapshot. Prompt labels updated to state the concrete artifact path.",
+  "migrations": [],
+  "notes": "Pure CLI-side bug fix — no project file migrations. Run `trellis update` to sync to the new CLI behavior."
+}

package/dist/migrations/manifests/0.5.0-beta.3.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.3",
+  "description": "Bug fix: update.skip no longer leaves breaking-release upgrades half-migrated — skip is bypassed for safe-file-delete and template writes when manifest is breaking + recommendMigrate + user passed --migrate",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Bug Fixes:**\n- fix(update): bypass `update.skip` across safe-file-delete + template writes for breaking releases. Previously, projects with paths under `update.skip` in `.trellis/config.yaml` would upgrade inconsistently when crossing a breaking release: `rename` migrations already ignored skip, but `safe-file-delete` and template writes honored it. Result: users ended up half-migrated — old deprecated files persisted under skip-protected paths, new commands like `continue.md` never landed, and every future update re-flagged the same mess.\n\n  Now when the current upgrade spans a manifest with `breaking: true + recommendMigrate: true` and the user passed `--migrate`, `update.skip` is bypassed for all three operations: rename / safe-file-delete / template writes. User customizations are still guarded by the per-file `Modified by you` confirm prompt at write time, and the hash check in `allowed_hashes` is still the ultimate safety net for safe-file-delete (user-modified files stay put with a `skip-modified` warning regardless).\n\n  Non-breaking updates continue to respect `update.skip` as before — only breaking releases trigger the bypass.\n\n  A new yellow `⚠ update.skip BYPASSED` notice appears in the breaking-change warning block so users aren't surprised when skip-protected files get cleaned up during the migration.",
+  "migrations": [],
+  "notes": "Pure CLI-side bug fix — no project file migrations. If upgrading from 0.4.x with an `update.skip` in config.yaml, this release finally lets the 0.5.0-beta.0 breaking migration complete cleanly: run `trellis update --migrate` to finish any half-migrated state from prior 0.5 beta upgrades."
+}

package/dist/migrations/manifests/0.5.0-beta.4.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.4",
+  "description": "Critical bug fix: workflow.md is now included in update's template set — previously excluded, causing 0.4.x → 0.5 upgrades to silently leave workflow.md at the old structure that 0.5's get_context.py / hooks can't parse",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Bug Fixes:**\n- fix(update): include workflow.md in `collectTemplateFiles` — `.trellis/workflow.md` was explicitly excluded from `trellis update`'s template set on the assumption that it's \"user-customizable documentation, written once at init\". That assumption broke in 0.5.0 because workflow.md started carrying **script-parsed structure**: `## Phase Index` (read by `get_context.py --mode phase`), `## Phase 1/2/3` headings (inlined into SessionStart payload), and `[workflow-state:STATUS]` tag blocks (consumed by the per-turn breadcrumb hook). Users upgrading from 0.4.x → 0.5 ended up with `get_context.py` reporting `Phase Index section not found in workflow.md` and the `/continue` command unable to route. workflow.md is now included in the normal update flow — unmodified copies auto-update, user-modified copies go through the existing \"Modified by you\" confirm prompt with diff. `workspace/index.md` stays excluded (it's runtime-appended by `add_session.py`, no script-parsed structure).",
+  "migrations": [],
+  "notes": "Pure CLI-side bug fix — no project file migrations. If you upgraded to any 0.5.0-beta.0..beta.3 and see `Phase Index section not found in workflow.md` from `get_context.py`, this release fixes it: run `trellis update --migrate`. Unmodified workflow.md auto-updates; if you customized it, you'll see the \"Modified by you\" confirm prompt with a diff — pick `Overwrite` to get the new 0.5.0 structure, or merge your edits manually into the new template."
+}

package/dist/migrations/manifests/0.5.0-beta.5.json

@@ -0,0 +1,222 @@
+{
+  "version": "0.5.0-beta.5",
+  "description": "Sub-agent rename + remove model: opus from all agent templates. Prefixes implement/check/research with trellis- to prevent accidental invocation by user's own agents or the main agent's description heuristics. Drops hardcoded model: opus from agent frontmatter across all 10 platforms — this caused Cursor users real cost pain because Cursor mapped opus to Claude Opus (~5x Sonnet pricing).",
+  "breaking": true,
+  "recommendMigrate": true,
+  "changelog": "**Breaking Changes:**\n- rename(agents): `implement` / `check` / `research` sub-agents are now `trellis-implement` / `trellis-check` / `trellis-research` across all 10 platforms (claude, cursor, opencode, codex, kiro, gemini, qoder, codebuddy, copilot, droid). Generic names were colliding with user-defined agents and being matched by the main agent's description heuristics on some platforms. Prefixing with `trellis-` makes them unambiguously Trellis sub-agents. `workflow.md`, copilot start prompt, `shared-hooks/inject-subagent-context.py`, and configurator detection all updated to use the new names.\n\n**Bug Fixes:**\n- fix(agents): drop `model: opus` from all 18 markdown agent frontmatters + the example `Task()` calls in `copilot/prompts/start.prompt.md`. On Claude Code this merely hardcoded Opus for all sub-agent runs (ignoring user preference); on Cursor it actively mapped to Claude Opus billing at ~5x Sonnet cost and surprised users; on Gemini/Droid/Codebuddy/Qoder `opus` isn't even a valid model identifier. Agents now inherit whatever model the user configured for their platform.",
+  "migrationGuide": "## Sub-Agent Rename: `implement` / `check` / `research` → `trellis-*`\n\nbeta.5 renames the three core sub-agents to add a `trellis-` prefix across all 10 agent-capable platforms (Claude, Cursor, OpenCode, Codex, Kiro, Gemini, Qoder, CodeBuddy, Copilot, Droid). The generic names (`implement`, `check`, `research`) were colliding with user-defined agents in some setups.\n\n### What changes\n\n| Old name | New name |\n|---|---|\n| `implement` | `trellis-implement` |\n| `check` | `trellis-check` |\n| `research` | `trellis-research` |\n\nPaths per platform:\n\n- **Claude / OpenCode / Cursor / etc.**: `.<platform>/agents/implement.md` → `.<platform>/agents/trellis-implement.md`\n- **Codex**: `.codex/agents/implement.toml` → `.codex/agents/trellis-implement.toml`\n- **Kiro**: `.kiro/agents/implement.json` → `.kiro/agents/trellis-implement.json`\n\n### Side-effect: removed `model: opus` from agent templates\n\nAgent YAML frontmatter no longer hardcodes a model. Falls back to whatever the platform default is. If you pinned opus explicitly for a reason (budget, performance), re-add `model: opus` to your local agent files after migrate.\n\n### How to upgrade\n\n```bash\ntrellis update --migrate\n```\n\n30 rename entries run. Unmodified agent files are renamed silently; customized ones (e.g. you tweaked the agent prompt) land on the standard `Modified by you` confirm prompt — pressing Enter (backup-rename) is safe.\n\n### What to check after migrate\n\n1. **Any code that spawns agents by name** — shell scripts, CI jobs, or other automation calling `Task(subagent_type=\"implement\")` must update to `Task(subagent_type=\"trellis-implement\")`.\n2. **Aliases / hot keys** — if you had a keyboard shortcut or prompt alias that referenced `implement` / `check` / `research`, update it.\n3. **Model pin** — if you customized `model: opus` in agent frontmatter, re-add it. Trellis no longer pins a model by default.",
+  "aiInstructions": "When helping a user migrate to 0.5.0-beta.5:\n\n1. **Grep for bare agent names in user code**: look for `Task(subagent_type=\"implement\"|\"check\"|\"research\")` in any .md / .ts / .py / shell files. Rename each to the `trellis-` prefixed version.\n\n2. **Check agent customizations**: diff the user's `.<platform>/agents/{implement,check,research}.*` against the new `trellis-*` templates. If they had custom content, help merge it into the new file.\n\n3. **Model pinning**: if their agent frontmatter had `model: opus` and they still want it pinned, re-add it after migrate. beta.5 removes the default pin in favor of platform-default.\n\n4. **Run migrate**: `trellis update --migrate`. Hash-verified renames — pristine files renamed silently, customized files land on the confirm prompt (Enter = backup-rename is safe).\n\n5. **Verify clean second run**: after migrate, running `trellis update` again should report \"Already up to date!\". Any diff indicates a rename that didn't complete (user chose skip on a modified file).",
+  "migrations": [
+    {
+      "type": "rename",
+      "from": ".claude/agents/implement.md",
+      "to": ".claude/agents/trellis-implement.md",
+      "description": "v0.5.0-beta.5: prefix claude sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".claude/agents/check.md",
+      "to": ".claude/agents/trellis-check.md",
+      "description": "v0.5.0-beta.5: prefix claude sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".claude/agents/research.md",
+      "to": ".claude/agents/trellis-research.md",
+      "description": "v0.5.0-beta.5: prefix claude sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".cursor/agents/implement.md",
+      "to": ".cursor/agents/trellis-implement.md",
+      "description": "v0.5.0-beta.5: prefix cursor sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".cursor/agents/check.md",
+      "to": ".cursor/agents/trellis-check.md",
+      "description": "v0.5.0-beta.5: prefix cursor sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".cursor/agents/research.md",
+      "to": ".cursor/agents/trellis-research.md",
+      "description": "v0.5.0-beta.5: prefix cursor sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".opencode/agents/implement.md",
+      "to": ".opencode/agents/trellis-implement.md",
+      "description": "v0.5.0-beta.5: prefix opencode sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".opencode/agents/check.md",
+      "to": ".opencode/agents/trellis-check.md",
+      "description": "v0.5.0-beta.5: prefix opencode sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".opencode/agents/research.md",
+      "to": ".opencode/agents/trellis-research.md",
+      "description": "v0.5.0-beta.5: prefix opencode sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".codex/agents/implement.toml",
+      "to": ".codex/agents/trellis-implement.toml",
+      "description": "v0.5.0-beta.5: prefix codex sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".codex/agents/check.toml",
+      "to": ".codex/agents/trellis-check.toml",
+      "description": "v0.5.0-beta.5: prefix codex sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".codex/agents/research.toml",
+      "to": ".codex/agents/trellis-research.toml",
+      "description": "v0.5.0-beta.5: prefix codex sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".kiro/agents/implement.json",
+      "to": ".kiro/agents/trellis-implement.json",
+      "description": "v0.5.0-beta.5: prefix kiro sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".kiro/agents/check.json",
+      "to": ".kiro/agents/trellis-check.json",
+      "description": "v0.5.0-beta.5: prefix kiro sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".kiro/agents/research.json",
+      "to": ".kiro/agents/trellis-research.json",
+      "description": "v0.5.0-beta.5: prefix kiro sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".gemini/agents/implement.md",
+      "to": ".gemini/agents/trellis-implement.md",
+      "description": "v0.5.0-beta.5: prefix gemini sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".gemini/agents/check.md",
+      "to": ".gemini/agents/trellis-check.md",
+      "description": "v0.5.0-beta.5: prefix gemini sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".gemini/agents/research.md",
+      "to": ".gemini/agents/trellis-research.md",
+      "description": "v0.5.0-beta.5: prefix gemini sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".qoder/agents/implement.md",
+      "to": ".qoder/agents/trellis-implement.md",
+      "description": "v0.5.0-beta.5: prefix qoder sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".qoder/agents/check.md",
+      "to": ".qoder/agents/trellis-check.md",
+      "description": "v0.5.0-beta.5: prefix qoder sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".qoder/agents/research.md",
+      "to": ".qoder/agents/trellis-research.md",
+      "description": "v0.5.0-beta.5: prefix qoder sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".codebuddy/agents/implement.md",
+      "to": ".codebuddy/agents/trellis-implement.md",
+      "description": "v0.5.0-beta.5: prefix codebuddy sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".codebuddy/agents/check.md",
+      "to": ".codebuddy/agents/trellis-check.md",
+      "description": "v0.5.0-beta.5: prefix codebuddy sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".codebuddy/agents/research.md",
+      "to": ".codebuddy/agents/trellis-research.md",
+      "description": "v0.5.0-beta.5: prefix codebuddy sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".github/agents/implement.agent.md",
+      "to": ".github/agents/trellis-implement.agent.md",
+      "description": "v0.5.0-beta.5: prefix copilot sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".github/agents/check.agent.md",
+      "to": ".github/agents/trellis-check.agent.md",
+      "description": "v0.5.0-beta.5: prefix copilot sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".github/agents/research.agent.md",
+      "to": ".github/agents/trellis-research.agent.md",
+      "description": "v0.5.0-beta.5: prefix copilot sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".factory/droids/implement.md",
+      "to": ".factory/droids/trellis-implement.md",
+      "description": "v0.5.0-beta.5: prefix droid sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".factory/droids/check.md",
+      "to": ".factory/droids/trellis-check.md",
+      "description": "v0.5.0-beta.5: prefix droid sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    },
+    {
+      "type": "rename",
+      "from": ".factory/droids/research.md",
+      "to": ".factory/droids/trellis-research.md",
+      "description": "v0.5.0-beta.5: prefix droid sub-agent with trellis- to prevent accidental invocation",
+      "reason": "Generic names like 'implement'/'check'/'research' can collide with the user's own agent definitions or get picked up by the main agent's description heuristics. Prefixing with 'trellis-' makes them explicit Trellis agents."
+    }
+  ],
+  "notes": "This is a breaking rename for sub-agent invocation. The migration is automatic for unmodified agent files (hash-matched via .trellis/.template-hashes.json). If you customized an agent, you'll see the usual `Modified by you` confirm prompt with diff — pick `[1] Overwrite` to adopt the new name, or `[3] Skip` if you've built your own workflow on the old names (in which case you must update `workflow.md`, any skill prompts, and hook constants yourself).\n\n`update.skip` is BYPASSED for this release (breaking + recommendMigrate both true, invoked with `--migrate`) to prevent a half-migrated state where workflow.md points to `trellis-implement` but your `.claude/agents/` still has `implement.md`.\n\nAction required: run `trellis update --migrate`."
+}

package/dist/migrations/manifests/0.5.0-beta.6.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.6",
+  "description": "Fix codex trellis-check agent: change from read-only to workspace-write, rewrite developer_instructions to match other platforms' self-fix behavior per workflow.md contract.",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Bug Fixes:**\n- fix(codex): `trellis-check.toml` was shipped with `sandbox_mode = \"read-only\"` and 'Read-only Trellis reviewer' framing, which directly contradicted `workflow.md` (the check agent is supposed to auto-fix issues it finds — all other platforms' check agents have Write+Edit tools). Codex users running `trellis-check` could report findings but not fix them, forcing a manual roundtrip through the main agent. Changed to `sandbox_mode = \"workspace-write\"` and rewrote developer_instructions to instruct self-fix + re-run lint/type-check until green, matching the behavior contract of every other platform.",
+  "migrations": [],
+  "notes": "Pure template-content fix for codex users. No path migrations — `trellis update` will flag `.codex/agents/trellis-check.toml` as a template update and either auto-update (if unmodified) or prompt for confirm (if you customized it)."
+}

package/dist/migrations/manifests/0.5.0-beta.7.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.7",
+  "description": "Fix opencode plugin loader incompatibility with OpenCode 1.2.x. Plugins shipped `export default { id, server: async (...) => hooks }` object shape; OpenCode iterates `Object.entries(mod)` and calls each export as a function (`packages/opencode/src/plugin/index.ts:90 — for ([_, fn] of Object.entries(mod)) await fn(input)`), which crashes with `TypeError: fn is not a function`. Fixed by changing all 3 plugins to the current factory-function shape: `export default async (input) => hooks`.",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Bug Fixes:**\n- fix(opencode): plugins now use the factory-function export shape (`export default async ({ directory, client }) => hooks`) that OpenCode 1.2.x requires. The previous `{ id, server }` object shape crashed OpenCode on startup with `TypeError: fn3 is not a function. (In 'fn3(input)', 'fn3' is an instance of Object)` at `src/plugin/index.ts:90:28`, because OpenCode 1.2.x iterates every module export with `Object.entries(mod)` and calls each one as a function (`for ([_, fn] of Object.entries(mod)) await fn(input)`). The `server:` field was never unwrapped by the runtime. Affects all 3 plugins: `inject-subagent-context.js`, `inject-workflow-state.js`, `session-start.js`.\n  Users on any trellis version that configured opencode — including 0.4.x stable — were affected as soon as they updated opencode to 1.2.x. Upgrade to this version to restore opencode startup.",
+  "migrations": [],
+  "notes": "Pure template-content fix for opencode users. No path migrations. `trellis update` auto-updates the 3 plugin files (unmodified copies) or prompts for confirm with diff (if you customized them)."
+}

package/dist/migrations/manifests/0.5.0-beta.8.json

@@ -0,0 +1,9 @@
+{
+  "version": "0.5.0-beta.8",
+  "description": "Two Windows/opencode-user bug fixes: (1) add collectTemplates for opencode so `trellis update` actually delivers opencode plugin/agent/lib changes (was the only platform with no update tracking); (2) pin CLAUDE_BASH_MAINTAIN_PROJECT_WORKING_DIR=1 in .claude/settings.json so Bash tool cwd changes don't leak into hook invocations (fixes Windows ENOENT on hook paths after cd).",
+  "breaking": false,
+  "recommendMigrate": false,
+  "changelog": "**Bug Fixes:**\n- fix(update): opencode templates now participate in `trellis update` hash tracking. Before this, `packages/cli/src/configurators/index.ts:184` had `opencode: { configure: configureOpenCode }` with no `collectTemplates` — every other configured platform (claude, cursor, codex, kiro, gemini, qoder, codebuddy, copilot, droid) had one. Result: when beta.7 fixed the opencode plugin factory-function shape, upgraders running `trellis update` would see every other platform update but `.opencode/plugins/*.js` remain untouched — still crashing with `TypeError: fn3 is not a function`. Any future opencode-side change had the same fate. Fixed by adding `collectOpenCodeTemplates()` that walks the opencode template directory and enumerates agents, plugins, lib, package.json plus common commands/skills. `configureOpenCode` was refactored to use the same enumeration, guaranteeing init and update produce byte-identical file sets.\n- fix(claude): `.claude/settings.json` now pins `CLAUDE_BASH_MAINTAIN_PROJECT_WORKING_DIR=1` in its `env` block. Without this, a user who runs `cd frontend/` via Bash tool leaves cwd stuck in `frontend/`, and the next UserPromptSubmit hook (which resolves `python .claude/hooks/inject-workflow-state.py` relative to cwd) crashes on Windows with `[Errno 2] No such file or directory` because `.claude/` is at the real project root one level up. The env-var approach is read by Claude Code internally — works identically on Windows / macOS / Linux, doesn't depend on shell variable expansion (the alternative `$CLAUDE_PROJECT_DIR` approach is broken on Windows cmd/PowerShell per CC issue #6023).",
+  "migrations": [],
+  "notes": "If you're on any beta < 0.5.0-beta.7 with opencode configured, upgrading auto-updates the 3 plugin files + agents + lib + package.json to current templates (hash-matched). If you customized `.claude/settings.json`, you'll get the standard 'Modified by you' confirm prompt — pick `[1] Overwrite` to adopt the new env block, or `[3] Skip` and manually add `\"env\": { \"CLAUDE_BASH_MAINTAIN_PROJECT_WORKING_DIR\": \"1\" }` to your settings to get the Windows hook-path fix."
+}