docs: align roadmap with Product SDK

[knzeng-e]

Summary

• replans the Dotify roadmap against the current Product SDK / Playground / Humanity direction while keeping standalone web first-class
• adds an unnumbered Product SDK roadmap note that supersedes draft PR docs: align Dotify with Polkadot Product standards and production UX #91 and avoids the duplicate ticket-25 problem
• updates backlog/public docs, Product/technical memory, README, spec, and the GitHub Pages roadmap section
• adds docs/backlog/backlog.json plus scripts/backlog-sync.mjs and a Backlog sync workflow for Project 5 drift checks

Product SDK evidence

Verified on 2026-07-14 against paritytech/product-sdk@2f359bb (@parity/product-sdk 0.17.0). The docs now treat Product SDK / Playground as prototype, reference, unaudited code; Product mode is a progressive enhancement, not a blocker for first sound.

GitHub sync performed

• added Project 5 fields: Priority, Track, Phase, Type, Backlog doc
• added [Product SDK][P1] Prove Product host compatibility before integration #85-[UX][P1] One-click shared listening and wallet-later onboarding #90 to Project 5
• set [Sprint 2][P1] Observability and health checks #11 to In Progress, [Product SDK][P1] Prove Product host compatibility before integration #85-[UX][P1] One-click shared listening and wallet-later onboarding #90 and [Production MVP][P1] Validate injected wallet support on public wallets/devices #33/[Production MVP][P0] Deploy hosted signaling infrastructure for public rooms #36/[Production MVP][P0] Production environment validation and unsafe-secret guards #37 to Todo, delivered records to Done
• closed [Production MVP][P0] Move Pinata uploads behind a backend service #34 and [Production MVP][P0] Per-track key custody and wallet-signed content-key requests #35 as superseded by delivered backend/key-delivery work
• labeled active backlog issues with dotify-backlog and Product SDK scope where relevant
• added scope-sync comments to [Sprint 2][P2] Proof of Personhood integration research #12, [Production MVP][P1] Validate injected wallet support on public wallets/devices #33, [Product SDK][P1] Prove Product host compatibility before integration #85, and [Rooms][P1] Productionize WebRTC with TURN, quality metrics, and an SFU path #89

Validation

• node scripts/backlog-sync.mjs --check --offline
• node scripts/backlog-sync.mjs --check --live
• git diff --check

Both backlog checks pass with intentional warnings for ticket 24 as an epic without a single issue and the existing ticket-08 tracker sidecar.

[netlify]

✅ Deploy Preview for muzinga canceled.

Name	Link
🔨 Latest commit	a2e6c05
🔍 Latest deploy log	https://app.netlify.com/projects/muzinga/deploys/6a592eeeba83740008260331

[knzeng-e]

@claude please review this

[claude]

Claude finished @knzeng-e's task in 2m 9s —— View job

---

Review complete

• Gather context (PR diff, CLAUDE.md, backlog docs)
• Review docs/backlog changes for consistency
• Review scripts/backlog-sync.mjs and workflow
• Review docs/index.html alignment rule compliance
• Post review feedback

This is a large, well-organized docs-only change (1031/-116 across 14 files, no application code touched). Cross-checked the issue numbers, backlog IDs, and phase/track labels across backlog.json, improvement-plan.md, the new roadmap note, docs/backlog/README.md, README.md, and spec.md — they line up consistently (e.g. #85-#90 triage in the roadmap doc matches the manifest and the improvement-plan table; ticket 24/25 statuses match across all three summary tables).

Finding: CLAUDE.md's "Active ticket" section is now stale relative to this PR

CLAUDE.md (lines 59-68) still says:

Design track · Ticket 25 — Thresholds functional v1 ... The active PR also keeps the hosted signaling and observability surfaces from tickets 04/10 aligned with the current UI ...

But this PR itself declares ticket 25 delivered everywhere else:

• docs/backlog/backlog.json: "id": "25", "kind": "record", "note": "Delivered by merged PR #92."
• docs/backlog/README.md:74: "Delivered on main by merged PR feat: harden production readiness and rebuild Dotify UX #92; follow-up validation passed 2026-07-14"
• docs/backlog/25-thresholds-functional-v1.md: "landed on main through merged PR feat: harden production readiness and rebuild Dotify UX #92"

CLAUDE.md is listed in the repo's own "Source of truth" reading list and is what a future Claude Code session (or engineer) will read first to find the current active ticket — right now it points at a ticket this same PR marks as done, with no replacement "Now" ticket named. Since the PR restructures execution order into Phase 0-6 with #11/#36/#37/#90 as the immediate "Now" work, CLAUDE.md's Active ticket section should probably be updated in this PR (or a fast follow) to point at that new phase/ticket set instead of ticket 25.

Everything else

• scripts/backlog-sync.mjs: sound structure — validates manifest shape, cross-references docs on disk, flags duplicate ticket-number files, and the live check queries gh issue view for Project 5 membership/labels. The offline/live warning behavior (ticket 24 epic with no single issue, ticket 08 duplicate-number warning) matches what the PR description claims.
• .github/workflows/backlog-sync.yml: offline check runs on relevant pull_request paths; live check is correctly gated behind workflow_dispatch/schedule and requires PROJECT_SYNC_TOKEN, so it won't run (or fail) on every PR.
• docs/index.html: updated in the same PR per the GitHub Pages alignment rule, footer/resources links now point at the new roadmap doc instead of the ticket-25 doc, and the "Current gate" copy was refreshed to match the new priorities — consistent with the CLAUDE.md GitHub Pages alignment rule.
• No curly quotes/smart quotes introduced (checked the diffs); git diff --check in the validation section matches a clean check here too.

No blocking issues. The one thing worth fixing before/soon after merge is the stale CLAUDE.md Active ticket section noted above, since it's the doc most likely to steer the next engineering session.