Repository navigation
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, aPreToolUseBash hook judges each command asafk.py checkdoes 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 asunsafe, and it never answers allow and stores no command text. The agent no longer has to callcheckbefore a Bash command on Claude Code.FNL_AFK_HOOK=offdisables 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/compacton Codex, and/newor/forkwith the handover on Antigravity, whose/compactmay not exist. -
/setup add delegationasks which AI helpers vibecode uses as one native multiple-choice question built from the agent scan (AskUserQuestion,request_user_inputon Codex,ask_questionon 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 themlevels 1-5). The new read-onlymatrix_setup.py choicesprints every helper name the matrix accepts, from## Agents on this machineand 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 scanshould run first. -
README: a warning under "Supported agents" that delegation, cross-agent reviews,
advisorand 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 afklists the lines ofAGENTS.md,CLAUDE.mdand the Spec Kit constitution that still require your approval for an action your away rules allow, and offers a localAGENTS.afk.mdholding only override entries for those rules, each naming the rule it replaces.instructions_write.pywrites 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 startprint 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 stopsays it no longer applies. Instrict,afk.py checkprotectsAGENTS.afk.md*and.specify/memory/constitution.mdand the writer refuses during a lease; inopenneither applies. A constitution rule is never replaced: setup only proposes the amendment.FNL_AFK_OVERLAY=offstops the printing;/setup checkreports the overlay's state. -
A recorded rework limit:
- Rework limit: <2-4>under## Reviewsofhost.md(default 2 when absent or invalid), asked with the review roles in/setup add delegation.review-gatestops at that limit instead of always after two rounds (advisory), andledger.py finishrefuses 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 aStophook adds one fixed line to the agent's context, asking it to run the targeted tests and read the output (or runchecks) before reporting done, when this session committed the current head and nochecksorverify_claim.pyreceipt names it; once per head per session, never blocking. ASessionStarthook records the session's start.FNL_PROOF_NUDGE=offturns 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.claudeonly 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 aftergh pr mergereminds the agent to; the help pages fortidy,setup,review-gate, troubleshooting and/setup checkdescribe 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 compactionproposes 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'stidynudge 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 checkanswersfloor(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 inopen: instructions from third-party content never grant actions (advisory), andcheckanswersguardedfor a commit on the default branch, a push to it, and every force, delete and mirror push.- Default branch: openand- Third-party instructions: openswitch them off; a repository's approvedmode,default-branchandthird-party-instructionskeys win there.- Mode: strictkeeps every earlier list, category, limit and gate. A lease set up before this change, with noModeline, is nowopen; add- Mode: strictto## afkto keep the earlier rules. InopentheMergeanswer 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 isopen(the## afkModeline, or the repository's approvedmode; any doubt counts asstrict) 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.mdD). Astrictlease and runs outside a lease keep the earlier conditions. -
/setup add afkasks the mode first,openrecommended with one plain paragraph on what agents may do, then the two guards ofopen, each defaulting toguard, and foropenonly the apps and the lease hours;strictkeeps every earlier question. A repository's own away rules ask itsmodeand guards first, and the repository settings preview showsMode,Third-party instructionsandDefault branchfirst. -
afk.py rulesprints the afk rule table, generated from the datacheckreads (modes and guards, the credential floor, the default-branch guard, thestrictsettings, paths and rule rows, the log kinds);skills/afk/references/rules.mdis that output andtests/test_afk_rules.pykeeps 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,setandenvexception 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 answersfloor.merge_check.pyreads a lease asstrictwhen its## afksection has a keyafk.pydoes not read or an invalid guard value. -
The afk mechanism and away decision diagrams say they show
strictand thatopen, the default, runs every action except the credential floor and the default-branch guard (git commitandgit pushonly), with an advisory third-party-instructions guard and no enforced review ormerge_check.py; their PNG renderings and the README alt text are updated. The README,helpmap 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 toreferences/branches.md;checks"Accepting someone else's work" moves toreferences/accepting.md;review-gate's merge step points to the worktree sweep incommit-messages"Branches" instead of repeating it. -
delegatereferences/agents.mdkeeps what every dispatch shares and an index; each family's contract moves toreferences/agents/claude-code.md,codex.md,antigravity.mdandzcode.md, and a dispatch reads only the routed family's file.delegate'sreferences/ledger.mdis regrouped under headings with history sentences pruned, androute.mdandhost-template.mddrop 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;checksis still invoked before accepting a delegated run.tidy"Context pressure" moves toreferences/context-pressure.md, read when the compaction nudge fires, context passes about 60% or work hands over. -
The session-start state block:
Open ledger dispatchescounts this project's open records and those past budget (with aledger.py stalehint) 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 machinemarks 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.pyandmerge_check.py --independentcount 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.mdand the relay line/setup instructionsoffers cover a security review while an away lease is live inopenmode, or instrictmode with Merge yes (owner decision, 17/11/2026); before,opennever matched the "Merge yes" wording. -
Same-family security fallback as a recorded choice (owner decision, 17/11/2026):
/setup add rolesasks 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## Reviewsof 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" andCLAUDE.md"Reviews" state the rule. -
afk: a bare
exportorsetcut out of a search pattern after a lone|or&now floors like a bareenv, sorg 'import|export'floors (its argv is the same as an unquotedrg import|export, which prints the environment); writerg -e import -e export. -
Breaking: the instruction-check consent moves from the legacy
## Route judgmentsection, whose judge line nothing read, to its own## Instruction checksection ofhost.md;/setup checkrequires the new heading, reads the consent only there and names a leftover## Route judgmentwith its fix.matrix_setup.py migratemoves the line (onlyonoroffand 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. -
statusrunsledger.py stalefor this repository on every run, not only whenopenshows long-overdue records, and offers the onestale --close --digestcommand it prints; closing stays your step. -
advisorpicks its family from the assignment matrix: the helper holding theadvisorrole, else the firstroute_pick.py pick --kind advisorcandidate 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 modulesscripts/select_tests.py --base origin/mainlists, 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 oldfnl-skill point at nothing:/setup checklists each one with its new name. Thefnl-reviewandfnl-routermarkers 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 asfinolabs-vibecode:reviewer,finolabs-vibecode:security-reviewerandfinolabs-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-routerno longer asks the configured judge for the depth, the Spec Kit depth gate or the next activity, andreferences/activity-selection.mdis removed:judge.pyhas 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
floorfor a bareenvcut 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 bareexportandsetexception there stays, sorg 'import|export'is still Tier 1. - The afk overlay writer's
mode()refuses a## afkkey or value thatafk.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 asopen. merge_check.pyunder anopenlease folds case, spacing and compatibility forms (NFKC) before it compares a marker'sReviewer:name with the configured role, soReviewer: ClaudeorReviewer: claudeno longer counts as the role's review; the check that a same-family fallback marker needs--fallback-familynow covers every family,zcodeincluded.- 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, andafkandreview-gatecarry the language line. Before, setup and away questions copied in English reached users who write another language. - afk:
checkanswers Tier 1 for an allowedgh pr mergethat passes--author-email(or-A) with one plain email address, as this repository's commit rules ask (any other value stays Tier 3); inopenit answeredunsafe, since the merge pin's grammar did not know the option and raised, and instrictit answeredunknown. A pinned merge inopenwith 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.pytook 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.pyunder anopenlease refuses a marker whoseReviewer: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 namedzcode<suffix>now keeps the zcode family in roles and routing (before, every extra name became claude).