Repository navigation
v0.2.4
v0.2.4 - 2026-11-11
Highlights
This release helps you check your work when cloud CI is expensive or out of minutes, and makes updating the plugin walk you through what is new.
- Repository checks.
/fnl-setup add checksfinds a repository's checks and saves the list you approve.checks.py runruns it locally, with an optional pre-push hook. - A local receipt when cloud CI cannot run. Opt in per repository, and a passing full run can stand in for missing or failing cloud checks at the merge gate. It is self-reported, so it suits a repository one person works on.
- Cheaper CI. Setup can write a GitHub Actions workflow that skips document-only changes and cancels superseded runs, and
checks.py usageshows what your CI minutes cost. - Guided updates.
/fnl-updatenow goes on to a checklist of what the new version adds;/fnl-update whats-newonly shows it. You can also pick or pin a version. - Renamed.
fnl-verificationis nowfnl-checks; the old name keeps working through 0.2.x.
Not verified on a live host: a real git push through the installed hook, and a run of the generated workflow on GitHub Actions.
Added
/fnl-setup add checksreads a repository'spackage.jsonscripts, declared Python test runner andMakefiletargets without running them, listsrun:lines from its CI workflows as unverified candidates it never converts, proposes an ordered check list (a name and a JSON argument array each, never run through a shell by the plugin; known shells, launchers and inline-code forms are refused as a best-effort guard, not a sandbox; skipped items named) and, after a digest-bound yes,checks_setup.pysaves it as that repository's entry in the host config's own## Checkssection (at most 20 checks of 1 KB each);## Project settingsis unchanged.fnl-checks'checks.py run [--changed] [--base <ref>]runs a repository's stored checks in order throughheavy_run.pyand stops at the first failure (--changednarrowspython -m unittest discover -s testsover a flat tests folder to one discovery per moduleselect_tests.pynames, and runs every other form and layout whole); an opt-in per-repository local-receipt mode lets a whole passing run on a clean, unmoved head stand in for missing or failing hosted checks inmerge_check.py(only when the checkout'soriginis the--reporepository, and the latest full run decides, one full run per repository at a time), which names itchecks: local receipt (<head>); andchecks_setup.py hook install|removeadds or removes an optional git pre-push hook that runschecks.py run --changed, refusing whencore.hooksPathis set and never overwriting a different hook without a second flag.checks_setup.py ci preview|applywrites, after a digest-bound yes, one new GitHub Actions workflow from a repository's stored checks: pull requests, pushes to the default branch, a weekly schedule, superseded runs cancelled, document-only changes skipped, caching for a known ecosystem. It refuses a link on the path and an Actions expression, keeps a backup, never overwrites without--replace-existing, and never commits or pushes;fnl-checks'references/ci.mddescribes it.fnl-checks'checks.py usage --from <file> [--files-from <file>] [--limit-minutes N]summarises hosted CI runs from agh run list --jsonfile: run count, minutes rounded up per run, minutes per workflow and per event, the share spent on document-only changes and days left at the observed rate. It makes no network call and starts no process./fnl-updatenow goes on, after the host update, to a checklist from the newreferences/upgrades.json(one closed-schema entry per release, starting with 0.2.4) and offers each open setup step throughfnl-setupwith its own consent;/fnl-update whats-newonly shows the checklist, and the session-start hook adds one read-only line naming/fnl-updatewhile the installed version's notes are unseen.update_check.pygainswhats-new,onboard seen <version>andonboard skip <id>(the only writers ofonboard.json:last_seenand skipped ids),target [<version>] [--evidence <file>](latest by default; a chosen version only with matchinggh release viewevidence, an older one reported as a rollback with what is lost) andpin <version>/unpin, which silences the newer-release notice; the network check is unchanged. The Codex refresh procedure is now marked verified, andfnl-versioningasks the release pull request to write the upgrade-notes entry, which a test enforces.
Changed
fnl-verificationis now fnl-checks, which also covers where a repository's checks run (locally or in CI);/fnl-verificationkeeps working as a user-only alias through 0.2.x.