What's new in rule pack 2026.11.3

Updates - released 2026-10-30 for kit 0.1.1

This pack brings a third agent into the kit. If you run opencode, the same policy that guards Claude Code and Codex now guards it as well: the shell guard, the write scan and the session ledger run inside opencode as a plugin. The rest of the pack is lessons from running agents every day, folded into the skills.

Who it helps

• You use opencode, alone or next to Claude Code or Codex, and want the same guard rails in all of them.
• Your agents keep falling into the same trap and you want each session to leave a lesson behind.
• You clean up worktrees by hand and have hit a locked folder or a refused git step.

What changed

opencode hooks

A new hooks/opencode.mjs plugin runs the shell guard, write scan and session ledger inside opencode with your existing policy. opencode has no approval prompt for plugins, so anything that would ask on Claude Code is refused with its reason, as on Codex, and you run that command yourself. Install is one small file in ~/.config/opencode/plugins.

Same decisions everywhere

The hook suite now runs every shell and write case for opencode too: 511 tests, up from 362, and Claude Code and Codex decisions are unchanged. opencode reads the project AGENTS.md the kit already generates.

Hook bypass

git config core.hooksPath <dir> is refused like the other ways to skip repository hooks, and git commit -uno or -S<keyid> no longer reads as the -n that skips them.

Learning sweep at close-out

Before its report, the session reads itself start to finish for anything that went wrong, cost rework or had to be corrected, and files each lesson in exactly one place. A trap the kit already documents that still caught the agent counts as a rule that is not landing.

Cleanup and CI

Remove a worktree from the main checkout, never from inside it; a destructive git step your harness refuses comes to you as one copy-paste block per repo instead of being retried. A later CI pass that contains your commit also ends the lane.

How to apply it

1. Apply 2026.11.1 and 2026.11.2 first if you skipped them, then back up or commit your kit folder.
2. Download the pack with your updates licence key (GET /v1/updates lists it) and follow PACK.md inside it: copy the changed files over yours, merging any you edited.
3. Using opencode: add "opencode" to hooks.engines in your policy and create the one-line plugin file shown in hooks/README.md. Keep hooks.mode at log for a few days there first.
4. Run node hooks/tests/run-tests.mjs from the kit root.