7 Commits

Include renames

Author	SHA1	Message	Date
archipelagoandClaude Opus 5	3086f5addb	fix(btcpay): pin 2.4.2 (actively exploited 2FA bypass); teach drift check the release catalog ... BTCPay 2.4.2 fixes a critical vulnerability that upstream reports as actively exploited: a TOTP two-factor bypass via Greenfield Basic authentication (btcpayserver/btcpayserver#7491). Checked the 2.3.9 -> 2.4.2 breaking changes against how Archipelago actually configures BTCPay; both are inert here: - 2.4.0 removed the LNBank and Lightning Charge backends. Ours is a direct LND connection built by container::lnd::ensure_btcpay_lnd_connection_secret. - 2.4.2 disables Greenfield Basic auth five minutes after account creation. Nothing in the daemon or frontend consumes BTCPay's API. The manifest bump alone does NOT reach nodes: catalog_image_override makes the signed catalog authoritative whenever the image repo matches, so a node would be forced back to 2.3.9. The catalog edit is held locally until the signing ceremony runs, because an unsigned catalog published to main would be accepted by nodes (absent signatures are allowed) and would quietly drop authenticity. check-app-catalog-drift.py only understood app-catalog/catalog.json, where `apps` is a list. releases/app-catalog.json — the SIGNED catalog nodes actually resolve apps through — keys `apps` by id and wraps each app's full manifest under manifest.app. So the checker parsed the file that governs nothing and raised ValueError on the file that governs everything. It now reads both shapes. Running it against the release catalog shows the repo and the catalog agree on content: of 34 image differences, all 34 are the registry host alone and every tag is identical. The remaining version-string drift (v1.18.0 vs 1.18.0, 1.30.0-alpine vs 1.30.0) is cosmetic metadata, not image drift. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-07 12:19:24 -04:00
archipelagoandClaude Fable 5	184257390d	feat(pine): 1.3.0 manifests — openwakeword member + live node status on the launcher page ... pine-openwakeword manifest (wyoming-openwakeword 2.1.0, :10400, /custom model dir for the future Yo Archy model). Pine 1.3.0: launcher page gains a live node-status card fed by /api/pine/status via a same-origin nginx proxy, and copy for the new intents / Claude fallback / mesh announcements. Catalogs, app-session config, drift ids regenerated; release catalog embeds 56 manifests (unsigned until the ceremony). Framework PT test plan in docs/. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>	2026-07-22 02:59:34 -04:00
archipelagoandClaude Opus 4.8	1730d02003	feat(pine): add Pine voice-assistant app package (manifests + icon) ... Package the PineVoice/Wyoming local voice assistant as ONE store app "Pine" that runs three rootless containers: - pine-whisper — Wyoming faster-whisper STT (docker.io/rhasspy/wyoming-whisper 3.4.1, model base-int8/en), publishes :10300 - pine-piper — Wyoming Piper TTS (2.2.2, voice en_GB-alba-medium), publishes :10200 - pine — nginx launcher serving a self-contained setup/status page (WiFi provisioning + Home Assistant wiring instructions), the Open target The two engines publish their Wyoming ports so Home Assistant reaches them via host.containers.internal. All rootless (cap-drop=ALL, no_new_privileges), manifest-driven — no hardcoded podman/installer. The engines are internal stack members (added to the drift-check INTERNAL_MANIFEST_IDS allowlist); only "pine" carries a catalog entry. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>	2026-07-21 05:14:32 -04:00
archipelago	df9d3a55be	integration: preserve deployed 1.8.0 OTA work	2026-06-30 05:08:17 -04:00
archipelago	f818f1dcc1	app-platform: remove unsupported saleor release surface	2026-06-11 01:16:21 -04:00
archipelago	de60f7e21e	app-platform: remove revoked onlyoffice app	2026-06-11 01:03:45 -04:00
archipelago	09ec64932f	app-platform: generate catalog from app manifests	2026-06-11 00:24:20 -04:00