[fizzy-publish]

heronin: pin fizzy with the Android launch fix

In plain words

Heronin now uses the fizzy revision containing the Android launch fix. This brings the upstream fix into Heronin; launching it on a phone still needs to be checked after merge.

What changes

• Update the pinned fizzy revision to 612f90b8aa1282f3d1fe1b79b1675a8a677af193 and its package hash.

    .dependencies = .{ .fizzy = .{ .url = "https://github.com/fizzyedit/fizzy/archive/612f90b8aa1282f3d1fe1b79b1675a8a677af193.tar.gz", .hash = "fizzy-0.2.0-c46aVj9UyQDD3hiUClf4LvLikHxmdenMg-ghakvXMjgO" } },

What you will notice

The update is intended to fix Android launch. The APK build and phone launch could not be verified in this job.

How we know it works

The pin check prints 1, and formatting passes. All five build gates and the APK build stop at dependency fetching with server connection failed: Unexpected; a separate download attempt reports that github.com cannot be resolved. No tests reached execution. The upstream socket-folder implementation could not be inspected because the dependency was not fetched.

How this serves fizzy

Platform support: bringing the Android launch fix into Heronin supports people using fizzy on Android.

Part of fizzyedit/work#1200

For agents: technical summary

Goal

Pin Heronin to fizzy's Android launch fix without changing application code.

What changed and why

Only the fizzy dependency line in build.zig.zon changes. SHA: 612f90b8aa1282f3d1fe1b79b1675a8a677af193. Hash: fizzy-0.2.0-c46aVj9UyQDD3hiUClf4LvLikHxmdenMg-ghakvXMjgO.

Budget: git diff --numstat HEAD reports 1 added, 1 deleted line in build.zig.zon; 0 new non-test implementation lines. The requested PR page and report are delivery artifacts outside the implementation budget.

zig fetch --save=fizzy failed before updating the manifest, so the specified URL and hash were applied directly, preserving the rest of the file.

How it was verified

• grep -c 612f90b8aa1282f3d1fe1b79b1675a8a677af193 build.zig.zon: 1.
• zig fmt --check build.zig tools tests/check_public model app server: exit 0.
• zig build, zig build server, zig build test, zig build web, zig build check-public: each exit 1 at dependency fetching with server connection failed: Unexpected.
• PATH=/opt/android-jdk/bin:$PATH JAVA_HOME=/opt/android-jdk zig build apk -Dtarget=aarch64-linux-android -Dandroid-sdk=/opt/android-sdk: exit 1 at the same dependency-fetch error.

APK evidence command:

/opt/android-sdk/build-tools/35.0.0/aapt dump badging zig-out/heronin.apk | grep -E "^package|application-label"

Output (exit 1):

11-11 19:45:51.214    29    29 W asset   : Asset path zig-out/heronin.apk is neither a directory nor file (type=1).
ERROR: dump failed because assets could not be loaded

ls -l zig-out/heronin.apk

Output (exit 2):

ls: cannot access 'zig-out/heronin.apk': No such file or directory

Not done / follow-ups

Rerun the build gates and APK evidence when the dependency is available. Verify the fetched app/control/Server.zig uses openDir with .follow_symlinks = false and sets socket-folder mode through the fd. These remain unverified here. The Architect's reported green trial was not independently reproduced. Phone launch is Ops' A7 smoke after merge; release key, install script, and console pin remain outside this change.

Part of fizzyedit/work#1200