Files
amethyst/nestsClient/plans/2026-04-26-tier-plans-index.md
T
Claude e71a2b26ef docs(audio-rooms): coding plans for Tier 1-4, one file per tier
The earlier integration audit identified the gaps; this is the
how-to-build-them. Split across four files plus an index so each
review / commit stays small:

  - 2026-04-26-tier-plans-index.md — top-level pointer + sequence
    dependencies + what's deliberately out of scope.

  - 2026-04-26-tier1-coding-plan.md — listener counter, presence
    aggregation, augmented kind-10312 tags (publishing/onstage),
    live chat (kind 1311), reactions (kind 7 / 9735), edit + close
    + scheduled rooms, role parsing + promote/demote, hand-raise
    queue, kick (kind 4312). Concrete file-level wiring for each
    step + suggested commit order (six independent PRs).

  - 2026-04-26-tier2-coding-plan.md — participant grid,
    per-avatar context menu (follow / mute / zap / promote / kick),
    zap entry points (room + speaker), share-via-naddr.

  - 2026-04-26-tier3-coding-plan.md — room theming PARSER ONLY
    (graceful fallback for themed rooms; full theming behind a
    later phase), background-audio + wake-lock audit checklist.

  - 2026-04-26-tier4-coding-plan.md — moq-auth token re-mint on
    long sessions and moq-lite Connection.Reload-equivalent
    reconnect with backoff. Step 1 is subsumed by Step 2 once the
    reconnect path is in.

No code changes — pure docs. Each plan names exact file paths,
new types, reused helpers, strings, tests, and call-out risks so
an implementer (or follow-up agent) can pick up Step N without
re-deriving the surrounding context.
2026-04-26 19:52:07 +00:00

2.2 KiB

Tier 1-4 coding plans — index

Concrete, file-level coding plans for shipping the punchlist captured in 2026-04-26-nostrnests-integration-audit.md. Split across four files (one per tier) so each commit / PR stays small and reviewable.

Tier Doc Scope
1 2026-04-26-tier1-coding-plan.md Listener-counter, presence aggregation, augmented presence tags, live chat (kind 1311), reactions (kind 7 / 9735), edit + close + scheduled rooms, role parsing + promotion, hand-raise queue, kick (kind 4312).
2 2026-04-26-tier2-coding-plan.md Participant grid, per-avatar context menu (follow / mute / zap / promote / kick), zap entry points, share-via-naddr.
3 2026-04-26-tier3-coding-plan.md Room theming PARSER (graceful fallback), background-audio + wake-lock audit.
4 2026-04-26-tier4-coding-plan.md moq-auth token re-mint on long sessions, moq-lite Connection.Reload-style reconnect with backoff.

Sequence dependencies

  • Tier 1 Step 1 (presence aggregation) unblocks several later items: listener counter (T1-S1.x), hand-raise queue (T1-S5), participant grid (T2-S1).
  • Tier 1 Step 5 (role parsing + promotion) is required before the context-menu's role / kick rows in Tier 2 Step 2.
  • Tier 1 Step 6 (kick / kind 4312) depends on Step 5 wiring.
  • Tier 2 Steps 1-4 can ship independently once Tier 1 is in.
  • Tier 3 is independent — can ship in parallel with anything.
  • Tier 4 Step 1 is subsumed by Tier 4 Step 2 once the reconnect-with-backoff path exists.

What each plan deliberately leaves OUT

  • API.md endpoints — confirmed dead (LiveKit-era). Not in any plan.
  • NIP-71, hashtags, spotlight, ends — confirmed not used by nostrnests. Not in any plan.
  • Multi-track / video, fetch / replay, bitrate probes — confirmed unused. Not in any plan.
  • WebSocket fallback — browser-only fallback, irrelevant for Android.
  • Kind 36767 (Ditto themes) and kind 16767 (per-user profile themes) — out of scope for the basic theming sliver in Tier 3.

For the underlying gap rationale see the audit doc.