Skip to content

v0.3.2

Latest

Choose a tag to compare

@fioenix fioenix released this 17 Nov 07:44
· 226 commits to main since this release
8ccfeb3

Added

  • afk check hook on Claude Code (tenth scoped exception, owner decisions 17/11/2026; docs/specs/afk-check-hook.md): while an away lease is live, a PreToolUse Bash hook judges each command as afk.py check does and denies every Tier 3 answer, in both modes, and every form outside the syntax it reads in full (a syntax allowlist: variables other than a plain $HOME, command substitution, xargs, find -exec, directory changes with a relative glob, glued operators and more; false denials are expected); once a lease is live any error denies as unsafe, and it never answers allow and stores no command text. The agent no longer has to call check before a Bash command on Claude Code. FNL_AFK_HOOK=off disables it.

  • tidy: when the agent asks the user to compact, it hands over the command ready to copy in its own block, on Claude Code /compact <focus> with a one-line focus naming what the summary must keep (goal, current task, open runs and pull requests, next action, handover saved), a bare /compact on Codex, and /new or /fork with the handover on Antigravity, whose /compact may not exist.

  • /setup add delegation asks which AI helpers vibecode uses as one native multiple-choice question built from the agent scan (AskUserQuestion, request_user_input on Codex, ask_question on Antigravity; numbered text choices where a host has none), then one single-choice question per role (code-review, security-review, navigator, advisor) among the chosen helpers plus "None", recommending a family other than the coordinator's. A helper left unchosen gets no matrix line, and the levels, types and model questions are asked only for the chosen ones (Quick mode gives them levels 1-5). The new read-only matrix_setup.py choices prints every helper name the matrix accepts, from ## Agents on this machine and the ~/.claude-<name> folders, with its family, presence and the coordinator mark, never a path, and says when the inventory is missing or stale and /setup scan should run first.

  • README: a warning under "Supported agents" that delegation, cross-agent reviews, advisor and the quota and context probes run other agents' CLIs headless under your own accounts (afk included), that a consumer plan may forbid that use, and that which agents run is your decision and responsibility.

  • The afk overlay (docs/specs/afk-overlay.md, owner decisions 16/11/2026): /setup add afk lists the lines of AGENTS.md, CLAUDE.md and the Spec Kit constitution that still require your approval for an action your away rules allow, and offers a local AGENTS.afk.md holding only override entries for those rules, each naming the rule it replaces. instructions_write.py writes it after its own question, keeps it out of Git, keeps earlier versions in the private state and records its SHA-256; while a lease is live the session-start hook (Claude Code, Codex) and /afk start print it only when its bytes still match and hold no control or format character other than tab and newline, else one fixed "not in force" line (the writer refuses such text too), and /afk stop says it no longer applies. In strict, afk.py check protects AGENTS.afk.md* and .specify/memory/constitution.md and the writer refuses during a lease; in open neither applies. A constitution rule is never replaced: setup only proposes the amendment. FNL_AFK_OVERLAY=off stops the printing; /setup check reports the overlay's state.

  • A recorded rework limit: - Rework limit: <2-4> under ## Reviews of host.md (default 2 when absent or invalid), asked with the review roles in /setup add delegation. review-gate stops at that limit instead of always after two rounds (advisory), and ledger.py finish refuses more rework rounds than the limit without a --reason.

  • The proof nudge (docs/specs/proof-nudge.md, owner decision 17/11/2026): on Claude Code a Stop hook adds one fixed line to the agent's context, asking it to run the targeted tests and read the output (or run checks) before reporting done, when this session committed the current head and no checks or verify_claim.py receipt names it; once per head per session, never blocking. A SessionStart hook records the session's start. FNL_PROOF_NUDGE=off turns it off.

  • compact_setup.py preview --host claude --project <repository root> writes the auto-compact window to that repository's untracked .claude/settings.local.json (this machine only), with the same preview, digest, 60-minute expiry, backup and atomic write as user scope; it refuses a path that is not the checkout root or a file in Git's index, and creates .claude only when applying.

