docs(messaging): parallel milestones (#386)

* feat: Add Nimble Migration and Fleet Stability milestones

* feat: Introduce Support Mobile Platforms milestone

* feat: Define Status integration milestones for Logos Chat and Delivery

Author: igor-sirotin

content/messaging/roadmap/milestones/2026-fleet-stability.md

@@ -0,0 +1,82 @@
+---
+title: Fleet Stability
+tags:
+  - messaging-milestone
+date: 2026-02-01
+---
+
+# Fleet Stability
+
+**Estimated date of completion**: Ongoing
+
+**Resources Required**:
+- 1 Delivery engineer (intermittent)
+- Infra team support
+
+Ensure all Logos Delivery production fleets are stable, monitored, and recoverable. This covers:
+- `logos.dev` — Logos testnet development fleet
+- `logos.test` — Logos testnet staging fleet
+- `status.prod` — Status production fleet
+- `waku.sandbox` — Waku sandbox fleet
+
+**Note on monitoring**: Status and Waku fleets (`status.prod`, `waku.sandbox`) already have monitoring infrastructure in place (Grafana, Kibana, alerts). For Logos fleets (`logos.dev`, `logos.test`), not all monitoring is available yet — in particular, Grafana dashboards are not possible because Logos Core does not yet expose metrics of modules. This is a blocker that needs to be resolved with the Logos Core team.
+
+## Definition of Done
+
+This milestone is considered complete when **all** of the following are true for every operated fleet:
+
+1. **Monitoring**: Dashboards exist showing node health, connectivity, message throughput, and resource usage. For Logos fleets, this requires Logos Core to expose module metrics.
+2. **Alerting**: Alerts fire for node crashes, database issues, connectivity drops, and resource exhaustion.
+3. **Crash reporting**: Sentry is integrated and reporting crashes for fleet builds.
+4. **Stability**: No known P0 or P1 stability issues. P0 = fleet-wide outage or data loss. P1 = recurring crashes or degraded service affecting users.
+
+## Deliverables
+
+### Integrate Sentry for crash reporting
+
+**Owner**: Delivery Team
+
+- Compile-time flag (`-d:sentry`) for public/open-source builds (no telemetry code present)
+- Runtime dynamic loading for fleet builds
+- Dual approach satisfies privacy narrative while enabling crash reporting for operated fleets
+- Sentry project configured and receiving reports from all fleet nodes
+
+**Done when**: All fleet nodes report crashes to Sentry. Crash reports include stack traces and node metadata.
+
+### Fleet monitoring dashboards for Logos fleets
+
+**Owner**: Delivery Team + Infra + Logos Core Team
+
+- Logos Core exposes module metrics (blocker — coordinate with Logos Core team)
+- Dashboards for `logos.dev` and `logos.test` showing:
+  - Node uptime and restart frequency
+  - Message send/receive rates and latency
+  - Peer connectivity (number of peers, connection stability)
+  - Resource usage (CPU, memory, disk, bandwidth)
+  - Database health (size, query latency, corruption indicators)
+
+**Done when**: Dashboards are deployed and accessible for Logos fleets. Data is current and accurate. (Status and Waku fleets already have this.)
+
+### Fleet alerting for Logos fleets
+
+**Owner**: Delivery Team + Infra
+
+- Alerts configured for:
+  - Node crash or unexpected restart
+  - Database corruption or excessive size
+  - Connectivity drops (below minimum peer threshold)
+  - Memory or disk exhaustion
+  - Message delivery failure rate exceeding threshold
+
+**Done when**: Alerts fire within 5 minutes of incident. (Status and Waku fleets already have alerting.)
+
+### Resolve known fleet stability issues
+
+**Owner**: Delivery Team
+
+- Address recurring crashes reported in DST testing
+- Database corruption issues
+- Memory leaks in long-running nodes
+- Discovery issues blocking DST benchmarking
+
+**Done when**: No known P0 or P1 stability issues across all fleets for 30 consecutive days.

content/messaging/roadmap/milestones/2026-nimble-migration.md

@@ -0,0 +1,49 @@
+---
+title: Nimble Migration
+tags:
+  - messaging-milestone
+date: 2026-01-15
+---
+
+# Nimble Migration
+
+**Estimated date of completion**: Q2 2026
+
+**Resources Required**:
+- 1 Delivery engineer (intermittent)
+- 1 Chat engineer (intermittent)
+
+Migrate all main Logos Messaging Nim repositories from the legacy build system to Nimble package manager. This enables reproducible builds, proper dependency management, and aligns with the broader Logos ecosystem tooling.
+
+Note: `libchat` is a Rust library and does not use Nimble.
+
+## Deliverables
+
+### Migrate logos-delivery to Nimble
+
+**Owner**: Delivery Team
+
+- `logos-messaging/logos-delivery` uses Nimble for build and dependency management
+- CI/CD updated accordingly
+- Nix flake integration with Nimble
+
+### Migrate logos-chat to Nimble
+
+**Owner**: Chat Team
+
+- `logos-messaging/logos-chat` uses Nimble for build and dependency management
+- CI/CD updated accordingly
+
+### Migrate nim-sds to Nimble
+
+**Owner**: Delivery Team
+
+- `logos-messaging/nim-sds` uses Nimble for build and dependency management
+
+### Verify Nimble-based builds across all platforms
+
+**Owner**: Delivery Team
+
+- Linux, macOS, Windows builds verified
+- Nix flake outputs working with Nimble
+- Cross-compilation for mobile targets verified (prerequisite for mobile support milestone)

content/messaging/roadmap/milestones/2026-status-logos-chat-integration.md

@@ -0,0 +1,77 @@
+---
+title: 'Status: Logos Chat Integration'
+tags:
+  - messaging-milestone
+date: 2026-02-01
+---
+
+# Status: Logos Chat Integration
+
+**Estimated date of completion**: ~Q4 2026 (after Logos Chat Developer Preview)
+
+**Resources Required**:
+- 1 Chat engineer
+- Status Core team (`status-go` changes)
+- QA support from both teams
+
+Status switches from its current chat protocol implementation to Logos Chat, consumed through Logos Core. This is the largest integration milestone and replaces Status's chat backend for 1:1 chats, group chats, and eventually communities.
+
+**Prerequisites**:
+- [Chat — Developer Preview](2026-chat-developer-preview) (v0.3) must be delivered
+- [Logos Core Integration — Phase 2](2026-logos-core-integration-phase-2) (v0.2) — Chat and Delivery modules working through Logos Core
+
+**Migration approach**:
+- Both parties (old Status Protocol and new Logos Chat) need to be supported in parallel during migration
+- Migration order: 1:1 chats → group chats → communities
+- Backend must support running old and new protocols simultaneously
+- Communities are "groups of group chats" — Status keeps its own token-gated access layer on top
+
+**Key constraints** (from CTO alignment):
+- Communities are not the Messaging team's responsibility
+- Integration maintenance transfers to Status after initial delivery
+- Messaging team involvement should remain minimal post-handoff
+
+## Related milestones
+
+- [Chat — Foundations](2025-create-chat-sdk-mvp.md) (v0.1) — 1:1 chats
+- [Chat — Group Conversations](2025-extend-chat-sdk-with-group-conversations) (v0.2) — group chats via de-MLS
+- [Chat — Developer Preview](2026-chat-developer-preview) (v0.3) — first external release
+- [Logos Core Integration — Phase 2](2026-logos-core-integration-phase-2) — Chat ↔ Delivery through Logos Core
+
+## Risks
+
+| Risk                          | (Accept, Own, Mitigation)                                                                                                        |
+| ----------------------------- | -------------------------------------------------------------------------------------------------------------------------------- |
+| Migration complexity          | Running two chat protocols in parallel is complex. Clear migration path and rollback strategy needed.                             |
+| Status team capacity          | Status Core team needs to allocate developers for `status-go` integration. Coordination needed early.                             |
+| Communities scope creep       | Communities architecture ("groups of group chats") may require Messaging team involvement beyond initial expectations.             |
+| de-MLS group size limits      | de-MLS targets up to 10,000 members, but Status communities may need more. Scaling assessment needed.                             |
+| Breaking changes              | Logos Chat is still evolving. Breaking changes between Developer Preview and GA may impact Status integration timeline.            |
+
+## Deliverables
+
+### Integrate Logos Chat 1:1 chats in Status
+
+**Owner**: Chat Team + Status Core
+
+- Status uses Logos Chat for 1:1 conversations
+- Consumed through Logos Core
+- Migration path from existing Status 1:1 chat protocol
+- Go bindings via C-bindings from Logos Core
+
+### Integrate Logos Chat group chats in Status
+
+**Owner**: Chat Team + Status Core
+
+- Status uses Logos Chat group chats (de-MLS) for group conversations
+- Migration path from existing Status group chat protocol
+- Multi-device support through de-MLS installations
+
+### Define communities architecture on Logos Chat
+
+**Owner**: Status Core (with Messaging team advisory)
+
+- Communities as "groups of group chats" using Logos Chat
+- Token-gated access layer remains Status-owned
+- No separate community protocol from Messaging team
+- Logos Chat provides the group chat substrate; Status builds community features on top

content/messaging/roadmap/milestones/2026-status-logos-delivery-integration.md

@@ -0,0 +1,81 @@
+---
+title: 'Status: Logos Delivery Integration'
+tags:
+  - messaging-milestone
+date: 2026-02-01
+---
+
+# Status: Logos Delivery Integration
+
+**Estimated date of completion**: TBD (after Messaging API is integration-ready)
+
+**Resources Required**:
+- 1 Delivery engineer (50% of work)
+- Status Core team — 1 engineer (50% of work)
+- Infra team (fleet management, CI)
+
+Status currently has partial Logos Delivery (nwaku) integration in relay mode, with significant issues (see [current state](2024-nwaku-in-status-desktop)). The integration plan has been agreed:
+
+1. **Remove nwaku CI jobs** — stop maintaining duplicated CI for go-waku and nwaku
+2. **Remove existing nwaku integration** from `status-go`
+3. **Wait** for Messaging API to be integration-ready
+4. **Integrate Messaging API** in `status-go` — full switch to Logos Delivery, drop `go-waku` dependency
+5. **Remove existing peer management** from `status-go` — peer management is encapsulated in Logos Delivery Messaging API
+
+Work is split **50/50** between Delivery team and Status team. Delivery team provides the library and Go bindings; Status team adapts `status-go`.
+
+## Related milestones
+
+- [Integrate nwaku in Status Desktop relay mode only](2024-nwaku-in-status-desktop) — current partial state (to be removed)
+- [Messaging API — General Availability](2026-messaging-api-general-availability) — prerequisite (includes edge mode for mobile, Subscribe API)
+- [Foundation for Communities Optimization](2025-foundation-for-communities-optimization) — content topic sharding for communities
+- [E2E Reliability in Status Communities](2024-e2e-reliability-protocol) — SDS protocol for communities
+
+## Risks
+
+| Risk                        | (Accept, Own, Mitigation)                                                                                               |
+| --------------------------- | ----------------------------------------------------------------------------------------------------------------------- |
+| Go bindings for C libraries | `status-go` needs Go bindings for Logos Delivery C-bindings. Extra development work.                                     |
+| Messaging API readiness     | Integration cannot begin until Messaging API is stable enough. Track readiness closely.                                  |
+| DST blocked on discovery    | DST testing of Logos Delivery in Status is blocked by a discovery issue. Needs resolution before meaningful benchmarking. |
+
+## Deliverables
+
+### Remove existing nwaku integration
+
+**Owner**: Delivery Team + Status Core
+
+- Remove nwaku CI jobs from `status-go` (no more duplicated jobs)
+- Remove existing nwaku relay integration code from `status-go`
+- Status continues with go-waku only until Messaging API is ready
+
+### Integrate Messaging API in status-go
+
+**Owner**: Delivery Team (library + Go bindings) + Status Core (status-go adaptation)
+
+- Provide Go bindings for Logos Delivery Messaging API (via C-bindings)
+- Replace go-waku usage in `status-go` with Messaging API (send, health, subscribe)
+- Drop `go-waku` dependency entirely
+- Remove existing peer management from `status-go` — Messaging API handles this internally
+- Single implementation path in CI
+
+### Enable SDS protocol for Status Communities
+
+**Owner**: Delivery Team
+
+Related milestones:
+- [Foundation for Communities Optimization](2025-foundation-for-communities-optimization) — content topic sharding for communities
+- [E2E Reliability in Status Communities](2024-e2e-reliability-protocol) — SDS protocol integration
+
+SDS in Status Communities provides:
+- Detection of missed messages in community channels
+- Resending unacknowledged messages
+- Recovery of missed messages via store queries
+
+### Enable RLN for Status on Status Network
+
+**Owner**: Delivery Team
+
+Using the [pluggable RLN membership interface](2026-add-support-for-rln-on-lee), configure Status to use RLN with the EVM-based backend on Status Network (gasless L2).
+
+**Dependency**: AnonComms RLN Prover for gasless L2 transactions.

content/messaging/roadmap/milestones/2026-support-mobile-platforms.md

@@ -0,0 +1,66 @@
+---
+title: Support Mobile Platforms
+tags:
+  - messaging-milestone
+date: 2026-02-21
+---
+
+# Support Mobile Platforms
+
+**Estimated date of completion**: Required for Mainnet
+
+**Resources Required**:
+- 1 Delivery engineer
+- 1 Chat engineer
+- Logos Core team for mobile runtime support
+
+Ensure that Logos Chat and Logos Delivery modules are usable in Logos Core on mobile platforms (iOS and Android).
+
+Edge mode (light push, filter, peer exchange) is implemented in earlier milestones ([Messaging API — General Availability](2026-messaging-api-general-availability)). This milestone ensures it fully works on mobile, with testing and DST validation.
+
+This involves three areas:
+1. **nim-ffi mobile support** — Ensure C-bindings produced by nim-ffi work on iOS and Android
+2. **Edge mode on mobile** — Verify and test edge mode on resource-constrained mobile devices. Edge mode implementation is done in previous milestones; this milestone covers mobile-specific testing, tuning, and DST validation.
+3. **Logos Core on mobile** — Verify no multiple-runtime conflicts when running Chat and Delivery modules in a single mobile process
+
+## FURPS
+
+- [Nim FFI](/messaging/furps/application/nim_ffi.md): S2
+- [Messaging API](/messaging/furps/core/messaging_sdk.md): F2 (edge mode — verification on mobile)
+
+## Risks
+
+| Risk                     | (Accept, Own, Mitigation)                                                                                              |
+| ------------------------ | ---------------------------------------------------------------------------------------------------------------------- |
+| Mobile cross-compilation | Nim cross-compilation for iOS and Android is not straightforward. Requires build system work.                           |
+| Single-process constraint | Mobile platforms require a single process. Multiple async runtimes (Nim Chronos + Rust Tokio) may conflict.            |
+| Resource constraints     | Mobile devices have limited bandwidth, battery, and memory. Edge mode must be tuned for these constraints.             |
+
+## Deliverables
+
+### Ensure nim-ffi libraries work on mobile platforms
+
+**Owner**: Delivery Team
+
+**Feature**: [Nim FFI](/messaging/furps/application/nim_ffi.md)
+
+**FURPS**:
+- S2. The exposed C library can be used in Logos Core for mobile: iOS and Android.
+
+### Verify and test edge mode on mobile
+
+**Owner**: Delivery Team + DST
+
+Edge mode is implemented in [Messaging API — General Availability](2026-messaging-api-general-availability). This deliverable covers:
+- Testing edge mode on iOS and Android devices
+- Battery and bandwidth impact assessment
+- Performance tuning for mobile constraints
+- DST validation of reliability in edge mode on mobile
+
+### Verify Chat and Delivery modules on Logos Core mobile
+
+**Owner**: Delivery Team + Chat Team
+
+- No multiple-runtime conflicts in single-process mobile environment
+- Performance testing on mobile devices
+- End-to-end validation: 1:1 chats, group chats, identity, on mobile