feat(pine): node-status endpoint + Claude voice brain + mesh announcements + wake-word groundwork

- GET /api/pine/status: public tier (version/uptime/bitcoin/mesh facts) for
  the Pine page; bearer-token tier (Lightning balances, latest mesh message)
  for the seeded Home Assistant sensors. Token minted 0600 at
  secrets/pine-status-token; nginx location ships via the bootstrap
  self-heal + canonical ISO conf. Replaces the per-node socat forwarder and
  bitcoind RPC credentials living in HA's configuration.yaml.
- pine_ha seeder: REST sensors + four ask-Archy intents (block height,
  peers, sync %, Lightning balance) with LLM tool descriptions; Claude
  conversation agent (anthropic entry from the node's claude-api-key) set as
  pipeline default with prefer_local_intents so exact phrases stay local and
  fuzzy ones tool-route through Claude; mesh-message announce automation on
  every Assist satellite; bounded config markers with legacy-block migration.
- pine-openwakeword joins the pine stack (all lifecycle sites) — on-node
  wake-word engine groundwork for the custom "Yo Archy" model.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

core/archipelago/src/crash_recovery.rs

@@ -768,6 +768,7 @@ fn should_auto_start_stopped_container(name: &str, include_stack_members: bool)
                 | "netbird"
                 | "pine-whisper"
                 | "pine-piper"
+                | "pine-openwakeword"
                 | "pine"
         )
 }
@@ -836,9 +837,10 @@ fn stack_recovery_specs() -> &'static [StackRecoverySpec] {
             aliases: &[
                 ("pine-whisper", "pine-whisper"),
                 ("pine-piper", "pine-piper"),
+                ("pine-openwakeword", "pine-openwakeword"),
                 ("pine", "pine"),
             ],
-            containers: &["pine-whisper", "pine-piper", "pine"],
+            containers: &["pine-whisper", "pine-piper", "pine-openwakeword", "pine"],
             // The launcher only depends on the two engines; whisper is the
             // heaviest/first member, so treat it as the stack anchor (its
             // presence means the stack was really installed, not orphan debris).