Task 26: Acceptance pass and documentation (#26) #100

Manually merged
charles merged 0 commits from task/26-acceptance into foundation 2026-11-11 18:28:26 +00:00
Owner

Stacked on: task/23-notifications, task/25-packaging-release (base of this branch's own commit: 23c10ce, which contains every task branch 1 to 25).

What this builds

  • docs/acceptance/2026-11-foundation.md: the ten criteria of the Foundation spec §9, each with its evidence (test names, CI run links, captures, measurements) and its status. Result: Foundation is not accepted yet. Met as far as an agent can check: 5, 7, 8. Not met in the code: 3 (nothing emits MarkRead, #60) and 9 (the app never starts the status server, #58). Waiting for Charles: 1, 2, 6, 10 and the live half of the others (#99). Criterion 4 has never been exercised with 5,000 messages (#97).
  • Plan, "Follow-ups": one entry per gap, each with its issue (F1 to F8, plus Charles's steps).
  • README.md: install, run, build from source, layout, documents.
  • Crate READMEs: forward references to finished tasks replaced by what is true now (apps/fluxer, fluxer-ui, fluxer-core, fluxer-platform, xtask).
  • CLAUDE.md: the stacked-PR rule (copied from main, where Charles put it), the branch-model line that still said the orchestrator merges, and what cargo xtask ci runs.
  • docs/screenshots/acceptance-devserver-main.png, acceptance-appimage-login.png: captures of the running client (debug build with --devserver; the packaged AppImage), fixture data only.

How it was tested

  • FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci green on the merged base (23c10ce) and on this branch.
  • cargo xtask package --target linux built the AppImage; --debug-info exits 0; it was started in a private headless sway with empty XDG directories and no session bus (nothing of the user's settings, keyring or desktop was touched) and shows the login screen.
  • fluxer --devserver in the same setup: logs in, READY with 2 guilds, the scenario's live message raises the unread dot and the mention badge.
  • Launch to first frame, by polling the compositor's screen: AppImage 0.26 to 0.29 s, release binary 0.22 s (warm cache, logged out).
  • Nothing was run against fluxer.forked.io or on a Windows desktop.

Deviations from the plan

  • Step 1 (CI from main on both runners): not possible, main has no code until the stack is merged. The record links the green runs of the two stacked branches instead.
  • Step 2: the live-instance and Windows checks are Charles's (#99, label question). --debug-info --time-startup was never implemented by any task (#96), so the cold-start time is an outside measurement.
  • No side-by-side PNGs with the Electron app: the Electron side needs a live session, and docs/screenshots/README.md keeps Electron images out of the repository.
  • Also touched, outside the task's file list: docs/screenshots/README.md (names the new captures), xtask/README.md and the plan itself (Step 3 asks for that).
  • New issues: #96, #97 (follow-up), #98 (bug: without a display the client panics instead of exiting 1), #99 (question).

Closes #26

🤖 Generated with Claude Code

Stacked on: task/23-notifications, task/25-packaging-release (base of this branch's own commit: 23c10ce, which contains every task branch 1 to 25). ## What this builds - `docs/acceptance/2026-11-foundation.md`: the ten criteria of the Foundation spec §9, each with its evidence (test names, CI run links, captures, measurements) and its status. **Result: Foundation is not accepted yet.** Met as far as an agent can check: 5, 7, 8. Not met in the code: 3 (nothing emits `MarkRead`, #60) and 9 (the app never starts the status server, #58). Waiting for Charles: 1, 2, 6, 10 and the live half of the others (#99). Criterion 4 has never been exercised with 5,000 messages (#97). - Plan, "Follow-ups": one entry per gap, each with its issue (F1 to F8, plus Charles's steps). - `README.md`: install, run, build from source, layout, documents. - Crate READMEs: forward references to finished tasks replaced by what is true now (`apps/fluxer`, `fluxer-ui`, `fluxer-core`, `fluxer-platform`, `xtask`). - `CLAUDE.md`: the stacked-PR rule (copied from `main`, where Charles put it), the branch-model line that still said the orchestrator merges, and what `cargo xtask ci` runs. - `docs/screenshots/acceptance-devserver-main.png`, `acceptance-appimage-login.png`: captures of the running client (debug build with `--devserver`; the packaged AppImage), fixture data only. ## How it was tested - `FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci` green on the merged base (23c10ce) and on this branch. - `cargo xtask package --target linux` built the AppImage; `--debug-info` exits 0; it was started in a private headless sway with empty XDG directories and no session bus (nothing of the user's settings, keyring or desktop was touched) and shows the login screen. - `fluxer --devserver` in the same setup: logs in, READY with 2 guilds, the scenario's live message raises the unread dot and the mention badge. - Launch to first frame, by polling the compositor's screen: AppImage 0.26 to 0.29 s, release binary 0.22 s (warm cache, logged out). - Nothing was run against fluxer.forked.io or on a Windows desktop. ## Deviations from the plan - Step 1 (CI from `main` on both runners): not possible, `main` has no code until the stack is merged. The record links the green runs of the two stacked branches instead. - Step 2: the live-instance and Windows checks are Charles's (#99, label `question`). `--debug-info --time-startup` was never implemented by any task (#96), so the cold-start time is an outside measurement. - No side-by-side PNGs with the Electron app: the Electron side needs a live session, and `docs/screenshots/README.md` keeps Electron images out of the repository. - Also touched, outside the task's file list: `docs/screenshots/README.md` (names the new captures), `xtask/README.md` and the plan itself (Step 3 asks for that). - New issues: #96, #97 (follow-up), #98 (bug: without a display the client panics instead of exiting 1), #99 (question). Closes #26 🤖 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
Refs #23

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
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: native mention notifications
All checks were successful
ci / Linux (x86_64) (push) Successful in 2m8s
ci / Linux (x86_64) (pull_request) Successful in 1m49s
ci / Windows (x64) (push) Successful in 2m55s
ci / Windows (x64) (pull_request) Successful in 2m33s
c0c5a4e629
fluxer-core decides which MESSAGE_CREATE dispatches notify (mention, @everyone
in a visible channel, DM; not while the channel is open in the focused window;
not when notifications are off) and emits Effect::Notify. fluxer-platform shows
it through notify-rust (freedesktop service on Linux, WinRT toast on Windows);
the fork's fluxer_linux_notifications crate is napi-only. The runtime runs the
notifier on a blocking worker and turns a click into SelectGuild/SelectChannel.

Refs #23

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>
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>
# Conflicts:
#	Cargo.lock
#	Cargo.toml
#	crates/fluxer-platform/Cargo.toml
#	crates/fluxer-platform/README.md
#	crates/fluxer-platform/src/lib.rs
#	deny.toml
docs: Foundation acceptance record
Some checks failed
ci / Linux (x86_64) (pull_request) Failing after 12s
ci / Linux (x86_64) (push) Failing after 11s
ci / Windows (x64) (push) Has been cancelled
ci / Windows (x64) (pull_request) Has been cancelled
f327ade9ba
Acceptance checklist of the Foundation spec §9 with evidence, the plan's
follow-ups for every criterion that cannot be ticked, install/run
instructions in the README, and READMEs/CLAUDE.md brought up to date.

Refs #26

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

Independent review of Task 26 (acceptance), commit f327ade

Scope: git diff 23c10ce..f327ade (12 files, docs only, no code or fixture change).

Checked

  1. Plan steps. Task 26 names no tests. The record covers all ten §9 criteria with the spec's wording. All 68 test names it cites as evidence exist as fns in the tree; the counts it gives are right (21 tests in rich_text.rs, 18 in status-api/tests/server.rs, 13 in core/tests/notifications.rs, parity list 119 = 1 done + 118 planned). Step 3 is done: "Follow-ups" F1 to F8 plus Charles's steps, and the result is "not accepted yet", not "done". Step 4: commit message, Refs #26 and the trailer are as required.
  2. Interfaces: the task has no Interfaces block. Nothing consumed by other tasks changed.
  3. Invariants: no code touched. No token-shaped string in the diff; the two PNGs show fixture data only (login form with the default instance; demo user "Charlie", "Ada L."). The "not met" claims hold: apps/fluxer/Cargo.toml has no fluxer-status-api dependency (criterion 9), UserAction::MarkRead is handled in fluxer-core but emitted nowhere outside tests (criterion 3), no --time-startup exists.
  4. Review Focus: none belongs to this task. The record points at the tests for Focus 2 and 4 correctly.
  5. FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci in a fresh worktree and target dir: green ("all steps passed", 110 test binaries ok). Remote runs not checked.

Also verified: 23c10ce contains every origin/task/1..25 branch; issues #54, #55, #58, #60, #93, #96, #97, #98, #99 exist, are open and carry the labels the contract asks for; the CLAUDE.md stacked-PR paragraph is identical to the one on main; the README's apt package list matches release.yaml; --out-dir exists in xtask package; --devserver uses no real persistence (runtime.rs).

Findings

  • minor docs/screenshots/: the plan asks for side-by-side images with the Electron app for login, main and settings. None is committed. The record explains why and hands it to Charles (#99 step 5), so criterion 2 is correctly left open, but the task's file list is not fulfilled.
  • minor docs/screenshots/acceptance-devserver-main.png: offered as the native side of the criterion 2 comparison, but it shows the DM home with an empty message area: no channel list and no message view. It is evidence for the badge of criterion 3 only. A capture with a guild channel selected would serve criterion 2.
  • minor docs/acceptance/2026-11-foundation.md, criterion 10: the figures (0.26 to 0.29 s) are warm starts of a logged-out client measured from outside, not the cold start the spec asks for. The record says so itself; the sentence "the 1 s budget holds with a wide margin" should not be read as the criterion being measured. Stays open under #96.
  • minor Step 1 (CI from main on both runners) and the Windows half of Step 2 were not done; both are recorded as open, with run links for the stacked branches only. Runs 83, 84, 99, 100 were not re-checked by me.
  • minor CLAUDE.md: the branch-model line now says Charles merges task PRs into foundation instead of the orchestrator. It agrees with the stacked-PR paragraph Charles put on main, but it is a change of a rule about who merges, so Charles should confirm it when merging.
  • minor Issue #40 is flagged in the record as probably done but left open; someone has to close it or say what is missing.

Verdict: approve. No blocking finding; local ci green. Foundation itself remains not accepted, as the record states.

## Independent review of Task 26 (acceptance), commit `f327ade` Scope: `git diff 23c10ce..f327ade` (12 files, docs only, no code or fixture change). **Checked** 1. Plan steps. Task 26 names no tests. The record covers all ten §9 criteria with the spec's wording. All 68 test names it cites as evidence exist as `fn`s in the tree; the counts it gives are right (21 tests in `rich_text.rs`, 18 in `status-api/tests/server.rs`, 13 in `core/tests/notifications.rs`, parity list 119 = 1 done + 118 planned). Step 3 is done: "Follow-ups" F1 to F8 plus Charles's steps, and the result is "not accepted yet", not "done". Step 4: commit message, `Refs #26` and the trailer are as required. 2. Interfaces: the task has no Interfaces block. Nothing consumed by other tasks changed. 3. Invariants: no code touched. No token-shaped string in the diff; the two PNGs show fixture data only (login form with the default instance; demo user "Charlie", "Ada L."). The "not met" claims hold: `apps/fluxer/Cargo.toml` has no `fluxer-status-api` dependency (criterion 9), `UserAction::MarkRead` is handled in `fluxer-core` but emitted nowhere outside tests (criterion 3), no `--time-startup` exists. 4. Review Focus: none belongs to this task. The record points at the tests for Focus 2 and 4 correctly. 5. `FLUXER_SCREENSHOT_TESTS=1 cargo xtask ci` in a fresh worktree and target dir: **green** ("all steps passed", 110 test binaries ok). Remote runs not checked. Also verified: `23c10ce` contains every `origin/task/1..25` branch; issues #54, #55, #58, #60, #93, #96, #97, #98, #99 exist, are open and carry the labels the contract asks for; the CLAUDE.md stacked-PR paragraph is identical to the one on `main`; the README's apt package list matches `release.yaml`; `--out-dir` exists in `xtask package`; `--devserver` uses no real persistence (`runtime.rs`). **Findings** - **minor** `docs/screenshots/`: the plan asks for side-by-side images with the Electron app for login, main and settings. None is committed. The record explains why and hands it to Charles (#99 step 5), so criterion 2 is correctly left open, but the task's file list is not fulfilled. - **minor** `docs/screenshots/acceptance-devserver-main.png`: offered as the native side of the criterion 2 comparison, but it shows the DM home with an empty message area: no channel list and no message view. It is evidence for the badge of criterion 3 only. A capture with a guild channel selected would serve criterion 2. - **minor** `docs/acceptance/2026-11-foundation.md`, criterion 10: the figures (0.26 to 0.29 s) are warm starts of a logged-out client measured from outside, not the cold start the spec asks for. The record says so itself; the sentence "the 1 s budget holds with a wide margin" should not be read as the criterion being measured. Stays open under #96. - **minor** Step 1 (CI from `main` on both runners) and the Windows half of Step 2 were not done; both are recorded as open, with run links for the stacked branches only. Runs 83, 84, 99, 100 were not re-checked by me. - **minor** `CLAUDE.md`: the branch-model line now says Charles merges task PRs into `foundation` instead of the orchestrator. It agrees with the stacked-PR paragraph Charles put on `main`, but it is a change of a rule about who merges, so Charles should confirm it when merging. - **minor** Issue #40 is flagged in the record as probably done but left open; someone has to close it or say what is missing. **Verdict: approve.** No blocking finding; local ci green. Foundation itself remains not accepted, as the record states.
ci: re-run the runners for the acceptance branch
Some checks failed
ci / Linux (x86_64) (pull_request) Failing after 11s
ci / Linux (x86_64) (push) Failing after 14s
ci / Windows (x64) (pull_request) Successful in 6m49s
ci / Windows (x64) (push) Successful in 6m50s
402cb49d09
The Linux job of runs 101 and 102 failed 12 s in, before the step that installs
curl, so no log was published; the tree is unchanged and cargo xtask ci passes locally.

Refs #26

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
ci: re-run the Linux runner after the DNS outage (#101)
Some checks failed
ci / Linux (x86_64) (pull_request) Successful in 7m27s
ci / Windows (x64) (pull_request) Successful in 7m53s
ci / Linux (x86_64) (push) Failing after 15s
ci / Windows (x64) (push) Successful in 6m51s
8b37da4897
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
charles manually merged commit 24e7c9d137 into foundation 2026-11-11 18:28:26 +00:00
Sign in to join this conversation.
No description provided.