66 Commits
Author SHA1 Message Date
FredApps 2c06746765 ci: pin nested shared gate actions to reviewed revision (#289) 2026-11-19 13:34:26 +07:00
FredApps 139cccb97f ci: pin native runner fixture to production Rust 1.100.0 (#288) 2026-11-19 13:10:45 +07:00
FredApps 438b785997 ci: validate native Cargo runner semantics with tiny fixtures (#287)
* ci: validate native Cargo runner semantics with tiny fixtures

* test: separate doctest runner context without weakening allowlist
2026-11-19 13:02:16 +07:00
FredApps 5e475d5d1e ci: audit implicit-host FreeBSD runtime planned-unit reuse (#286) 2026-11-19 12:46:00 +07:00
FredApps a44bf91fb5 ci: measure planned FreeBSD prebuild target projection without compiling (#285) 2026-11-19 12:33:12 +07:00
FredApps 0be61baefd ci: measure native bootstrap while preserving workspace features (#284)
* ci: guard a bounded native geometry measurement with exact planned closure

* ci: preserve workspace features while measuring native browser bootstrap
2026-11-19 12:20:14 +07:00
FredApps b5c6f5913e ci: compare planned Photo units on native FreeBSD without builds (#283)
* ci: compare planned Photo units on native FreeBSD without builds

* ci: verify transferred source without overriding Git ownership guard
2026-11-19 11:59:33 +07:00
FredApps cccebf20a1 ci: compare pinned Photo resolved features without builds (#282) 2026-11-19 11:43:25 +07:00
FredApps dbe0fbf6af ci: inventory pinned Photo targets without building (#281) 2026-11-19 11:34:22 +07:00
FredApps 2317dca7b2 test(ci): prototype bounded libtest subprocess fixtures (#280) 2026-11-19 11:01:46 +07:00
FredApps 21a58ac409 ci(freebsd): measure bounded complete target toolchain setup (#279) 2026-11-19 10:44:00 +07:00
FredApps 254d31bf25 Merge pull request #278 from FredApps/ci/778-freebsd-download-diagnostic
ci(freebsd): add bounded verified-download phase diagnostic
2026-11-19 10:13:03 +07:00
FredApps 9fe0627fb4 ci(freebsd): add bounded verified-download diagnostic 2026-11-19 04:01:00 +01:00
FredApps 3324beedeb Merge pull request #277 from FredApps/fix/778-freebsd-cross-cache-target
fix(freebsd): preserve and isolate cross-target Cargo caches
2026-11-19 09:51:22 +07:00
FredApps 2261f42f01 Merge current main for combined short-suite validation 2026-11-19 03:46:15 +01:00
FredApps fa34e3106d fix(freebsd): preserve and isolate cross-target Cargo caches 2026-11-19 03:42:06 +01:00
FredApps 1db5954800 Merge pull request #276 from FredApps/fix/778-freebsd-download-retries
fix(freebsd): bound verified sysroot download retries
2026-11-19 09:29:53 +07:00
FredApps c0e799e2a0 fix(freebsd): bound release-file download retries 2026-11-19 03:23:37 +01:00
FredApps 7d4597abb2 Merge pull request #263 from ephraimm/gate-artifact-upload
gate: optional artifact upload
2026-11-19 07:44:35 +07:00
FredApps 71996d6a1d Merge pull request #269 from FredApps/ci/freebsd-resource-evidence-778
ci(freebsd): capture bounded resource evidence after failures
2026-11-18 19:09:12 +07:00
FredApps cbcc13c62a Merge pull request #267 from FredApps/ci/freebsd-host-disk-778
freebsd: reclaim unused hosted toolchains before VM startup
2026-11-18 16:21:14 +07:00
FredApps 00cf4bb817 Merge pull request #258 from benandez/fix/249-windows-rust-cache
fix(rust-cache): pin v2.9.1 so Windows jobs save their cache
2026-11-17 16:51:08 +01:00
FredApps 5b4eeb2323 fix(freebsd): fail closed if the aarch64 job has no CARGO_BUILD_TARGET
The 15 November scheduled dry-run wrote x86_64 archives in the aarch64
job because an unset PKG_CONFIG_PATH in the cross env heredoc left
CARGO_BUILD_TARGET unset, and FreeBSD sh did not abort. #242 already
stops the heredoc from expanding that unset variable. This checks that
the env file actually exported the target, and that the build and
package steps still have it, so a similar miss fails before packaging.
2026-11-15 12:17:00 +01:00
FredApps 78c3c88191 Merge pull request #234 from storytold/fix/cut-release-minor-bump
cut_release: a minor bump follows stale path versions and versioned lock names
2026-11-15 11:24:50 +01:00
FredApps 9f9f16987c ci: never cancel a running main-branch Sonar scan (#151)
* ci: preserve every main-branch Sonar scan

* ci: never cancel a running main Sonar scan, as the app repos do

Per-run concurrency groups let main scans run side by side, so an older
commit's analysis can reach SonarCloud after a newer one. Keep one group
per ref and only stop cancelling on main, matching every app repo's
sonarcloud.yml.
2026-11-14 21:38:10 +01:00
FredApps f76646c68b Merge pull request #198 from storytold/ci/opt-in-sccache
gate: opt-in sccache; sonarcloud: free disk space in the background in the archive build
2026-11-13 22:08:20 +01:00
FredApps debd222436 Merge pull request #155 from storytold/fix/house-rules-preserve-local-text
Preserve local instructions when updating house rules
2026-11-13 21:24:00 +01:00
FredApps 82834fe754 Merge pull request #105 from FredApps/fix/shared-appimage-cli-check
Run AppImage CLI regression checks in shared packaging lint
2026-11-13 21:10:46 +01:00
FredApps cb96afc6e2 Merge pull request #229 from storytold/sonarcloud/bin-exe-paths
sonarcloud: let shard tests find workspace binaries by their build path
2026-11-13 21:10:36 +01:00
FredApps ce1d914f7c Merge branch 'main' into fix/house-rules-preserve-local-text 2026-11-13 20:42:47 +01:00
FredApps 00db6e35c0 sonarcloud: let shard tests find workspace binaries by their build path
Tests that run a workspace binary through env!("CARGO_BIN_EXE_<name>")
hold the build job's absolute target path. nextest extracts the archive
to a temporary directory, so in every coverage shard those tests failed
with "No such file or directory" while the gate passed them. Since #222
made shard test failures fail the scan, that turned SonarCloud red on
designcraft, cadcraft, pdfcraft and wordcraft main.

The build job now records cargo's target directory next to the archive.
Each shard extracts the archive to a known directory and links the
recorded path to it before running its partition.
2026-11-13 15:24:29 +01:00
FredApps 7d19a7f5e4 release.yml: a publish input publishes a complete draft at the end of the run (#209)
* release.yml: a publish input publishes a complete draft at the end of the run

Part E of the faster-release plan: no one waits by the run to publish. Only on the release
branch, not in a dry run, only when no build job failed (the job already requires that) or was
cancelled, and only when the draft has at least as many assets as the last published release, so
a skipped build job can't publish an incomplete release. Off by default; apps opt in.

* publish: compare with the most recently published release, and say why in the summary

gh release list orders by creation, so the newest-created release was the baseline; an older
draft published later would have been missed. Every refusal now also writes its reason to the
job summary, not only an error annotation.

* tests: publish doesn't change the FreeBSD build, so it stays out of the cache key
2026-11-13 14:09:41 +01:00
FredAppsandFredApps 20ebee3cb1 fix(ci): provide pinned translations to coverage tests (#227)
* fix(ci): provide pinned translations to coverage tests

* fix(ci): keep translation checkout out of scan

---------

Co-authored-by: FredApps <FredApps@users.noreply.github.com>
2026-11-13 00:33:06 -05:00
FredApps 3eaa8798ac release_train: --logs is a relative folder inside the current directory (#214)
Closes SonarCloud's path-injection alert on the merged release_train.py (pythonsecurity:S8707):
an absolute path, .., or anything outside the working directory is refused before the folder is
made.
2026-11-12 21:52:12 -05:00
FredApps 804f702057 fix(sonar): surface archived Rust test failures after analysis (#222)
* fix(sonar): report archived Rust test failures after scanning

* test(sonar): cover shard status production and document result semantics
2026-11-12 23:38:33 +01:00
FredApps 293de72429 release.yml: a FreeBSD cache a later release can restore, with the aarch64 cross output (#216)
The release FreeBSD jobs keyed their Cargo cache on toJSON(inputs), and
contributors-artifact is contributor-snapshot-<run id>-<attempt>, so every run
wrote an entry no other run could restore: on 11 Nov every release built FreeBSD
cold. The key now holds only the inputs that change the FreeBSD build (app name,
architecture, craft-fonts ref, FreeBSD release); dry-run is left out too, so a dry
run warms the cache a release restores. A test makes every new input pick a side.

The aarch64 job cross-compiles, and Cargo writes that output to
target/aarch64-unknown-freebsd/release, which the cache action never saved: only
the host build scripts in target/release were kept. The action takes the triple as
a new target input and saves and restores that directory too.
2026-11-12 07:25:29 +01:00
FredApps 17eb0f0717 release.yml: build Windows arm64 natively on the windows-11-arm runner (#215) 2026-11-12 07:25:20 +01:00
FredApps 3951f6df01 sonarcloud: merge each shard's profiles before the scan downloads them (#210)
Each coverage shard now merges its own raw profiles into one sparse
.profdata with the archive toolchain's llvm-profdata and uploads only
that. The scan job merges the shard profiles instead of downloading
every raw profile beside the test archive, which on 11 Nov 2026 filled
the runner for vectorcraft (four ~7 GB zipped profraw artifacts).

A raw profile llvm-profdata cannot read, such as one cut short by a
test process that crashed while writing it (lightcraft, 11 Nov 2026),
now fails its shard with an error naming the file, instead of being
uploaded and failing the scan's merge.

Single-shard callers keep the cargo llvm-cov path unchanged.
2026-11-11 19:55:14 -05:00
FredApps 840a417e3d Release: scripts/cut_release.py cuts a release from green main without a bump pull request (#207)
* Release: scripts/cut_release.py cuts a release from green main without a bump pull request

On 11 Nov 2026 the release of 14 apps took most of the day. A large part went to version-bump pull
requests that changed only version strings yet waited on the full CI of a pull request (1-2 h of
FreeBSD, sharded SonarCloud coverage), and to rerunning it. The script commits the bump on the
newest main commit whose CI passed, merges it into release (which starts release.yml), opens the
same bump for main as its own pull request, and with --publish publishes the draft once the run
passed and has assets. Tests cover the bump: workspace and path-dependency versions, only the
workspace's own Cargo.lock entries, CRLF files, the repository hook.

* cut_release: review fixes

- A trailing comment after the workspace version stays; the value alone is replaced.
- Cargo.lock: only the workspace members' entries (cargo metadata --no-deps) change, not a local
  path dependency outside the workspace that shares the version.
- Cargo.lock is checked with a resolving cargo metadata --locked, on the bump, on release after
  the merge and on the sync branch; --no-deps never compared it with path dependency versions.
- --publish refuses a draft with fewer assets than the last release (a skipped build job leaves
  the run green), unless --allow-fewer-assets.
- The sync PR never moves main backwards: versions compare as numbers, and a main at or past the
  release gets none.
- A failed auto-merge says so, with the PR to merge by hand.
- Arguments that reach git or gh are checked first (owner/name, version, commit hash, workflow,
  title), so none can be read as an option. git, gh and cargo are required up front.

* Release: scripts/release_train.py releases many apps at once with cut_release.py

Every app in parallel, a log per app, and one summary line each (published, pushed, or stopped
and why); one app stopping doesn't stop the rest. Tested on figcraft and soundcraft with
--dry-run (both done in under a minute).

* tests: release_train options before -- in the test

* release_train: only owner/name repos and known cut_release.py options reach the subprocess
2026-11-11 23:02:43 +01:00
FredApps 603045e42d release.yml: a dry-run input builds and checks without releasing (#208)
* release.yml: a dry-run input builds and checks without releasing

For a nightly run on main that finds release-only breakage before release day. On 11 Nov 2026
gridcraft's riscv64 build, materialcraft's private-repo FreeBSD jobs, wordcraft's Print job and
the riscv64 apt mirrors each surfaced only during the release, one fix PR and release run at a
time. With dry-run: no job enters the release environment (no signing secrets; the environment
admits only the release branch), the macOS job and the draft are skipped, and the Flatpak OCI
layouts are not pushed to GHCR or Docker Hub.

* tests: the Flatpak OCI push and the release environment also stay out of a dry run
2026-11-11 22:46:06 +01:00
FredApps 5d42870ead apt: wait for cloud-init before rewriting the sources (#204)
During the ubuntu.com outage, cloud-init's apt_configure module (once per
instance, at boot) spent two 10-second DNS timeouts looking for a mirror
and then wrote ubuntu.sources from its template, after the job had
started. On those VMs configure-apt-mirrors had already pointed the
sources at its list: apt-get update fetched every index for that list,
cloud-init put the image's mirror list back, and apt-get install found
no indexes for it, so no Ubuntu package had a candidate (materialcraft's
Flatpak x86_64 job, the FreeBSD tests job on 26.04). A repro on 12
runners failed on 8, every round, and a file watcher caught cloud-init's
write landing mid-update.

wait-for-cloud-init.sh runs `cloud-init status --wait` (at most 300 s,
never failing the job) before configure-apt-mirrors and
install-riscv64-cross's select-mirrors.sh touch anything.
2026-11-11 17:57:29 +01:00
FredApps 3f541b8904 install-riscv64-cross: fall back to mirrors outside ubuntu.com (#202)
The release builds' Linux riscv64 job read amd64 from archive and
security.ubuntu.com and riscv64 from ports.ubuntu.com only. With no
ubuntu.com name resolving on the runners, apt spent 3m20s on failed
lookups and then found no libc6-dev:riscv64, so every app's release
failed there.

select-mirrors.sh now chooses one pair of mirrors for both architectures:
Ubuntu's own, then dotsrc (it carries both trees), then kernel.org with
TU Chemnitz's ports. It takes the first pair whose amd64 and riscv64
InRelease files answer for every suite with the same Date (Ubuntu signs
one Release for archive and ports), so Multi-Arch: same packages still
match. The image's own Ubuntu sources are disabled in that job: they
only added a second, lagging snapshot and, during the outage, the stall.

The riscv64 job runs Harden-Runner in audit mode, so release.yml needs
no allowlist change.
2026-11-11 17:01:34 +01:00
FredApps 0817d766c4 test-freebsd: show apt's view and the CPU when the package install fails (#201)
One run on 11 Nov 2026 found no candidate for tcsh or debsigs right after
an update that fetched every index from kernel.org; the runs before and
after it, under the same ubuntu.com outage, passed. Print apt-cache policy,
the architecture settings, the universe index files and whether the CPU
supports x86-64-v3, so the next failure shows the cause.
2026-11-11 16:36:11 +01:00
FredApps d97dcd6dcf apt: fall back to mirrors outside ubuntu.com when it is down (#199)
On 11 Nov 2026 no ubuntu.com name resolved on the runners for about
half an hour. The images' mirror list (azure.archive, archive and
security.ubuntu.com) sits entirely in that zone, so every retry spent
its five minutes on 20-second lookups of the same dead names and the
SonarCloud archive builds failed with "downloading the packages failed
3 times".

configure-apt-mirrors points the image's Ubuntu sources at
/etc/apt/craft-apt-mirrors.txt: the image's mirrors in the image's
order, then mirrors.edge.kernel.org and mirrors.dotsrc.org (arm:
mirrors.dotsrc.org and ftp.tu-chemnitz.de). Each mirror is checked
first, in parallel; those that do not serve this release's InRelease
move to the end. install-apt-packages runs it before every network
attempt, and the plain apt-get steps (Flatpak, release, packaging lint,
RPM signing, Linux deps, FreeBSD test) run it before apt-get update.
Block-mode Harden-Runner lists allow the new hosts.
2026-11-11 16:21:03 +01:00
FredApps 9b9e0f5128 Merge pull request #188 from storytold/sonar/docker-build-job-permissions
fix(docker-build): scope packages: write to the pushing jobs
2026-11-10 18:27:46 +01:00
FredApps 567530acb5 Merge branch 'main' into sonar/docker-build-job-permissions 2026-11-10 18:23:14 +01:00
FredApps b24513e795 fix(freebsd): cap the VM's ZFS ARC so big test crates aren't OOM-killed (#190)
* fix(freebsd): give the VM a swap file and cap the ZFS ARC

photocraft's FreeBSD job was SIGKILLed compiling photocraft-ui-egui's lib tests late in the run (release run 42609972735, dispatch 42805955303). Add an 8 GB swap file when the guest has none, cap the ARC at 2 GB when the image uses ZFS, and print disk, swap and memory so the next OOM is diagnosable.

* fix(freebsd): only touch swap and the ARC inside a FreeBSD guest

The workflow tests run the prepare script on Linux under sh -eu, where swapctl doesn't exist. Run the ARC cap, swap file and diagnostics only when uname is FreeBSD, and don't let the diagnostics fail the step.

* fix(freebsd): add the swap file only with room to spare, and remove a partial one

Per review: a dd that runs out of space must not leave a partial /var/swap0 that then starves the build. Require 16 GB free on /var first and delete the file if any step fails.

* fix(freebsd): keep only the ZFS ARC cap; drop the swap-file fallback

Per review: swap on a ZFS-backed file can hang FreeBSD under memory pressure, and today's image already has a swap partition, so the fallback never ran. The verified run passed on the ARC cap alone.
2026-11-10 16:40:36 +01:00
FredApps 1a6c6c0dd5 fix(docker-build): scope packages: write to the pushing jobs 2026-11-10 11:10:27 +01:00
FredApps 4b23a68072 fix(packaging-lint): retry transient actionlint downloads (#176)
Bound archive and checksum download retries, including refused connections, while retaining HTTPS and SHA-256 validation. Report missing checksum entries using an exact archive filename lookup. Add nine real-curl regression tests for recovery, permanent failures, retry bounds and checksum validation.
2026-11-08 14:16:10 +01:00
FredApps 8fb29161c2 fix(sonar): reduce sharded coverage disk usage (#174)
* fix(sonar): bound sharded coverage disk usage

* test(signing): detect restricted GPG agent sockets
2026-11-08 14:15:27 +01:00
FredApps d2855b97d0 fix: preserve local text when updating house rules 2026-11-06 12:56:48 +01:00
FredApps e8500913a3 Merge pull request #153 from storytold/house-rules-check
Check that AGENTS.md copies the shared house rules
2026-11-06 11:45:26 +01:00
FredAppsandCursor 3207fcf8ad Keep the house-rules rewrite on the checked AGENTS.md path.
The path is resolved and has to stay inside the named directory. The existing file's text is written back as text, so the path-traversal finding on that write is suppressed.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-11-06 11:42:33 +01:00
FredAppsandCursor 9a3db2d31d Validate house-rules paths and revisions before git or file access.
A checkout path and a recorded commit have to match a fixed pattern, and the standards path has to be one of the two known files. The per-block check is its own function.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-11-06 11:39:18 +01:00
FredAppsandCursor 70fc5d4964 Check that AGENTS.md copies the shared house rules.
The writer and the checker share one normalization. A rewritten digest does not make an edit pass, an intact older copy warns only when main has moved on, and a source that cannot be read is reported as could not check.

Co-authored-by: Cursor <cursoragent@cursor.com>
2026-11-06 11:34:30 +01:00
FredApps bb16e4122a gate.yml: optional gate-timeout-minutes stops a hung gate with a process list and a clear error (#143)
CI green; CodeRabbit rate-limited with no findings; 0 review threads.
2026-11-05 11:27:56 +01:00
FredApps 0755fd19c7 Add changed-paths.yml: run a job only when its paths change or a label asks (#142)
* Add changed-paths.yml: run a job only when its paths change or a label asks

* changed-paths: read paths NUL-separated, keep the reason on one line; README: what the checkout holds
2026-11-05 11:12:34 +01:00
FredApps 88c42c9714 Merge pull request #123 from nanox333/codex/shared-contributor-generator
Release: provide a shared contributor snapshot generator
2026-11-04 13:54:10 +01:00
FredAppsandClaude Opus 5.5 e09a018c65 Build model titles only from each provider's known words
Anyone can commit under an agent email, so a free-form Git name such as
"Private Person <noreply@anthropic.com>" became a published model title,
which the apps would ship in their About windows. Each provider now lists
the words a model title may use. A name with any other word credits the
agent's default model and repeats none of it; versions are bounded too.

Across the co-author trailers in the 13 apps' history, 18,099 keep their
model row and 7 unusual names now fall back to the default. Also pin that
the PR lookup reads the merge commit rather than the PR head.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-04 13:49:44 +01:00
FredAppsandClaude Opus 5.5 c2e0e404ab Batch PR lookups gently and ignore bot PR openers
effectcraft's 4,000-commit history made 50-commit association queries time
out on GitHub, so batches are smaller and a failed batch is retried once.
GraphQL names bot openers without the [bot] suffix, which turned dependabot
into a person; only User accounts now count as PR openers.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 19:38:06 +01:00
FredAppsandClaude Opus 5.5 fbfdcb1b5e Credit AI agents as models and verify merge-commit and carried PRs
GitHub links agent trailers such as noreply@anthropic.com to the claude and
codex accounts, so they appeared as the top human contributors. Agents are now
recognized by exact Git email or GitHub account, never by name, and credited
only in the snapshot's models (About > Models), including commits an agent
authored itself. Bots are no longer listed as people. Model and version are
read from the agent's Git name, covering every provider the apps' history
uses.

Commits merged with a merge commit or rebase never equal a PR's merge commit,
so self-added names lost verification and unlinked commits lost their author.
GitHub's commit-to-PR association now supplies the opener of the one merged PR
containing the commit. An integration PR opened by a writer that carries the
person's own linked commit also verifies their entry.

Against the shipped snapshots of effectcraft, pdfcraft, photocraft and
lightcraft at their recorded heads, no person loses a row, a name or a commit.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-03 19:30:28 +01:00
52dc54c75e ci: pin install-action v2.87.33, the first that knows cargo-nextest 0.9.150 (#122)
v2.87.29 knows nextest only up to 0.9.148, so every gate and coverage run that installs the
pinned cargo-nextest@0.9.150 fell back to cargo-binstall@latest: an unpinned download, then a
binstall of nextest. v2.87.33 is the oldest release whose manifest has 0.9.150; the releases
since v2.87.29 change only tool manifests.

Co-authored-by: FredApps <FredApps@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 05:32:27 +01:00
e031880d47 fix(install-apt-packages): time-limit and retry mirror downloads (#117)
* fix(install-apt-packages): time-limit and retry mirror downloads

A SonarCloud job in vectorcraft (run 41253493430) sat in this step for 58 minutes: the Azure
Ubuntu mirror timed out, apt fell back to archive.ubuntu.com, then a connection went silent and
apt printed nothing until the run was cancelled. Acquire::http::Timeout doesn't end a connection
that stays open, so the job's 90-minute timeout was the only bound.

apt-get update and a new --download-only pass now each run under timeout(1), 300 s per attempt,
up to 3 attempts. The install itself then works from downloaded files only, so dpkg is never
killed mid-configure. Acquire::https::Timeout is set alongside the http one for the HTTPS fallback.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* fix(install-apt-packages): retry an update that fetched only some indexes

apt-get update warns and exits 0 when an index fails to download, so the retry never ran for
it. APT::Update::Error-Mode=any makes that a failure, which is retried. If indexes are still
missing after the last attempt the step continues with a warning, as it did before: they often
belong to a repository the packages don't need, and a package that needs one fails the download.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: FredApps <FredApps@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 02:05:24 +01:00
84ad881711 ci(windows-arm64): only main saves the packaging cache (#116)
Pull requests that touch Windows packaging saved their own windows-arm64-package cache (about
0.7 GB), visible only to that pull request. Every app repository is at the 10 GB cache limit,
so each one evicted a cache main's gate restores. The nightly run on main still saves it.

Co-authored-by: FredApps <FredApps@users.noreply.github.com>
Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-01 01:39:08 +01:00
FredApps 2b3fb9dc05 ci: preserve dependency cache reuse across root manifest updates (#108)
* ci: preserve dependency cache reuse across root manifest updates

* docs: align gate cache overview with profile keys and dispatch opt-in
2026-10-30 07:47:08 -04:00
FredApps 7cb1cfbbd8 Run AppImage CLI regression checks in shared packaging lint 2026-10-30 00:10:37 +01:00