You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This commit was created on GitHub.com and signed with GitHub’s verified signature.
Added
Models per kind of work in the assignment matrix: an agent line may carry models <rule> | <rule> ..., each <model>[ then <fallback>] for <kind, type or levels>, read in order with the first match winning (a rule naming no kind applies only to implementation). route_pick.py pick gains --kind (implement, code-review, security-review, navigator, advisor), makes --type optional and prints the model chosen for each dispatch, with quota-fallback when an Antigravity rule's then replaced a model whose quota pool (argon, gemini, claude-gpt, other) is out; an agent whose chosen model is out is dropped. review_route.py judges Antigravity's quota per review kind on the model its rules pick (--level for level-bound rules), matrix_setup.py show lists the rules, and /setup add delegation asks for them. Any malformed rule makes the whole matrix invalid.
merge_check.py --independent --fallback-family <family> lets an away lease merge on reviews by the author's own family when no other family is reachable: it needs a live lease, the author's family, positive out-of-quota evidence (a fresh reading with every pool below the floor, or a live rate-limit marker) for every other present family, a router trigger other than security, permission or privacy, no changed enforcer script or instruction file, and the exact fallback reviewer line on each counted marker. afk.py log --kind review-fallback --pr <n> --head <sha> records it for the user's return.
ledger.py finish --retro marks a record written after the fact.
/setup add afk inside a repository can list its own test-commands (exact commands, never starting with git, gh or rm) and top-level-files (exact top-level file names such as TASKS.md). During a lease, afk.py check answers Tier 1 for a listed test command, bare or through heavy_run.py run --, and treats a listed file as a known path, in that repository only; the strict and no-repository states list none, and a repository without its own lists uses the account defaults in ## afk (see the account-default lists below). Before, a lease could not run a repository's tests, which its own merge gate needs, or tick its task list.
afk.py start adds a This folder line with the rules of the repository it ran in (limits, decided categories, deploy targets, test commands, top-level files), and afk.py effective adds them as rules; before, both showed only the account values, so a user saw rules that did not apply in the repository. Re-running /setup add afk now offers the saved limits and table answers instead of the defaults.
afk.py check allows creating a new own work branch during a lease: git switch -c <branch> or git checkout -b <branch> (no start point) is Tier 1 in a found repository with Push and pull requests or Merge yes, never with a default-branch name; before, no branch could be created and the own-branch flow parked at its first step.
afk release targets: a tag, GitHub release or publish (git tag, gh release, npm publish, pnpm publish) runs under a lease only when the exact command is listed (Release targets in ## afk, or a repository's own release-targets), in addition to Tags and releases or Publishing at decide; /setup add afk asks for the list in its own question with the commands read back in the preview. Reading tags and releases (git tag -l, gh release view or list) needs no entry.
Changed
The README's afk mechanism diagram shows the whole away flow on one page, and the away decision diagram shows the evaluation table instead of Jev at 0.8.
Breaking: afk tags, releases and publishing that were Tier 1 with their category at decide alone now park until the exact command is listed as a release target (owner decision, 15/11/2026).
afk command and file lists load like environment variables (owner decision, 15/11/2026): Production targets, Test commands, Top-level files and Release targets in ## afk (afk_setup.py preview --production-target, --test-command, --top-level-file, --release-target) are the default for every repository, and a repository's own list replaces the whole list there. The strict and no-repository states use none, and an invalid ## afk list line fails start. Before, the three older lists were read only from a repository's settings. Production stays decidable only in a repository's own decide list.
The same-family review fallback (merge_check.py --fallback-family) may now merge a pull request that changes an enforcer script or instruction file when each kind of review has approvals at the head from two different models of the author's family, each marker naming its model as model=<name> right after the fallback reviewer line; one model, the same model twice, a REWORK from either, or a missing model name still refuses (owner decision, 15/11/2026). Every other fallback condition stays.
afk limits are counted per repository: each repository under one lease has its own runs, runtime minutes (from its first allowed action) and actions an hour, and a repository may set its own max-runs, max-runtime-minutes and max-actions-per-hour in /setup add afk (wider or narrower than the user value). Breaking for away loops: a spent repository answers spent with no end line, so the loop goes on in other repositories, exhausted is no longer returned, and a changed setup now adds the end line like an ended lease; a lease started before the update reads as invalid, so start it again.
afk categories and deploy targets can differ per repository: /setup add afk inside a repository may set its own decide list (an explicit list replaces your account's table there; every unlisted category stops), its own non-production-targets, and, only there, production-targets: exact production deploy commands that run while you are away only when production is in that repository's decide. Breaking for away flows: outside a repository and in the strict state every category stops and no deploy target applies, and gh release create now needs --repo github.com/OWNER/NAME equal to the verified target, like a merge.
afk decisions take an evaluation table before the deciders: judge.py ask --site away-evaluation prints the probability of each option ({"source", "of", "probabilities"}), and without Jev the host's small fast model writes the same table, checked by the new judge.py check-table --file <brief> --of <k>. The table goes to the advisor and the host as data and never settles a decision. Breaking for away flows: the away-decision site and its 0.8 threshold are removed, afk.py log --kind decision replaces rung jev with table (--settled yes --by jev|host-small --of <k> --probability <top p>, or --settled unavailable --by jev|host-small), and the ledger's away summary and the dashboard show the table's top probability instead of a Jev spread.
ledger.py summary leaves cancelled records closed late (by ledger stale or the coordinator) out of the counts, acceptance rates and medians and prints them as a separate total, and leaves finish --retro records out of the medians (a group with only such records shows -). The text table gains the quota, error and cancelled columns that --json has, and below it flags accepted runs whose log scan had findings and review acceptances recorded without --review-url. --json rows gain cancelled, closed_late, retro, accepted_findings and review_unposted; median_min may be null. The status dashboard uses the same rows.
ledger.py finish refuses a negative --rework-rounds, more than 2 rework rounds without a --reason, and accepted with --tests failed; start warns, and still records, when the model is not in the assignment matrix or the project label differs from the repository's ledger project setting.
Fixed
ledger.py finish --log-path accepts a log directly in .finolabs/logs/ of the --checkout checkout or of the main checkout, not only of the current one, so a coordinator in another worktree can close a run; a refused log gets one fixed reason line instead of a bare ledger: log refused. An empty log is now not_scanned, not no_findings. delegate "Where files go" names one place for logs.
Two ledger.py start calls in the same second can no longer share a dispatch id: the id is checked against the ledger under the finish lock.
afk no longer parks review posting: afk.py check allows post_review.py <number> and post_review.py <number> --body-file <run body> (either order) when the repository's target is verified and Repository comments is decide; the body must be post_review.py's own private run body, its first line one review marker and the rest free of secrets, machine paths and other gate markers.
The afk advisor rung follows the model table: afk.py check accepts an advisor run only on a model that delegatereferences/models.md lists as that family's frontier or strong tier (an unknown or fast-tier model such as Flash is denied), and for a Claude coordinator denies a Claude model served through Antigravity, so the advisor is frontier else strong as advisor choose mode says. Breaking for away flows: a new model name is denied until the table and the check list it.
afk.py log and review refusals of a schema error now name the flag and why (for example the advisor no row takes no --of, --option) instead of the generic setup message, which stays for missing, invalid or unsafe private state; no passed value is echoed.
advisor choose mode says to check the advise dispatch's ledger.py start argv with afk.py check, the only check that counts a run against the lease's run limit, and that an advisor family whose program moved after an update stays denied until /setup add quota records it again (the exact program record is kept on purpose). afk decide names delegate's judge.py as the copy check allows.
afk works in a Markdown skill repository: a repository approved as one (skill-repository: yes, a new question in /setup add afk inside the repository) may edit its root SKILL.md, references/**, scripts/** and evals/** on a work branch; a SKILL.md below the root stays protected.