Task 25: Packaging and release workflow (#25) #95

Manually merged
charles merged 0 commits from task/25-packaging-release into foundation 2026-11-11 18:28:25 +00:00
Owner

Stacked on: task/14-app-runtime, task/24-screenshot-tests

What this builds

  • cargo xtask package --target <linux|windows> [--version <v>] [--out-dir <dir>] (xtask/src/package.rs): release build of fluxer (--no-default-features, so no devserver), then
    • Linux: dist/Fluxer-Native-<version>-linux-x86_64.AppImage. AppDir staged from packaging/linux (AppRun, fluxer-native.desktop, fluxer-native.svg) plus the binary; squashed by appimagetool 1.9.1 with the type-2 runtime 20251108. Both are downloaded with curl on first use into the target dir and used only if they match the SHA-256 pinned in the source. No FUSE needed (APPIMAGE_EXTRACT_AND_RUN=1).
    • Windows: dist/Fluxer-Native-<version>-win-x64.exe, static CRT, icon (packaging/windows/fluxer-native.ico) and version resource embedded by apps/fluxer/build.rs.
    • Both: dist/SHA256SUMS (sha256sum --check format).
    • Version: --version, else the native-* tag on HEAD without its prefix, else 0.0.0-dev+<sha>. Packaging for the other OS is refused (no cross-compiling).
  • .forgejo/workflows/release.yaml (workflow_dispatch, input version): prepare validates the version and creates a draft release; linux and windows run cargo xtask package, smoke-test the package (--debug-info) and upload it to the draft; publish writes SHA256SUMS from the checksums each build machine computed, checks both assets are attached, uploads it and publishes the draft (which creates the tag native-<version>). A failed run leaves at most a draft; an existing release or tag is never replaced.
  • Icons are the Electron app's (fluxer_desktop/build_resources/icons-stable in the fork): the .ico is copied, the SVG is the logo mark on the brand disc, matching the fork's 512x512.png.

How it was tested

  • xtask/tests/package.rs::package_produces_appimage_on_linux (written first, seen failing on the unimplemented subcommand): AppImage exists, is executable, --appimage-extract works, squashfs-root/usr/bin/fluxer --debug-info and squashfs-root/AppRun --debug-info exit 0, SHA256SUMS verifies. Also packaging_for_another_os_is_refused, and unit tests for version parsing, package names and SHA256SUMS merging.
  • FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci green locally on Linux (base and this branch).
  • The appimagetool step was run in a bare ubuntu:22.04 container (what the runner uses): it works without FUSE once file is installed, which is why file is added to the apt lists.
  • cargo clippy -p xtask --all-targets --target x86_64-pc-windows-msvc -- -D warnings is clean; the Windows-only part of build.rs was type-checked in a scratch crate. The shell steps of release.yaml pass bash -n and the publish job's checksum validation was run against sample data.

Not verified here (please look)

  • release.yaml was not dispatched. The plan asks for one dispatch with 2026.1111.0. That publishes a real release and tag from an unmerged task branch, and I cannot watch the run. Left for Charles after merge: tools/fj.sh POST /repos/charles/fluxer-native/actions/workflows/release.yaml/dispatches '{"ref":"<branch>","inputs":{"version":"2026.1111.0"}}'. Until the first run, the workflow (job outputs between jobs, draft → publish through the API) is untested on the runners.
  • Nothing Windows-specific has run: package_produces_portable_exe_on_windows (new, runs on the Windows runner as part of cargo xtask ci), the winresource step in build.rs (needs the SDK's rc.exe; a normal build only warns without it, the packaging build fails), and the +crt-static release build.

Deviations from the plan

  • winresource 0.1 instead of winres: winres (last release 2021) links the resource into every target of the package, which breaks a package that has a library and a binary, as apps/fluxer does; winresource is its maintained fork and links it into the fluxer binary only. The metadata table is therefore [package.metadata.winresource], and the icon path is set in build.rs (every key of that table becomes a version-info string, so it cannot hold a path).
  • Files outside the task's list: Cargo.toml/Cargo.lock (winresource), xtask/Cargo.toml (sha2, already a workspace dependency; tempfile for the test), xtask/src/main.rs (dispatch), xtask/tests/ci_smoke.rs (its "package is unimplemented" test became "package needs a target"), .forgejo/workflows/ci.yaml (file in the Linux apt list), xtask/README.md and apps/fluxer/README.md.
  • --version and --out-dir flags added: the release workflow builds before the tag exists, and the test must not write into dist/.
  • The release token is the job's automatic GITHUB_TOKEN secret (as in ci.yaml and the fork's release job), not a separately created secret.
  • The packaging test is part of the normal test run, so cargo xtask ci now does a release build on Linux and Windows and, on Linux, needs network once to fetch the two pinned tools.
  • The version only names the package; fluxer --debug-info still prints the crate version (0.1.0) and the commit. Changing that touches debug_info.rs (Task 14) and the version sent to the gateway, so it is left for a decision.

Closes #25

🤖 Generated with Claude Code

Stacked on: task/14-app-runtime, task/24-screenshot-tests ## What this builds - `cargo xtask package --target <linux|windows> [--version <v>] [--out-dir <dir>]` (`xtask/src/package.rs`): release build of `fluxer` (`--no-default-features`, so no devserver), then - Linux: `dist/Fluxer-Native-<version>-linux-x86_64.AppImage`. AppDir staged from `packaging/linux` (`AppRun`, `fluxer-native.desktop`, `fluxer-native.svg`) plus the binary; squashed by `appimagetool` 1.9.1 with the type-2 runtime 20251108. Both are downloaded with `curl` on first use into the target dir and used only if they match the SHA-256 pinned in the source. No FUSE needed (`APPIMAGE_EXTRACT_AND_RUN=1`). - Windows: `dist/Fluxer-Native-<version>-win-x64.exe`, static CRT, icon (`packaging/windows/fluxer-native.ico`) and version resource embedded by `apps/fluxer/build.rs`. - Both: `dist/SHA256SUMS` (`sha256sum --check` format). - Version: `--version`, else the `native-*` tag on `HEAD` without its prefix, else `0.0.0-dev+<sha>`. Packaging for the other OS is refused (no cross-compiling). - `.forgejo/workflows/release.yaml` (`workflow_dispatch`, input `version`): `prepare` validates the version and creates a **draft** release; `linux` and `windows` run `cargo xtask package`, smoke-test the package (`--debug-info`) and upload it to the draft; `publish` writes `SHA256SUMS` from the checksums each build machine computed, checks both assets are attached, uploads it and publishes the draft (which creates the tag `native-<version>`). A failed run leaves at most a draft; an existing release or tag is never replaced. - Icons are the Electron app's (`fluxer_desktop/build_resources/icons-stable` in the fork): the `.ico` is copied, the SVG is the logo mark on the brand disc, matching the fork's `512x512.png`. ## How it was tested - `xtask/tests/package.rs::package_produces_appimage_on_linux` (written first, seen failing on the unimplemented subcommand): AppImage exists, is executable, `--appimage-extract` works, `squashfs-root/usr/bin/fluxer --debug-info` and `squashfs-root/AppRun --debug-info` exit 0, `SHA256SUMS` verifies. Also `packaging_for_another_os_is_refused`, and unit tests for version parsing, package names and `SHA256SUMS` merging. - `FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci` green locally on Linux (base and this branch). - The appimagetool step was run in a bare `ubuntu:22.04` container (what the runner uses): it works without FUSE once `file` is installed, which is why `file` is added to the apt lists. - `cargo clippy -p xtask --all-targets --target x86_64-pc-windows-msvc -- -D warnings` is clean; the Windows-only part of `build.rs` was type-checked in a scratch crate. The shell steps of `release.yaml` pass `bash -n` and the publish job's checksum validation was run against sample data. ## Not verified here (please look) - **`release.yaml` was not dispatched.** The plan asks for one dispatch with `2026.1111.0`. That publishes a real release and tag from an unmerged task branch, and I cannot watch the run. Left for Charles after merge: `tools/fj.sh POST /repos/charles/fluxer-native/actions/workflows/release.yaml/dispatches '{"ref":"<branch>","inputs":{"version":"2026.1111.0"}}'`. Until the first run, the workflow (job outputs between jobs, draft → publish through the API) is untested on the runners. - **Nothing Windows-specific has run**: `package_produces_portable_exe_on_windows` (new, runs on the Windows runner as part of `cargo xtask ci`), the `winresource` step in `build.rs` (needs the SDK's `rc.exe`; a normal build only warns without it, the packaging build fails), and the `+crt-static` release build. ## Deviations from the plan - `winresource` 0.1 instead of `winres`: `winres` (last release 2021) links the resource into every target of the package, which breaks a package that has a library and a binary, as `apps/fluxer` does; `winresource` is its maintained fork and links it into the `fluxer` binary only. The metadata table is therefore `[package.metadata.winresource]`, and the icon path is set in `build.rs` (every key of that table becomes a version-info string, so it cannot hold a path). - Files outside the task's list: `Cargo.toml`/`Cargo.lock` (`winresource`), `xtask/Cargo.toml` (`sha2`, already a workspace dependency; `tempfile` for the test), `xtask/src/main.rs` (dispatch), `xtask/tests/ci_smoke.rs` (its "package is unimplemented" test became "package needs a target"), `.forgejo/workflows/ci.yaml` (`file` in the Linux apt list), `xtask/README.md` and `apps/fluxer/README.md`. - `--version` and `--out-dir` flags added: the release workflow builds before the tag exists, and the test must not write into `dist/`. - The release token is the job's automatic `GITHUB_TOKEN` secret (as in `ci.yaml` and the fork's release job), not a separately created secret. - The packaging test is part of the normal test run, so `cargo xtask ci` now does a release build on Linux and Windows and, on Linux, needs network once to fetch the two pinned tools. - The version only names the package; `fluxer --debug-info` still prints the crate version (0.1.0) and the commit. Changing that touches `debug_info.rs` (Task 14) and the version sent to the gateway, so it is left for a decision. Closes #25 🤖 Generated with [Claude Code](https://claude.com/claude-code)
feat(ui): generated theme tokens, fonts and icons
All checks were successful
ci / Windows (x64) (push) Successful in 22s
ci / Windows (x64) (pull_request) Successful in 15s
ci / Linux (x86_64) (push) Successful in 1m22s
ci / Linux (x86_64) (pull_request) Successful in 1m23s
64430a109d
- xtask gen-theme --fork <path>: parses the Electron app's colour system,
  globals and message-layout CSS into crates/fluxer-ui/src/theme/tokens.rs
  (hsl/hsla/rgb/hex, saturation-factor calc, var() fallbacks, color-mix in
  srgb and oklab; rem to px).
- fluxer-ui::theme: tokens (DARK), palette::Theme with iced's Base and
  widget catalogs, fonts (Fluxer Sans/Mono as TTF) and icons (Phosphor SVGs).
- Adds iced 0.14 to the workspace; deny.toml allows BSL-1.0 and CC0-1.0 and
  ignores three unmaintained-crate advisories that iced pulls in.

Refs #16

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Merge origin/foundation into task/16-ui-theme-fonts-icons
All checks were successful
ci / Windows (x64) (push) Successful in 1m32s
ci / Windows (x64) (pull_request) Successful in 38s
ci / Linux (x86_64) (push) Successful in 1m28s
ci / Linux (x86_64) (pull_request) Successful in 1m34s
897ebaae93
Conflicts in xtask (both sides implemented dispatch stubs: gen-theme here,
vendor-spec/spec-check on foundation) and Cargo.lock resolved as the union.

Refs #16

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Merge origin/foundation into task/16-ui-theme-fonts-icons
All checks were successful
ci / Windows (x64) (push) Successful in 44s
ci / Linux (x86_64) (push) Successful in 1m41s
ci / Windows (x64) (pull_request) Successful in 52s
ci / Linux (x86_64) (pull_request) Successful in 1m31s
301b889ef7
Mechanical conflicts: both sides added workspace dependencies (iced, futures-util)
and Cargo.lock entries.

Refs #16

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Refs #8

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
feat(core): store skeleton and session reducer
All checks were successful
ci / Windows (x64) (push) Successful in 42s
ci / Linux (x86_64) (push) Successful in 1m0s
ci / Windows (x64) (pull_request) Successful in 41s
ci / Linux (x86_64) (pull_request) Successful in 1m5s
cacedcbbf7
Refs #8

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Adds the gateway crate's dependencies (rustls, rustls-native-certs and zstd are
new to the workspace; Task 7 names tokio-tungstenite with rustls and zstd).

