Skip to content

v0.3.1

Choose a tag to compare

@fioenix fioenix released this 15 Nov 13:33
· 436 commits to main since this release
e6fc1dd

Added

  • The compaction nudge runs on Codex too: one UserPromptSubmit hook (compact_nudge.py --host codex) reads only last_token_usage.total_tokens and model_context_window of the latest token_count event in the session's transcript under the Codex home's sessions folder, and the top-level model_auto_compact_token_limit of its config.toml; the threshold is the smaller of that limit and 90% of the window, as Codex resolves it. Same bands, message, mark and FNL_COMPACT_NUDGE=off; it never blocks. Codex asks to trust the plugin's hooks again after this update.
  • merge_check.py --ci-context <name> runs the merge check as a hosted commit status: it leaves its own status out of the checks, accepts merge state BLOCKED, consults no local receipt and exits 3 while another hosted check is still running. This repository's new Merge check workflow posts it as merge-check from the default branch's code only (never checking out the pull request), on pull request changes, writers' comments, a finished Validate run and by hand (owner decision, 15/11/2026).
  • /setup instructions covers the away mode and the assignment matrix: the contract template points to afk for decisions while the user is away and keeps the lease limits in the host config, says model routing lives in the assignment matrix and machine limits in ## Machine rules and ## Heavy jobs, and the explore step offers to replace hand-written lines that restate those features with a pointer.
  • An away lease decides unknown requests instead of parking them (owner decision, 15/11/2026). When afk.py check answers unknown, the agent asks the away ladder "run this exact request?"; a rule, advisor or host attempt that settles on option 1 adds --approve-argv-json '<argv>' or --approve-paths <paths> to its log --kind decision call, and the next check of that exact request in that folder answers decided (Tier 1) once. The approval is refused unless the request is unknown, runs in a found repository with user or project settings, keeps every path inside the checkout and outside its protected paths, and has one of the allowlisted shapes: a script file of this checkout run directly or by python or node; make with plain targets and VAR=value of a plain value, never a variable naming a program, flags or a path; npm, pnpm, yarn or bun with test, run <script> or an install with no package named; python -m with a listed test or lint module (unittest, pytest, ruff, mypy and the like, never one that runs other code such as coverage run or pylint --init-hook), or pip install only of -r, -c and -e operands inside the checkout; cargo build, test and lint verbs without --config; go build, test and vet verbs with flags from a closed list and local package paths only; go mod download, tidy or verify; uv sync, poetry install, bundle install; git with a listed verb (fetch from origin by branch name, cherry-pick, revert, add, mv and the read verbs) and listed flags only; gh with a listed group and verb (pr view, checks, diff; issue create, comment, edit, close; run view, watch, rerun; workflow run; read verbs) and no other repository than the verified one in any -R or --repo form; and this install's delegated run through delegate_env.py with an approved program of a lease family. A repository's own CI script, make target, module test run or app launch no longer parks the lease.
  • /setup instructions offers a dated standing relay line for a repository whose reviewers cannot post, including security reviews while an away lease with Merge yes is live, and /setup add afk points to it after a Merge yes; this repository's CLAUDE.md "Reviews" records that clause (owner decision, 15/11/2026). Before, an away lease could not merge a pull request whose security reviewer could not post.
  • afk: a third rework round goes through the away ladder like every other stop after two rounds, instead of waiting for the user.
  • help has one short page per skill (what it does, when to use it, the command on each host and a few tips), listed under "Skill pages" in its contents reference, plus a tips page and a troubleshooting page (native Windows needs WSL, Codex hooks to trust again after an update, a stale update cache and more), each routed from help.

