Task 14: apps/fluxer runtime (effect executor, config, logging) (#14) #50

Manually merged
charles merged 0 commits from task/14-app-runtime into foundation 2026-11-11 18:28:11 +00:00
Owner

Stacked on: task/7-gateway-machine-transport, task/12-platform-persistence, task/13-devserver (merged into this branch at 3aae67d; the diff against foundation includes them until they land).

What was built

apps/fluxer is now a library plus a thin binary:

  • runtime.rs — Runtime::new(config, paths), start(self) -> (mpsc::Sender<CoreEvent>, mpsc::Receiver<CoreEvent>, Handle). A tokio task owns the App, applies events and executes effects in order: Api via ApiClient (GETs Discover/Me/FetchMessages tried 3 times with 0.5 s / 1 s backoff on transport errors, 5xx and short rate limits; everything else once -> EffectFailed), gateway via Connection (one task per connection; retries the first socket with backoff), Persist via fluxer_platform::Store on a blocking worker (strictly ordered, consecutive SaveSettings coalesced), Schedule via tokio::time::sleep, OpenUrl via the system opener, Notify logged until Task 23. AppSnapshot = Arc<App> is published on a watch channel once per batch of events (Handle::snapshots()), so the store is copied at most once per batch.
  • config.rs — --instance/FLUXER_INSTANCE, FLUXER_LOG, --devserver [scenario], --record <dir>, --debug-info.
  • logging.rs — stderr + daily-rotated files in paths.log_dir (tracing-appender), EnvFilter, panic hook writing panic-<ts>.txt.
  • debug_info.rs — version, git sha (new build.rs), OS, wgpu adapters (name, backend, driver), paths.
  • record.rs — gateway.jsonl / rest.jsonl with authorization, token, *_token, email, password, new_password, phone, ticket values replaced by "<redacted>".
  • main.rs — headless until Task 17: starts the runtime, logs session changes, stops cleanly on Ctrl-C.

How it was tested

  • apps/fluxer/tests/runtime.rs (in-process devserver, no keyring, temp dirs): runtime_logs_in_against_devserver_and_reaches_ready, record_mode_redacts_tokens, plus ui_events_fetch_history_and_send_a_message, logout_disconnects_and_returns_to_the_login_screen, start_outside_a_tokio_runtime_brings_its_own.
  • 30 unit tests: config parsing, redaction, retry policy and timing (paused clock), error/state mapping, persist worker ordering and coalescing, panic report, debug-info rendering.
  • Manual: cargo run -p fluxer -- --devserver --record <dir> (reaches READY, 2 guilds, Ctrl-C exits 0, recording has no token), --debug-info, --version, bad --instance.
  • cargo xtask ci green locally (Linux). cargo clippy/test -p fluxer --no-default-features also green.

Deviations from the plan / things to look at

  • Touches fluxer-api and fluxer-gateway (separate commit 683bfd8): ApiClient::with_observer and Connection::connect_with_tap. Record mode needs the raw frames and bodies, which neither crate exposed (GatewayEvent is not even Serialize). Both hooks are opt-in and carry no headers.
  • Extra files: src/lib.rs (integration tests cannot import a bin-only crate) and build.rs (git sha).
  • Second element of start's tuple: the plan does not say what the Receiver<CoreEvent> yields. Here it is every event the store reduced, in order (for UiMessage::Core); advisory, bounded (1024), skipped when full or dropped.
  • --devserver is hermetic: Store always uses the real OS keyring outside its own unit tests, so devserver mode (and therefore the tests) uses in-memory persistence instead of settings file/keyring/cache. fluxer-devserver is an optional dependency behind the default-on devserver feature; Task 25 should package with --no-default-features.
  • --instance/FLUXER_INSTANCE is saved to settings (the keyring entry is per instance host and Store derives it from the settings file); the cache of the previous instance is cleared on a switch.
  • Stale answers are dropped: REST answers from a session with another token and events from an earlier gateway connection never reach the store.
  • Message writes (SendMessage/EditMessage/DeleteMessage) go through one FIFO so two quick sends cannot swap; other requests run concurrently.
  • Workspace deps added (named by the task): tracing-appender, tracing-subscriber, wgpu = 27 (the version iced 0.14 uses on the Task 16 branch). deny.toml: CC0-1.0 (hexf-parse via naga) and RUSTSEC-2024-0436 (paste via metal), the same two entries Task 16 adds; expect a mechanical conflict there. The dependency merges needed toml = "1" with default features (platform writes TOML, devserver only parses).
  • Not wired, not in this task's interface: UserAction::RegenerateStatusToken (core has no event to receive a generated token) and starting fluxer-status-api; headers are not recorded at all rather than recorded with Authorization redacted.
  • Record redaction is by member name; code is deliberately not redacted (it is the API's error-code member).

Closes #14

🤖 Generated with Claude Code

Stacked on: task/7-gateway-machine-transport, task/12-platform-persistence, task/13-devserver (merged into this branch at 3aae67d; the diff against `foundation` includes them until they land). ## What was built `apps/fluxer` is now a library plus a thin binary: - `runtime.rs` — `Runtime::new(config, paths)`, `start(self) -> (mpsc::Sender<CoreEvent>, mpsc::Receiver<CoreEvent>, Handle)`. A tokio task owns the `App`, applies events and executes effects in order: `Api` via `ApiClient` (GETs `Discover`/`Me`/`FetchMessages` tried 3 times with 0.5 s / 1 s backoff on transport errors, 5xx and short rate limits; everything else once -> `EffectFailed`), gateway via `Connection` (one task per connection; retries the first socket with backoff), `Persist` via `fluxer_platform::Store` on a blocking worker (strictly ordered, consecutive `SaveSettings` coalesced), `Schedule` via `tokio::time::sleep`, `OpenUrl` via the system opener, `Notify` logged until Task 23. `AppSnapshot = Arc<App>` is published on a `watch` channel once per batch of events (`Handle::snapshots()`), so the store is copied at most once per batch. - `config.rs` — `--instance`/`FLUXER_INSTANCE`, `FLUXER_LOG`, `--devserver [scenario]`, `--record <dir>`, `--debug-info`. - `logging.rs` — stderr + daily-rotated files in `paths.log_dir` (`tracing-appender`), `EnvFilter`, panic hook writing `panic-<ts>.txt`. - `debug_info.rs` — version, git sha (new `build.rs`), OS, wgpu adapters (name, backend, driver), paths. - `record.rs` — `gateway.jsonl` / `rest.jsonl` with `authorization`, `token`, `*_token`, `email`, `password`, `new_password`, `phone`, `ticket` values replaced by `"<redacted>"`. - `main.rs` — headless until Task 17: starts the runtime, logs session changes, stops cleanly on Ctrl-C. ## How it was tested - `apps/fluxer/tests/runtime.rs` (in-process devserver, no keyring, temp dirs): `runtime_logs_in_against_devserver_and_reaches_ready`, `record_mode_redacts_tokens`, plus `ui_events_fetch_history_and_send_a_message`, `logout_disconnects_and_returns_to_the_login_screen`, `start_outside_a_tokio_runtime_brings_its_own`. - 30 unit tests: config parsing, redaction, retry policy and timing (paused clock), error/state mapping, persist worker ordering and coalescing, panic report, debug-info rendering. - Manual: `cargo run -p fluxer -- --devserver --record <dir>` (reaches READY, 2 guilds, Ctrl-C exits 0, recording has no token), `--debug-info`, `--version`, bad `--instance`. - `cargo xtask ci` green locally (Linux). `cargo clippy/test -p fluxer --no-default-features` also green. ## Deviations from the plan / things to look at - **Touches `fluxer-api` and `fluxer-gateway`** (separate commit 683bfd8): `ApiClient::with_observer` and `Connection::connect_with_tap`. Record mode needs the raw frames and bodies, which neither crate exposed (`GatewayEvent` is not even `Serialize`). Both hooks are opt-in and carry no headers. - **Extra files**: `src/lib.rs` (integration tests cannot import a bin-only crate) and `build.rs` (git sha). - **Second element of `start`'s tuple**: the plan does not say what the `Receiver<CoreEvent>` yields. Here it is every event the store reduced, in order (for `UiMessage::Core`); advisory, bounded (1024), skipped when full or dropped. - **`--devserver` is hermetic**: `Store` always uses the real OS keyring outside its own unit tests, so devserver mode (and therefore the tests) uses in-memory persistence instead of settings file/keyring/cache. `fluxer-devserver` is an optional dependency behind the default-on `devserver` feature; Task 25 should package with `--no-default-features`. - **`--instance`/`FLUXER_INSTANCE` is saved to settings** (the keyring entry is per instance host and `Store` derives it from the settings file); the cache of the previous instance is cleared on a switch. - **Stale answers are dropped**: REST answers from a session with another token and events from an earlier gateway connection never reach the store. - **Message writes (`SendMessage`/`EditMessage`/`DeleteMessage`) go through one FIFO** so two quick sends cannot swap; other requests run concurrently. - **Workspace deps added** (named by the task): `tracing-appender`, `tracing-subscriber`, `wgpu = 27` (the version iced 0.14 uses on the Task 16 branch). `deny.toml`: `CC0-1.0` (hexf-parse via naga) and `RUSTSEC-2024-0436` (paste via metal), the same two entries Task 16 adds; expect a mechanical conflict there. The dependency merges needed `toml = "1"` with default features (platform writes TOML, devserver only parses). - **Not wired, not in this task's interface**: `UserAction::RegenerateStatusToken` (core has no event to receive a generated token) and starting `fluxer-status-api`; headers are not recorded at all rather than recorded with `Authorization` redacted. - Record redaction is by member name; `code` is deliberately not redacted (it is the API's error-code member). Closes #14 🤖 Generated with [Claude Code](https://claude.com/claude-code)
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>
Refs #7

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(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>
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>
Author
Owner

Independent review: Task 14 (app-runtime) at a2ce504

Scope: git diff 3aae67d..origin/task/14-app-runtime. Read cold; the implementer's notes were verified, not trusted.

Checks

  1. Plan tests: runtime_logs_in_against_devserver_and_reaches_ready waits on the snapshot for Auth::LoggedIn plus non-empty guilds, then GatewayState::Ready. record_mode_redacts_tokens reads the live session token (asserts it starts with flx_), asserts the recording is non-empty, holds the login exchange and READY, and that no file contains the token or the fixture e-mail. Neither is vacuous. Both pass.
  2. Interfaces: Runtime::new(config: Config, paths: Paths) -> Runtime, fn start(self) -> (mpsc::Sender<CoreEvent>, mpsc::Receiver<CoreEvent>, Handle), AppSnapshot = Arc<App> over watch (Handle::snapshots()), Config with --instance/FLUXER_INSTANCE, FLUXER_LOG, --devserver [scenario], --record <dir>, --debug-info all exist as written. GET retry is 3 tries (0.5 s, 1 s), unit-tested with paused time. The fluxer-api / fluxer-gateway changes are additive (with_observer, connect_with_tap); existing signatures are untouched.
  3. Invariants: fluxer-core and fluxer-ui are not touched. No non-test unwrap/panic on server data (the one expect is on the DEFAULT_INSTANCE constant, with a test). No real tokens in code or fixtures; logs name persist ops without their payloads.
  4. Review Focus: no item belongs to this task.
  5. cargo xtask ci in the review worktree (Linux): green (fmt, clippy, deny, tests; screenshot step skipped as configured). Also ran: cargo clippy -p fluxer --no-default-features --all-targets -- -D warnings clean; fluxer --debug-info prints version, sha, OS, adapters, backend, paths; fluxer --devserver --record <dir> reaches READY, writes no settings/keyring/cache, and the recording contains no flx_ string. Windows was not run here.

Findings (none blocking)

  • minor apps/fluxer/src/runtime.rs (shutdown): writes_task.abort() drops queued or in-flight message send/edit/delete requests on shutdown, while Handle::shutdown is documented as waiting for queued writes. A message sent just before quitting can be lost without the store hearing about it. Consider draining with the same 5 s timeout as persistence.
  • minor apps/fluxer/src/runtime.rs (Persistence::execute): a failed persist op is only logged; no event reaches the store. The plan says everything else fails once into EffectFailed. A token that could not be saved to the keyring is invisible to the user until the next start.
  • minor apps/fluxer/src/runtime.rs (switch_instance): --instance / FLUXER_INSTANCE rewrites settings.toml and empties the previous instance's cache before login. A one-off environment variable therefore changes the saved instance permanently. The cache is disposable per spec, so not data loss, but this is a behaviour decision the plan did not make; worth a question or a note for Task 17.
  • minor apps/fluxer/src/record.rs: session_id and auth_session_id_hash are recorded as is, and Authorization is omitted instead of written as "<redacted>". The plan's list (Authorization, token, email) is covered; scrub the session identifiers too before recordings of a real session become fixtures.
  • minor apps/fluxer/src/runtime.rs (retry_get): stacks on fluxer-api's own retry-once on 429, so a rate-limited GET can be sent up to 6 times.
  • minor process: UserAction::RegenerateStatusToken (core comment says the runtime generates it), Effect::Notify and starting fluxer-status-api are not wired. Per CLAUDE.md these need follow-up issues linked from this PR before merge. The cross-crate touch (fluxer-api, fluxer-gateway) is in its own commit and opt-in, but the plan did not name it.

Verdict: APPROVE (0 blocking, 6 minor; local CI green on Linux, Windows left to the integrator).

## Independent review: Task 14 (app-runtime) at a2ce504 Scope: `git diff 3aae67d..origin/task/14-app-runtime`. Read cold; the implementer's notes were verified, not trusted. **Checks** 1. Plan tests: `runtime_logs_in_against_devserver_and_reaches_ready` waits on the snapshot for `Auth::LoggedIn` plus non-empty guilds, then `GatewayState::Ready`. `record_mode_redacts_tokens` reads the live session token (asserts it starts with `flx_`), asserts the recording is non-empty, holds the login exchange and READY, and that no file contains the token or the fixture e-mail. Neither is vacuous. Both pass. 2. Interfaces: `Runtime::new(config: Config, paths: Paths) -> Runtime`, `fn start(self) -> (mpsc::Sender<CoreEvent>, mpsc::Receiver<CoreEvent>, Handle)`, `AppSnapshot = Arc<App>` over `watch` (`Handle::snapshots()`), `Config` with `--instance`/`FLUXER_INSTANCE`, `FLUXER_LOG`, `--devserver [scenario]`, `--record <dir>`, `--debug-info` all exist as written. GET retry is 3 tries (0.5 s, 1 s), unit-tested with paused time. The `fluxer-api` / `fluxer-gateway` changes are additive (`with_observer`, `connect_with_tap`); existing signatures are untouched. 3. Invariants: `fluxer-core` and `fluxer-ui` are not touched. No non-test `unwrap`/`panic` on server data (the one `expect` is on the `DEFAULT_INSTANCE` constant, with a test). No real tokens in code or fixtures; logs name persist ops without their payloads. 4. Review Focus: no item belongs to this task. 5. `cargo xtask ci` in the review worktree (Linux): **green** (fmt, clippy, deny, tests; screenshot step skipped as configured). Also ran: `cargo clippy -p fluxer --no-default-features --all-targets -- -D warnings` clean; `fluxer --debug-info` prints version, sha, OS, adapters, backend, paths; `fluxer --devserver --record <dir>` reaches READY, writes no settings/keyring/cache, and the recording contains no `flx_` string. Windows was not run here. **Findings** (none blocking) - **minor** `apps/fluxer/src/runtime.rs` (shutdown): `writes_task.abort()` drops queued or in-flight message send/edit/delete requests on shutdown, while `Handle::shutdown` is documented as waiting for queued writes. A message sent just before quitting can be lost without the store hearing about it. Consider draining with the same 5 s timeout as persistence. - **minor** `apps/fluxer/src/runtime.rs` (`Persistence::execute`): a failed persist op is only logged; no event reaches the store. The plan says everything else fails once into `EffectFailed`. A token that could not be saved to the keyring is invisible to the user until the next start. - **minor** `apps/fluxer/src/runtime.rs` (`switch_instance`): `--instance` / `FLUXER_INSTANCE` rewrites `settings.toml` and empties the previous instance's cache before login. A one-off environment variable therefore changes the saved instance permanently. The cache is disposable per spec, so not data loss, but this is a behaviour decision the plan did not make; worth a `question` or a note for Task 17. - **minor** `apps/fluxer/src/record.rs`: `session_id` and `auth_session_id_hash` are recorded as is, and `Authorization` is omitted instead of written as `"<redacted>"`. The plan's list (`Authorization`, `token`, `email`) is covered; scrub the session identifiers too before recordings of a real session become fixtures. - **minor** `apps/fluxer/src/runtime.rs` (`retry_get`): stacks on `fluxer-api`'s own retry-once on 429, so a rate-limited GET can be sent up to 6 times. - **minor** process: `UserAction::RegenerateStatusToken` (core comment says the runtime generates it), `Effect::Notify` and starting `fluxer-status-api` are not wired. Per CLAUDE.md these need `follow-up` issues linked from this PR before merge. The cross-crate touch (`fluxer-api`, `fluxer-gateway`) is in its own commit and opt-in, but the plan did not name it. **Verdict: APPROVE** (0 blocking, 6 minor; local CI green on Linux, Windows left to the integrator).
Author
Owner

Finalizer: branch head a2ce504 is up to date with foundation, cargo xtask ci passes locally and the Linux runner is green. Both Windows jobs (runs 75, 76) failed because the runner disk is full (os error 112), before any code was tested; see #51. Not labelled ready-to-merge until a Windows run is green; re-run the Windows job once space is freed.

Finalizer: branch head a2ce504 is up to date with `foundation`, `cargo xtask ci` passes locally and the Linux runner is green. Both Windows jobs (runs 75, 76) failed because the runner disk is full (os error 112), before any code was tested; see #51. Not labelled `ready-to-merge` until a Windows run is green; re-run the Windows job once space is freed.
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
charles manually merged commit 24e7c9d137 into foundation 2026-11-11 18:28:11 +00:00
Sign in to join this conversation.
No description provided.