Refs #7

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Refs #7

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
fluxer_markdown_parser is pinned to the fork's main (ba98441b) over the anonymous
HTTPS URL: the fork is public, so the CI runners need no deploy key. cargo-deny
gets the git source and a per-crate AGPL-3.0-or-later licence exception.

Refs #19

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Refs #19

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Refs #7

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
feat(ui): rich text from the native Markdown parser
All checks were successful
ci / Linux (x86_64) (push) Successful in 4m44s
ci / Windows (x64) (push) Successful in 5m45s
ci / Windows (x64) (pull_request) Successful in 46s
ci / Linux (x86_64) (pull_request) Successful in 4m29s
72276377ff
parse_message runs the fork's parser with the message flags; blocks/spans turn the
AST into a span model (tested instead of pixels); rich_text draws it with iced rich
text spans, code blocks and block quotes, and emits LinkClicked / SpoilerToggled.

Refs #19

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Refs #7

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Refs #9

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Refs #11

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
feat(core): presence, users and ui state
All checks were successful
ci / Windows (x64) (push) Successful in 39s
ci / Windows (x64) (pull_request) Successful in 39s
ci / Linux (x86_64) (push) Successful in 1m7s
ci / Linux (x86_64) (pull_request) Successful in 1m3s
f4ce82e123
Refs #11

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
feat(gateway): websocket transport with zstd streaming
All checks were successful
ci / Windows (x64) (push) Successful in 57s
ci / Windows (x64) (pull_request) Successful in 48s
ci / Linux (x86_64) (push) Successful in 1m3s
ci / Linux (x86_64) (pull_request) Successful in 1m3s
e60021584a
Refs #7

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
feat(core): guild and channel reducers and sidebar selectors
All checks were successful
ci / Windows (x64) (pull_request) Successful in 45s
ci / Windows (x64) (push) Successful in 43s
ci / Linux (x86_64) (pull_request) Successful in 1m3s
ci / Linux (x86_64) (push) Successful in 1m10s
e753f32ec6
Refs #9

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Refs #10

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
feat(ui): avatars with cached image loading
Some checks failed
ci / Windows (x64) (pull_request) Successful in 1m11s
ci / Windows (x64) (push) Successful in 55s
ci / Linux (x86_64) (pull_request) Failing after 1m32s
ci / Linux (x86_64) (push) Has been cancelled
5c961c3ca6
fluxer-core: media_urls ports the web app's AvatarUtils/MediaProxyUtils
(avatar_url, guild_icon_url, default avatar index, size snapping,
buildMediaProxyURL).
fluxer-ui: images::ImageLoader (the crate's single I/O boundary) with the
per-URL Images state, and widgets::avatar (round clip, bundled default
avatars, presence dot from the theme tokens).
fluxer-platform: images::ImageCache (reqwest, PNG/JPEG/GIF/WebP decode,
disk cache under cache_dir/images/<sha256>, in-memory LRU) implementing
ImageLoader.

Refs #21

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
feat(core): messages, typing and read state
All checks were successful
ci / Windows (x64) (push) Successful in 44s
ci / Windows (x64) (pull_request) Successful in 44s
ci / Linux (x86_64) (push) Successful in 1m4s
ci / Linux (x86_64) (pull_request) Successful in 1m3s
38a4f01a14
Refs #10

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
docs(ui): mark illustrative snippets as text, not ignored doctests
All checks were successful
ci / Windows (x64) (push) Successful in 57s
ci / Windows (x64) (pull_request) Successful in 54s
ci / Linux (x86_64) (push) Successful in 1m35s
ci / Linux (x86_64) (pull_request) Successful in 1m43s
2d16dfbfec
The Linux CI screenshot step runs 'cargo test --workspace -- --ignored',
which compiles 'ignore' doctests; the images.rs fragment is not a
compilable item and failed there.

Refs #21

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Refs #13

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
# Conflicts:
#	crates/fluxer-core/README.md
#	crates/fluxer-core/src/app.rs
#	crates/fluxer-core/src/lib.rs
#	crates/fluxer-core/src/selectors/mod.rs
# Conflicts:
#	crates/fluxer-core/README.md
#	crates/fluxer-core/src/app.rs
#	crates/fluxer-core/src/lib.rs
#	crates/fluxer-core/src/selectors/mod.rs
feat(devserver): fixture-backed API and gateway for tests
All checks were successful
ci / Windows (x64) (pull_request) Successful in 1m11s
ci / Linux (x86_64) (pull_request) Successful in 1m20s
ci / Windows (x64) (push) Successful in 57s
ci / Linux (x86_64) (push) Successful in 1m10s
4c00cf12fd
Refs #13

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Refs #12

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
feat(platform,core): settings, keyring token and sqlite cache
Some checks failed
ci / Windows (x64) (push) Failing after 23s
ci / Linux (x86_64) (push) Failing after 56s
ci / Windows (x64) (pull_request) Failing after 13s
ci / Linux (x86_64) (pull_request) Failing after 54s
6eb27db77c
Core: PersistOp/PersistResult/LocalSettings in fluxer_core::persist, the
stored-token login (Loaded -> Discover -> Me -> ConnectGateway), cached READY
data marked App::stale until the live READY, and the CacheReady/CacheMessages/
SaveSettings writes.

Platform: Paths, settings.toml (defaults on missing, .bad on invalid), the
keyring token, the SQLite cache (rebuilt when corrupt or of another schema
version, in memory if the file is unusable) and Store, which ties them to
PersistOp for the runtime.

New dependencies: directories, keyring, rusqlite (bundled), toml, base64,
getrandom, tempfile (dev), keyring-core (dev, mock store).

Refs #12

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
chore(deps): bump num-bigint 0.4.7 -> 0.4.8 (0.4.7 was yanked)
All checks were successful
ci / Windows (x64) (push) Successful in 1m2s
ci / Linux (x86_64) (push) Successful in 1m20s
ci / Windows (x64) (pull_request) Successful in 51s
ci / Linux (x86_64) (pull_request) Successful in 1m18s
6b043c3a08
cargo deny (yanked = deny) failed on both runners for run 71/72: num-bigint 0.4.7,
a transitive dependency of keyring's Secret Service store, was yanked from crates.io.
Lockfile-only patch bump; no manifest change.

Refs #12

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
# Conflicts:
#	Cargo.lock
# Conflicts:
#	Cargo.lock
#	Cargo.toml
Refs #14

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
ApiClient::with_observer shows each exchange that got a response (no
headers); Connection::connect_with_tap shows each frame received and
sent. Both are off unless asked for.

Refs #14

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
feat(app): effect runtime, config, logging and record mode
Some checks failed
ci / Windows (x64) (pull_request) Failing after 19s
ci / Windows (x64) (push) Failing after 4s
ci / Linux (x86_64) (pull_request) Successful in 1m37s
ci / Linux (x86_64) (push) Successful in 1m43s
a2ce504001
Refs #14

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
ci(windows): free the build cache when the runner disk is low
All checks were successful
ci / Linux (x86_64) (push) Successful in 1m9s
ci / Windows (x64) (push) Successful in 1m33s
ci / Linux (x86_64) (pull_request) Successful in 1m12s
ci / Windows (x64) (pull_request) Successful in 1m21s
6ada26ce7e
The persistent Windows runner ran out of space on C: (os error 112). Log free
space, remove this project's own target dirs when it drops below 30 GB, and
turn off incremental compilation there. Also correct CLAUDE.md: one target dir
per worktree, and run the screenshot step locally before pushing.

Refs #51

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Merge remote-tracking branch 'origin/ci/51-windows-disk-space' into task/14-app-runtime
All checks were successful
ci / Linux (x86_64) (push) Successful in 1m49s
ci / Windows (x64) (push) Successful in 2m59s
ci / Linux (x86_64) (pull_request) Successful in 1m53s
ci / Windows (x64) (pull_request) Successful in 2m46s
d0f3c10f86
# Conflicts:
#	Cargo.lock
#	Cargo.toml
#	deny.toml
feat(ui): iced shell and login screen
All checks were successful
ci / Linux (x86_64) (push) Successful in 2m18s
ci / Windows (x64) (push) Successful in 3m51s
ci / Linux (x86_64) (pull_request) Successful in 2m9s
ci / Windows (x64) (pull_request) Successful in 3m38s
9e1bc0a481
fluxer_ui::run shows the runtime's snapshots in an iced window and sends
what the user does back as CoreEvents; the login screen covers the
instance field, credentials, the TOTP step and one text per AuthError
(captcha included). apps/fluxer launches it in place of the headless loop.

Refs #17

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
feat(ui): main three-pane layout
All checks were successful
ci / Linux (x86_64) (push) Successful in 2m12s
ci / Windows (x64) (push) Successful in 3m50s
ci / Linux (x86_64) (pull_request) Successful in 2m12s
ci / Windows (x64) (pull_request) Successful in 3m12s
f9183ef0ef
screens::main draws the guild rail, the resizable channel sidebar, the
channel header and the member list from main::model(&App), which reads
the store through the core selectors. Its messages map to UserActions.
New widgets: mention badge, tooltip card and resizable split. The shell
shows the main screen once logged in.

Refs #18

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
# Conflicts:
#	Cargo.lock
#	crates/fluxer-ui/Cargo.toml
#	crates/fluxer-ui/README.md
#	crates/fluxer-ui/src/lib.rs
#	crates/fluxer-ui/src/widgets/mod.rs
# Conflicts:
#	Cargo.lock
#	Cargo.toml
#	crates/fluxer-core/README.md
#	crates/fluxer-core/src/lib.rs
#	crates/fluxer-platform/Cargo.toml
#	crates/fluxer-platform/README.md
#	crates/fluxer-platform/src/lib.rs
#	crates/fluxer-ui/Cargo.toml
#	crates/fluxer-ui/README.md
#	crates/fluxer-ui/src/lib.rs
#	crates/fluxer-ui/src/widgets/mod.rs
Refs #22

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
extract-parity reads the fork's 21 settings search index files (117
entries) into docs/parity/settings.toml and merges on re-run;
parity-check validates status and owner and is a step of xtask ci.

