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>
6.8 KiB
Unified Task Tracker — OTA 1.8.0 + Master Plan
Single working list for everything left before 1.8.0 ships and the next master-plan
exit criteria (multinode + workstreams B/C/D) are met. Supersedes the open-task
sections of docs/SESSION-1.8.0-OTA-PROGRESS.md and docs/PRODUCTION-MASTER-PLAN.md
as the day-to-day tracker — those docs remain the historical record / detailed
narrative and are still linked from here where useful. Ordered fastest/simplest
first so we work top-down instead of hunting across docs.
Verified against actual code state on 2026-07-01 (not just doc text — several items the source docs still listed as "open" turned out to already be shipped; those are marked ✅ below with the commit that did it, so we stop re-litigating them).
Tier 0 — Quick / mechanical, no blockers
- Update
tests/lifecycle/TESTING.md's stale Release Gates checklist (lines 289–296) — several boxes are unchecked but actually true now:- #1 bitcoin-stops: covered by
tests/lifecycle/bats/bitcoin-knots.batsstop/restart tier, included in the 5/5 green gate run. - #2
ARCHY_ITERATIONS=5on .228: GREEN 2026-06-23 per CLAUDE.md — check the box. - #5 cargo 0 warnings: confirmed 0 warnings on
cargo build --release(2026-07-01). - #7 layman changelog:
CHANGELOG.mdis backfilled with layman-readable entries through v1.8.00-alpha — check the box. - Leave #3 (multinode), #4 (backend-survives-restart / Phase-3 default-on), #6 (LoC decision), #8 (tag pushed) unchecked — genuinely still open, see Tier 2/3.
- #1 bitcoin-stops: covered by
Finish the archival/full-node manifest generalization— investigated 2026-07-01: the hardcoded fallback names independencies.rs:48-52(electrs,mempool-electrs,mempool-web) are legacy alias ids forelectrumx/mempool, resolved via id-mapping in a dozen other places (install.rs,runtime.rs,config.rs, etc.), not separate un-migrated apps with their own manifests.electrumxandmempoolthemselves already declarebitcoin:archival. The fallback is correct as-is — not tech debt, closing this item rather than risk breaking alias resolution.Confirm/close the Portainer image-pin item— confirmed 2026-07-01:146.59.87.168:3000/lfg2025/portainer:2.19.4is present inpodman imageson all 3 LAN nodes (.116/.198/.228), i.e. actually resolvable/pulled from the mirror. Not a live bug.grafana Quadlet "stuck activating"— checked live on .116 (2026-07-01):grafana.serviceisactive (running), containerUp 2 hours (healthy). The 2026-06-21 report is stale for grafana. strfry still unconfirmed — not installed on any of .116/.198/.228 to check directly; low priority until someone actually needs it installed.
Tier 1 — Medium effort, unblocked
- immich → Quadlet migration — last legacy in-cgroup app; manifest still
declares plain
immich-postgres/immich-rediscontainers instead of Quadlet units (apps/immich/manifest.yml). Blocks deleting the legacycreate_containerpath (see Phase 3.5 in master plan). - Netbird reinstall adoption path — verify whether the adopted-container path
actually skips cert/file rendering on reinstall (unconfirmed either way;
wait_for_adopted_containerininstall.rs:326exists but no dedicated cert-render check was found). Reproduce on .228 (has netbird installed) before fixing. - TanStack Query (or equivalent) investigation — still just a backlog idea, no code. Time-box a spike: is neode-ui's current fetch/store pattern actually causing real bugs, or is this nice-to-have? Decide before spending real time.
Tier 2 — High effort, unblocked (the actual next exit criteria)
- Multinode test pass (
docs/multinode-testing-plan.md) — per-node preconditions on .198 + rest of fleet, then 5× on-node gate per node, then cross-node federation/mesh/transport suites. This is the literal "next exit criterion" called out inCLAUDE.md. - Phase-3 Quadlet default-flip — code is validated + opt-in via
ARCHIPELAGO_USE_QUADLET_BACKENDS=trueon .228/.198 already (confirmed live 2026-07-01). Flip needs: re-test on a healthy idle legacy node, then flip the default, then multinode gate re-run. - Per-app test coverage for the ~30 apps with zero automated coverage — framework exists (bats + reusable helpers), just needs per-app suites written.
- Convert remaining multi-container legacy stacks to the manifest-owned model
(workstream A tail) — netbird's legacy installer is already deleted (
89d397bb); immich (see Tier 1) and any other multi-container stacks are what's left. - Developer tooling CLI suite (validate/render/local-install/lifecycle-test) — APP-PACKAGING-MIGRATION-PLAN.md step 5, needed before external devs can publish.
Tier 3 — Blocked on a decision or resource only you can supply
- Version naming decision (1.7.99-alpha → 1.8.0 vs 1.8.00-alpha) — code is otherwise ready to tag; this is a one-line decision, then a mechanical bump + tag + push. Needs your call, not more engineering.
- Workstream B signing ceremony —
core/archipelago/src/trust/anchor.rs:21still hasRELEASE_ROOT_PUBKEY_HEX = None. Needs the offlineRELEASE_MASTER_MNEMONICto rundocs/workstream-b-signing-runbook.md's 4-step ceremony — can't be automated by me. - Bitcoin multi-version fleet-wide OTA —
.228fully working on branch, per your prior gating this rollout is explicitly held for your decision on timing (docs/bitcoin-version-bulletproof-rollout.md). - 3ccc stock-Meshtastic RF validation — needs a live send/receive test with physical radios in your hands; code fix is in place, just unverified live.
Backlog — deferred, no scope decided, low priority
- Marketplace protocol (workstream C) — design-only (
docs/marketplace-protocol.md), no tooling/trust UX built. Future work, not urgent. - DHT distribution (workstream D) — confirmed design-only, no code
(
docs/dht-distribution-design.mdexplicitly says "Status: Design (no code yet)"); an experimental iroh provider skeleton exists behind a feature flag for future PoC measurement, nothing fleet-facing. - Custom live voice-call protocol — deprioritized 2026-07-01 per user request; scope not yet decided. Revisit after the tiers above are worked down.
Historical narrative and detailed per-session logs remain in
docs/SESSION-1.8.0-OTA-PROGRESS.md and docs/PRODUCTION-MASTER-PLAN.md §6/§8b —
this doc is the live "what's left, in priority order" list. Update it (don't just
append to the old docs) as items close or new ones surface.