Changed

  • Session titles follow a coordinator's work (owner request, 17/11/2026): the session-start rule and tidy "Titles" rename the session when a spec, story or large pull request it ran is done, and the merge notice after gh pr merge reminds the agent to; the help pages for tidy, setup, review-gate, troubleshooting and /setup check describe the 0.3.2 changes; CLAUDE.md "Versions" lists the docs every user-facing pull request updates.

  • The README diagrams are re-rendered from their 0.3.2 sources (task lifecycle, session health, skills architecture, delegation sequence, afk mechanism, request to merge), each as the diagram alone at 2x like the others; the afk mechanism names the afk check hook on Claude Code, and request to merge says an open lease merges on its own as a strict lease with Merge yes does.

  • /setup add compaction proposes an auto-compact level instead of prescribing none (owner decision, 17/11/2026): before the token question it shows an advisory value by session kind with its reason, never preselected (about 300000 to 500000 for a coordinator on a 1M-window model, later or a fresh session per story for single-task work, about 70% to 80% of a smaller window), then asks where it applies, user scope or, on Claude Code, this repository only. The beginner path and Quick setup now ask the threshold with its own question and say that without one Claude Code's tidy nudge stays silent.

  • Breaking: afk gains two modes (owner decisions, 16/11/2026; docs/specs/afk-autonomy.md). open, the default, lets every command, path, category and merge run under a live lease except the credential floor: afk.py check answers floor (Tier 3, never approvable through Decide) for a request that changes a credential or reads, prints, copies or sends a secret or key, after splitting operators, dropping wrapper prefixes and reading inline code. Two guards are on by default in open: instructions from third-party content never grant actions (advisory), and check answers guarded for a commit on the default branch, a push to it, and every force, delete and mirror push. - Default branch: open and - Third-party instructions: open switch them off; a repository's approved mode, default-branch and third-party-instructions keys win there. - Mode: strict keeps every earlier list, category, limit and gate. A lease set up before this change, with no Mode line, is now open; add - Mode: strict to ## afk to keep the earlier rules. In open the Merge answer is ignored and optional, and /setup add afk (afk_setup.py preview --mode) writes the mode first.

  • merge_check.py --independent --fallback-family <family> under a lease whose effective mode is open (the ## afk Mode line, or the repository's approved mode; any doubt counts as strict) accepts same-family markers that carry the fallback reviewer line without quota evidence, a router-trigger limit or two models for an enforcer change, and counts a marker without that line as another family's when the configured review role for its kind names one (docs/specs/afk-autonomy.md D). A strict lease and runs outside a lease keep the earlier conditions.

  • /setup add afk asks the mode first, open recommended with one plain paragraph on what agents may do, then the two guards of open, each defaulting to guard, and for open only the apps and the lease hours; strict keeps every earlier question. A repository's own away rules ask its mode and guards first, and the repository settings preview shows Mode, Third-party instructions and Default branch first.

  • afk.py rules prints the afk rule table, generated from the data check reads (modes and guards, the credential floor, the default-branch guard, the strict settings, paths and rule rows, the log kinds); skills/afk/references/rules.md is that output and tests/test_afk_rules.py keeps them equal. The afk skill, its lease rules, the decision and merge-gate references point to it instead of restating rules; the skill and its lease rules shrink from 16.5 KB to 7.4 KB.

  • afk: the bare export, set and env exception of the credential floor applies only to a word cut out of a search pattern after a lone | or &; find . -exec sh -c 'a;export' ';' now answers floor. merge_check.py reads a lease as strict when its ## afk section has a key afk.py does not read or an invalid guard value.

  • The afk mechanism and away decision diagrams say they show strict and that open, the default, runs every action except the credential floor and the default-branch guard (git commit and git push only), with an advisory third-party-instructions guard and no enforced review or merge_check.py; their PNG renderings and the README alt text are updated. The README, help map and pages, and the comparison page describe the modes, the guards, the overlay, the setup mode question and the helper picker.

  • Long sections load only when needed: commit-messages "Branches" keeps a short summary and moves the full branch flow to references/branches.md; checks "Accepting someone else's work" moves to references/accepting.md; review-gate's merge step points to the worktree sweep in commit-messages "Branches" instead of repeating it.

  • delegate references/agents.md keeps what every dispatch shares and an index; each family's contract moves to references/agents/claude-code.md, codex.md, antigravity.md and zcode.md, and a dispatch reads only the routed family's file. delegate's references/ledger.md is regrouped under headings with history sentences pruned, and route.md and host-template.md drop their "since 0.x" notes; no rule changes.

  • The session-start rules carry the proof rule (a report is a claim: run the targeted tests yourself and read the output; a missing setup or credential is BLOCKED, not PASS) and the session title format and per-host mechanism, so a rename no longer loads tidy; checks is still invoked before accepting a delegated run. tidy "Context pressure" moves to references/context-pressure.md, read when the compaction nudge fires, context passes about 60% or work hands over.

  • The session-start state block: Open ledger dispatches counts this project's open records and those past budget (with a ledger.py stale hint) instead of every project on the machine, and the posting, quota and parallel-slot words list only the families the assignment matrix or ## Agents on this machine marks present (all four when neither does; a family with an open dispatch still shows).

  • Reviews route to ZCode (owner decision, 17/11/2026): review_route.py and merge_check.py --independent count ZCode as a review family, run headless in --mode plan; before, the router skipped it and an independent merge with a ZCode role failed closed. A pull request ZCode wrote does not route its reviews yet (no ZCode commit trailer is recognised).

  • The standing relay rule in CLAUDE.md and the relay line /setup instructions offers cover a security review while an away lease is live in open mode, or in strict mode with Merge yes (owner decision, 17/11/2026); before, open never matched the "Merge yes" wording.

  • Same-family security fallback as a recorded choice (owner decision, 17/11/2026): /setup add roles asks once, with a preview, whether a same-family security review may count outside an away lease when every other reviewer is out of quota, and writes - Same-family security fallback: yes|no (YYYY-MM-DD) under ## Reviews of the host config. With yes, merge_check.py --independent --fallback-family <family> runs the lease fallback's conditions outside a lease (positive out-of-quota evidence for every other present family, the exact fallback reviewer line, two models for an enforcer change), without the router-trigger condition, and its ok line says it came from the recorded choice; without it, the flag still refuses outside a lease. review-gate "Same family" and CLAUDE.md "Reviews" state the rule.

  • afk: a bare export or set cut out of a search pattern after a lone | or & now floors like a bare env, so rg 'import|export' floors (its argv is the same as an unquoted rg import|export, which prints the environment); write rg -e import -e export.

  • Breaking: the instruction-check consent moves from the legacy ## Route judgment section, whose judge line nothing read, to its own ## Instruction check section of host.md; /setup check requires the new heading, reads the consent only there and names a leftover ## Route judgment with its fix. matrix_setup.py migrate moves the line (only on or off and its date) and removes the old section, with the matrix conversion or on its own beside an existing matrix; until you run it the instruction check is off.

  • status runs ledger.py stale for this repository on every run, not only when open shows long-overdue records, and offers the one stale --close --digest command it prints; closing stays your step.

  • advisor picks its family from the assignment matrix: the helper holding the advisor role, else the first route_pick.py pick --kind advisor candidate of another family, else a contrasting family; it no longer proposes a fixed Claude, Codex or Antigravity Argon list. The committee picks its second member the same way.

  • The model-invocable skill descriptions are at most 320 characters each (5,306 to 3,912 characters always loaded), leading with the action and keeping every trigger case.

  • CLAUDE.md "Checks before committing": run the test modules scripts/select_tests.py --base origin/main lists, at most two per command, instead of the full suite; the full suite runs in CI and before a release tag (owner decision, 17/11/2026).

Removed

  • Breaking: the 22 fnl- skill aliases (skills/fnl-<name>/) are removed (owner decision, 16/11/2026); type the current name instead: /fnl-advisor → /advisor, /fnl-afk → /afk, /fnl-ask → /help, /fnl-brb → /afk, /fnl-checks → /checks, /fnl-coding-router → /coding-router, /fnl-commit-messages → /commit-messages, /fnl-delegate → /delegate, /fnl-gtg → /pause, /fnl-handoff → /handoff, /fnl-help → /help, /fnl-open-source-review → /open-source-review, /fnl-pause → /pause, /fnl-plugin-packaging → /plugin-packaging, /fnl-restore-point → /restore-point, /fnl-review-gate → /review-gate, /fnl-security-review-gate → /security-review-gate, /fnl-session-hygiene → /tidy, /fnl-setup → /setup, /fnl-status → /status, /fnl-update → /update, /fnl-versioning → /versioning. Instruction files that still name an old fnl- skill point at nothing: /setup check lists each one with its new name. The fnl-review and fnl-router markers keep their names, so reviews already posted on open pull requests still count; usage metrics recorded under an old skill name still count under the new one.
  • Breaking: the three agents lose the prefix too (owner decision, 16/11/2026): fnl-reviewer → reviewer, fnl-security-reviewer → security-reviewer, fnl-navigator → navigator. On Claude Code start them as finolabs-vibecode:reviewer, finolabs-vibecode:security-reviewer and finolabs-vibecode:navigator; a brief, instruction file or host config that names an old agent must use the new name. Usage metrics record the new names, and agent events stored under an old name count under the new one. On Claude Code and Antigravity the aliases go away with the update; on Codex they stay until the plugin is refreshed.
  • coding-router no longer asks the configured judge for the depth, the Spec Kit depth gate or the next activity, and references/activity-selection.md is removed: judge.py has no such site and no judge call was made in 247 routed tasks. The agent decides them (advisory), the depth triggers still set the depth, and the judge keeps its five sites (verification, navigator, compaction, delegation, away evaluation).

Fixed

  • afk: the credential floor now answers floor for a bare env cut out of a search pattern after a lone | or & (rg x|env): an argv cannot show whether the pipe was quoted, and unquoted the shell prints the environment. The bare export and set exception there stays, so rg 'import|export' is still Tier 1.
  • The afk overlay writer's mode() refuses a ## afk key or value that afk.py settings() refuses (an unknown key, a closed choice such as - Merge: maybe, a limit, the apps or a list), so it fails closed instead of reading such a section as open.
  • merge_check.py under an open lease folds case, spacing and compatibility forms (NFKC) before it compares a marker's Reviewer: name with the configured role, so Reviewer: Claude or Reviewer: claude no longer counts as the role's review; the check that a same-family fallback marker needs --fallback-family now covers every family, zcode included.
  • Questions follow the user's language: the rule injected at session start says to ask in the language the user is using and to translate every question, description and choice label a skill quotes, keeping command names, flags, paths and skill names unchanged; setup's interview rules open with the same point, and afk and review-gate carry the language line. Before, setup and away questions copied in English reached users who write another language.
  • afk: check answers Tier 1 for an allowed gh pr merge that passes --author-email (or -A) with one plain email address, as this repository's commit rules ask (any other value stays Tier 3); in open it answered unsafe, since the merge pin's grammar did not know the option and raised, and in strict it answered unknown. A pinned merge in open with an option the pin cannot read now records no pin instead of failing.
  • Reviews never route to a family the assignment matrix leaves out: review_route.py took only ## Agents on this machine, so a present Antigravity with no matrix line took the code and security reviews when Codex ran out of quota. With a usable matrix, only families with a matrix line are candidates.
  • merge_check.py under an open lease refuses a marker whose Reviewer: name holds a letter outside ASCII (a Cyrillic look-alike such as Сlaude) or starts with another family's name (ClaudeCode, Cl-aude), which before counted as the configured role's review. An extra matrix command named zcode<suffix> now keeps the zcode family in roles and routing (before, every extra name became claude).