[baldurpan]

Two commits:

1. chore(context): update ai-workflow to 0.26.0: tool-owned files only (skills, agents, AGENTS.md's workflow block, workflow.md, the plan template, the coder role, the per-stub *.notes.md). Nothing in it was hand-edited. New in 0.26.0: /release, parallel phase rounds in /feature-implement, and plan splitting in /feature-plan.
2. chore(context): re-onboard the stubs under ai-workflow 0.26.0: the project-owned answers, filled in by /onboard, plus one .gitignore line.

What changed in the answers

• .gitignore: adds .phase-trees/, where /feature-implement puts the checkouts for a round of phases. Without it, pnpm check fails: Biome finds each checkout's own biome.json and stops with Found a nested root configuration.
• verify.md:
  • Prepare a fresh tree (new): pnpm install --frozen-lockfile.
  • Test markers (new gate section): a git grep that fails on .only, .skip, .todo, .fails, skipIf or runIf in any test file, including untracked ones.
  • Also updated: the Prerequisites, a note on .gitignore and nested Biome configs, and the test counts.
• executors.md: the concurrency cap, kept at 3, plus a note that .phase-trees/ checkouts aren't made or removed by the worktree commands.
• tracking.md: adds How much a plan may hold (65,536-character ceiling, 500 characters per phase row). The body-ceiling section now points to it. The tracker answer is unchanged.
• release.md:
  • /release is named as what runs the Bump step, alongside a maintainer running pnpm changeset:prepare-release by hand.
  • The run history is brought up to date: see Fixed since the last update.
• git.md, stack.md: their install pointers now point at Prepare a fresh tree.

Fixed since the last update

Two problems the 0.22.0 PR (#69) reported are fixed now. release.md still described them as open:

• publish.yml has published, tagged and released v2.1.0, v2.1.1 and v2.1.2. npm serves 2.1.2.
• worker-deploy.yml: the Cloudflare secrets were set on 2026-10-03, and a manual run that day succeeded. No push has touched docs/worker/** since, so the push trigger hasn't yet been seen to succeed.

Found along the way, not fixed here

• Biome's noFocusedTests reports it.only but pnpm check still exits 0, and nothing in the recommended rules flags .skip, .todo or .fails. The new Test markers gate section covers this; biome.json is unchanged.
• release-note.yml still fails PRs that the release table says owe no note, such as a devDependency-only bump. Whether pnpm changeset:add --empty is an acceptable workaround in the meantime is still undecided.

Verification

All on 2026-10-18:

• Gates: after pnpm install --frozen-lockfile, all five commands exited 0:
  • pnpm check
  • pnpm typecheck
  • pnpm build
  • pnpm test: 1006 tests
  • pnpm docs:test: 68 tests
• Fresh tree: in a git clone --no-hardlinks copy, that one install was enough for all five, and git status --porcelain stayed empty.
• .phase-trees/: I planted a lint error, a type error and failing tests inside a full nested checkout. With the .gitignore entry, no gate saw them. Without it, pnpm check failed.
• Test markers: passes on the current tree, and fails when a .skip, .only, .todo, .fails or skipIf test is planted. It ignores .only under .phase-trees/.

This PR changes docs and config only, so it owes no release note.