6 Commits

Include renames

Author	SHA1	Message	Date
archipelago	576c642da4	fix(apps): ollama resource type + adguardhome port; gate on collisions ... Ollama's embedded manifest failed the typed parse (memory_limit wants a string) so the catalog overlay was skipped for it; AdGuard Home's conventional :3000 collided with Grafana's. The release gate now runs the host-port collision test (repo_app_manifests_have_no_host_port_collisions) so this class can never ship untested again.	2026-09-01 03:31:02 -04:00
archipelago	54431fc856	fix(host): enforce the full kdump crash reservation	2026-08-31 09:16:18 -04:00
archipelago	cbd463e980	feat(host): crash/hardware-error capture, delivered by a new host-fixup OTA channel (#144) ... kdump + rasdaemon on every node, per docs/kdump-rasdaemon-design.md with the approved decisions: hang capture ON (a wedged kiosk dumps and reboots itself instead of sitting dead), crashkernel=256M, backfill ships with this release, phase-2 UI surfacing deferred. Host fixups (docs/system-level-ota-design.md) are the general answer to 'deliver system-level updates OTA': curated OS packages, sysctl drop-ins, service enablement and the GRUB crashkernel line, carried by the signed binary and applied idempotently at startup — non-fatal by construction (offline/locked-dpkg nodes converge on a later boot), skipped on dev boxes and non-Debian hosts. This formalizes the polkit/audio repair precedents into a channel with a stated policy: pinned packages and parameter intent only, never dist-upgrade automation; the ISO bakes the identical end state into fresh installs (next commit). The one runtime limitation is honest: crashkernel memory can only be reserved at boot, so the fixup writes GRUB, runs update-grub, and logs that it takes effect on the next reboot. tests/lifecycle/os-audit.sh gains section D — a graded baseline check: FAIL if capture never landed, WARN if written but awaiting reboot, PASS when reserved, policy live and rasdaemon recording. Section D runs independently of RPC health: a wedged backend must not mask that the node also stopped capturing evidence. Verification: host_fixups unit tests 4/4; cargo fmt clean; full suite runs in the release gate (create-release) and the archi-dev-box lifecycle gate before the tag.	2026-08-31 07:23:44 -04:00
archipelagoandClaude Opus 5	f5b112c508	fix(gate): stop reporting a compile timeout as a test failure ... cargo-test-weekly failed twice today with exit 124 at unit 427/429 — the non-incremental test-profile build running out of wall clock mid-compile, before a single test executed. The summary said only "FAIL: cargo-test- weekly", which reads as a broken test and sends you hunting for one that does not exist. Two changes: the ceiling goes 1500s -> 3600s (580s was already found too short; 1500s now dies on the biggest link on a loaded, swapping box), and stage() names exit 124 as a timeout rather than printing a bare code. Verified both reporting branches: a timed-out stage and an ordinary non-zero exit. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-20 01:50:52 -04:00
archipelagoandClaude Opus 5	d75963de10	fix(gate): show which UI test failed instead of swallowing it ... The ui-unit-tests stage piped vitest through `tail -4`, which cut off the failure block. A red gate reported "1 failed | 999 passed" and nothing else — no file, no test name, no assertion — so the failure could not be diagnosed after the run. Success still prints the quiet 4-line summary; failure now dumps the full log and keeps it on disk so a scrolled-off terminal isn't the end of it. Verified both paths: green run unchanged, and a deliberately failing spec now surfaces its file, test name, assertion and line number. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-19 14:33:09 -04:00
Archipelago	b67e1527a2	Archipelago — open-source initial import	2026-08-12 10:55:50 +00:00