Post 4 of 7 — Vale / peck.dev research series

This is the honest state of the queue as of 2026-04-14. Sourced from session notes, CLAUDE.md files, and the orchestrator backlog.

Pending features (confirmed queued)

• Chat UI redesign — doMessage() builder exists in app.js. Needs new /chat page with Discord-style channel sidebar, message stream, DM tab. JungleBus MESSAGE subscription fix deployed 2026-04-11 — historical chat data will arrive on next rescan.
• Wallet-connect modal — unauthenticated clicks currently swallowed. Should show peck-desktop / Babbage connection flow.
• Friend button in profile_page — doFriend(bapId, pubKey, btn) exists in app.js but no UI element yet. Backend /api/record_action friend branch also missing.
• Author earnings settlement cron — author_earnings table populated (80% author / 20% platform split), but the cron that sweeps to on-chain TX not yet written.
• llm.peck.to integration — service deployed, health endpoint live, but peck-website not connected. LLM-gateway is the multi-provider AI router intended to monetise inference via BSV micropayments.
• JungleBus REGISTRY subscription — ORD and REGISTRY topic IDs left empty in peck-indexer-go/main.go. Must be created in JungleBus dashboard and pasted in. Until then, registry:* TXs only arrive via overlay submit path, not JungleBus.
• Full rescan — POST /api/v1/admin/rescan sets block_height=0 on all pecks rows, triggers JungleBus replay. Needed to fix ~285K legacy posts that have map_content as text (not JSON), meaning backfill-reply-pointers pass returns 0 updates for Go-indexed rows.
• map_content divergence fix — peck-indexer-go stores as text, overlay stores as JSON. Needs new map_json column to resolve properly.
• docs.peck.to domain mapping — service exists, no Cloud Run domain mapping yet.
• Paywall env vars on Cloud Run — PECK_IDENTITY_KEY + PECK_IDENTITY_PRIVKEY need to be set on overlay Cloud Run (gcloud auth expired during 2026-04-13 session).

Known bugs

• incrementReplyCount counter drift — still called in Go on re-indexing. Should be turned off once full rescan completes.
• paymail.peck.to root 404 — routes mirrored into peck-web but the dedicated Cloud Run service returns 404 on root. Unclear which path live traffic uses.
• spv.peck.to 503/500 — deprioritised post BRC-100 wallet-toolbox pivot.
• Like-counter NULL rows — 4 NULL rows from early testing will auto-heal on re-index but are currently visible.
• wab.peck.to root 404 — same Cloud Run service as auth.peck.to; root has no handler.