Repository navigation
finolabs-vibecode v0.1.3
Added
fnl-review-gateshipsscripts/merge_check.py <number> --repo <owner/name>, which applies the pull request merge check withgh: the latest unedited marker of each kind for the head from an author with write access, the owner's approving review for an outside author's pull request, passing checks and a mergeable state. It exits 0, 1 or 2 (merge, blocked, cannot tell) and fails closed: a failed permission lookup, an uncomputed merge state, a full page of comments, no reported checks or a compare result without every file or a merge base never pass. It compares manifests as parsed JSON (only the top-level"version"may differ, duplicate keys refused), reads the lane's files from the compare API, bound to the head SHA and diffed from the merge base, treats only GitHub's 404 as no access and gives eachghcall a timeout. Unit tests cover each blocking rule, including a comment-only review after an approval and a tie between verdicts, plus the lane and permission paths through the CLI.fnl-review-gate"Pull requests" rule 7, the low-risk lane, for repositories whose agent context file adopts it: a pull request whose files are all modified in place and are only the root documents written for people (README.md,CHANGELOG.md,CONTRIBUTING.md,CODE_OF_CONDUCT.md,SECURITY.md,PRIVACY.md,TERMS.md) or the plugin manifests' top-level version takes one pass byfnl-reviewer, which reads text addressed to agents, such as a README's install steps, as instructions agents will follow and posts both markers, the security one withlane=yes.merge_check.py --lanedecides, not an agent, and the merge check blocks a lane verdict on a pull request that does not qualify. Agent context files, skills, agents, rules and every other path stay out.fnl-setup's optional combined-review line now adopts this lane, andfnl-security-reviewerruns on every pull request outside it. A behavior eval guards it: against a no-plugin baseline it separates (1.0 and 1.0 with the plugin, 0.33 and 0.33 without).
Changed
- The merge check (
fnl-review-gaterule 4), by hand or by script, also requires every check on the head to have passed and GitHub to report the pull request mergeable;UNKNOWNmeans wait.fnl-verifierreads review markers the same way, counting alane=yessecurity verdict only when the pull request qualifies. - A standing relay approval counts only when recorded in the agent context file as committed on the default branch; untracked files, agent memory, the host config and uncommitted edits no longer count, because a coordinator can write them. The relayed comment's second line is defined once.
fnl-delegatereads an Antigravity run's error before retrying: withagybird0.3.2 or later,evidence.agy_errorwithRESOURCE_EXHAUSTEDor a 429 means that model's pool is out, so the run is recorded asquotaand follows the quota fallback with its tier rules instead of retrying the same model; only a 429 that says it is a short rate limit is retried, once. The direct-agyandagybirdoutcome tables follow the same rule. The host template asks how to look up theagybirdrunner at each dispatch, not for a pinned or highest cached folder.- Antigravity review inputs go to
.orchestration/briefs/inside the worktree and are removed once the report is read, and the long-lived worktree switches branch once the previous run's work is committed or handed over.
What to do
- If a standing relay approval lives in your host config or another untracked file, move it, with its scope and date, into the agent context file (
CLAUDE.mdorAGENTS.md) through a reviewed pull request; until then the coordinator hands relayed reviews to you. - If your agent context file carries the 0.1.2 optional line letting documentation pull requests take one combined review, replace it with the line
/fnl-setupnow offers. The lane still covers the README and other root documents, but no longer adocs/folder; pull requests there go to both reviewers.
These two steps would make this a minor release under fnl-versioning; the owner kept it a patch because the plugin is in early use with few installs outside the maintainer's, and both steps are stated here. The owner also waived the release checklist's adversarial review by another model family for this release: Gemini 4 Argon and Codex were out of quota.