* Load and verify the signed website catalog with bundled fallback
* Preserve signed fixture bytes across platforms and fix web lint
* Document the opt-in live catalog integration check
Add MailCraft (UCS-Care-Group/mailcraft) to the catalog as a community app by
UCS Care Group, with its icon, licences, details page and tagline in every
complete catalog. Downloads are checked against its SHA256SUMS.txt. Its macOS
builds are unsigned, so mac_team is None: the launcher opens an installed copy
there but installs nothing.
AGENTS.md lists its repo as an approved community app (approved 2026-11-08).
Two review findings on the one-prompt session:
- The results file is bound to its session by a random token, written as
the file's first line and carried in the held manifest; a leftover or
planted file in the downloads folder can no longer pass for a
session's report. The session's name is only taken once its results
and process-id files are free too.
- The waiting side falls back to one-by-one installs only when the
elevated session is shown to be over (its process waited out, or its
process id gone). A session that was launched but cannot be seen to
finish - a slow antivirus start-up, a process that will not open -
now reports an error per app instead of racing a second installer.
The Linux gate never compiles this test, and Windows clippy stops at the
first hard error, so the field came to light only once the errors before
it were fixed.
Clippy on Windows (never compiled on the Linux gate) asked for two
things: run_msi now keeps to its caller's module, the visibility its
Package argument already has, and the session's cleanup-on-error uses
inspect_err, which is what removing a pid file on the way out is.
A job whose run_install ends before the installer is reached (a
repository-managed Flatpak, a missing release, the overwrite question, a
paused download) dropped its batch's gather without leaving it, so the
rest of the batch waited out the full ten-minute cap before their shared
prompt. The backend now holds the place with the same BatchPlace guard
install_at uses, so every way out of a job gives the place back.
* fix(macos): respect disabled Gatekeeper assessments
* fix(macos): read disabled assessment status on exit 1
* fix(native): allow the macOS-only exit details on other targets
Linux and Windows clippy (-D warnings) flagged RunOutput::code and the test
constructors as unused there. Same change as #1177.
Co-authored-by: AxoIsAxo <133877250+AxoIsAxo@users.noreply.github.com>
---------
Co-authored-by: AxoIsAxo <133877250+AxoIsAxo@users.noreply.github.com>
- Support ArtCraft Studio's published MSI and DMG asset formats in parse_asset_name while preserving existing asset naming
- Add real artcraft-release.json fixture and test asset selection across desktop platforms
- Add runs_on to CraftApp and filter out ArtCraft Studio on FreeBSD across backend and UI
- List ArtCraft Studio as app #01 in the README Craft App Suite table and xtask APPS array
The Flatpak check took any entry with this app's X-Flatpak and a flatpak run
Exec as on, also one a startup manager had hidden (Hidden=true, or GNOME's
X-GNOME-Autostart-enabled=false) or whose Exec started a different app.
It now reads the [Desktop Entry] keys as desktop-entry parsers do and
counts the entry only when it isn't hidden and its Exec is exactly the line
this launcher writes for its own app id.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
After switching from the host build to the Flatpak, the old host entry has
the same file name, so the setting showed on while its Exec still named the
host program. In the Flatpak only the Flatpak form (X-Flatpak=<id> and an
Exec of flatpak run) counts as on, and turning it on rewrites an old entry.
Both manifests grant xdg-config/autostart:create. Flatpak resolves that
on the host and binds the folder at its own path (common/flatpak-context.c,
common/flatpak-exports.c), so the entry can be written there also when
$XDG_CONFIG_HOME is outside home, and the folder is made on a fresh account.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Recompute the current revision, options and download plan when report_download rejects stale work. Add a real publication-boundary regression that fails with a missing plan before the fix and checks the accepted size plus Paused/Ready events. Local validation: serial native suite 279 passed, 3 existing ignored; Windows MSI integration 1 passed; strict all-target Clippy and repository formatting passed. The first parallel suite hit two unchanged HTTP fixture failures; both pass in the complete serial run.
Move the existing plan report after detected-state publication so post-job invalidation does not erase it. Strengthen the real-worker JobFinished observer regression: it fails with a missing plan before the fix. Full native validation passes 278 unit tests (3 existing ignored), the Windows MSI integration test, strict all-target Clippy and scoped formatting.
Observe the background Configure result before exercising stale-report rejection. Keep the existing plan and installed-format assertions, while excluding unrelated apps from the no-stale-events check. Full native validation: 278 tests passed, 3 existing ignored, plus the Windows MSI integration test; strict all-target Clippy passed.
Inside the Flatpak the autostart entry went into the sandbox's own config
folder (~/.var/app/<id>/config/autostart), which the host session never
reads, and its Exec line named the in-sandbox /app/bin path. When
/.flatpak-info exists the entry now goes into the host's autostart folder
($HOST_XDG_CONFIG_HOME, else ~/.config), is named after the Flatpak app id,
and starts the app with `flatpak run --command=artcraft-launcher <id>
--hidden` plus X-Flatpak, as the XDG Background portal writes it. Outside a
Flatpak the path and the entry are unchanged. Both manifests note that the
entry relies on --filesystem=home.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Keep the two newly merged upstream UI fixtures compatible with the existing download-size fake. Initialize its empty cache without changing either installability assertion.
- The dialog's Install is disabled with a reason for a refused version.
- The out-of-reach tooltip in card and table; no note for a repository
copy; the note for a release without a download here.
- Clicking Reinstall installs; clicking a greyed-out Install version X
sends nothing.
- German rows: a single main button must sit on the menu's line, a
stacked pair must be centred on it and stay out of the next row.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The version dialog's Install used has_download, so for a copy the
backend can't replace it stayed enabled and the install was refused
(CodeRabbit). version_installs and version_refusal are now shared by
the card's Install version X and the dialog: both are disabled and
say why on hover.
- A stacked Open/Update sat at the top of its table row, 7 px above the
menu; it is now laid out at its own size and centred like the rest.
- Docs of AppEntry::installable and AppStatus::Installed say what the
answer means now: an install would go ahead.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- When a copy appears between a publisher looking and taking reporting,
the answer uses the view its detection asked for (last_system_kinds)
instead of probing there. A copy only enters installed through
publish_detected, which asks first.
- Event::Installable's doc covers both emissions: in the batch with the
Latest or Detected it depends on, and alone when only the plan changes.
- Tests: no probe under the lock (expired view kept), a plan report's
answer follows the current settings, a concurrent poll never splits a
pair.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- A disabled 'Install version X' for a version that can't replace this
copy says so on hover (Jeremy8776).
- The 'latest X' note for a release that can't install here only shows
while the app follows the latest release: right after a version is
chosen, the old track's release is refused for that alone (Jeremy8776).
- Tests: the note in the table, the kept-version case, a repository
Flatpak keeping Reinstall.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
run_install updates a repository-managed Flatpak with flatpak update (on
Linux, on the stable track) before any download is planned, but the
answer treated it as managed elsewhere and said no, so the new Reinstall
gate hid the launcher's only route to that update (Jeremy8776).
repository_update now holds that rule, and both run_install and the
answer ask it. The system_kinds doc says when it runs under a lock.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Stages the race deterministically: a report in progress holds the
planning lock, a worker started before the settings change waits behind
it, the preferred format changes, and the worker's report is checked to
be the new one. Capturing settings at the worker's start would fail it.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Detection, an install's end and a check's end reported kept downloads
with settings captured when their thread started, so one could land
after the report of a newer settings change and show a stale Resume or
Retry. report_partial now reads the settings itself under a planning
lock, so whichever report comes last was worked out last.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Configure recomputed every app's planned download on the UI thread, and
inside the Flatpak sandbox each asks the host (up to 3 s). That now runs
on a thread, one at a time, each with the settings as they are when it
starts, so the newest settings have the last word. Installs and planned
downloads still ask the system afresh.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- An installed copy behind a release the launcher can't install over it
shows 'latest X' beside its version, with a tooltip saying why, the
way a version kept on purpose does (Jeremy8776).
- The single update button keeps its full accessible name when its label
is shortened (Jeremy8776).
- Reinstall and 'Install version X' only show or enable where an install
would go ahead, so they can't end in 'has no download' (Jeremy8776).
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
- The answer reads the backend options when it is worked out, so a job
that started before a settings change no longer answers with the old
version track (Jeremy8776).
- What the system can install is asked before the reporting lock is
taken and kept for a minute: in the Flatpak sandbox asking runs
flatpak-spawn on the host (up to 3 s). Installs still ask afresh
(Jeremy8776, CodeRabbit).
- No answer, and nothing asked, for an app that isn't installed: the UI
only uses it for an installed copy. Startup's cached replay, before
detection, no longer asks at all.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
install_plan takes how a copy managed elsewhere is explained. Installs
keep the full message (with pacman -Si naming the repository); the
installability answer, which runs on every check under the reporting
lock, only needs yes or no.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>