Changed

  • Breaking: ## Agent levels in the host config is no longer read (owner decision, 15/11/2026). The assignment matrix is the only source of levels; without a valid matrix no levels are set and routing falls to the strength table. levels_setup.py and the setup reference levels.md are removed; matrix_setup.py migrate is the only reader left, so /setup add delegation still moves the levels into the matrix. /setup check reports a leftover section as no longer read with that fix, and the update checklist gains the 0.3.1/agent-levels-retired note.
  • Breaking: the verification aliases (verification and its older fnl- name) are removed; type checks (owner decision, 15/11/2026).
  • The repository moved to finolabs/vibecode (owner decision, 15/11/2026); the plugin keeps its name, finolabs-vibecode, so commands, the catalog entry and installs are unchanged. Links, install commands and the update check's release endpoint use the new path. An install of 0.3.0 or earlier stops seeing update notices, because its update check follows no redirect: update it once by hand with the host's update command.
  • versioning ends every release with tidy: once the tag, the forge release, the -dev bump and any approved catalog pull request are done, the agent saves the handover, writes back the release's owner decisions and lessons, and renames or retires the session; tidy counts a finished release as a natural boundary (owner decision, 15/11/2026; advisory).
  • afk: git commit under a lease is Tier 1 only on a work branch; on the default branch it answers protected (owner decision, 15/11/2026).
  • ledger.py finish prints a warning when it accepts a run with --accept-unverified, or a review without --review-url; the acceptance is still recorded.
  • The afk mechanism and away decision diagrams show the third answer of afk.py check: an unknown request of an allowlisted shape goes up the decide ladder as "run this exact request?", and an approval recorded with the decision makes the next check of that exact request answer decided (Tier 1) once; the afk mechanism also shows that a merge needs a recorded MERGE OK under 15 minutes old. The PNG renderings and the README alt text are updated.
  • The request-to-merge diagram shows shape interviewing you before the router when the idea is unclear, and the implementer working in one worktree per branch while the main checkout stays on the default branch.
  • The eighth scoped exception in CLAUDE.md, PRIVACY.md ("Compaction nudge") and docs/specs/compaction-nudge.md gain a Codex clause (owner decision, 15/11/2026): the same nudge as one Codex UserPromptSubmit hook that reads only two integers of the latest token_count event in the session's own transcript under the Codex home's sessions folder and only model_auto_compact_token_limit from its config.toml. The code is compact_nudge.py --host codex, under Added.
  • afk: checks.py run --dispatch <dispatch id> is Tier 1 under a lease, so an away coordinator can write the receipt that accepting a delegated run needs; checks.py still writes it only after the whole approved list passes on a clean tree at an unmoved head (owner decision, 15/11/2026).
  • afk consumers follow the unknown-request ladder: afk names the own-worktree branch form and checks.py as test runners, the delegate route rule for an absent user defers to afk "Decide" during a lease, review-gate sends the stop after two rework rounds through Decide during a lease, the /setup add afk test-command question says other allowlisted shapes may still be decided, and the spec, README and index wording match.
  • The review-gate low-risk lane also takes a post-release record: merge_check.py --lane qualifies a pull request that changes only the Status: line of a docs/specs/release-X.Y.Z.md record from its prepared form to released; tagged vX.Y.Z on YYYY-MM-DD; ... and that release's row in docs/specs/index.md the same way, beside the changelog and the manifest version bumps. A second changed line in either file, a record without its row, a wrong version or date form, or any other spec still takes both reviewers.

Fixed

  • /setup check and /setup scan on native Windows print the one WSL line and exit 1 instead of a traceback (issue 193).
  • checks names the host config's Load limit (12 by default) for manual heavy jobs instead of a fixed 12; the setup beginner line says where the skipped steps come back, and the matrix migration's TypeSafe No branch says its plan removes no old section.
  • An approved check list (checks-approved) is bound to the full identity digest of its main checkout, so another repository whose eight-character code collides never inherits it; a record written before this release still counts until /setup add checks writes it again. The update checklist gains the missing 0.2.5 note for the compaction setting check.
  • readme_check.py hardening: a local link that resolves outside the repository fails K1 even when the file exists; file:, loopback, private and link-local URLs fail K1 (I1 for images) instead of being listed as EXTERNAL; heading and comment scanning run in linear time; override heading patterns over 200 characters are bad input; a closing fence must be at least as long as its opening one; anchors, table rows (C2) and the License line (L1) ignore HTML comments and code; a non-string manifest description fails D1 instead of crashing; and a second, unclosed <!-- after a --> on one line keeps the comment open.
  • afk: a merge pin and the merged head it allows name the repository the merge check verified, so a worktree of a fork or mirror with the same head is not removed; a full away log refuses a merge (log-unwritable) before an action is reserved; a work-tree git command checked without a working folder is protected instead of judged from the process's folder.
  • afk: a lease merges only after merge_check.py --independent printed MERGE OK for that pull request, head and repository within 15 minutes. MERGE OK writes a private receipt during the lease, and afk.py check answers merge-unchecked (Tier 3) for a gh pr merge without one; before, the merge gate's MERGE OK was agent judgment. A worktree's removal needs the head an allowed merge check pinned, so it now also follows a recorded MERGE OK (owner decision, 15/11/2026).
  • readme_check.py reads only regular files inside the repository, each at most 1 MiB, so a link to a FIFO or /dev/zero no longer hangs it or exhausts memory (exit 2 instead), and a hosts override that leaves out a manifest folder that still ships fails H1 instead of skipping that manifest's checks.
  • The host config template no longer creates the retired ## Limits section, whose bare heading parallel_slots.py check-config reports as legacy: its machine notes move to ## Machine rules, and the parallel-limit lines left under ## Heavy jobs are removed.
  • Usage metrics count the shape skill, which was missing from the skill list.
  • /setup check no longer reports a host config without ## Limits as missing a required heading: the section was retired in 0.2.5 and nothing reads it.
  • afk.py check lets an away lease follow the plugin's own branch rule and run its checks. git worktree add -b <branch> <path> [origin/<default>] is Tier 1 when the path is a new folder directly under the main checkout's .claude/worktrees (a plain name that is not protected, with no link at .claude or .claude/worktrees) and the branch passes the new-work-branch rule. This install's checks.py runs as a trusted wrapper with show, run or run --changed [--base <branch or commit>] (never usage; run --dispatch is under Changed) in a repository with user or project settings. Before, the .claude name made every worktree path Tier 3, git worktree add had no rule at all, and checks.py was not an allowed script, so an away session could neither cut a worktree nor run the approved check list.