Refs #22

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Refs #22

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
feat(ui): settings skeleton and settings parity list
All checks were successful
ci / Linux (x86_64) (push) Successful in 2m20s
ci / Windows (x64) (push) Successful in 3m59s
ci / Linux (x86_64) (pull_request) Successful in 2m19s
ci / Windows (x64) (pull_request) Successful in 3m32s
4deffe7c3f
screens::settings draws the web app's settings navigation (22 tabs in
four groups, from fluxer_core::settings_tabs) and the open tab's page:
Account, Appearance, Notifications and Companion apps panels are built,
every other section is a "Coming in sub-project N" placeholder whose
owner matches docs/parity/settings.toml. Regenerating the status API
token goes through PersistOp::RegenerateStatusToken, which the runtime
answers with PersistResult::StatusToken.

Refs #22

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
feat(ui): virtualised message list and composer
Some checks failed
ci / Linux (x86_64) (push) Successful in 5m38s
ci / Windows (x64) (push) Failing after 4m12s
ci / Linux (x86_64) (pull_request) Successful in 5m28s
ci / Windows (x64) (pull_request) Failing after 4m3s
a1c70f1036
The main screen's message view: widgets::message_list builds and lays out
only the rows that show (pure rules: layout, anchor_at/scroll_for_anchor,
ReachTop), keeps what is being read in place when older messages arrive,
asks for history near the top and shows "Jump to present" for messages
that arrive while scrolled up. message_row draws a message (avatar, role
colour, HH:MM, rich text, "(edited)", pending at 50 %, "Failed to send -
Retry"), day_separator the dated line, composer the growing text box with
Enter/Shift+Enter and the typing line. screens::main::messages ties them
to the store: model, view-local state, and update -> UserActions.

rich_text::rich_text no longer borrows its nodes and context for the
element's lifetime; main::Message gains Messages(..) and is turned into
UserActions by main::update.

Refs #20

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
ci(windows): name the DLLs a failed test binary cannot load
Some checks failed
ci / Windows (x64) (push) Failing after 3m30s
ci / Linux (x86_64) (push) Successful in 5m19s
ci / Windows (x64) (pull_request) Failing after 4m3s
ci / Linux (x86_64) (pull_request) Has been cancelled
5a7b2c3386
cargo reports a test binary that dies in the loader only as exit code
0xc0000135 (STATUS_DLL_NOT_FOUND). After a failed Windows job, read the PE
imports of every executable the cargo log blames for that code and print
the ones that do not resolve, plus the Windows edition, into the published
log.

Refs #20

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
test(ui): run the message view's renderer tests in their own binary, off Windows
All checks were successful
ci / Windows (x64) (push) Successful in 3m37s
ci / Linux (x86_64) (push) Successful in 5m30s
ci / Windows (x64) (pull_request) Successful in 4m5s
ci / Linux (x86_64) (pull_request) Successful in 5m12s
4febcd11ab
The Windows runner is a Windows Server 2025 Server Core install without
opengl32.dll. A test binary that builds an iced::Renderer links wgpu's GL
backend, imports that DLL statically, and is killed by the loader
(0xc0000135) before any test runs, even when it only asks for tiny-skia.

Move the five headless widget tests from tests/message_list.rs to
tests/message_view.rs, which is cfg(not(windows)); the ten layout, composer
and model tests keep running on Windows. Shared fixtures and helpers go to
tests/common. Linux runs all fifteen as before. Follow-up: #93.

Refs #20

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
# Conflicts:
#	crates/fluxer-ui/README.md
#	crates/fluxer-ui/src/app.rs
test(ui): offscreen screenshot tests
All checks were successful
ci / Windows (x64) (push) Successful in 3m49s
ci / Linux (x86_64) (push) Successful in 5m26s
ci / Windows (x64) (pull_request) Successful in 4m3s
ci / Linux (x86_64) (pull_request) Successful in 5m12s
480fde6c20
fluxer_ui::testing::render draws a view with iced's wgpu renderer into an offscreen
texture; assert_matches_golden compares it with fixtures/golden/<name>.png (0.5 % of
differing pixels allowed, UPDATE_GOLDEN=1 rewrites). Three screen tests: login, main
with the basic scenario, Settings -> Appearance. The goldens are drawn by lavapipe on
Ubuntu 22.04, which the Linux CI job now pins with WGPU_BACKEND and VK_ICD_FILENAMES.

Refs #24

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
build: AppImage and Windows packaging with release workflow
Some checks failed
ci / Linux (x86_64) (push) Successful in 7m7s
ci / Windows (x64) (push) Failing after 7m47s
ci / Linux (x86_64) (pull_request) Successful in 7m18s
ci / Windows (x64) (pull_request) Failing after 7m45s
1f68186f55
`cargo xtask package --target linux|windows` builds the release binary
and wraps it as dist/Fluxer-Native-<version>-linux-x86_64.AppImage
(appimagetool and the AppImage runtime are downloaded once and verified
against pinned SHA-256s) or dist/Fluxer-Native-<version>-win-x64.exe
(static CRT, icon and version resource), plus dist/SHA256SUMS.

release.yaml (workflow_dispatch, input `version`) builds both on the
runners into a draft release and publishes native-<version> with both
packages and SHA256SUMS once both builds succeeded.

Refs #25

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
Author
Owner

Independent review: Task 25 (packaging-release), commit 1f68186

Reviewed 480fde6..1f68186 only, read cold.

Local gate: FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci in a fresh worktree and target dir on Linux: green ("all steps passed"), including package_produces_appimage_on_linux, packaging_for_another_os_is_refused and package_needs_a_target. Nothing Windows-specific was run by me either.

Checks

  1. Plan test xtask/tests/package.rs::package_produces_appimage_on_linux exists and asserts what the plan says: file exists, is executable, --appimage-extract succeeds, squashfs-root/usr/bin/fluxer --debug-info exits 0 (plus AppRun --debug-info and SHA256SUMS). Linux-only via cfg.
  2. Interfaces: cargo xtask package --target linux -> dist/Fluxer-Native-<version>-linux-x86_64.AppImage, --target windows -> dist/Fluxer-Native-<version>-win-x64.exe + SHA256SUMS; version from the native-* tag or 0.0.0-dev+<sha>; appimagetool and runtime downloaded and SHA-256 verified before use. release.yaml is workflow_dispatch with input version, a Linux job, a Windows job and a final publish job creating native-<version> with both assets and SHA256SUMS. Names match the plan.
  3. Invariants: no change to fluxer-core or fluxer-ui; no secrets or tokens in code or assets; the workflow passes the token through the environment and masks it in the checkout log; cargo deny green with winresource.
  4. No Review Focus item belongs to this task.

Findings

  • minor .forgejo/workflows/release.yaml (prepare): the "already exists" check runs GET releases/tags/native-<version> before the stale drafts are deleted. As far as I know Forgejo returns a draft release from that endpoint to a token with write access, so a draft left by a failed run would make the rerun stop with "already exists, bump N" instead of the documented "the next run removes it and starts over". Not verified here (it needs a draft on the real repo). Fix: delete stale drafts first, or let the check ignore .draft == true.
  • minor .forgejo/workflows/release.yaml: the workflow has never run (plan step "dispatch once with 2026.1111.0 and verify assets" is not done). Only reading-level review was possible: draft creation without a tag, cross-job sums outputs, and tag creation on PATCH {"draft": false} are untested on this Forgejo. Needs one dispatch after merge; until then spec §9 item 10 is open. Should be a follow-up issue linked from this PR.
  • minor apps/fluxer/build.rs, xtask/src/package.rs (Windows path): unverified on Windows by implementer and by me. package_produces_portable_exe_on_windows is not ignored and builds with FLUXER_REQUIRE_ICON=1, so the Windows CI job goes red if the runner has no rc.exe, or if the cfg(windows) build-script code trips clippy -D warnings. I checked the winresource 0.1.34 API against the source (set_icon(&str), compile_for(&str), [package.metadata.winresource] is the table it reads): it matches. The Windows runner result on this commit is the only real evidence; the integrator must see it green before merging.
  • minor xtask/tests/package.rs: cargo xtask ci now does a release build and, on Linux, downloads two files from github.com when <target>/package/tools is empty (every run in a fresh CI container unless the target dir is cached). The hashes are pinned, so this is an availability dependency, not an integrity one.
  • minor apps/fluxer/Cargo.toml: winresource instead of the plan's winres, and [package.metadata.winresource] instead of [package.metadata.winres]. No other task consumes the name; acceptable, but the plan text should be updated.
  • minor xtask/src/package.rs: the release version only names the file; the binary reports crate version 0.1.0 and packages have no devserver feature, which Task 26 step 2 ("run the AppImage against the devserver") has to account for.

Verdict: APPROVE (0 blocking, 6 minor; local ci green on Linux). Conditions for the integrator: Windows runner green on this commit, and a follow-up issue for the first release.yaml dispatch.

## Independent review: Task 25 (packaging-release), commit 1f68186 Reviewed `480fde6..1f68186` only, read cold. **Local gate:** `FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci` in a fresh worktree and target dir on Linux: **green** ("all steps passed"), including `package_produces_appimage_on_linux`, `packaging_for_another_os_is_refused` and `package_needs_a_target`. Nothing Windows-specific was run by me either. **Checks** 1. Plan test `xtask/tests/package.rs::package_produces_appimage_on_linux` exists and asserts what the plan says: file exists, is executable, `--appimage-extract` succeeds, `squashfs-root/usr/bin/fluxer --debug-info` exits 0 (plus `AppRun --debug-info` and `SHA256SUMS`). Linux-only via `cfg`. 2. Interfaces: `cargo xtask package --target linux` -> `dist/Fluxer-Native-<version>-linux-x86_64.AppImage`, `--target windows` -> `dist/Fluxer-Native-<version>-win-x64.exe` + `SHA256SUMS`; version from the `native-*` tag or `0.0.0-dev+<sha>`; appimagetool and runtime downloaded and SHA-256 verified before use. `release.yaml` is `workflow_dispatch` with input `version`, a Linux job, a Windows job and a final publish job creating `native-<version>` with both assets and `SHA256SUMS`. Names match the plan. 3. Invariants: no change to `fluxer-core` or `fluxer-ui`; no secrets or tokens in code or assets; the workflow passes the token through the environment and masks it in the checkout log; `cargo deny` green with `winresource`. 4. No Review Focus item belongs to this task. **Findings** - **minor** `.forgejo/workflows/release.yaml` (prepare): the "already exists" check runs `GET releases/tags/native-<version>` *before* the stale drafts are deleted. As far as I know Forgejo returns a draft release from that endpoint to a token with write access, so a draft left by a failed run would make the rerun stop with "already exists, bump N" instead of the documented "the next run removes it and starts over". Not verified here (it needs a draft on the real repo). Fix: delete stale drafts first, or let the check ignore `.draft == true`. - **minor** `.forgejo/workflows/release.yaml`: the workflow has never run (plan step "dispatch once with 2026.1111.0 and verify assets" is not done). Only reading-level review was possible: draft creation without a tag, cross-job `sums` outputs, and tag creation on `PATCH {"draft": false}` are untested on this Forgejo. Needs one dispatch after merge; until then spec §9 item 10 is open. Should be a `follow-up` issue linked from this PR. - **minor** `apps/fluxer/build.rs`, `xtask/src/package.rs` (Windows path): unverified on Windows by implementer and by me. `package_produces_portable_exe_on_windows` is not ignored and builds with `FLUXER_REQUIRE_ICON=1`, so the Windows CI job goes red if the runner has no `rc.exe`, or if the `cfg(windows)` build-script code trips clippy `-D warnings`. I checked the `winresource` 0.1.34 API against the source (`set_icon(&str)`, `compile_for(&str)`, `[package.metadata.winresource]` is the table it reads): it matches. The Windows runner result on this commit is the only real evidence; the integrator must see it green before merging. - **minor** `xtask/tests/package.rs`: `cargo xtask ci` now does a release build and, on Linux, downloads two files from github.com when `<target>/package/tools` is empty (every run in a fresh CI container unless the target dir is cached). The hashes are pinned, so this is an availability dependency, not an integrity one. - **minor** `apps/fluxer/Cargo.toml`: `winresource` instead of the plan's `winres`, and `[package.metadata.winresource]` instead of `[package.metadata.winres]`. No other task consumes the name; acceptable, but the plan text should be updated. - **minor** `xtask/src/package.rs`: the release version only names the file; the binary reports crate version 0.1.0 and packages have no `devserver` feature, which Task 26 step 2 ("run the AppImage against the devserver") has to account for. **Verdict: APPROVE** (0 blocking, 6 minor; local ci green on Linux). Conditions for the integrator: Windows runner green on this commit, and a follow-up issue for the first `release.yaml` dispatch.
test(xtask): skip the packaged-exe launch check on hosts without opengl32.dll
Some checks failed
ci / Linux (x86_64) (pull_request) Successful in 7m11s
ci / Windows (x64) (pull_request) Successful in 7m44s
ci / Linux (x86_64) (push) Failing after 12s
ci / Windows (x64) (push) Successful in 6m47s
1d91f7985d
The Windows runner is Server Core, where the loader rejects the exe (#93).

Refs #25

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
charles manually merged commit 24e7c9d137 into foundation 2026-11-11 18:28:25 +00:00
Sign in to join this conversation.
No description provided.