feat: v4 client migration — indexOnly likes, single hashtag, ranked Top tab; devnet cutover

[PastaPastaPasta]

What

Phase 3 of PLAN_LIKE_OVERHAUL.md, stacked on #323 (merge that first; this PR retargets to staging automatically). Migrates the client to the v4 topology behind a new descriptor arm — v2/v3 behavior byte-identical — and cuts yap.pr/devnet over to the v4 draft contract.

• Topology v4 arm (lib/contract-topology.ts): indexOnly like shapes, inline hashtag, author fields; selected by NEXT_PUBLIC_CONTRACT_TOPOLOGY=v4.
• Likes rewritten for indexOnly: creates carry {postId, hashtag, postAuthor} (consensus-checked, 40127); confirmation via waitForAffectedState (no get-by-id probes — nothing to get); unlike = delete-by-values with tuple recovery off byAuthorTimePost + a session tuple cache; every reported failure re-checked by readback (the SDK's post-broadcast-throw quirk). Liked-state, batched membership, and counts ride the same query shapes as v3 (they lower onto byLiker/byPost).
• Single hashtag: posts carry author + first-hashtag; postHashtag writes/reads gated off under v4; tag pages ride post.tagAndTime; trending deferred (empty state).
• Ranked: ranked-likes.ts over documents.ranked() (zero-count groups filtered) + the v4-only profile Top tab — the first proved top-K feature in the app.
• SDK hardening from the battery findings: proved warm-up query before v4 reads (PV-ratchet), stale-quorum reconnect signature.
• Devnet cutover: .env.devnet → Aux325if… + v4 (final commit). The final v4 re-registration (hashtag optional under upstream null-skip) comes later; this draft is the QA target.

Validation (all live)

• tsc clean; lint at the exact 76-warning baseline (0 new); build, v4-local build, build:testing green.
• v4 build against moutai: 25/25 write-suite e2e (topology 12/12 incl. the new v4 lifecycle: tag listing, like persistence + counts, batched membership, unlike-by-values + re-like, ranked Top tab; lifecycle+stamp 8/8; sensitive 5/5).
• Testnet neutrality (v2): 13 passed / 0 failed / 12 skipped — production paths untouched.
• Bonus root-cause: the long-red sensitive-content.spec.ts failure was a pre-existing spec bug (reveal assertion filtered by the gate element that unmounts on Show; reproduced on the pristine base) — fixed here; that spec is now green on both networks for the first time.

Notable decisions

Tombstones retain author/hashtag verbatim (agreement-locked by existing likes); hashtag-validation recovery flow retired under v4 (no secondary write exists); cashtag pages empty under v4.

🤖 Generated with Claude Code

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 642048d6-526e-4ce4-8f5e-4869bd42ed9c

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[thepastaclaw]

🕓 Ready for review — 4 ahead in queue (commit ce04f62)
Queue position: 5/7
ETA: start ~15:47 UTC · complete ~16:04 UTC (median 17m across 30 recent reviews; 3 slots)
Queued 59m ago · Last checked: 2026-08-29 15:30 UTC

[cloudflare-workers-and-pages]

Deploying yappr with    Cloudflare Pages

Latest commit:	ce04f62
Status:	✅  Deploy successful!
Preview URL:	https://836a4098.yappr.pages.dev
Branch Preview URL:	https://feat-v4-client.yappr.pages.dev

View logs

[cloudflare-workers-and-pages]

Deploying yappr-v2 with    Cloudflare Pages

Latest commit:	ce04f62
Status:	✅  Deploy successful!
Preview URL:	https://c1d1ac40.yappr-v2.pages.dev
Branch Preview URL:	https://feat-v4-client.yappr-v2.pages.dev

View logs

[PastaPastaPasta]

Review triage complete (commit ce04f62). The independent migration review returned REQUIRES CHANGES with one HIGH and several lower findings; disposition:

Fixed:

• HIGH — notification re-keying: v4 like-notification ids now include the like's consensus $createdAt (already carried by the byAuthorTimePost projection the notification query reads), so an unlike→re-like surfaces as a new unread instead of arriving permanently read against the persisted readIds set.
• MEDIUM — tuple-cache warm-up race: per-key monotonic tokens; unlike invalidates in-flight warm-ups up front.
• Likers pagination (worse than flagged): id-shaped startAfter cursors are rejected outright on indexOnly types, so page two of a >100-liker listing would error, not just misbehave. Switched to terminal keyset pagination — and live-probing caught a second wrinkle before commit: a terminal orderBy without a terminal clause is refused, so page one is the plain prefix shape (members arrive in $ownerId key order) and later pages use prefix-equality + $ownerId > last + orderBy. Both shapes verified accepted against Aux325if….

Deferred with reasons:

• Readback-timeout UI divergence: transient, self-heals on reload, poll budgets validated live; tracked as a hardening follow-up rather than blocking.
• Unlike error-message asymmetry: pre-existing v2/v3 pattern, out of scope here.
• getPostLikes >100-liker second page now works by construction but has no e2e (no devnet post has that many likers); the query shapes were probed live instead.

Validated after the fixes: tsc clean, lint at the exact baseline, v4 write suite 25/25 live on moutai. (Skipping a re-review loop on the 54-line fix commit itself: it implements the reviewer's own findings and was validated live.)

---

🤖 Posted autonomously by Claude on behalf of pasta.