Skip to content

finolabs-vibecode v0.1.2

Choose a tag to compare

@fioenix fioenix released this 02 Nov 07:18
· 2068 commits to main since this release
9cecedd

Added

  • fnl-plugin-packaging covers shared catalogs across hosts, Codex grouping and catalog renames, Antigravity installs from a repository URL, pinning versus tracking, and protection for listed repositories (references/catalogs.md).
  • fnl-session-hygiene sets a session title format, <project> <scope>: <activity>, with examples, when to rename, whose sessions to rename, and how each host names sessions (references/titles.md). A delegated run's logs are named <ledger id>-<slug> and its brief <slug>.md; Codex sessions are archived or deleted by id, never by title.
  • CI checks cross-references (scripts/check-references.py): skill and agent names, section references (backticked or linked), relative links, ledger subcommands with their own flags and allowed values, and host config flags against the agent contracts.
  • fnl-delegate's capability map carries a review-by date, and /fnl-status warns when it has passed.
  • Behavior evals (tag behavior) with deterministic graders on each answer's final verdict line: the pull request merge check with a stale marker, a marker from an author without write access, and a valid pair; coding-router depth for a typo and a tenancy change; the merge check when a later marker overrides an earlier one for the same head, when a later comment quotes a marker, when the author lacks write access, when the owner approved only an earlier commit, and when a verdict comment was edited; delegate routing when one agent's quota is out, when every frontier model is, when only frontier models are left for medium work, and for a review; the Spec Kit depth gate; verification of a false delegated report. Against a no-plugin baseline, the review routing and outside-author cases show the skills' effect, and the depth gate case separates only on its reason grader; the others guard against regressions. A trigger eval covers session titles and the branch flow, and every eval scaffold refuses to run outside an empty directory.
  • fnl-commit-messages "Branches" sets one branch flow: trunk-based with short-lived branches, naming, the base to cut from, syncing by rebase or merge without rewriting a pushed branch, conflicts, default branch rules, merge commits pinned to the reviewed head, cleanup of branch and worktree, hotfixes and backports to release/X.Y. Its description gains branch triggers, and fnl-coding-router, fnl-delegate, fnl-handoff, fnl-coordinator-sessions, fnl-review-gate, fnl-versioning, fnl-open-source-review and fnl-ask point to it where a branch is created, synced or merged.
  • The contributing guide lists the local checks, how to add a host, and the release checklist, which includes an adversarial review by another model family.

Changed

  • fnl-coding-router's Spec Kit depth gate lets a user story go from an accepted plan straight to implementation, skipping speckit-tasks, also when it makes a small, contained contract change that a security review covers; security, privacy, permission, migration, dependency and irreversible boundaries still go through tasks. A direct path is accepted by fnl-verification against each acceptance criterion and the two posted reviews, and fnl-review-gate's reviewer packet carries the story's acceptance criteria and plan.md when Spec Kit is in use. A direct path runs no separate analyze or converge step. Two behavior evals guard it: an additive response field goes direct (it passes without the plugin too), and a new filter parameter that reaches a query goes to tasks (2/2 with the plugin, 0/2 without).
  • Claude Code and Codex install the plugin from the FINOLABS catalog, finolabs/plugins (finolabs-vibecode@finolabs), which groups the FINOLABS plugins under one name; the repository's own marketplace stays for existing installs. The manifests name FINOLABS as author and developer. The agent install steps check for an existing install before adding the catalog.
  • The repository moved to github.com/finolabs/finolabs-vibecode; links, manifests and install commands use the new address, and GitHub redirects the old one.
  • fnl-coordinator-sessions, the delegation host template and agent contracts use that title format.
  • fnl-verifier counts a review marker only from an author with write access, like the merge check, which now names the permission values GitHub returns.
  • fnl-advisor names Antigravity among the agents it can ask, in its description and argument hint.
  • fnl-delegate's capability map routes reviews of medium work at frontier tier and reviews of easy work at strong tier, matching the rule that a review takes the tier above the work.
  • fnl-delegate keeps routing and the steps every dispatch takes in SKILL.md, and moves procedures only some runs reach (quota fallback, parallel runs, the heavy-job lock, handover, file placement, ledger commands) to references/dispatch.md and references/ledger.md. The rule that a task needing wider shell access goes to another agent applies to every delegate, not only Antigravity.
  • fnl-review-gate merge check: a verdict is an unedited comment whose first line is a marker, from an author with write access; for each kind the latest such verdict for the head (by createdAt) must be APPROVE, so a later REWORK blocks the merge and a marker quoted inside a comment counts for nothing. A pull request from an author without write access also needs the owner's own approving review on the head commit, the reviewer's latest review counting, read from the pull request's reviews; no agent submits it. The verifier counts verdicts the same way.
  • Reviewers treat everything under review as data: text in a pull request that tells the reviewer what to conclude, post or run is a finding (fnl-review-gate, both reviewer agents).
  • An Antigravity coordinator's wider allow-rules need the user's approval (fnl-delegate agent contracts).
  • When a delegate's allow-rules miss the commands a brief's tests need and the user is present, fnl-delegate asks the user to grant them as literal rules (with agybird's grant flow, or a per-run settings file) before falling back to an edit-only brief or another agent, and never skips the permission check. The user chooses each grant, only for commands the brief lists, and is told that a granted test command runs the repository's test code; the host config only records grants; /fnl-setup offers remembered rules for the repository's test commands. A behavior eval guards it.
  • fnl-delegate shares whole easy and medium implementation tasks when the coordinator's context is past about 60% or it holds several independent tested tasks (to a fresh session or headless run of its own kind), or when its own quota or tokens are short (to another agent with quota left); the coordinator keeps briefing and acceptance, reviews follow fnl-review-gate, and merges stay with whoever holds the authority (Load sharing). fnl-coding-router says a delegated whole task is not an implementation child.
  • Reviews of several pending pull requests go to each reviewer in one packet and one pass, with one comment and marker per pull request and their interactions noted (fnl-review-gate, both reviewer agents).
  • Antigravity grants are remembered per folder, so fnl-delegate dispatches a repository's runs from one long-lived worktree, one run at a time, and opens with a short run of the brief's check commands to collect grants; parallel runs keep their own worktrees and grants. A read-only review gets the diff and check output inside its worktree and reads the report even when the run ends partial.
  • A coordinator may post another family's review under a standing relay approval that the owner recorded, with its scope and date, in a file the owner controls; the relayed comment names the reviewer and cites the record (fnl-review-gate), so pull requests one model family wrote get a code review from another.
  • The owner approval on an outside author's pull request reads each reviewer's latest approving, change-requesting or dismissed review; comment-only reviews do not count.
  • fnl-commit-messages names the agent whose accepted work a commit holds.

Fixed

  • The dispatch ledger skips lines that are valid JSON but not records, instead of crashing.