docs/UNIFIED-TASK-TRACKER.md replaces hunting across SESSION-1.8.0-OTA-PROGRESS.md and PRODUCTION-MASTER-PLAN.md for "what's left" — fastest/simplest tasks first. Verified against live code/nodes rather than trusting doc text: several previously "open" items (bind-dir chown, netbird legacy installer, launch-port fallback, archival-bitcoin manifest field, progress-UI monotonicity, all-apps coverage, fedimint test coverage, changelog backfill, portainer image pin, grafana quadlet activation) turned out already shipped or non-issues, and are closed out here. TESTING.md's release-gate checklist updated to match reality (cargo warnings, 5x gate, changelog already green; multinode/backend-default-flip/tag genuinely open). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
3.7 KiB
Archipelago — agent guide
✅ Single-node production gate is GREEN (2026-06-23)
tests/lifecycle/run-gate.sh is 5/5 on .228, 0 failures — the single-node exit
criterion is met and the priority banner is demoted. Next exit-criteria: the
multinode pass (docs/multinode-testing-plan.md) and workstreams B/C/D.
For day-to-day work, use docs/UNIFIED-TASK-TRACKER.md — the consolidated,
priority-ordered "what's left" list across the 1.8.0 OTA and master-plan docs
(fastest/simplest tasks first). It supersedes hunting through the two source docs
below for open items; those remain the narrative/history.
Read docs/PRODUCTION-MASTER-PLAN.md first — it is still the authoritative plan
for the north star: a world-class, developer-ready app platform where every app
is manifest-driven, manifests ship via the signed registry (not OTA disk files),
and third-party developers publish apps via an external/decentralized registry —
all rootless, secure, robust, and 100%-uptime-capable. It no longer overrides all
ad-hoc direction now that the gate is green, but it remains the source of truth for
sequencing the remaining workstreams.
Detailed sub-plans (all linked from the master):
- App platform / packaging phases + security model →
docs/APP-PACKAGING-MIGRATION-PLAN.md - Registry-distributed manifests (in progress) →
docs/registry-manifest-design.md - External/decentralized marketplace for devs →
docs/marketplace-protocol.md - Current per-app state →
docs/app-registry-status-2026-06-21.md - Production test gate (exit criterion) →
tests/lifecycle/TESTING.md
Invariants (never violate)
- Rootless Podman only. No rootful, no Docker-socket mounts, no privileged containers unless explicitly approved.
- No per-app Rust installers / no OS-level reliance. Apps are declarative;
the orchestrator owns the lifecycle.
install_immich_stack(hardcodedpodman run+sudo chown) is the anti-pattern being deleted, not a template. - Secrets are manifest-declared (
generated_secrets, materialised bycontainer::secrets, 0600/rootless) — never hardcoded, per-app, or logged. - Migrations never destroy data — preserve
/var/lib/archipelago/<app>, secrets, credentials, ports, and adoption container names; keep a rollback path. - Verify on the real node .228 before any tag. (Fleet-wide multinode
verification is a separate plan:
docs/multinode-testing-plan.md.)
Build / verify
- Rust workspace root is
core/(no Cargo.toml at repo root).cargofromcore/. - If a
cargo test/build hitsrust-lld: undefined hidden symbol, it's incremental-cache corruption — rebuild withCARGO_INCREMENTAL=0. - Frontend:
neode-ui/→npm run buildoutputs toweb/dist/neode-ui/. Grep the built bundle for new strings before shipping (build can silently no-op). - App manifests load from disk on nodes at
/opt/archipelago/apps/*/manifest.yml(today); the goal is to distribute them via the signed catalog instead.
Production test gate (definition of done)
tests/lifecycle/run-gate.sh green across install / UI / stop / start / restart /
reinstall / reboot-survive / archipelago-restart-survive / uninstall — 5× on
.228 (ARCHY_ITERATIONS=5). Run the gate ON the node (it uses local podman/systemctl/bitcoin
probes), not via RPC from another host. ✅ GREEN 2026-06-23 (5/5, 0 not-ok) — keep it
green (re-run after orchestrator/lifecycle changes); regressions are top priority again.
Multinode testing (.198 + the rest of the fleet) is a SEPARATE plan —
docs/multinode-testing-plan.md — not part of this single-node gate criterion, and is
the next exit criterion now that single-node is green.