v0.9.6

Fugaro v0.9.6

Install:

• Homebrew: brew install dimipaun/tap/fugaro
• Go: go install github.com/dimipaun/fugaro/cmd/fugaro@v0.9.6
• Or download an archive below and verify it against checksums.txt (see docs/release.md).

Highlights

• fugaro setup and fugaro update replace fugaro init: setup is the first run, which creates the installation or adopts one that already exists, and update re-converges an installation after a CLI upgrade; fugaro init now only says which of the two to run.
• fugaro setup asks its questions once, in a fixed order, each with a suggestion that Enter takes and a flag that answers it (the GCP project's ID, the region, whether to create the project or adopt an existing one, and the project's name), and a run nobody can ask names every missing flag in one error instead of one at a time.
• A cloud run's review stage now compares the branch with the base the run actually works on instead of with main, so a run on a long-lived branch no longer reads the whole branch against main, a follow-up uses the pull request's current base, binary files reach the reviewer as one line each, and a very large diff is flagged to the reviewer up front; runs on such branches cost a fraction of what they did.
• fugaro --version and fugaro -v print the version, like fugaro version.
• The working and parallelism skills warn about the review cost of runs on long-lived branches and teach a daily look at the most expensive runs.

For operators

1. Per machine — upgrade the CLI on every machine that runs Fugaro: brew upgrade dimipaun/tap/fugaro.
2. Per repo checkout — run fugaro upgrade: it pins the plugin to this release, updates it in Claude Code and refreshes the repository's job images. The cheaper review stage reaches your runs only after this refresh, because the runner that does the review is the one in the job image; it builds images, which costs money (--yes confirms each build).
3. Per installation — wherever a document or a script of yours says fugaro init, say fugaro setup for a first run and fugaro update after an upgrade; fugaro update --help lists the flags, and it refuses by name the flags that only setup takes. This release changes no cloud resource by itself.

Known limits

• The setup wizard is not finished. fugaro setup and fugaro update work as described, but the questions that suggest a project ID, pick a region apart from the Firestore location, find your billing accounts and ask for a first repository belong to the next release, so for now the flags the old command took keep their names and still have to be typed.
• fugaro init no longer does anything. It refuses and names the two commands that replaced it, so a script or a CI job that calls it fails until it is changed.
• The credentials service, the managed deployer and the Batch backend are not in this release. They are built on their own branch and ship with the next one.
• Cloud runs on branches other than main keep their old review cost until step 2 above has run for the repository, because the images still carry the previous runner.

Changelog

• website: the security drawing is one picture in two layouts, and every "Also true of a run" fact carries a bullet (owner's feedback C) (#843)

• Task: setup wizard W1.3: setup is the wizard (the create/adopt ques… (#835)

• website: the owner's 2026-10-21 feedback — the spark, Home in the menu, and the slider (#842)
• runner: the review stage diffs against the run's real base, not main (#840)
• website console: the screenshots slider counts, clicks and advances; the download cards stand in one row; the shasum line comes out (#841)
• skills: a run on a long-lived branch names its base, and says what its review costs (#839)
• cli: every fugaro init line names the door the reader is at (setup-wizard W2.1) (#832)
• website console: the four screenshots are on the page (#818)
• cli: W1.2's four review leftovers, and the two red tests on main they hid behind (#834)
• W2.2: the strings outside internal/cli name fugaro update or fugaro setup, not fugaro init (#833)
• cli: fugaro setup and fugaro update replace fugaro init; init is a tombstone naming both (#789)
• website: the run drawing is painted again, and the paint is a gate (#816)
• fix forward: main's ci job test is red on four tests — the rigor-modes census figure, the rename census's frozen list, the ignored-output coverage, and the copy-in proof they break (#815)
• FAQ: the empty "How Fugaro compares" section comes out (#817)
• review: the reviewer may not read a binary, and the marker's name is always quoted (#814)

• Task: the Fugaro CLI on Windows, Slice 1: compile, start, and read th… (#763)

• review: the reviewer is handed the diff as text, binary files as one line (#807)
• console: the bold redesign — the hero, the screenshot frame, per-OS download cards, the facts (#805)
• setup-wizard W0.2: the fugaro init rename census, pinned as a test (#772)
• leftover minors before the 0.10.0 tag: mobile leftovers: #666 #695 (#785)
• website leftovers before 0.10.0: #739's two closed, #678/#705/#726 verified already landed (#786)
• website: the privacy page wears the bold look (redesign P1) (#809)
• website: the caps-and-costs page in the bold look (#804)
• website: the community page in the bold look (redesign P1) (#803)
• website: the security page in the bold look (redesign P4) (#801)
• website docs: the bold look on the docs hub, from the site's own shapes (#800)
• website: the getting-started page rebuilt from the owner's board (redesign P4/P5) (#799)
• website: the changelog page in the bold look, pinned by five cases (#797)
• website: the bold look on the FAQ page (#795)
• website: how-it-works takes the bold look (redesign P8, board HowItWorksV3) (#802)
• cli: fugaro --version and fugaro -v print the version, like fugaro version (#794)
• website: the bold look, and the home page rebuilt from the owner's board (redesign P1) (#779)
• console: all five ledger leftovers (#694 #701 #709 #713 #717) are already closed at HEAD (#792)
• mobile: the Android launch crash, its cause, and a guarded startup that shows the next one (#790)
• console: a one-command, fixture-only screenshot run for the website's Console page (#768)
• mobile: the app wears the Fugaro logo on both platforms (#791)
• The 0.10.0 leftovers: #764 and #761 fixed, #742 already closed at the head (#784)
• setup wizard W4.2: gcloud billing accounts list as the fallback for the billing client (#781)
• website: the owner-approved bold design boards, kept as a read-only reference (#778)
• setup wizard W1.1: initflow stops naming a command (the stage engine) (#765)
• billing: list the open billing accounts a user can use, ids and display names only (#769)
• cli: pin the confirmation matrix both front doors must pass (setup wizard W0.1) (#770)
• console: a Linux build (AppImage and .deb, unsigned) for 0.10.0 (#758)
• terraform, schema and the example config: the descriptions name fugaro setup or fugaro update (W2.5) (#766)
• docs/mobile/voice-session: the owner's spec for a hands-free voice session, reconciled against the tree (#761)
• website: "Why Fugaro?" heading, the security drawing's cards, and budget re-derivation only on request (#762)
• website: retire the orphaned four-step flow and give its gates to what the pages show now (#756)
• mobile: record the App Store Connect app id in the submit profile, and the submit path in the README (#759)

Base images

Published by the images workflow for this tag:

• ghcr.io/dimipaun/fugaro-history:0.9.6 and ghcr.io/dimipaun/fugaro-history:0 (the sweeper and history job's image)
• ghcr.io/dimipaun/fugaro-base:0.9.6 and ghcr.io/dimipaun/fugaro-base:0 (one index for linux/amd64 and linux/arm64; per-architecture tags 0.9.6-amd64 and 0.9.6-arm64)

The images workflow then pulls each one with no login and fails if it is not public or lacks linux/amd64 (and, for fugaro-base, linux/arm64); each image's digest is in that run's summary.

The Terraform modules, the schemas and the plugin are versioned by this same tag.