enricobuehler
ac60db5410
ci / web (push) Successful in 50s
ci / docs-site (push) Successful in 53s
decky / build-publish (push) Successful in 22s
docker / build-push (--build-arg FEDORA_VERSION=44, ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora44-rpm) (push) Successful in 12s
docker / build-push (., web/Dockerfile, punktfunk-web) (push) Successful in 9s
docker / build-push (ci, ci/fedora-rpm.Dockerfile, punktfunk-fedora-rpm) (push) Successful in 8s
docker / build-push (ci, ci/rust-ci.Dockerfile, punktfunk-rust-ci) (push) Successful in 7s
docker / build-push (docs-site, docs-site/Dockerfile, punktfunk-docs) (push) Successful in 7s
ci / bench (push) Successful in 6m20s
docker / deploy-docs (push) Successful in 24s
windows-host / package (push) Successful in 8m17s
arch / build-publish (push) Successful in 12m27s
android / android (push) Successful in 13m42s
deb / build-publish (push) Successful in 14m38s
ci / rust (push) Successful in 19m11s
rpm / build-publish (43, bazzite, punktfunk-fedora-rpm) (push) Successful in 16m7s
rpm / build-publish (44, fedora-44, punktfunk-fedora44-rpm) (push) Successful in 15m52s
apple / swift (push) Has been cancelled
apple / screenshots (push) Has been cancelled
marker_appears_while_held_and_vanishes_after drove the PROCESS-GLOBAL registry and mutated XDG_RUNTIME_DIR mid-run — the punktfunk1 integration tests announce real sessions concurrently in the same test process, so whichever registered first became the primary and the marker carried its mode instead of the test's 2560x1440 (flaky on CI, green locally by timing). The registry gains insert/remove methods and rewrite() takes the target path, so the test now exercises the same end-to-end lifecycle (atomic write, primary retention, session count, removal) against a LOCAL registry and an explicit temp path — no env mutation, no shared state. Production behavior unchanged. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>