fix(cuprate): file log level should be info, not cuprated's debug default

The previous commit on this branch copied cuprated's raw --generate-config defaults (stdout=info, file=debug, max_log_files=7) verbatim. Turns out that's the wrong reference: compared against ssmithx@archy-dev-pa:/home/ssmithx/cuprate/Cuprated.toml — the actual dev config this app was built and tested against — file logging is meant to run at "info" with 14 rotated files, not the binary's raw "debug"/7. Confirmed live on amishparadise: podman logs (stdout) was already clean at info, but the on-disk file log (.local/share/cuprate/logs/<date>) was flooding with per-peer DEBUG gossip (~400KB in 2 minutes) because it inherited the binary default instead of the intended one. Left the resource-tuning knobs in the reference config (8GB target_max_memory, tokio/rayon thread counts, P2P connection counts, explicit reader_threads) out of this file — those were sized for ssmithx's dev box and don't apply here; this manifest's target_max_memory already stays deliberately under the container's 4Gi memory_limit. Regenerated releases/app-catalog.json (still unsigned). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ga6N8Jk1YdCTMMX1LjDpAr
fix(cuprate): make Cuprated.toml logging levels explicit
2026-09-01 12:27:33 +00:00 · 2026-09-01 12:19:20 +00:00 · 2026-09-01 07:45:39 -04:00 · 2026-09-01 05:27:15 -04:00 · 2026-09-01 05:27:00 -04:00 · 2026-09-01 05:14:50 -04:00
23 changed files with 3361 additions and 3385 deletions
@@ -13,13 +13,13 @@
    {
      "id": "adguardhome",
      "title": "AdGuard Home",
-      "version": "v0.107.55",
+      "version": "v0.107.79",
      "description": "Network-wide ad and tracker blocking: a DNS server that filters every device on your LAN, with a web console for rules and client management.",
      "icon": "",
      "author": "AdGuard",
      "category": "networking",
      "tier": "optional",
-      "dockerImage": "source.archipelago-foundation.org/lfg2025/adguardhome:v0.107.55",
+      "dockerImage": "source.archipelago-foundation.org/lfg2025/adguardhome:v0.107.79",
      "repoUrl": "https://github.com/AdguardTeam/AdGuardHome"
    },
    {
@@ -191,13 +191,13 @@
    {
      "id": "filebrowser",
      "title": "File Browser",
-      "version": "2.27.0",
+      "version": "2.63.23",
      "description": "Baseline Archipelago file manager service.",
      "icon": "/assets/img/app-icons/file-browser.webp",
      "author": "File Browser",
      "category": "data",
      "tier": "core",
-      "dockerImage": "source.archipelago-foundation.org/lfg2025/filebrowser:v2.27.0",
+      "dockerImage": "source.archipelago-foundation.org/lfg2025/filebrowser:v2.63.23",
      "repoUrl": "https://github.com/filebrowser/filebrowser",
      "containerConfig": {
        "ports": [
@@ -218,12 +218,12 @@
    {
      "id": "gitea",
      "title": "Gitea",
-      "version": "1.23",
+      "version": "1.27.3",
      "description": "Self-hosted Git service with built-in container registry, CI/CD, and package hosting.",
      "icon": "/assets/img/app-icons/gitea.svg",
      "author": "Gitea",
      "category": "development",
-      "dockerImage": "docker.io/gitea/gitea:1.23",
+      "dockerImage": "source.archipelago-foundation.org/lfg2025/gitea:1.27.3",
      "repoUrl": "https://gitea.com",
      "containerConfig": {
        "ports": [
@@ -274,12 +274,12 @@
    {
      "id": "homeassistant",
      "title": "Home Assistant",
-      "version": "2026.7.3",
+      "version": "2026.8.3",
      "description": "Open source home automation platform. Control and monitor your smart home devices.",
      "icon": "/assets/img/app-icons/homeassistant.png",
      "author": "Home Assistant",
      "category": "home",
-      "dockerImage": "source.archipelago-foundation.org/lfg2025/home-assistant:2026.8.2",
+      "dockerImage": "source.archipelago-foundation.org/lfg2025/home-assistant:2026.8.3",
      "repoUrl": "https://github.com/home-assistant/core",
      "containerConfig": {
        "ports": [
@@ -338,13 +338,13 @@
    {
      "id": "lnd",
      "title": "LND",
-      "version": "0.18.4",
+      "version": "0.21.2",
      "description": "Lightning Network implementation by Lightning Labs. Enables instant, low-cost Bitcoin payments.",
      "icon": "/assets/img/app-icons/lnd.png",
      "author": "Lightning Labs",
      "category": "money",
      "tier": "core",
-      "dockerImage": "source.archipelago-foundation.org/lfg2025/lnd:v0.18.4-beta",
+      "dockerImage": "source.archipelago-foundation.org/lfg2025/lnd:v0.21.2-beta",
      "repoUrl": "https://github.com/lightningnetwork/lnd",
      "requires": [
        "bitcoin-knots"
@@ -505,13 +505,13 @@
    {
      "id": "portainer",
      "title": "Portainer",
-      "version": "2.19.4",
+      "version": "2.45.0",
      "description": "Container management web UI for the local Podman socket.",
      "icon": "/assets/img/app-icons/portainer.webp",
      "author": "Portainer",
      "category": "development",
      "tier": "optional",
-      "dockerImage": "source.archipelago-foundation.org/lfg2025/portainer:2.39.6",
+      "dockerImage": "source.archipelago-foundation.org/lfg2025/portainer:2.45.0",
      "repoUrl": "https://github.com/portainer/portainer",
      "containerConfig": {
        "ports": [
@@ -603,13 +603,13 @@
    {
      "id": "vaultwarden",
      "title": "Vaultwarden",
-      "version": "1.30.0",
+      "version": "1.37.2",
      "description": "Self-hosted password vault with zero-knowledge encryption.",
      "icon": "/assets/img/app-icons/vaultwarden.webp",
      "author": "Vaultwarden",
      "category": "data",
      "tier": "recommended",
-      "dockerImage": "source.archipelago-foundation.org/lfg2025/vaultwarden:1.37.1-alpine",
+      "dockerImage": "source.archipelago-foundation.org/lfg2025/vaultwarden:1.37.2-alpine",
      "repoUrl": "https://github.com/dani-garcia/vaultwarden",
      "containerConfig": {
        "ports": [
@@ -1,7 +1,7 @@
 app:
  id: adguardhome
  name: AdGuard Home
-  version: v0.107.55
+  version: v0.107.79
  upstream:
    kind: github
    repo: AdguardTeam/AdGuardHome
@@ -10,7 +10,7 @@ app:
    device on your LAN, with a web console for rules and client management.
  container:
-    image: source.archipelago-foundation.org/lfg2025/adguardhome:v0.107.55
+    image: source.archipelago-foundation.org/lfg2025/adguardhome:v0.107.79
    pull_policy: if-not-present
    network: pasta
@@ -125,6 +125,19 @@ app:
  #     uses for its own RPC port (-rpcbind=0.0.0.0:8332 internally, gate
  #     restricts it externally) — not a new risk, the same one already
  #     reviewed and accepted for Bitcoin's RPC.
  #   - tracing.stdout.level / tracing.file.{level,max_log_files}: an
  #     operator reading Cuprated.toml on disk should be able to see and
  #     tune the log level directly instead of the file silently omitting
  #     the whole [tracing] table (verified live on amishparadise
  #     2026-09-01: the deployed file had no [tracing] section at all, and
  #     the level was only discoverable by running `cuprated
  #     --generate-config` and diffing). file.level is set to "info", NOT
  #     cuprated's own raw default of "debug" — matches the reference dev
  #     config this app was built and tested against
  #     (ssmithx@archy-dev-pa:/home/ssmithx/cuprate/Cuprated.toml,
  #     verified 2026-09-01), which deliberately runs file logging quieter
  #     than the binary default. max_log_files similarly follows that
  #     reference (14, not the binary default of 7).
  files:
    - path: /var/lib/archipelago/cuprate/Cuprated.toml
      content: |
@@ -133,6 +146,13 @@ app:
        [rpc.restricted]
        enable = true
        [tracing.stdout]
        level = "info"
        [tracing.file]
        level = "info"
        max_log_files = 14
      overwrite: false
  health_check:
@@ -1,7 +1,7 @@
 app:
  id: filebrowser
  name: File Browser
-  version: 2.27.0
+  version: 2.63.23
  # Where this app comes from, so scripts/check-upstream-releases.py can
  # tell us when the pin below has fallen behind. Without it nothing can:
  # container.image names our mirror, not the project it was mirrored from.
@@ -11,7 +11,7 @@ app:
  description: Baseline Archipelago file manager service.
  container:
-    image: source.archipelago-foundation.org/lfg2025/filebrowser:v2.27.0
+    image: source.archipelago-foundation.org/lfg2025/filebrowser:v2.63.23
    pull_policy: if-not-present
    network: archy-net
    custom_args: ["--config", "/data/.filebrowser.json"]
@@ -1,7 +1,7 @@
 app:
  id: gitea
  name: Gitea
-  version: "1.23"
+  version: "1.27.3"
  # Where this app comes from, so scripts/check-upstream-releases.py can
  # tell us when the pin below has fallen behind. Without it nothing can:
  # container.image names our mirror, not the project it was mirrored from.
@@ -12,7 +12,7 @@ app:
  category: development
  container:
-    image: docker.io/gitea/gitea:1.23
+    image: source.archipelago-foundation.org/lfg2025/gitea:1.27.3
    pull_policy: if-not-present
  dependencies:
@@ -1,7 +1,7 @@
 app:
  id: homeassistant
  name: Home Assistant
-  version: 2026.7.3
+  version: 2026.8.3
  # Where this app comes from, so scripts/check-upstream-releases.py can
  # tell us when the pin below has fallen behind. Without it nothing can:
  # container.image names our mirror, not the project it was mirrored from.
@@ -11,7 +11,7 @@ app:
  description: Open source home automation platform. Control and monitor your smart home devices.
  container:
-    image: source.archipelago-foundation.org/lfg2025/home-assistant:2026.8.2
+    image: source.archipelago-foundation.org/lfg2025/home-assistant:2026.8.3
    pull_policy: if-not-present
    network: pasta
@@ -1,7 +1,7 @@
 app:
  id: lnd
  name: LND
-  version: 0.18.4
+  version: 0.21.2
  # Where this app comes from, so scripts/check-upstream-releases.py can
  # tell us when the pin below has fallen behind. Without it nothing can:
  # container.image names our mirror, not the project it was mirrored from.
@@ -11,7 +11,7 @@ app:
  description: Lightning Network implementation by Lightning Labs. Enables instant, low-cost Bitcoin payments.
  container:
-    image: source.archipelago-foundation.org/lfg2025/lnd:v0.18.4-beta
+    image: source.archipelago-foundation.org/lfg2025/lnd:v0.21.2-beta
    pull_policy: if-not-present
    network: archy-net
    # BITCOIND_HOST must follow the node's actual Bitcoin container — Knots or
@@ -5,7 +5,7 @@ app:
  # (--beam-size 1). Bumped past the image version so catalog-driven nodes
  # pick up the args change; the pre-release form "3.4.1-1" would compare
  # LOWER than 3.4.1 under semver and never roll out.
-  version: "3.4.2"
+  version: "3.6.0"
  # Tracks the rhasspy/wyoming-whisper image we pin (Docker Hub — the
  # project's GitHub tags are not the image tags). NOTE: this manifest
  # deliberately ships an args-tuned revision AHEAD of the image tag (see
@@ -24,7 +24,7 @@ app:
  container_name: pine-whisper
  container:
-    image: docker.io/rhasspy/wyoming-whisper:3.4.1
+    image: docker.io/rhasspy/wyoming-whisper:3.6.0
    pull_policy: if-not-present
    network: archy-net
    network_aliases: [pine-whisper]
@@ -1,7 +1,7 @@
 app:
  id: portainer
  name: Portainer
-  version: 2.19.4
+  version: 2.45.0
  # Where this app comes from, so scripts/check-upstream-releases.py can
  # tell us when the pin below has fallen behind. Without it nothing can:
  # container.image names our mirror, not the project it was mirrored from.
@@ -12,7 +12,7 @@ app:
  category: development
  container:
-    image: source.archipelago-foundation.org/lfg2025/portainer:2.39.6
+    image: source.archipelago-foundation.org/lfg2025/portainer:2.45.0
    pull_policy: if-not-present
    data_uid: "1000:1000"
@@ -1,7 +1,7 @@
 app:
  id: vaultwarden
  name: Vaultwarden
-  version: 1.30.0
+  version: 1.37.2
  # Where this app comes from, so scripts/check-upstream-releases.py can
  # tell us when the pin below has fallen behind. Without it nothing can:
  # container.image names our mirror, not the project it was mirrored from.
@@ -11,7 +11,7 @@ app:
  description: Self-hosted password vault with zero-knowledge encryption.
  container:
-    image: source.archipelago-foundation.org/lfg2025/vaultwarden:1.37.1-alpine
+    image: source.archipelago-foundation.org/lfg2025/vaultwarden:1.37.2-alpine
    pull_policy: if-not-present
    network: pasta
@@ -13,13 +13,13 @@
    {
      "id": "adguardhome",
      "title": "AdGuard Home",
-      "version": "v0.107.55",
+      "version": "v0.107.79",
      "description": "Network-wide ad and tracker blocking: a DNS server that filters every device on your LAN, with a web console for rules and client management.",
      "icon": "",
      "author": "AdGuard",
      "category": "networking",
      "tier": "optional",
-      "dockerImage": "source.archipelago-foundation.org/lfg2025/adguardhome:v0.107.55",
+      "dockerImage": "source.archipelago-foundation.org/lfg2025/adguardhome:v0.107.79",
      "repoUrl": "https://github.com/AdguardTeam/AdGuardHome"
    },
    {
@@ -191,13 +191,13 @@
    {
      "id": "filebrowser",
      "title": "File Browser",
-      "version": "2.27.0",
+      "version": "2.63.23",
      "description": "Baseline Archipelago file manager service.",
      "icon": "/assets/img/app-icons/file-browser.webp",
      "author": "File Browser",
      "category": "data",
      "tier": "core",
-      "dockerImage": "source.archipelago-foundation.org/lfg2025/filebrowser:v2.27.0",
+      "dockerImage": "source.archipelago-foundation.org/lfg2025/filebrowser:v2.63.23",
      "repoUrl": "https://github.com/filebrowser/filebrowser",
      "containerConfig": {
        "ports": [
@@ -218,12 +218,12 @@
    {
      "id": "gitea",
      "title": "Gitea",
-      "version": "1.23",
+      "version": "1.27.3",
      "description": "Self-hosted Git service with built-in container registry, CI/CD, and package hosting.",
      "icon": "/assets/img/app-icons/gitea.svg",
      "author": "Gitea",
      "category": "development",
-      "dockerImage": "docker.io/gitea/gitea:1.23",
+      "dockerImage": "source.archipelago-foundation.org/lfg2025/gitea:1.27.3",
      "repoUrl": "https://gitea.com",
      "containerConfig": {
        "ports": [
@@ -274,12 +274,12 @@
    {
      "id": "homeassistant",
      "title": "Home Assistant",
-      "version": "2026.7.3",
+      "version": "2026.8.3",
      "description": "Open source home automation platform. Control and monitor your smart home devices.",
      "icon": "/assets/img/app-icons/homeassistant.png",
      "author": "Home Assistant",
      "category": "home",
-      "dockerImage": "source.archipelago-foundation.org/lfg2025/home-assistant:2026.8.2",
+      "dockerImage": "source.archipelago-foundation.org/lfg2025/home-assistant:2026.8.3",
      "repoUrl": "https://github.com/home-assistant/core",
      "containerConfig": {
        "ports": [
@@ -338,13 +338,13 @@
    {
      "id": "lnd",
      "title": "LND",
-      "version": "0.18.4",
+      "version": "0.21.2",
      "description": "Lightning Network implementation by Lightning Labs. Enables instant, low-cost Bitcoin payments.",
      "icon": "/assets/img/app-icons/lnd.png",
      "author": "Lightning Labs",
      "category": "money",
      "tier": "core",
-      "dockerImage": "source.archipelago-foundation.org/lfg2025/lnd:v0.18.4-beta",
+      "dockerImage": "source.archipelago-foundation.org/lfg2025/lnd:v0.21.2-beta",
      "repoUrl": "https://github.com/lightningnetwork/lnd",
      "requires": [
        "bitcoin-knots"
@@ -505,13 +505,13 @@
    {
      "id": "portainer",
      "title": "Portainer",
-      "version": "2.19.4",
+      "version": "2.45.0",
      "description": "Container management web UI for the local Podman socket.",
      "icon": "/assets/img/app-icons/portainer.webp",
      "author": "Portainer",
      "category": "development",
      "tier": "optional",
-      "dockerImage": "source.archipelago-foundation.org/lfg2025/portainer:2.39.6",
+      "dockerImage": "source.archipelago-foundation.org/lfg2025/portainer:2.45.0",
      "repoUrl": "https://github.com/portainer/portainer",
      "containerConfig": {
        "ports": [
@@ -603,13 +603,13 @@
    {
      "id": "vaultwarden",
      "title": "Vaultwarden",
-      "version": "1.30.0",
+      "version": "1.37.2",
      "description": "Self-hosted password vault with zero-knowledge encryption.",
      "icon": "/assets/img/app-icons/vaultwarden.webp",
      "author": "Vaultwarden",
      "category": "data",
      "tier": "recommended",
-      "dockerImage": "source.archipelago-foundation.org/lfg2025/vaultwarden:1.37.1-alpine",
+      "dockerImage": "source.archipelago-foundation.org/lfg2025/vaultwarden:1.37.2-alpine",
      "repoUrl": "https://github.com/dani-garcia/vaultwarden",
      "containerConfig": {
        "ports": [
@@ -44,10 +44,8 @@
            class="tier-badge"
            :class="tier === 'core' ? 'tier-badge-core' : 'tier-badge-recommended'"
          >{{ tier }}</span>
-          <span
+          <!-- Update state is the bottom-left button only: a second pill up
-            v-if="pkg['available-update']"
+               here duplicated the signal and crowded the title. -->
            class="inline-flex items-center px-1.5 py-0.5 rounded text-[10px] font-semibold bg-orange-500/20 text-orange-300 border border-orange-500/30"
          >Update</span>
        </div>
        <p class="text-sm text-white/50">{{ version ? $ver(version) : '' }}</p>
        <p v-if="author" class="text-xs text-white/40 mt-0.5">{{ author }}</p>
@@ -1,32 +1,30 @@
 {
  "changelog": [
-    "**What's New really does stop at v1.8.0 now.** The first correction removed old generated release blocks but missed six much older hand-written v1.2 sections at the bottom of the modal. Those sections are gone, and the release check now recognizes and rejects that legacy format too, so the history floor cannot falsely pass again.",
+    "**SSH over the mesh is now a first-class setting.** Settings gains an \"SSH over mesh\" card: off by default, and when you allow it the node's mesh firewall opens port 22 — either to every mesh peer (behind an explicit \"I understand\" confirmation, because that's a real exposure) or only to the mesh addresses you list. The rule is owned by the node (the `90-ssh.nft` drop-in), so it survives upgrades and daemon reinstalls, and the card tells you up front whether sshd is running, whether it listens on IPv6 (the mesh is IPv6-only — this is what a broken attempt looks like before it happens), and whether password login is on (keys-only is the recommended pairing). From Termux on your phone, `fipssh <user>@<node-npub>` connects once the toggle is on — the npub is the durable address, and the command is shown with a copy button on the card.",
-    "**The installer carries the same corrected release and Companion 0.5.28.** Its artifact gate now checks the companion APK version and the v1.8.0 What's New floor inside the finished ISO, so a stale frontend or phone app cannot be published under the current release label.",
+    "**The App Store now lists apps — not parts of apps.** The signed catalog carries every manifest because the node's update layer needs their pins, and the store briefly listed them all: Mempool API, LND UI, Bitcoin UI, the Pine voice engines, the IndeeHub and Immich backends, the mesh router and friends. Components are hidden from the store listing (they still appear where they belong — the Services tab of My Apps, once installed), and four entries that never earned a tile are gone outright: MorphOS server (old), the Web5 DID wallet, Lightning Stack (an untracked upstream bundle — LND covers the need), and CryptPad (never tested).",
-    "**Crash dumps work on fresh installs as well as upgraded nodes.** The installer gate checks every kdump package inside the finished ISO, and `makedumpfile` is installed explicitly rather than accidentally relying on a recommended dependency that the minimal image deliberately omits.",
+    "**App icons now persist everywhere, in the proper container style.** Two fixes: installed apps render the icon from their own manifest — Cuprate no longer falls back to the generic A-mark on its Services tile — and the store grids (the Discover page) apply the same icon container treatment (backdrop, border, shadow) as My Apps, the detail pages, and Home. Manifest-declared UI apps also classify correctly again: Alby Hub installs into My Apps with a working tile, not into Services, because a probe miss no longer buries an app the manifest itself says has a frontend.",
-    "**Apps open over HTTPS when your node does.** Connect to your node over HTTPS and the apps you open — Vaultwarden in its own tab, BTCPay, Grafana, and the rest, on a remote browser or in the phone's in-app browser — now open on the same secure connection instead of silently dropping to plain HTTP. The node's app gate already served TLS on every app port; the dashboard was handing out `http://` addresses regardless of how you reached it. Ports the gate does not front (plain-HTTP publishes, and the API ports like Cuprate's RPC) deliberately stay on `http` — `https` there would simply fail to connect. Plain-HTTP access (the kiosk, LAN browsing) is unchanged.",
+    "**Installing from the store keeps you on the store page.** The install progress lives on the tile itself and the app appears in My Apps when it lands — no more being yanked to My Apps mid-browse."
    "**Every app in the store is now a first-class platform app.** The last stragglers — Nginx Proxy Manager, Tailscale, Ollama, CryptPad, and AdGuard Home — now carry full manifests: the node's app gate fronts their web ports (TLS on the same port, the node login where appropriate, embedding fixes, Tor), installs go through the orchestrator like every other app, and their pins live in the signed catalog. Ollama stays loopback-only — it is the assistant's local model backend, not a web app. The four apps retired earlier (FIPS, Nostr VPN, Routstr, Penpot) are finally dropped from the catalog, and Cuprate's manifest — which carried a duplicated metadata block that strict parsers reject — is fixed.",
    "**Newly signed apps appear in the App Store immediately.** The App Store now serves the release-signed catalog the node has already fetched and verified — so publishing a signed app (like Cuprate) makes it appear for every updated node without waiting for a dashboard release. The unsigned community catalog remains only as a fallback for nodes that can't reach the registry. The same signed catalog now also decides which ports serve TLS, so nothing is upgraded to `https` that can't answer it."
  ],
  "components": [
    {
-      "current_version": "1.8.7-alpha",
+      "current_version": "1.8.8-alpha",
-      "download_url": "https://source.archipelago-foundation.org/lfg2025/archy/releases/download/v1.8.7-alpha/archipelago",
+      "download_url": "https://source.archipelago-foundation.org/lfg2025/archy/releases/download/v1.8.8-alpha/archipelago",
      "name": "archipelago",
-      "new_version": "1.8.7-alpha",
+      "new_version": "1.8.8-alpha",
-      "sha256": "572accec81e73fbcd5218ddc41f5ec719deda30f104c838398fdfa85a7a276f0",
+      "sha256": "96f39b8db6f08386200e1eab91c8444a7758526e6034100c8a33907ff9263530",
-      "size_bytes": 63990960
+      "size_bytes": 64175864
    },
    {
-      "current_version": "1.8.7-alpha",
+      "current_version": "1.8.8-alpha",
-      "download_url": "https://source.archipelago-foundation.org/lfg2025/archy/releases/download/v1.8.7-alpha/archipelago-frontend-1.8.7-alpha.tar.gz",
+      "download_url": "https://source.archipelago-foundation.org/lfg2025/archy/releases/download/v1.8.8-alpha/archipelago-frontend-1.8.8-alpha.tar.gz",
-      "name": "archipelago-frontend-1.8.7-alpha.tar.gz",
+      "name": "archipelago-frontend-1.8.8-alpha.tar.gz",
-      "new_version": "1.8.7-alpha",
+      "new_version": "1.8.8-alpha",
-      "sha256": "26b8c12b1b3e6b5c93841f3713037f65d0ea6a52401bd28888eb8d2f5dc483b5",
+      "sha256": "7829b67edf8dec27997dd821650ed4d61aea721f802d46a8d47014f4b4246db1",
-      "size_bytes": 97779181
+      "size_bytes": 97730549
    }
  ],
-  "release_date": "2026-08-31",
+  "release_date": "2026-09-01",
-  "signature": "79332435d436e7bae1a5b0c12158b02083b681b6818ac90219021f1e39eb61a3e1039ed38ee8089006a0dec862fd92997e44a6c9ccf0be17e91a95cba5de6402",
+  "signature": "c839cbdcb356a503d87bc17f52b6e5f3a934ae1e72a891f2d21d85366f23debb224a2a40b9124bab50fe95444e01e27711690b1bc50062f40b7ed4f34e078d06",
  "signed_by": "did:key:z6Mkfu5LT8d4DjETtrkATvHh9Dvcbnr7zBCUwfau8Sw7DLWT",
-  "version": "1.8.7-alpha"
+  "version": "1.8.8-alpha"
 }
@@ -1,32 +1,30 @@
 {
  "changelog": [
-    "**What's New really does stop at v1.8.0 now.** The first correction removed old generated release blocks but missed six much older hand-written v1.2 sections at the bottom of the modal. Those sections are gone, and the release check now recognizes and rejects that legacy format too, so the history floor cannot falsely pass again.",
+    "**SSH over the mesh is now a first-class setting.** Settings gains an \"SSH over mesh\" card: off by default, and when you allow it the node's mesh firewall opens port 22 — either to every mesh peer (behind an explicit \"I understand\" confirmation, because that's a real exposure) or only to the mesh addresses you list. The rule is owned by the node (the `90-ssh.nft` drop-in), so it survives upgrades and daemon reinstalls, and the card tells you up front whether sshd is running, whether it listens on IPv6 (the mesh is IPv6-only — this is what a broken attempt looks like before it happens), and whether password login is on (keys-only is the recommended pairing). From Termux on your phone, `fipssh <user>@<node-npub>` connects once the toggle is on — the npub is the durable address, and the command is shown with a copy button on the card.",
-    "**The installer carries the same corrected release and Companion 0.5.28.** Its artifact gate now checks the companion APK version and the v1.8.0 What's New floor inside the finished ISO, so a stale frontend or phone app cannot be published under the current release label.",
+    "**The App Store now lists apps — not parts of apps.** The signed catalog carries every manifest because the node's update layer needs their pins, and the store briefly listed them all: Mempool API, LND UI, Bitcoin UI, the Pine voice engines, the IndeeHub and Immich backends, the mesh router and friends. Components are hidden from the store listing (they still appear where they belong — the Services tab of My Apps, once installed), and four entries that never earned a tile are gone outright: MorphOS server (old), the Web5 DID wallet, Lightning Stack (an untracked upstream bundle — LND covers the need), and CryptPad (never tested).",
-    "**Crash dumps work on fresh installs as well as upgraded nodes.** The installer gate checks every kdump package inside the finished ISO, and `makedumpfile` is installed explicitly rather than accidentally relying on a recommended dependency that the minimal image deliberately omits.",
+    "**App icons now persist everywhere, in the proper container style.** Two fixes: installed apps render the icon from their own manifest — Cuprate no longer falls back to the generic A-mark on its Services tile — and the store grids (the Discover page) apply the same icon container treatment (backdrop, border, shadow) as My Apps, the detail pages, and Home. Manifest-declared UI apps also classify correctly again: Alby Hub installs into My Apps with a working tile, not into Services, because a probe miss no longer buries an app the manifest itself says has a frontend.",
-    "**Apps open over HTTPS when your node does.** Connect to your node over HTTPS and the apps you open — Vaultwarden in its own tab, BTCPay, Grafana, and the rest, on a remote browser or in the phone's in-app browser — now open on the same secure connection instead of silently dropping to plain HTTP. The node's app gate already served TLS on every app port; the dashboard was handing out `http://` addresses regardless of how you reached it. Ports the gate does not front (plain-HTTP publishes, and the API ports like Cuprate's RPC) deliberately stay on `http` — `https` there would simply fail to connect. Plain-HTTP access (the kiosk, LAN browsing) is unchanged.",
+    "**Installing from the store keeps you on the store page.** The install progress lives on the tile itself and the app appears in My Apps when it lands — no more being yanked to My Apps mid-browse."
    "**Every app in the store is now a first-class platform app.** The last stragglers — Nginx Proxy Manager, Tailscale, Ollama, CryptPad, and AdGuard Home — now carry full manifests: the node's app gate fronts their web ports (TLS on the same port, the node login where appropriate, embedding fixes, Tor), installs go through the orchestrator like every other app, and their pins live in the signed catalog. Ollama stays loopback-only — it is the assistant's local model backend, not a web app. The four apps retired earlier (FIPS, Nostr VPN, Routstr, Penpot) are finally dropped from the catalog, and Cuprate's manifest — which carried a duplicated metadata block that strict parsers reject — is fixed.",
    "**Newly signed apps appear in the App Store immediately.** The App Store now serves the release-signed catalog the node has already fetched and verified — so publishing a signed app (like Cuprate) makes it appear for every updated node without waiting for a dashboard release. The unsigned community catalog remains only as a fallback for nodes that can't reach the registry. The same signed catalog now also decides which ports serve TLS, so nothing is upgraded to `https` that can't answer it."
  ],
  "components": [
    {
-      "current_version": "1.8.7-alpha",
+      "current_version": "1.8.8-alpha",
-      "download_url": "https://source.archipelago-foundation.org/lfg2025/archy/releases/download/v1.8.7-alpha/archipelago",
+      "download_url": "https://source.archipelago-foundation.org/lfg2025/archy/releases/download/v1.8.8-alpha/archipelago",
      "name": "archipelago",
-      "new_version": "1.8.7-alpha",
+      "new_version": "1.8.8-alpha",
-      "sha256": "572accec81e73fbcd5218ddc41f5ec719deda30f104c838398fdfa85a7a276f0",
+      "sha256": "96f39b8db6f08386200e1eab91c8444a7758526e6034100c8a33907ff9263530",
-      "size_bytes": 63990960
+      "size_bytes": 64175864
    },
    {
-      "current_version": "1.8.7-alpha",
+      "current_version": "1.8.8-alpha",
-      "download_url": "https://source.archipelago-foundation.org/lfg2025/archy/releases/download/v1.8.7-alpha/archipelago-frontend-1.8.7-alpha.tar.gz",
+      "download_url": "https://source.archipelago-foundation.org/lfg2025/archy/releases/download/v1.8.8-alpha/archipelago-frontend-1.8.8-alpha.tar.gz",
-      "name": "archipelago-frontend-1.8.7-alpha.tar.gz",
+      "name": "archipelago-frontend-1.8.8-alpha.tar.gz",
-      "new_version": "1.8.7-alpha",
+      "new_version": "1.8.8-alpha",
-      "sha256": "26b8c12b1b3e6b5c93841f3713037f65d0ea6a52401bd28888eb8d2f5dc483b5",
+      "sha256": "7829b67edf8dec27997dd821650ed4d61aea721f802d46a8d47014f4b4246db1",
-      "size_bytes": 97779181
+      "size_bytes": 97730549
    }
  ],
-  "release_date": "2026-08-31",
+  "release_date": "2026-09-01",
-  "signature": "79332435d436e7bae1a5b0c12158b02083b681b6818ac90219021f1e39eb61a3e1039ed38ee8089006a0dec862fd92997e44a6c9ccf0be17e91a95cba5de6402",
+  "signature": "c839cbdcb356a503d87bc17f52b6e5f3a934ae1e72a891f2d21d85366f23debb224a2a40b9124bab50fe95444e01e27711690b1bc50062f40b7ed4f34e078d06",
  "signed_by": "did:key:z6Mkfu5LT8d4DjETtrkATvHh9Dvcbnr7zBCUwfau8Sw7DLWT",
-  "version": "1.8.7-alpha"
+  "version": "1.8.8-alpha"
 }
@@ -1,30 +0,0 @@
 {
  "changelog": [
    "**SSH over the mesh is now a first-class setting.** Settings gains an \"SSH over mesh\" card: off by default, and when you allow it the node's mesh firewall opens port 22 — either to every mesh peer (behind an explicit \"I understand\" confirmation, because that's a real exposure) or only to the mesh addresses you list. The rule is owned by the node (the `90-ssh.nft` drop-in), so it survives upgrades and daemon reinstalls, and the card tells you up front whether sshd is running, whether it listens on IPv6 (the mesh is IPv6-only — this is what a broken attempt looks like before it happens), and whether password login is on (keys-only is the recommended pairing). From Termux on your phone, `fipssh <user>@<node-npub>` connects once the toggle is on — the npub is the durable address, and the command is shown with a copy button on the card.",
    "**The App Store now lists apps — not parts of apps.** The signed catalog carries every manifest because the node's update layer needs their pins, and the store briefly listed them all: Mempool API, LND UI, Bitcoin UI, the Pine voice engines, the IndeeHub and Immich backends, the mesh router and friends. Components are hidden from the store listing (they still appear where they belong — the Services tab of My Apps, once installed), and four entries that never earned a tile are gone outright: MorphOS server (old), the Web5 DID wallet, Lightning Stack (an untracked upstream bundle — LND covers the need), and CryptPad (never tested).",
    "**App icons now persist everywhere, in the proper container style.** Two fixes: installed apps render the icon from their own manifest — Cuprate no longer falls back to the generic A-mark on its Services tile — and the store grids (the Discover page) apply the same icon container treatment (backdrop, border, shadow) as My Apps, the detail pages, and Home. Manifest-declared UI apps also classify correctly again: Alby Hub installs into My Apps with a working tile, not into Services, because a probe miss no longer buries an app the manifest itself says has a frontend.",
    "**Installing from the store keeps you on the store page.** The install progress lives on the tile itself and the app appears in My Apps when it lands — no more being yanked to My Apps mid-browse."
  ],
  "components": [
    {
      "current_version": "1.8.8-alpha",
      "download_url": "https://source.archipelago-foundation.org/lfg2025/archy/releases/download/v1.8.8-alpha/archipelago",
      "name": "archipelago",
      "new_version": "1.8.8-alpha",
      "sha256": "96f39b8db6f08386200e1eab91c8444a7758526e6034100c8a33907ff9263530",
      "size_bytes": 64175864
    },
    {
      "current_version": "1.8.8-alpha",
      "download_url": "https://source.archipelago-foundation.org/lfg2025/archy/releases/download/v1.8.8-alpha/archipelago-frontend-1.8.8-alpha.tar.gz",
      "name": "archipelago-frontend-1.8.8-alpha.tar.gz",
      "new_version": "1.8.8-alpha",
      "sha256": "7829b67edf8dec27997dd821650ed4d61aea721f802d46a8d47014f4b4246db1",
      "size_bytes": 97730549
    }
  ],
  "release_date": "2026-09-01",
  "signature": "c839cbdcb356a503d87bc17f52b6e5f3a934ae1e72a891f2d21d85366f23debb224a2a40b9124bab50fe95444e01e27711690b1bc50062f40b7ed4f34e078d06",
  "signed_by": "did:key:z6Mkfu5LT8d4DjETtrkATvHh9Dvcbnr7zBCUwfau8Sw7DLWT",
  "version": "1.8.8-alpha"
 }
@@ -28,7 +28,7 @@ ARCHY_REGISTRY_FALLBACK=""
 # halts pending the BIP110/RDTS consensus decision, so a moving tag can freeze
 # the fleet's chain sync. Bumping this is a consensus decision.
 BITCOIN_KNOTS_IMAGE="$ARCHY_REGISTRY/bitcoin-knots:29.3.knots20260210"
-LND_IMAGE="$ARCHY_REGISTRY/lnd:v0.18.4-beta"
+LND_IMAGE="$ARCHY_REGISTRY/lnd:v0.21.2-beta"
 ELECTRUMX_IMAGE="$ARCHY_REGISTRY/electrumx:v1.18.0"
 # Mempool stack
@@ -43,18 +43,18 @@ POSTGRES_IMAGE="$ARCHY_REGISTRY/postgres:15.17"
 BTCPAY_POSTGRES_IMAGE="$ARCHY_REGISTRY/postgres:15.17"
 # Apps
-HOMEASSISTANT_IMAGE="$ARCHY_REGISTRY/home-assistant:2026.8.2"
+HOMEASSISTANT_IMAGE="$ARCHY_REGISTRY/home-assistant:2026.8.3"
 GRAFANA_IMAGE="$ARCHY_REGISTRY/grafana:10.2.0"
 UPTIME_KUMA_IMAGE="$ARCHY_REGISTRY/uptime-kuma:1"
 JELLYFIN_IMAGE="$ARCHY_REGISTRY/jellyfin:10.11.11"
 PHOTOPRISM_IMAGE="$ARCHY_REGISTRY/photoprism:240915"
 OLLAMA_IMAGE="$ARCHY_REGISTRY/ollama:latest"
-VAULTWARDEN_IMAGE="$ARCHY_REGISTRY/vaultwarden:1.37.1-alpine"
+VAULTWARDEN_IMAGE="$ARCHY_REGISTRY/vaultwarden:1.37.2-alpine"
 NEXTCLOUD_IMAGE="$ARCHY_REGISTRY/nextcloud:29"
 SEARXNG_IMAGE="$ARCHY_REGISTRY/searxng:latest"
 # OnlyOffice removed — incompatible with rootless Podman (internal postgres/rabbitmq fail)
 # Replaced by CryptPad (single Node.js process, e2e encrypted)
-FILEBROWSER_IMAGE="$ARCHY_REGISTRY/filebrowser:v2.27.0"
+FILEBROWSER_IMAGE="$ARCHY_REGISTRY/filebrowser:v2.63.23"
 NPM_IMAGE="$ARCHY_REGISTRY/nginx-proxy-manager:latest"
 # 2.39.1 is what the fleet has actually been running via the moving :latest
 # tag, and it is the version that wrote their databases. Pinning back to
@@ -62,7 +62,7 @@ NPM_IMAGE="$ARCHY_REGISTRY/nginx-proxy-manager:latest"
 # container was recreated: "database schema version does not align with the
 # server version" — it migrates a DB forward, never backward. Pinned
 # forward and published as a concrete tag so this is reproducible.
-PORTAINER_IMAGE="$ARCHY_REGISTRY/portainer:2.39.6"
+PORTAINER_IMAGE="$ARCHY_REGISTRY/portainer:2.45.0"
 # Networking
 TAILSCALE_IMAGE="$ARCHY_REGISTRY/tailscale:stable"
@@ -70,7 +70,7 @@ NETBIRD_DASHBOARD_IMAGE="docker.io/netbirdio/dashboard:v2.38.0"
 NETBIRD_SERVER_IMAGE="docker.io/netbirdio/netbird-server:0.71.2"
 NETBIRD_PROXY_IMAGE="docker.io/library/nginx:1.27-alpine"
 ALPINE_TOR_IMAGE="$ARCHY_REGISTRY/alpine-tor:0.4.8.13"
-ADGUARDHOME_IMAGE="$ARCHY_REGISTRY/adguardhome:v0.107.55"
+ADGUARDHOME_IMAGE="$ARCHY_REGISTRY/adguardhome:v0.107.79"
 # Fedimint
 FEDIMINT_IMAGE="$ARCHY_REGISTRY/fedimintd:v0.10.1"
@@ -114,7 +114,7 @@ INDEEDHUB_POSTGRES_IMAGE="$ARCHY_REGISTRY/postgres:16.13-alpine"
 INDEEDHUB_REDIS_IMAGE="$ARCHY_REGISTRY/redis:7.4.8-alpine"
 # Gitea (Git + Container Registry)
-GITEA_IMAGE="docker.io/gitea/gitea:1.23"
+GITEA_IMAGE="source.archipelago-foundation.org/lfg2025/gitea:1.27.3"
 # DWN (Decentralized Web Node)
Author	SHA1	Message	Date
ssmithxandClaude Sonnet 5	bcdf2c75be	fix(cuprate): file log level should be info, not cuprated's debug default The previous commit on this branch copied cuprated's raw --generate-config defaults (stdout=info, file=debug, max_log_files=7) verbatim. Turns out that's the wrong reference: compared against ssmithx@archy-dev-pa:/home/ssmithx/cuprate/Cuprated.toml — the actual dev config this app was built and tested against — file logging is meant to run at "info" with 14 rotated files, not the binary's raw "debug"/7. Confirmed live on amishparadise: podman logs (stdout) was already clean at info, but the on-disk file log (.local/share/cuprate/logs/<date>) was flooding with per-peer DEBUG gossip (~400KB in 2 minutes) because it inherited the binary default instead of the intended one. Left the resource-tuning knobs in the reference config (8GB target_max_memory, tokio/rayon thread counts, P2P connection counts, explicit reader_threads) out of this file — those were sized for ssmithx's dev box and don't apply here; this manifest's target_max_memory already stays deliberately under the container's 4Gi memory_limit. Regenerated releases/app-catalog.json (still unsigned). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ga6N8Jk1YdCTMMX1LjDpAr	2026-09-01 12:27:33 +00:00
ssmithxandClaude Sonnet 5	e77f60085d	fix(cuprate): make Cuprated.toml logging levels explicit apps/cuprate/manifest.yml only ever wrote network/target_max_memory/ rpc.restricted.enable into Cuprated.toml, so the [tracing.stdout] and [tracing.file] tables were silently absent — cuprated still applied its built-in info/debug/7 defaults, but nothing on disk showed it. Verified live on amishparadise 2026-09-01: the deployed 5-line file had no [tracing] section at all, and the level was only discoverable by running `cuprated --generate-config` and diffing. Add both tables to the manifest's files[].content with the same values cuprated already defaults to, so every new install ships a Cuprated.toml an operator can actually read and tune. overwrite:false means already-deployed nodes (amishparadise included) keep their existing file untouched — this only changes what fresh installs get. Regenerated releases/app-catalog.json (unsigned) to embed the updated manifest; needs scripts/sign-catalog.sh before it's authoritative for the fleet. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01Ga6N8Jk1YdCTMMX1LjDpAr	2026-09-01 12:19:20 +00:00
archipelago	6c31eb9d4a	chore(catalog): sign the LND 0.21.2 sweep	2026-09-01 07:45:39 -04:00
archipelago	63e6c64c63	fix(ci): drop the remaining stray Claude-worktree gitlinks	2026-09-01 05:27:15 -04:00
archipelago	4d8bb1fd44	fix(ci): drop a stray gitlink that broke every demo build A Claude worktree under aiui/ was committed as a submodule gitlink (160000) with no .gitmodules entry, so actions/checkout's recursive submodule pass exited 128 and every 'Build & push demo images' run since v1.8.6 failed. Removing the index entry — the worktree is local state and was never meant to be tracked.	2026-09-01 05:27:00 -04:00
archipelago	2b4b60013c	feat(lnd): build LND 0.21.2-beta in-house and sweep the pin Demo images / Build & push demo images (push) Failing after 40s Details Upstream publishes no docker images; our v0.18.4 image was built in-house. This pass: official v0.21.2-beta release binaries (sha256-verified against the signed release manifest), static, on alpine with the same entrypoint shape as our existing image, pushed to our registry and smoke-run. LND 0.21 auto-migrates the channel DB on first start (keeping a backup) — the Update button is user-initiated, never auto-applied.	2026-09-01 05:14:50 -04:00
archipelago	f0ef410948	chore(catalog): sign the swept pins	2026-09-01 04:52:28 -04:00
archipelago	19467e9b7c	chore(apps): sweep pin bumps — gitea 1.27.3, vaultwarden 1.37.2, filebrowser 2.63.23, home-assistant 2026.8.3, adguardhome 0.107.79, portainer 2.45.0, pine-whisper 3.6.0 Demo images / Build & push demo images (push) Failing after 39s Details First upstream sweep since v1.8.5: the safe patch/minor pins, mirrored into our registry first (source.archipelago-foundation.org/lfg2025/*). Held for their own careful passes: the majors (grafana 11, nextcloud, uptime-kuma 2, bitcoin-core 29, the DBs) and consensus-sensitive apps (fedimint, electrumx 2.0). LND 0.21.2 needs an in-house image build — upstream publishes none.	2026-09-01 04:50:49 -04:00
archipelago	628ed252b4	chore: publish release v1.8.8-alpha	2026-09-01 04:18:16 -04:00