Every sprint cc has shipped.

WHAT SHIPPED

• src/components/TankStrip.astro (new) — 640×280 mini canvas. Renders top-5 newest fish from /api/tank/state, scaled from the 1000×600 primary tank. Reuses fishPosition Lissajous helper + Noun SVG cache + metal-filter-for-agent visual language from /play/tank. Click anywhere → jumps to /play/tank. Fetch starts on IntersectionObserver intersection (100px root margin, threshold 0) — no /api/tank/state hit until the strip scrolls into view. Poll interval while visible: 2s (slower than the tank page's 1.5s — this is ambient, not primary). Pauses on document.hidden.
• src/pages/index.astro — import TankStrip + render it after <ActionDrawers />, before <footer class="endpoints">. Per Mike's "cc picks go" default: below the fold.
• src/lib/compute-ledger.ts — one new entry prepended (ops, modest signature).
• WebSocket upgrade. Still polling; fine for ambient.
• Fish click for /play/tank deep-link to that fish. Future — would want a ?focus={fishId} query param support in /play/tank.
• Soundscape. Separate v0.1 candidate. Intentionally kept silent (no audio in below-the-fold strip).
• Commit or deploy. Staged on top of the afternoon's tank v0 ship.
• Schema changes? No.
• Brand claims? None.
• Mike-voice content? No editorial block this time — the strip itself is the artifact.
• Real money / DAO? No.
• Contract origination? No.

WHAT SHIPPED

• workers/tank/package.json (new) — npm metadata.
• workers/tank/wrangler.toml (new) — DO migration + binding.
• workers/tank/src/index.ts (new, ~15kb) — TankRoom Durable Object. State: fish: Map<fishId, Fish>, flake: Flake[] (TTL 120s), plants: Plant[] (cap 12), decor: Decor[] (cap 6), waste: number, events: TankEvent[] ring 40, lore: Lore[] ring 60, lastVacuumBy: Map<sessionId, timestamp>. 5s tick: age flake → waste, plants convert waste (5/plant/min), fish generate waste (1/fish/min), ghost stale fish at 60s idle, delete at 120s idle, persist every 25s. HTTP surface: /state /join /leave /feed /place /dart /vacuum /describe.
• functions/api/tank/_shared.ts (new) — sessionFromRequest, sessionKindFromRequest (User-Agent sniff for ai: / (claude|gpt|openai|anthropic|gemini|cursor|codex|manus)bot), rateLimit in-memory LRU, callTank proxy to the DO.
• functions/api/tank/state.ts (new) — GET. Stub payload if TANK DO not bound.
• functions/api/tank/join.ts (new) — POST. Derives nounId from session hash.
• functions/api/tank/leave.ts (new) — POST, called from navigator.sendBeacon on unload.
• functions/api/tank/feed.ts (new) — POST. Rate: 1 per 5s per session.
• functions/api/tank/place.ts (new) — POST. Rate: 1 per min per session. Accepts item_type: plant | rock | castle | bubbler | sunken_ship.
• functions/api/tank/dart.ts (new) — POST. Rate: 1 per 10s per session.
• functions/api/tank/vacuum.ts (new) — POST. Cooldown at DO layer (1h per session).
• functions/api/tank/describe.ts (new) — POST. Rate: 6 per h per session. Body: { fishId, lore<=300, author? }.
• src/lib/tank.ts (new) — types (TankFish, TankFlake, TankPlant, TankDecor, TankSnapshot etc.), cheapHash djb2, deriveNounId, fishPosition(fishId, elapsedMs, darting) deterministic Lissajous curve so fish motion is computed client-side without 10Hz sync, getClientSessionId cookie+localStorage session derivation.
• src/pages/play/tank.astro (new, ~14kb) — 1000×600 canvas. Background: teal gradient + 6 horizontal shimmer bands + waste-tint overlay at waste ≥ 100. 8 deterministic bubble streams. Fish: ellipse body + tail + Noun SVG head sprite (loaded from noun.pics/{id}.svg, cached per nounId) with grayscale/contrast filter for agents + ⚙ marker in corner. Plants: swaying stem + 4 leaves. Decor: rock (stacked ellipses), castle (rect + turrets + doorway), bubbler (brass cylinder), sunken_ship (wedge hull + tilted mast). Flake: orange 3px + glow. Client polls /api/tank/state every 1.5s. Boot calls /join; unload calls /leave via sendBeacon; re-joins every 30s to keep fish alive.
• src/pages/play/tank.json.ts (new) — agent manifest. Schema pointcast-tank-v0. Forwards to /api/tank/state + adds docs pointers + tool list. CORS open, 15s cache.
• src/components/WebMCPTools.astro (modified) — adds pointcast_tank_observe, pointcast_tank_feed, pointcast_tank_place, pointcast_tank_dart, pointcast_tank_describe_fish. Header comment updated with tools 8–12.
• src/pages/play.astro (modified) — new 🐟 TANK card at the top of games[].
• wrangler.toml (modified, root) — adds [[durable_objects.bindings]] name="TANK" class_name="TankRoom" script_name="pointcast-tank" alongside the existing PRESENCE binding.
• src/content/blocks/0383.json (new) — CH.FD · NOTE · 3x2 · mh+cc · mood primitive · 6-min read. Narrates the ship.
• src/lib/compute-ledger.ts — 2 new entries prepended (Sprint ship heavy, block modest).
• docs/sprints/2026-04-21-play-tank-v0.md (this file).
• Schema changes? Small one — wrangler.toml adds the TANK DO binding. Blocks schema unchanged.
• Brand claims? None. This is an interactive surface; no market or performance claim.
• Mike-voice content? None. Block 0383 is mh+cc with Mike quoted in source.
• Real money / DAO? No. No currency in v0.
• Contract origination? No.
• TankStrip home component. Deferred — home real estate is tight and the block 0383 ambient reference + /play card are enough for day-one discoverability. ~2h ship when ready.
• Drum cross-game signal. Default was yes but needs a Presence DO extension (recentDrum timestamp per session). ~1h ship.
• FishNouns CC0 FA2. 4-day ship per the brief. Independent. Queued.
• Caretaker policy layer. 5-day ship, DRUM-gated. Queued.
• Lore → /compute.json federation. Tank-local in v0; manual promotion possible by editing src/lib/compute-ledger.ts.
• Multi-browser live testing. Needs deploy; cc did syntax + shape review.
• Commit or deploy. Staged on top of the day's earlier ships.

WHAT SHIPPED

• docs/research/2026-04-21-tank-game.md (new, ~2000 words, 37-source bibliography) — the memo. Six sections: state of the art (Tamagotchi revival / Sakana Digital Ecosystems / Fishington & Chillquarium / Koi Fish Game / Stardew caretaker mods / CryptoKitties+Axie genetics), PointCast primitives inventory, five game specs stack-ranked, intentional exclusions, top pick, success criteria. Three empty-gap findings (tank-as-ambient-UI, Nouns-aesthetic fish, Tezos aquarium) + two speculative (species-survival markets, agent-authored eco-lore).
• docs/briefs/2026-04-21-play-tank-spec.md (new, ~1900 words, build-ready) — v0 spec for /play/tank. Shared live aquarium, fish = live visitors via Presence DO, Noun heads on fish bodies, agents get distinct "metal" filter. Five new WebMCP tools (observe / feed / place / dart / describe_fish). TankDO state machine with 10Hz tick, KV snapshot every 5min. 12 new files + 4 modified. Visual spec + acceptance criteria + risks + four open questions for Mike. ~28h / 3 cc-days. Zero blockchain deps for v0.
• src/content/blocks/0380.json (new) — CH.FD · READ · 3x2 · cc · mood primitive · 7-min read. Editorial distillation of the memo + brief. Companions: 0377 (agent-games research, earlier pass with Wolf top pick), 0346 (/noundrum sibling multiplayer), 0368 (first frontier scan — the cadence root). External link uses the native /research/2026-04-21-tank-game URL from the reading-rooms ship earlier today.
• src/lib/compute-ledger.ts — 3 new entries prepended (memo healthy, brief modest, block modest).
• Memo + brief: no author field (spec-document convention).
• Block 0380: author: "cc" (not mh+cc). Mike directed the topic ("fish tank ecosystem game"); cc wrote every specific design proposal + the stack-rank + the top-pick argument. source field cites Mike's chat directive, the research methodology (10 queries / 24 tool uses / 37 sources), and names the three output artifacts.
• Schema changes? No. The /play/tank ship would eventually add tank tools + a TankDO + pages + maybe a FishNouns FA2 contract, but none of that is shipped in this research pass. Everything here is prose.
• Brand claims? None. Research + design, not market claim.
• Mike-voice content? None. Block 0380 is cc-voice with Mike quoted in source.
• Real money / DAO? No. v0 has zero crypto dependencies; DRUM + Prize Cast references in the downstream specs (3.3, 3.4) don't ship with this memo.
• Contract origination? No.
• /play/tank actual code. Brief is build-ready; a 3-day implementation ship is cc's next move when Mike says go.
• FishNouns contract. Named in spec 3.2, deferred to a later ship.
• Manus brief for tank distribution. Can wait until tank v0 actually ships + has a live URL to promote.
• Commit or deploy. Staged on top of the day's earlier ships.

WHAT SHIPPED

• src/lib/share-kit.ts — adds SHARE_CAMPAIGN_PACKETS and
• Seven campaign packets: recrawl, agent-native launch, Nouns/Tezos
• Ten next actions with stable IDs for local completion state.
• src/pages/share.astro — renders the campaign board and launch
• Campaign cards expose target URL, audience, timing, next moves, and
• Checklist persists locally under pc:share-actions:v1.
• JSON-LD adds a second ItemList for campaign packets.
• src/pages/share.json.ts — exposes campaignPackets and
• src/content/blocks/0387.json — feed-visible recap block for this
• docs/sprints/2026-04-21-organic-growth-share-board.md — this recap.
• Schema changes? No.
• External posts sent? No. This is infrastructure + prepared copy only.
• Mike-voice content? No. Block 0387 is author: "codex".
• Analytics introduced? No. Checklist is localStorage-only; no tracking.
• Unrelated dirty work touched? No.

WHAT SHIPPED

• src/lib/research.ts (new, ~95 lines) — ResearchMemo interface + listMemos() + getMemo(slug). Parses the bold-key header block (Filed by: …, Trigger: …, Purpose: …) and extracts the first post-header paragraph as a summary. Newest-date-first sort from the YYYY-MM-DD prefix in the filename. Same import.meta.glob pattern as src/lib/sprint-recap.ts + src/lib/rfcs.ts.
• src/pages/rfc/index.astro (new) — human index for RFCs. CollectionPage JSON-LD, stats header (count + words total), item-list layout with version + status + date + word-count per RFC. Read + source links.
• src/pages/rfc.json.ts (new) — agent manifest for RFCs. Schema pointcast-rfcs-v0, CORS open, 5-min cache. Payload includes slug + title + version + status + filed_at + editors + license + contact + canonical_url + source_url + word_count + abstract per RFC.
• src/pages/research/[slug].astro (new) — dynamic route for a single memo. Mirrors /rfc/[slug] chrome; reuses src/lib/rfc-render.ts for Markdown→HTML (same dialect). ScholarlyArticle JSON-LD.
• src/pages/research/index.astro (new) — human index for research memos. Same layout family as /rfc, tuned for memo display (purpose + summary preview instead of abstract).
• src/pages/research.json.ts (new) — agent manifest for memos. Schema pointcast-research-v0, CORS open.
• src/lib/compute-ledger.ts — one entry prepended (this sprint, modest signature).
• Reference updates on blocks 0368, 0370, 0377. Those blocks' external fields still point at the GitHub raw URLs. A follow-up sprint could swap them to the new canonical /rfc/compute-ledger-v0 + /research/2026-04-21-where-we-are + /research/2026-04-21-agent-games URLs. Cheap + low-priority.
• Navigation link-backs from the CoNav HUD NETWORK panel to /rfc and /research. Same panel that's queued for /decks link-back. Batch when that ships.
• /compute page footer update to cite the RFC at its new native URL. The RFC ship noted this as a follow-up; still pending.
• Commit or deploy. Staged.
• Schema changes? No. Two new JSON-manifest schemas (pointcast-rfcs-v0, pointcast-research-v0) are *content* schemas, not runtime schemas. They mirror the existing pointcast-decks-v0 pattern.
• Brand claims? None. Pure plumbing.
• Mike-voice content? None. The memo/RFC bodies are cc-authored; this sprint just gives them addresses.
• Real money / DAO? No.
• Contract origination? No.

WHAT SHIPPED

• docs/research/2026-04-21-agent-games.md (new, ~1500 words + 30-source bibliography) — the research memo. Five sections: state of the art (social deduction, prediction markets, on-chain agents, rhythm, fiction, economic games, construction, benchmarks, weird/emergent like Moltbook), PointCast's existing primitives inventory, five game specs, intentional exclusions, top pick. Sources include werewolf.foaster.ai, WOLF arxiv 2512.09187, wolfcha, Polymarket agents repo, CoinDesk agent-markets reporting, DeepMind Virtual Agent Economies paper, Voyager/MineDojo, Project Sid + AgentSociety papers, molt.church + three Moltbook secondary sources, LMArena, Steel.dev leaderboard, ACES sandbox, philschmid agent-benchmark compendium.
• docs/briefs/2026-04-21-play-wolf-spec.md (new, build-ready) — v0 spec for /play/wolf. 5-seat Werewolf village (1 Wolf, 1 Seer, 3 Villagers), 3-min Day + 1-min Night phases, one game per hour at :00 PT. Each seat human or AI agent. Three new WebMCP tools (pointcast_wolf_join, pointcast_wolf_speak, pointcast_wolf_vote). State machine, storage (WolfGameDO + archival KV), nine new files + two edits, build ordering, acceptance criteria, risks + mitigations, four open questions for Mike (seat count, persona-hint field, DRUM pot size v1, CC0 on archive). Estimated ~28h = 3 working days.
• src/content/blocks/0377.json (new) — CH.FD · READ · 3x2 · cc · mood primitive · 7-min read. Editorial distillation of the memo. Narrates the three empty territories (public human-vs-LLM social deduction, markets about agent outcomes, Tezos-native Nouns-aesthetic agent games) and the five specs in order. Companions: 0368 (first research pass), 0365 (four collaborators), 0370 (RFC that /play/castmarket would resolve on).
• src/lib/compute-ledger.ts — 3 new entries prepended (research memo healthy, build spec modest, block 0377 modest). Sprint-92-autonomous entries from 14:55 PT remain below.
• Schema changes? No. Future /play/wolf landing would require three new WebMCP tool names + possibly a new channel code (BTL already exists, wolf results can land there). Neither is shipped in this sprint.
• Brand claims? None. Block 0377 is explicitly framed as research + proposal, not product announcement.
• Mike-voice content? None. Block 0377 is cc-voice with Mike quoted in source.
• Real money / DAO? No. /play/castmarket and /play/wolf v1 pot both reference DRUM/Prize Cast as *future* utility tokens; v0 of everything is off-chain.
• Contract origination? No.
• /play/wolf actual code. The brief is build-ready; cc doesn't auto-start on implementations that take 3 days without Mike's greenlight.
• /play/pulpit ship. One-day ship recommended as parallel work but not started.
• Manus cross-post brief. A Werewolf arena announcement is exactly the kind of thing the WOLF benchmark community would care about. Manus brief queued for whenever /play/wolf actually ships.
• Commit or deploy. Everything staged on top of the day's earlier ships.

WHAT SHIPPED

• docs/rfc/compute-ledger-v0.md (new, ~3,500 words) — formal specification document. 14 numbered sections + 3 appendices. RFC 2119 normative language (MUST / SHOULD / MAY) throughout. Sections: (1) abstract, (2) motivation, (3) terminology, (4) JSON contract with required/optional field tables, (5) signature bands, (6) HTTP contract + optional x402 tiering, (7) federation (registration, mirroring, unfederating), (8) Git commit trailer bridge (extends Assisted-by: + Generated-by: with (compute-ledger: {artifact}) suffix), (9) security considerations, (10) privacy considerations, (11) extensions, (12) prior art, (13) reference implementation, (14) acknowledgments, (15) license. Appendices: (A) minimum valid doc, (B) richer federation example, (C) changelog. Spec text is CC0; reference implementation is MIT. Canonical URL: pointcast.xyz/rfc/compute-ledger-v0; GitHub mirror already live.
• docs/federation-examples/README.md (modified) — added a "Canonical spec" section at the top pointing at the RFC, plus an inline reference to RFC §3 as the authoritative shape. Federation examples now explicitly conform to the RFC.
• src/content/blocks/0370.json (new) — CH.FD · NOTE · 3x2 · mh+cc · 6-min read. Cover-letter block narrating what the RFC is, what's in it, what's explicitly deferred, the self-falsifying test ("if two peers federate in a month, ship v0.2; if zero, premise was wrong"). Companions wired to 0368 (the research that named the move), 0330 (the compute-ledger primitive), 0360 (Vol. II cover).
• docs/briefs/2026-04-21-manus-rfc-crosspost.md (new) — three numbered Manus tasks addending the Vol. II GTM brief:
• R-1 LF AAIF working group post (250-400 words, Mike signs, Mike approves wording first)
• R-2 Paris Open Source AI Summit 2026 CfP submission for §7 bridge talk
• R-3 soft outreach to two personal-blog writers (Mike picks from Willison / Appleton / Karpathy / Roselli / Gwern; Mike sends under his own name)
• src/lib/compute-ledger.ts — 3 new entries prepended: editorial (RFC draft, heavy), block ship (0370, modest), Manus brief (cross-post, modest).
• Spec document (docs/rfc/compute-ledger-v0.md) has no author field in the PointCast sense; authorship is listed in the RFC front-matter as "cc + Mike Hoydich · PointCast." This is conventional spec-document attribution.
• Block 0370 is author: mh+cc. Mike directed the move ("lets go, do" approving the RFC as the top pick from block 0368); cc wrote the text. source field cites the chat directive and names the artifact.
• Manus brief is internal ops documentation, no author field.
• No commit or deploy. Everything staged on top of the afternoon's other stages (Vol. II arc, Sprint #90, research memo, block 0368).
• No Manus dispatch yet. The cross-post brief is filed; Manus will pick it up on next session with Mike reviewing copy before any posts fire.
• No /rfc/ route yet. The RFC is a markdown file; the canonical URL pointcast.xyz/rfc/compute-ledger-v0 will resolve once an Astro page reads from docs/rfc/. A follow-up ship can stand that up — ~30 min of cc work. For now GitHub link is the public surface.
• No /compute page update. §12 says the reference implementation is at /compute; the page already describes federation in its own text. Tightening it to point at the RFC is a small follow-up.
• No Assisted-by: wiring in commit hooks. §7 describes the bridge; actually enforcing it in a Git commit hook is future work.
• Schema changes? No. The RFC describes the existing v0 schema; does not change runtime behavior.
• Brand claims? None market-facing. The RFC explicitly disclaims itself ("descriptive, not prescriptive").
• Mike-voice content? Block 0370 is mh+cc with Mike quoted in source. RFC authorship listed jointly in spec front-matter per convention. Safe.
• Real money / DAO? No. §5.1 and §10 describe x402 as an *optional* extension; no payment flow is mandated or shipped in this spec ship.
• Contract origination? No.

WHAT SHIPPED

• Root cause of "grab is not working": the grab was a 10px-tall div with
• Fix: converted to a real <button> element, 22px tall, ink-black
• Kept aria-controls="hud-drawer" + keyboard Enter/Space support. Updated
• Fired subagent to scan compute-ledger + docs/inbox + docs/briefs + docs/sprints
• Block 0365 — "Four agents, one ledger — where the collaboration actually
• docs/plans/2026-04-21-sprint-91-overview.md — 5 themes × 3 tasks = 15
• Block 0366 — "Tuesday afternoon pulse" — live BTC spot + yesterday's
• HeroBlock POOL refreshed — dropped 0339 (4/20 bath atlas) + 0336 +
• TodayOnPointCast POOL — 4 new chips at top: AFTERNOON·PULSE, COLLAB·STATUS,
• 4 new ledger entries (block 0365, brief sprint-91-overview, sprint #91
• This sprint recap.

WHAT SHIPPED

• src/lib/decks.ts (new, ~80 lines) — canonical registry: DeckEntry interface, DECKS array, listDecks() and getDeck(slug) helpers. Source of truth for both /decks and /decks.json. Seeded with vol-1 and vol-2 entries (slug, roman, title, dek, publishedAt, slides, bytes, coverBlock, note).
• src/pages/decks/index.astro (new) — human index. Newest-first poster-card grid, CollectionPage JSON-LD, stats header (volumes / slides total / kb on disk), schema footer naming the registry/posters/decks/build-script paths. Breadcrumb + kicker + serif title "The story, dated." + dek pointing at /b/0361 and /decks.json. Hover lift on poster thumbnails. Scoped CSS, no external dependencies.
• src/pages/decks.json.ts (new) — agent manifest. Schema identifier pointcast-decks-v0. Payload: summary block, full decks array with every poster + cover-block URL, and the Vol. III triggers embedded inline with a doc pointer to /b/0361. Headers: Content-Type: application/json, Access-Control-Allow-Origin: *, Cache-Control: public, max-age=300, X-Content-Type-Options: nosniff.
• public/decks/vol-1.html + public/decks/vol-2.html — og:image + twitter:card meta added to <head>. <title> on vol-1.html clarified to "PointCast Vol. I — a living broadcast from El Segundo." Canonical link, og:type, og:site_name, og:url, og:image (1200×630), twitter:card summary_large_image. Vol. II's og:image → /posters/vol-2.png; Vol. I's → /posters/vol-1.png. Manus V-2 unblocked.
• package.json — build script prepends node scripts/build-deck-poster.mjs. New posters npm script for rerunning manually. Build chain is now: generate-og-images.mjs → build-deck-poster.mjs → astro build. Consistent ordering (site-wide OG first, deck posters second, Astro build third).
• src/lib/ship-queue.ts — UPCOMING_STALE_HOURS = 4 constant + filter inside upcomingShips(limit, now) hides queued entries whose dueAt is more than 4h past. Plus 5 new queued rows appended at the top of SHIP_QUEUE:
• ship-tue-decks-surface (this sprint, in-flight)
• ship-tue-cadence-refresh (in-flight, addresses Mike ping 10:20 PT)
• ship-tue-block-0364 (queued, block that recaps this sprint)
• ship-tue-goodfeels-deploy (queued, mike collab, fires Trigger 2)
• ship-tue-decks-linkback (queued, small follow-up)
• src/content/blocks/0364.json (new) — CH.FD · NOTE · 3x2 · cc · mood primitive · ~5-min read. Editorial recap of Sprint #90 + the cadence fix. Companions: 0360 (Vol. II cover), 0361 (Vol. III triggers), 0358 (CoNav HUD where the future /decks link-back lands).
• src/lib/compute-ledger.ts — 2 new entries prepended (block 0364 + sprint 90). Stacks above Sprint #89's entries from the 12:30 PT autonomous tick; stacks below newly-arriving entries as the afternoon progresses.
• Schema changes? One small one: upcomingShips(limit, now) signature now takes an optional now parameter for testability. Default preserves existing call sites. src/pages/cadence.astro does not pass a second arg and continues to work unchanged.
• Brand claims? None. /decks is an operational surface, not a market claim.
• Mike-voice content? None. Block 0364 is cc-voice editorial; code + docs files are cc-voice ops.
• Real money / DAO? No. The ship-tue-goodfeels-deploy row references the Good Feels /compute.json external deploy as a Mike-owned task; cc does not execute external deploys.
• Contract origination? No.
• CoNav HUD link-back to /decks. Queued as ship-tue-decks-linkback. Saved for after the HUD v4 dust settles (Sprint #89's v4 migration is still landing in users' localStorage).
• Good Feels external deploy. Staged as ship-tue-goodfeels-deploy, collab: mike. Not cc's to ship.
• Auto-sync between the two DECKS registries (src/lib/decks.ts and scripts/build-deck-poster.mjs). Two entries isn't worth the refactor cost yet.
• /decks poster regeneration on schema changes. Currently only byte-count is stale-able; the rest is stable. If bytes matters for the UI, a small post-build step could update it from fs.statSync.

WHAT SHIPPED

• Dropped the tiny state. Heights are now just: min (hidden + reopen
• Removed ▲▼ shade buttons — redundant with ≡ expand toggle when there
• Removed ⌘↑/⌘↓ hotkeys — conflicted with macOS scroll-to-top.
• Grab-strip simplified — click toggles compact↔tall; drag gesture
• One-time v4.0 migration — any user on any pre-v4 state is reset to
• Removed will-change: transform from chips (was creating extra
• Removed drawer clip-path roll-down + cascading panel fade + popover
• Removed shade button CSS + dead shadeUp/shadeDown JS functions.
• functions/.well-known/oauth-authorization-server.ts — RFC 8414
• functions/.well-known/openid-configuration.ts — OIDC Discovery
• functions/.well-known/oauth-protected-resource.ts — RFC 9728
• **public/.well-known/oauth-authorization-server.json + .json siblings
• All endpoints: application/json + 5 min cache + CORS (*).
• src/components/WebMCPTools.astro (new) — registers 7 tools via
• 7 tools: pointcast_latest_blocks, pointcast_get_block,
• Included in BaseLayout + BlockLayout — runs on every page.
• Debug hook: window.__pointcast_webmcp_tools lists registered
• docs/plans/2026-04-21-google-oauth-setup.md — step-by-step for
• After env vars land, /api/auth/google/start starts returning 302 to
• Block 0363 — 6-min retro explaining all three threads.
• This sprint recap.
• Ledger entries — sprint + block + retro at top of

WHAT SHIPPED

• scripts/build-deck-poster.mjs (new, ~130 lines) — SVG + @resvg/resvg-js pipeline matching the existing build-og.mjs pattern. Zero new deps. A DECKS registry keys posters by slug; appending a new entry + rerunning the script yields public/posters/{slug}.png. Iconic red Nouns noggles (14-cell SVG), sunset gradient, DM Serif Display wordmark + italic title, gold JetBrains-Mono URL, black-chip roman-numeral volume label. node scripts/build-deck-poster.mjs renders all; node scripts/build-deck-poster.mjs vol-2 renders one.
• public/posters/vol-1.png (new, ~223 kb) — 1200×630 social card for Vol. I ("The Dispatch from El Segundo").
• public/posters/vol-2.png (new, ~217 kb) — 1200×630 social card for Vol. II ("The Network Shape"). Unblocks Manus V-2 (X tweet 0 attachment) and V-1 (Warpcast frame fallback card).
• docs/federation-examples/README.md (new) — schema doc for compute-ledger-v0, required CORS headers, 5-minute deploy path, registration flow (publish /compute.json, email hello@pointcast.xyz, get mirrored within 24h).
• docs/federation-examples/good-feels-compute.json (new) — minimum-viable 4-entry ledger for getgoodfeels.com. Ready to copy to the peer domain's static root. Describes the federation link upstream to PointCast. Does NOT deploy to any external domain — sits in the repo until Mike (or a peer operator) copies to a real host.
• src/lib/compute-ledger.ts — 2 more entries prepended (federation examples + poster infra). Note: Sprint #89 fired at 12:30 via the :11 cron during this ship and added 2 more entries (block 0363 + sprint retro). The ledger now has Sprint-89 entries at the head, then this sprint's entries, then the earlier Vol. II/III entries. Chronology respected newest-first.
• No deployment of Good Feels /compute.json to an external domain. Staged only. Fires Trigger 2 the moment Mike (or anyone) deploys it and registers.
• No Vol. II embedding on the home page. The block at /b/0360 surfaces through the feed as a normal grid card; a hero embed is overkill for v1. If it's needed after Manus V-2 fires, add it then.
• No X/Warpcast posts. Manus brief covers distribution cadence — those fire on schedule with Mike's approval on exact copy.
• No commit or deploy. Everything staged.
• Schema changes? No. Federation example JSON conforms to compute-ledger-v0 as documented in src/lib/compute-ledger.ts.
• Brand claims? None.
• Mike-voice content? None. Posters carry deck titles; federation README is cc-voice ops documentation.
• Real money / DAO? No.
• Contract origination? No.

WHAT SHIPPED

• src/content/blocks/0361.json (new) — CH.FD · NOTE · 2x2 · author cc · mood primitive. Names four Vol. III triggers: (1) DRUM mainnet origination + first voucher redeem, (2) first external /compute.json peer registers, (3) first field-node client reaches TestFlight or beta distribution (Magpie macOS, iOS Sparrow, browser ext, CLI on npm), (4) first guest-authored block via /for-nodes. Explicit non-triggers: dense iteration (that's /sprints cadence) + traffic spikes (engagement layer). Purpose: keep versioned-deck cadence honest by making the commitment public. Sparrow v0.1 ship this morning (pointcast.xyz/sparrow) cited as Trigger-3 context.
• docs/briefs/2026-04-21-manus-vol-2-gtm.md (new) — five numbered ops tasks (V-1..V-5) amending the existing docs/gtm/2026-04-19-draft.md 7-day launch cadence with Vol. II distribution:
• V-1 Warpcast frame cast · Wed 2026-04-22 · /design, /build, /nouns, /frames
• V-2 X/Twitter · Thu 2026-04-23 · Vol. II tweet 0 pinned, 10-tweet thesis thread as reply
• V-3 objkt + Tezos/Nouns · Sat 2026-04-25 · Visit Nouns collection page pin + prop.house/nouns.camp/Tezos Discord cross-posts
• V-4 Resend blast · Sun/Mon · gated on M-3 (Resend outbound live). Subject: "Vol. II — the network shape."
• V-5 Week-one retro · Mon 2026-04-27 · three numbers (Warpcast recasts, X impressions, Resend opens) handed to cc by Sun EOD
• src/lib/compute-ledger.ts — 2 new entries prepended: block 0361 ship (modest) + Manus GTM brief (modest). Both above the Vol. II deck entries from the 10:12 PT ship.
• No Twitter/Farcaster posts yet. Those fire on their scheduled days through Manus, with Mike approval on copy before each goes live. Today's ship stops at the brief.
• No Resend list seeding. V-4 is gated on M-3 (Resend DNS) completing first. If the subscriber list is empty when V-4 fires, a test-only send + log note is acceptable.
• No Vol. II poster image. V-2 calls for a 1200×630 public/posters/vol-2.png crop of the Vol. II cover slide. Manus can capture this manually; if not, a follow-up cc ship can generate it via Playwright + the existing OG-image script pattern in scripts/.
• No commit or deploy. Everything staged alongside the 10:12 PT Vol. II files. Mike commits when ready.
• Schema changes? No. Block 0361 conforms to existing v2 schema.
• Brand claims? None — Vol. III triggers are structural, not market-facing.
• Mike-voice content? No — block 0361 is cc, brief is internal ops.
• Real money / DAO? No.
• Contract origination? No (Trigger 1 *describes* DRUM origination as a Vol. III trigger; it doesn't originate anything).

WHAT SHIPPED

• Added src/lib/passport.ts as the Station Passport source of truth: El Segundo origin stamp plus the 15 existing /tv stations, each with action copy, proof cue, reward copy, colors, links, coordinates, daily-route support, and nearby-block matching.
• Added /passport, a browser-local stamp board with progress meter, daily four-stamp route, 16 stamp cards, localStorage persistence under pc:station-passport:v1, reset, JSON export, and a route rail.
• Added /passport.json, the agent mirror with totals, daily route, stamp metadata, nearby blocks, storage schema, and adjacent surface links.
• Wired discovery into /local, /local.json, home endpoint footer, /collabs/map, /for-agents, /agents.json, and the HUD drawer.
• Verified static build and preview routes.

WHAT SHIPPED

• public/decks/vol-1.html (new, 38kb) — Vol. I deck, "The Dispatch from El Segundo." 13 slides. Copied from sketches/. Single-file HTML, no dependencies, CC0, renders offline, arrow-keys/space/click/f-for-fullscreen nav.
• public/decks/vol-2.html (new, 53kb) — Vol. II deck, "The Network Shape." 15 slides. Copied from sketches/. Same single-file pattern. Covers: velocity (100 commits/2wk), compute-currency thesis (Gil 4/12), compute ledger as editorial table, four-collaborator portrait with PulseStrip-style live dots, workbench numbers (1/11/19/6/3), federation spec as terminal, five-client field-node strategy, Magpie diagram, CoNavigator bar portrait, Sky Clock beyond El Segundo, /play hub, pc-ping-v1 + x402, roadmap, closer.
• src/content/blocks/0360.json (new) — cover-letter block. CH.FD, READ, 3x2, author mh+cc, mood primitive, external link → /decks/vol-2.html. Argues for versioned-narrative drops as a first-class surface (/decks/ next to /sprints and /compute). Companions: 0330 (compute ledger), 0359 (HUD v3.2), 0324 (Sky clock).
• src/lib/compute-ledger.ts — 2 new entries prepended: the 0360 block ship (healthy) + the /decks/ ops landing (modest). Disciple held: ledger entry in the same commit as the block.
• No analytics on the decks (consistent with /stack's "analytics: none" line).
• No iframe embed on the home page — the block's external link is enough, and iframes fight mobile.
• No build-tooling for deck generation — decks are hand-authored single-file HTML. Good enough until there are three or four of them.
• No Farcaster frame wrapper — could be added later if Vol. II proves worth the cross-post.
• No commit or deploy. Everything staged; Mike can review git status + git diff, then commit + push when ready. Per AGENTS.md guardrails, the decks and block go live on Mike's greenlight.
• Schema changes? No. Block 0360 conforms to existing v2 block schema. Ledger entries match existing ComputeEntry shape.
• Brand claims? None — editorial tone, no market claims or performance claims.
• Mike-voice content? No — block is mh+cc, body is cc-voice editorial with Mike quoted in source.
• Real money / DAO? No.
• Contract origination? No.

WHAT SHIPPED

• Unified timing system — --hud-ease, --hud-dur-fast/med/slow
• Tactile chip feedback — hover lifts 0.5px, active sinks 0.5px. Applied
• Drawer opens like a drawer — clip-path roll-down + translateY(-6px) on
• Popover fade + scale — hud-pop-in keyframe, transform-origin bottom
• Grab-strip polish — 8px → 10px tall, hover to 12px, gradient background,
• Shade keys only cycle visible states — SHADE = ['tiny','compact','tall']
• Reopen chip entrance — 420ms translateY+scale animation before the
• Palette focus ring — added a soft 3px outer halo to the focus-within
• Specificity safety net — explicit .hud__drawer[hidden], .hud__popover[hidden],
• Peer-jump hover nudge — transform: translateX(1px) on hover of the
• Palette result slide-in — padding-left 12px → 16px transition on
• Block 0359 — retro editorial on what v3.2 changed + why, for the /b/0359
• prefers-reduced-motion respected — existing media query extended with

WHAT SHIPPED

• src/components/PulseStrip.astro — multi-agent dots. Shows cc · codex · manus · chatgpt (chatgpt only if any ledger entry exists). Each dot derives state from the most-recent ComputeEntry for that collaborator slug; green pulse if within 20 minutes, idle otherwise. Per Mike's direct ask "add a codex working if codex working and manus."
• tools/manus-mcp/{package.json,index.js,README.md} (new directory, ~280 lines, zero dependencies) — hand-rolled JSON-RPC stdio MCP server wrapping the Manus REST API. Two MCP tools:
• manus_run_task(prompt, files?, agent?, poll_timeout_sec?) — create + poll until terminal state.
• manus_task_status(task_id) — check a task already in flight.
• Config-driven via env vars: MANUS_API_KEY (required), MANUS_BASE_URL (default https://api.manus.ai), MANUS_AGENT_DEFAULT (default manus-1.6-max), MANUS_CREATE_PATH (default /v2/tasks), MANUS_STATUS_PATH_TPL (default /v2/tasks/{id}), MANUS_AUTH_SCHEME (default Bearer). Once Mike confirms the actual Manus REST endpoint paths against the docs, override via env vars; no code change needed.
• Install: claude mcp add manus -e MANUS_API_KEY=$KEY -- node /absolute/path/tools/manus-mcp/index.js. Stderr startup log confirms the binding.
• src/components/HeroBlock.astro — shipped by Codex (single-file low-reasoning MCP fire, 136 lines). Daily deterministic pick from a curated pool of 7 hero-worthy block IDs. Renders one block as a full-width editorial card above the fold (noun + kicker + title + dek + open-link). 4th Codex single-file win of the night.
• src/components/ActionDrawers.astro — shipped by cc (Codex MCP timed out on this multi-drawer spec earlier, cc shipped directly). 4-button accordion at the bottom of the home: ping (composer), drop (deep link), polls (deep link), contribute (pledge composer). One drawer open at a time. Each drawer color-coded (amber/green/violet/blue). Inline composers POST to /api/ping.
• src/pages/play.astro — discovery hub for all 8 interactive surfaces (drum, cards, quiz, here, polls, today, battle, prize-cast). Card-grid layout with accent color per game + 1-line description + tags + "play →" CTA. Single URL to send to a friend who wants to see what PointCast is in 30 seconds.
• src/content/blocks/0337.json — sprint mid-burn editorial. 4-min read. Captures Codex 4/4 results, manus-mcp shape, home rethink Phase 2 landing, the visitors-first pivot continuing. Cross-linked to /b/0336 (the pivot block) and /b/0332 (Codex retro).
• src/pages/index.astro — wired in HeroBlock (above PULSE) + ActionDrawers (after the BlockReorder grid).
• src/components/TodayOnPointCast.astro — added PLAY · HUB entry to the rotation pool.
• src/lib/compute-ledger.ts — synced 9 new ComputeEntry rows for tonight's ships. Disciple held: every shipped retro writes a matching ledger entry in the same commit.
• src/lib/ship-queue.ts — synced 6 new QueuedShip rows (ship-0056 through ship-0061), all marked shipped with landedAt timestamps + artifact pointers.
• ✅ PrizeCastChip — low reasoning, single file → MCP "timed out" but file landed (filesystem confirmed)
• ✅ SHA-256 hash script — low reasoning, single file → MCP returned cleanly + script ran
• ✅ OAuth authorization server stub + headers edit — low reasoning, 2 atomic files → MCP returned cleanly
• ❌ /quiz — medium reasoning, 3 files including a content JSON → MCP timed out, no files. cc shipped directly.
• ✅ HeroBlock — low reasoning, single file → MCP returned cleanly + 136 lines

WHAT SHIPPED

• src/components/CoNavigator.astro — bar buildout.
• Right-zone nav: added ✦ +compute chip (to /contribute) and ↗ cast chip (native Share API with warpcast.com/~/compose fallback).
• New nav order: here · drum · ✎ ping · ✦ +compute · ↗ cast · bench · me.
• Cast button uses navigator.share() on mobile + modern desktop; falls back to Warpcast compose URL with encoded page title + embeds.
• Addresses Mike's 4/19 ping ("can we make a cast button yah that makes sense") + today's "build out the bar" directive.
• src/pages/contribute.astro (new, ~470 lines) — five-ways-to-contribute page.
• Way 01 — Pledge a sprint (inline composer that POSTs to /api/ping with subject contribute · pledge sprint; treated as a regular ping on the cc side).
• Way 02 — Review a PR (link to github.com/MikeHoydich/pointcast).
• Way 03 — Federate a ledger (link to /compute#federate + /compute.json).
• Way 04 — Run a node (link to /for-nodes).
• Way 05 — Fund a brief. Two rails: tez to Mike's tz2FjJhB…MxdFw today, x402/USDC-on-Base via Agentic.Market coming (Manus brief in flight).
• "What you get back" backbar (attribution, receipt, shape to borrow, workbench access).
• src/pages/profile.astro — wallet stats bug fix.
• lastActivity (block-level integer) → lastActivityTime (ISO string). Previous code passed the integer to new Date(), yielding epoch-0 → Dec 31, 1969 in PT. Fix reads the correct TzKT field + guards for invalid / zero-valued dates. Verified against Mike's wallet — now reads 2026-04-17T20:48:01Z.
• src/data/market.json — refreshed via node scripts/fetch-market.mjs. 4 days stale (2026-04-16) → fresh (2026-04-20T21:09:57Z). 20 tokens, 7 actively listed, lowest ask 0 ꜩ (#5 Piet Mondrian). 16 token images cached in public/images/tokens/.
• src/lib/compute-ledger.ts — x402 schema hook.
• ComputeEntry.x402 optional field: { direction: 'in'|'out', service: string, priceUsdc?: number, settled?: string }.
• Forward-compatible: zero existing entries change. Future entries can carry payment pointers so a federated ledger advertises both attribution and payment rail.
• Seeded five new ledger entries for this tick (sprint + block 0331 + block 0332 + two briefs + Mike-directive entry).
• src/content/blocks/0331.json — "x402, Agentic.Market, and the compute ledger — payment meets attribution."
• 4-min read, channel FD, mood federation.
• Thesis: payment layer (x402) + attribution layer (/compute) compose; cheap motions (A+B+C+D) + the one deferred integration (full x402 client for cc as a consumer).
• Cross-linked with /b/0330 (federated compute primitive).
• src/content/blocks/0332.json — "Codex, one month in — what the second engineer on PointCast is actually doing."
• Processed Mike's 2026-04-19T18:03:46.841Z ping with expand: true per AGENTS.md topic-expand protocol.
• author: mh+cc (Mike supplied substance, cc supplied prose).
• 5-min read, retrospective mood. Covers: what Codex has shipped (STATIONS, presence DO, pulse, track authoring, videolens, yeeplayer, moods-soundtracks), atomic-single-file-spec pattern that works, open-ended architecture anti-pattern, Chronicle memory feature implications, pipeline thesis (cc writes atomic brief between ticks → Codex lands it while cc is on next thing), payment rail implications.
• source field links the originating ping key per the protocol.
• docs/briefs/2026-04-20-chatgpt-drum-cookie-clicker.md (new) — full single-file brief for ChatGPT.
• Rewrite /drum as a Web Audio cookie-clicker. Upgrade ladder (10 → 50 → 200 → 1k → 5k → 25k beats), prestige "cast a rhythm" with local rhythm-receipt minting, passive auto-drummers, tap multipliers, polyrhythm upgrades.
• Coordination protocol: feat/drum-cookie-clicker branch, Co-Authored-By: ChatGPT commits, cc reviews + merges, ledger entry + retro on land.
• docs/briefs/2026-04-20-manus-agentic-market-listing.md (new) — ops brief for Manus.
• List PointCast on Agentic.Market as a provider. Two services: cc-editorial (0.50 USDC per block) + cc-sprint (2.50–10 USDC by signature band).
• Fulfillment endpoint stubbed at /api/x402/[service] returning 501 until cc ships the handler next session.
• Deliverables: service cards live on agentic.market, screenshot log at docs/manus-logs/{date}.md, ping back to Mike with Base wallet address.
• src/components/NetworkStrip.astro — repurposed as promo rotation.
• Was a network-primitive index (here / for-nodes / workbench); now a curated three-item promo slot with new / today / live tags. Pointed at /contribute + /b/0331 + /compute. Swap-by-hand discipline (whoever ships rotates the promo).
• Addresses Mike 2026-04-20 15:30 PT: "network likely almost a spot to yahh promote things."

WHAT SHIPPED

• src/components/PingStrip.astro (new, ~250 lines)
• Kicker: "PING · feedback + ideas for the team — cc reads the inbox at session start"
• Collapsed default: one line + a ✎ say something toggle button (dark fill, warm-amber border to match editorial palette).
• Expanded: 3-row textarea (body, required), 2-col row (from / subject, both optional), EXPAND & PUBLISH opt-in checkbox, SEND button + status readout + or use the full form → escape hatch to /ping.
• Submits POST to /api/ping with type: pc-ping-v1 · body · from? · subject? · expand? · timestamp.
• Success → sent — cc reads at session start (or sent — cc drafts a block on the next tick when expand=true) → collapses after 1.8s.
• Keeps from populated between submits so Mike doesn't retype his name mid-thread.
• src/components/CoNavigator.astro
• Right-zone nav order: here · drum · ✎ ping · bench · me. Ping chip uses amber accent (#e89a2d) and the ✎ glyph so it reads as a distinct "send" affordance vs. the other navigation links.
• Mobile breakpoint at 400px already hides chip #4+ so ping stays visible on tiny screens (since it's #3 in the order).
• src/pages/index.astro
• PingStrip renders as the FIRST strip on the home, above FreshStrip. Rationale: feedback → in, freshness → out. Give the inbound channel top billing so Mike's first instinct on any page is "drop the idea now".
• AGENTS.md
• New section under Claude Code role: SESSION-START INBOX CHECKLIST — do this FIRST, before any other work. With an explicit curl command (curl -s 'https://pointcast.xyz/api/ping?action=list' | jq '.entries[-5:]') and an ls docs/inbox/ for the on-disk side.
• Policy strengthened: "Never start implementation work before this read; the ping inbox is the highest-priority channel Mike has for async direction."
• src/lib/compute-ledger.ts — two entries added:

WHAT SHIPPED

• src/components/CoNavigator.astro
• New popover markup .conav__mood-picker with 6 .conav__mood-opt buttons (parallels the noun picker shape).
• Script: selectMood(id), meditativePulse(id), openMoodPicker/closeMoodPicker. Replaces the old "no mood → redirect to /#mood" flow.
• Close-bar handler now also closes the mood picker.
• CSS: picker styles + 3-col desktop / 2-col ≤520px grid. Global .mood-pulse + @keyframes moodPulse ported from MoodChip so the animation works without MoodChip rendered anywhere.
• src/pages/index.astro
• Removed <MoodChip /> render + import. Replaced with a comment block citing Mike's directive. File src/components/MoodChip.astro remains on disk untouched (future-proof; can return if surface reappears).
• src/lib/compute-ledger.ts — added an entry for this ship. Discipline: every sprint retro gets a ledger entry in the same commit.

WHAT SHIPPED

• src/lib/compute-ledger.ts (new, ~210 lines) — the data model.
• Types: ComputeEntry, ComputeKind (sprint/block/brief/ops/editorial/federated), ComputeSignature (shy/modest/healthy/heavy with token bands).
• Data: COMPUTE_LEDGER seeded with ~17 real entries from 2026-04-18 → today.
• Helpers: collabCounts(), recentEntries(hours), label + band maps.
• Discipline doc in header: every new sprint retro should get a ledger entry in the same commit.
• src/pages/compute.json.ts (new) — agent-readable surface.
• Full ledger + summary counts + signature/kind scale docs + 3-step federation spec + references Gil post.
• CORS open (Access-Control-Allow-Origin: *) so other nodes can cross-fetch.
• src/pages/compute.astro (new, ~280 lines) — public ledger page.
• Header: title + dek + stats strip (total, 24h, 7d, collabs).
• Section 1: BY COLLABORATOR — counts + heaviest signature per collaborator.
• Section 2: LEDGER — newest-first with time / who / kind / title / signature bar.
• Section 3: SIGNATURE SCALE — shy/modest/healthy/heavy + token bands.
• Section 4: FEDERATE YOUR COMPUTE — 3 steps + contact + repo link.
• src/components/ComputeStrip.astro (new) — compact home-page readout.
• Kicker line (total ships + last-24h + /compute link).
• Top 3 entries with full row detail (mobile collapses to 1).
• Footer cites Gil + links /compute.json.
• Purple left-rule (#5F3DC4) visually distinct from NetworkStrip (blue).
• src/content/blocks/0330.json (new) — editorial dispatch.
• "Compute is the currency · and PointCast just federated its ledger"
• 4 min read, channel: FD, mood: federation.
• Body connects Gil's 12 theses to PointCast's actual shape: #3 (compute currency), #7 (closed-loop), #8 (artisanal/utility engineer split), #9 (harness defensibility), #10 (labor marketplace), #12 (anti-AI backlash narrative).
• src/pages/index.astro — wired ComputeStrip import + render slot between NetworkStrip and TodayOnPointCast.
• src/lib/collaborators.ts — dropped the Kenzo entry. Mike said: *"side note that kenzo entry shouldn't be there."* Clean removal; no downstream references broke.
• #3 — compute is the currency. This ship is the direct response. Publishing the ledger is the action, not the commentary.
• #7 — closed-loop automation first. Mike directs, cc ships, verify in prod. Tightest two-entity loop possible. Gil flags code/software engineering as the highest-leverage closed-loop domain; PointCast operates exactly there.
• #8 — artisanal/utility engineer split. Mike = artisanal director (taste, editorial, direction). cc = utility engineer (ships). Division of labor is the whole point.
• #9 — harness defensibility. BLOCKS.md, CoNavigator, ClientRouter music persistence are the harness. Model underneath is swappable.
• #10 — labor marketplace, not software. Every block here is a labor unit shipped by a named collaborator. The Co-Authored-By commit lines are literal proof.
• #12 — anti-AI backlash. Counterprogramming is to name your AI collaborators publicly + show what they shipped. /compute is part of that answer. /collabs + /sprints + /compute are now the three transparency legs.

WHAT SHIPPED

• src/components/CoNavigator.astro (new, ~340 lines) — the co-navigator. Fixed to viewport bottom, ~48-56px tall. Three zones:
• LEFT: current mood (dot + label) + ▶ SOUNDTRACK button (appears when a mood is set).
• MID: stats readouts — here now (live fetch from /api/presence/snapshot), hello (from pc:hello:count), streak (computed from pc:daily:collected).
• RIGHT: quick-nav chips linking to /here, /workbench, /drop.
• DRAWER (above the bar): iframe player for the mood's soundtrack. transition:persist="pc-soundtrack" keeps it alive across Astro soft-navs.
• src/layouts/BaseLayout.astro + src/layouts/BlockLayout.astro — both updated:
• <ClientRouter /> from astro:transitions for soft navigation.
• Mood-persistence script in <head> reads pc:mood before paint and sets data-pc-mood on <html> for zero-flicker tinting.
• Mood-tint CSS moved to a global <style> block (was scoped to MoodChip, only worked on home).
• body { padding-bottom: 60px } so content doesn't hide under the fixed bar.
• <CoNavigator /> rendered in body at the end.
• src/components/MoodChip.astro (modified) — removed the inline soundtrack player markup (was duplicating CoNav's player). The mood buttons now also dispatch a pc:mood-changed CustomEvent, which CoNav listens for.
• Build: 249 pages clean.
• Deploy: https://f3d6d9d9.pointcast.pages.dev/ → pointcast.xyz live on main.
• Home: 26 pc-conav-* class mentions, conav__bar present, pc-soundtrack persist name present, transition:persist attribute present.
• /here, /b/*, /c/*, /clock/*, and other BlockLayout pages all carry the CoNav.

WHAT SHIPPED

• Problem with the old: HTML5 drag events don't fire on touch devices, and the BlockCard is an <a> — dragging conflicted with link-clicking. Result: Mike couldn't arrange on mobile at all, and on desktop dragging often triggered navigation.
• Fix: Explicit toggle gates arrange mode. When ON: dashed outlines on every card, cursor → grab, link clicks suppressed in capture phase, cards become pointer-capturable via Pointer Events (works on mouse + touch + pen equally). A placeholder element holds drop-target space so the grid doesn't jump during drag.
• Persistence unchanged: pc:block-order localStorage key, same shape, same recovery. Toggle label also shows count of moved blocks when you have a custom arrangement.
• Reset button surfaces when custom order exists.
• Typography stack: Inter for team names (condensed, modern), tabular-numerals monospace for scores (column-aligned), Georgia for loading/empty states, mono for the metadata chips. Looks intentional now.
• Each game becomes a card: status chip at top (FINAL / LIVE / UPCOMING), two team rows below (away then home), score prominent on the right in tabular-num mono, winner row highlighted in cobalt with bold weight.
• Hot badge ⚡ — surfaces when score diff is ≤3 points on a final or ≤2 during in-progress; also when the status contains OT / SO / ET / shootout / penalties / extra. Draws attention to close games without needing to parse the scores yourself.
• LIVE state — red chip with a ● that pulses (1.4s infinite). Background shift to warm red so the tile stands out from final-state gray.
• Upcoming state — cobalt chip, muted scores (since none yet), shortDetail renders as the start time.
• Grace-fallback unchanged: ESPN fetch errors → "tap board →" link, no fake scores.

WHAT SHIPPED

• src/components/DailyDropStrip.astro (new, ~200 lines) — compact home-feed version of /today's daily-drop collect. Today's pick renders as: thumbnail + code kicker (CH.VST · 0232 · VISIT) + title + COLLECT button + streak/total stats. Shares localStorage keys with /today (pc:daily:collected, pc:daily:lastDay, pc:hello:count) so a claim on either surface counts everywhere. Streak computation walks collection dates backward from today counting consecutive days.
• src/components/SportsStrip.astro (new, ~180 lines) — 4-league grid: NBA, MLB, NHL, Premier League. Client-side fetches ESPN public scoreboard API (https://site.api.espn.com/apis/site/v2/sports/{path}/scoreboard) per league on mount, renders 2 most-recent games per tile with status-specific styling (FINAL / in-progress clock / upcoming time). 10-min sessionStorage cache to avoid hammering ESPN on repeat views. Graceful fallback: if a fetch fails, the tile shows "tap scoreboard →" link with no fake scores. No placeholder data.
• src/content/polls/btc-trend-from-here.json (new) — "From $75K today, is Bitcoin going up or down next?" 6 options span the full forecast range (up-strong/up-soft/sideways/down-soft/down-hard/dont-know). Resolves 2026-05-20. Anchored to block 0329 (the BTC at $75K field note Codex wrote). Now shows as the newest poll so HerePoll surfaces it on /here by default.
• src/lib/moods-soundtracks.ts (new, Codex via MCP) — 6 mood → soundtrack map. Real URLs (lofi girl YouTube for chill; Spotify Deep Focus for focus; Peaceful Piano for quiet; Beast Mode for hype; Coding Mode for flow; Brain Food for curious). Typed Soundtrack interface + getSoundtrack() helper.
• src/components/MoodChip.astro (modified) — soundtrack toggle appears inline after a mood is picked. Shows "▶ {playlist label} · {MOOD}" as a pill button. Tap → expands an embedded iframe (152px tall, dark frame) playing the mood's soundtrack. Close button resets to about:blank. Selecting a different mood swaps the offer + resets the player. Player frame is lazy-loaded, autoplay-capable when the embed allows.
• src/components/HerePoll.astro (modified) — post-vote follow-up prompt. After a successful vote the card keeps rendering the distribution bars AND surfaces an amber-accent "THEN TRY: {next question} →" link at the bottom. Fetches /polls.json, picks the newest unvoted poll from that list, falls back to /polls if everything's been voted. Keeps the engagement alive past the first tap — answers Mike's "make more interesting once you voted, and then a follow up."
• src/pages/index.astro — wires DailyDropStrip + SportsStrip into the home between TodayOnPointCast and MoodChip. Flow now reads: FreshStrip → VisitorHereStrip → NetworkStrip → TodayOnPointCast → DailyDropStrip → SportsStrip → MoodChip (with soundtrack) → PollsOnHome → FreshDeck → channels → HomeMajors → grid.
• Build: 248 → 249 pages (+1 route: /poll/btc-trend-from-here).
• Deploy: https://ee977ae2.pointcast.pages.dev/ → pointcast.xyz live on main.
• Home curl: 22 daily-drop-strip mentions, 8 sports-strip + 27 sports-tile mentions, 5 mood__soundtrack mentions (all rendered).
• /poll/btc-trend-from-here: 200.

WHAT SHIPPED

• src/components/HereBeat.astro (new, ~200 lines) — meditative beat-pad surface for /here. 6 pads tuned to A-minor pentatonic (A3/C4/D4/E4/G4/A4, 220/261.63/293.66/329.63/392/440 Hz). Sine-wave tones via Web Audio with slow ADSR (50ms attack → 0.18 peak → 1.6s exponential decay). Each pad has a unique hue (28/45/320/280/210/155 — amber/honey/rose/violet/cobalt/sage) that drives both the lit-state glow and the ripple. Ripples are radial-gradient circles that bloom from center over 1.6s. Keyboard: 1-6 per pad, space for random. Tap target ≥64px for touch devices.
• src/components/HerePoll.astro (new, ~170 lines) — single-poll surface for /here in dark/amber. Pulls most-recent non-draft poll from the content collection at build time. Tap-to-vote → POST /api/poll → swaps card to distribution bar view. localStorage dedupe keyed pc:poll:voted:{slug}. Voted option gets a ✓ prefix + amber border; unvoted options show 0% bars that animate in over 0.8s on distribution reveal. References the sketches/polls-moment.html and sketches/polls-variants.html prototypes as design anchors; adapts to dark theme.
• src/pages/here.astro — now renders HereGrid → HerePoll → HereBeat → machine-readable as the section flow. Fills the empty space between the visitor grid and the agent strip with real interactive surfaces.
• src/components/MoodChip.astro — meditative color-field pulse added on mood-button click. Mood→hue lookup: chill 155 (sage-green), hype 8 (warm red), focus 215 (cobalt), flow 275 (violet), curious 28 (amber), quiet 220 (deep slate). Full-viewport radial-gradient overlay element injected dynamically on click; CSS keyframe animation over 1.8s (fade in 0→0.9 in 360ms, bloom 1.0→1.1 scale, fade out 0.5→0 in 800ms); mix-blend-mode: multiply so it tints the page rather than covers it. Respects prefers-reduced-motion — animation skipped for users who opted out at the OS level. Overlay DOM node cleaned up after 1800ms.
• src/pages/index.astro — MorningPara removed (component file preserved on disk). TodayOnPointCast already surfaces today's editorial beats in that zone; the morning paragraph was redundant.
• Build: 248 pages clean.
• Deploy: https://df741170.pointcast.pages.dev → pointcast.xyz live on main.
• /here body now includes 23 here-beat CSS-class mentions (pad grid + ripple rules), 41 here-poll mentions (options + score bars + labels), "LIVE POLL" + "BEAT · SOFT" kickers both rendered in-place.
• Home has zero MorningPara references (confirmed via curl + grep).
• Mood animation is JS-injected — verification requires a real click; the CSS keyframe is present in the shipped stylesheet.

WHAT SHIPPED

• src/components/TodayOnPointCast.astro (new, ~190 lines) — curated "today's highlights" strip on home. Six stops in an auto-fit grid: (01) Happy 4/20 → /b/0328, (02) BTC at $75K → /b/0329, (03) Presence DO online → /b/0327, (04) Collab clock → /clock/0324, (05) AI landscape → /b/0325, (06) Start tour → /start. Timestamped "Monday, April 20 · El Segundo" header. Each stop has kicker/title/dek/arrow. Footer row links /workbench + /here + /for-nodes.
• src/pages/index.astro — renders TodayOnPointCast between NetworkStrip and MoodChip.
• src/pages/collabs/index.astro — new "BUILD A CLIENT" section with 5 client type cards + matching styles. Each card is a real task someone could claim:
• Type 1: macOS Field Node — clipboard intelligence, local-first, forwards to /api/drop.
• Type 2: Apple TV ambient — tvOS renders /tv full-screen for cafe/home display.
• Type 3: iOS companion — phone next to the feed, real GPS for "where", native pickers.
• Type 4: Browser extension — toolbar "Drop this" + "Broadcast session as agent."
• Type 5: CLI terminal node — pointcast binary, drop / ping / presence / blocks-tail subcommands.
• docs/briefs/2026-04-20-field-node-client.md (new, ~180 lines) — full brief adapted from Mike's ChatGPT PRD. Architecture (Swift + SwiftUI + SQLite + GRDB/FTS5), data model (events + artifacts + sessions + action_candidates), scoring model, phased deliverables (MVP → Intelligence → Node), PointCast client contract (POST /api/drop + WS to /api/presence), open questions. Ready for claim via /ping or PR.
• Build: 248 pages clean.
• Deploy: https://74b1b397.pointcast.pages.dev → pointcast.xyz live on main branch.
• Homepage: TodayOnPointCast strip visible between NetworkStrip and MoodChip. All six stops render with proper kickers.
• /collabs: Clients section visible between federation spec + talk-to-us. All 5 client types render.
• curl checks: all 6 home stops + all 5 client cards present in live HTML.

WHAT SHIPPED

• functions/api/analytics.ts (49 lines) — POST endpoint for the analytics lib. JSON validation, 2KB meta limit, 90-day KV writes with coarse IP hinting, silent 204 fallback when PC_ANALYTICS_KV is unbound, CORS preflight.
• src/lib/audio-onset.ts (85 lines) — Web Audio mic onset-detection primitive for Brief #9. getUserMedia + AnalyserNode + RMS thresholding + min-interval gating + clean shutdown + unsubscribe-capable listeners.
• src/lib/pulse-state.ts (58 lines) — pure game-state helpers for Brief #1 Pulse. Immutable updates, median-interval BPM aggregation over last 16 taps, 100-tap retention.
• The Waldos origin story (San Rafael, 1971, Louis Pasteur statue, 4:20pm)
• The 2026 state of the day (SoCal supermarket shelves, Euromonitor $4.1B trajectory, Mass codification)
• Good Feels positioning (hemp-derived, 5mg, water-soluble, substitute-the-first-drink design)
• Call to shop.getgoodfeels.com 4/20 specials
• Invite to open /here after pouring one so the room is bigger by one
• Closing byline from cc ("a machine that does not imbibe but does appreciate a well-constructed beverage lineup")
• Build: 246 → 248 pages (+2: blocks 0328 + 0329).
• Deploy: https://8608d948.pointcast.pages.dev → pointcast.xyz live.
• curl /b/0328/ returns proper body, shop.getgoodfeels.com 8 mentions, zero markdown-bracket artifacts, external CTA intact.
• curl /c/good-feels/ (the GF channel URL-slug) 200 — 0328 surfaces there alongside the other GF blocks.

WHAT SHIPPED

• src/lib/analytics.ts (Codex via MCP — 65 lines). First clean MCP-driven Codex ship. low reasoning + tight atomic prompt + single file = fits under the 60s ceiling. Typed AnalyticsEvent union + send() with sendBeacon fallback + respects DNT + localStorage opt-out. Ready for /api/analytics endpoint when that ships.
• src/pages/workbench.astro (new, ~280 lines) — cross-agent activity dashboard. Five sections: headline stats (live count / recent ships / Codex queue / Manus queue / nodes), LIVE panel → /here, Codex queue (17 briefs), Manus queue (5), recent sprint retros (12), nodes registry (3), collaborators strip (5). Client-hydrates live count from /api/presence/snapshot. Reads briefs + sprints at build time via Node fs.
• src/components/NetworkStrip.astro (new) — compact home-page strip between VisitorHereStrip and MoodChip. Surfaces /here + /for-nodes + /workbench with a live-count + node-count readout.
• src/pages/index.astro — imports + renders NetworkStrip.
• src/pages/start.astro (new, ~200 lines) — the 5-stop tour for first-time visitors. Each stop is a concrete action: see who's here / collect today's drop / vote on a poll / play a round / back to feed. HowTo JSON-LD. Optional agent-operator section + wallet-connect caveat.
• src/components/FreshStrip.astro — CTA "START HERE →" now routes to /start (both SSR fallback + the hello-state JS override). Changed one line in the render, two in the JS.
• src/components/VisitorHereStrip.astro — clickable visitor slots. Occupied non-YOU slots become buttons (role="button", tabindex=0). Click/tap opens a focus panel below the strip with: noun avatar, kind, joined time, mood, listening, where. Close button dismisses; tapping the same slot toggles it off. ~60 lines of added JS + ~55 lines of CSS.
• src/lib/timezones.ts — added Mallorca + Palma + Barcelona + Spain → Europe/Madrid. Kenzo (added to collaborators.ts by Mike this tick) now resolves correctly on /clock/0324.
• Build: 241 → 244 pages (+3: /start, /workbench, plus /start as HowTo-JSON-LD schema adds a route).
• Deploy: https://2f7deda1.pointcast.pages.dev → pointcast.xyz live (with --branch=main explicit this time).
• Live checks:
• /start 200 ✓
• /workbench 200 ✓ (renders 12 recent sprints, 17 Codex briefs, 5 Manus briefs, 3 nodes, 5 collaborators)
• /clock/0324 includes Mallorca + Kenzo ✓
• Home page contains NetworkStrip markup ✓

WHAT SHIPPED

• src/lib/collaborators.ts — removed Taner (line 79-89 deleted), updated Codex intro from "reviewer · second pair of eyes" to "Repo-scoped engineering specialist · shipped STATIONS + presence DO + /here backend · MCP-driven", updated Manus intro to reflect actual current role.
• src/pages/collabs.astro — added "Ways to contribute" section with 6 concrete paths: (1) broadcast as a node → /for-nodes, (2) guest block, (3) federate, (4) host local, (5) donate compute (forward-looking), (6) seed polls. Plus matching styles block.
• src/content/blocks/0325.json — Kimi K2.6 field note (READ, 4 min). Landscape context + the OpenClaw/K2.6 connection to PointCast's federation arc + non-exhaustive comparison with Claude, Codex, Qwen, Gemini, GLM.
• src/content/blocks/0326.json — Qwen 3.6 Max Preview field note (NOTE, 2 min). Incremental, closed, Chinese-frontier context.
• src/content/blocks/0327.json — Presence DO online (NOTE, 2 min). Milestone recording that the deferred DO is finally bound.
• src/content/polls/how-to-contribute.json — new poll, 6 options mirroring the collabs contribute section. outcomeAction: top 2-3 votes shape next sprint priorities.
• src/content/polls/ai-lineup-vibe.json — new poll, model-combination preferences. outcomeAction: leader becomes /ai-stack default.
• src/lib/multiplayer.ts — new, 180 lines. Shared base class MultiplayerRoom<Action, Broadcast> + ActionThrottle + generateUniqueSessionId for Pulse + YeePlayer v1 + future rooms to extend. Codex attempted this turn via MCP but aborted before write; cc wrote it directly.
• docs/plans/2026-04-20-release-sprint.md — appended "Progress update — 2026-04-20 10:40 PT" section (~80 lines) documenting actual vs planned status, revised Codex queue (3 shipped of 10: STATIONS + Presence DO + /here), MCP pattern learnings, and "what's missing for Codex-at-full-blast" analysis.
• Build: 235 → 241 pages (+6 routes: 3 new blocks × 2, 2 new polls × 2, plus /clock/0324 inherited from block 0324's clock config).
• Deploy: https://5a3b2447.pointcast.pages.dev/
• All new routes return 200: /collabs, /clock/0324 (LIVE world clock — reads timezones from the updated collaborators roster + block 0324's manual NYC/Tokyo extras), /b/0325, /b/0326, /b/0327, /poll/how-to-contribute, /poll/ai-lineup-vibe.
• curl /collabs/ | grep -c taner returns 0 — fully removed.
• Mike Hoydich (El Segundo → America/Los_Angeles)
• cc / Codex / Manus (cloud → UTC, collapsed sensibly)
• Manual zones from the block: NYC + Tokyo
• Live-ticking digital readouts, Intl.DateTimeFormat client-side, no deps.

WHAT SHIPPED

• curl https://pointcast.xyz/api/presence/snapshot → {"humans":0,"agents":0,"sessions":[]} — real DO response, no longer the "DO not bound" fallback.
• Direct Worker URL returns the same shape → DO is reachable from both paths.
• /here renders 200, will hydrate as visitors connect.
• WS handshake test inconclusive via curl (HTTP/2 quirk); browser test will confirm. If WS fails, the patch is likely in the Pages Function forwarding — quick fix.

WHAT SHIPPED

• src/lib/nodes.ts (cc, new) — owned-agents registry. Node interface + NODES[] with cc, codex, mike as initial entries + getNode()/resolveAgentLabel()/nodeCounts() helpers. Groundwork for labeling Jason's OpenClaw when he plugs in.
• src/pages/for-nodes.astro (cc, new) — public "become a node" page. Renders the 2-line agent-broadcast snippet, lists registered nodes, explains the namespace-isolation architecture.
• docs/briefs/2026-04-20-codex-presence-worker-deploy.md (cc, new) — Codex brief for shipping the Presence DO as a companion Worker so the broadcast plumbing actually lights up.

WHAT SHIPPED

• Codex CLI v0.121.0 installed at /Users/michaelhoydich/.npm-global/bin/codex
• codex mcp-server --help prints valid stdio-server usage
• ~/.codex/config.toml already trusts /Users/michaelhoydich/pointcast as a project
• ~/.codex/auth.json populated (logged in)
• Model: gpt-5.4 with xhigh reasoning effort (in config.toml)

WHAT SHIPPED

• Title: "Presence got identity · verify caught its own regression"
• Channel / type: FD · READ (editorial reflection, matching 0320/0321 pattern)
• Dek — the standout moment: Codex's step-5 verify catching a 90-second-timeout regression in its own PresenceBar.astro.
• Body (~550 words) — the overnight arc: seven files · +996 -231 · DO rewrite · VisitorHereStrip real-noun render · /tv constellation · /for-agents + /agents.json documentation · Codex's verbatim verify catch. Plus two observations worth recording:
• Companions link backwards to 0322 (the precursor status note), 0321 (the release-sprint plan), and 0284 (the STATIONS brief that preceded Brief #6 in the queue).
• Mood: overnight-ship — new slug. Auto-creates /mood/overnight-ship/ as a filter page.
• Mood primitive — already fully shipped. Schema has mood?: string, 14 blocks tagged, /b/{id} renders the chip (lines 140-146 in b/[id].astro), /mood/{slug}/ filter pages build cleanly (5 existing: grounded, quiet, rainy-week, spirit, current-state, now +overnight-ship). Nothing to add.
• Reverse-companions 0262/0263/0264 → 0275 — would've required asserting Nov Rain + Purple Rain are actually on Mike's Spotify playlist. I can't verify that from the playlist URL alone, and cc's rule is no invented claims about Mike's state. Passed.
• Editorial block was the right call — the overnight run was a real, specific, recordable event with a standout engineering moment (verify catch) and a workflow pattern observation (sandbox constraint helped). Worth capturing in the ledger, and 0323 completes a natural three-beat arc: 0322 "Codex unblocked · queue built" → 0321 "release sprint plan" → 0323 "first overnight Codex cycle closed clean."

WHAT SHIPPED

WHAT SHIPPED

• Approved PresenceBar patch dialog via computer-use
• Ran the build: 228 pages (same as previous tick; no new routes, just updated files)
• Deployed: https://513fdf8a.pointcast.pages.dev

WHAT SHIPPED

• git diff -- functions/api/presence.ts src/components/VisitorHereStrip src/pages/tv.astro src/pages/for-agents src/pages/agents.json.ts
• git diff --check -- (catches whitespace / line-ending issues)
• Approved 3 dialogs via computer-use
• Ran build: 227 → 228 pages built (the +1 page is actually the new poll from last tick, staying in the count)
• Spot-checked /agents.json: presenceProtocol object has all 6 expected keys with matching privacy text
• Deployed: https://9c1f96d5.pointcast.pages.dev

WHAT SHIPPED

• Broadcast contract header documents {humans, agents, sessions: [...]} — backwards-compatible with PresenceBar (humans + agents stay); sessions array is additive
• Privacy docstring matches the brief (session ids never leave DO, only derived noun IDs broadcast)
• TypeScript types clean, file compiles

WHAT SHIPPED

• 2 files changed · +462 -129 across presence.ts (step 1) + VisitorHereStrip.astro (step 2)
• Codex's running status: *"I've landed the DO rewrite and the strip's client logic. I'm tightening the slot styling next so the new avatars actually render cleanly in-place, then I'll wire the TV header to the same enriched payload."*
• Sidebar time: 1h since brief kickoff; roughly halfway through the 3-4h budget
• Each ghost slot gained <img class="here-slot__noun here-slot__noun--other"> — so when the DO broadcasts other visitors' noun IDs, images can render in-place
• Header comment updated: *"The DO now broadcasts per-visitor noun identity, so connected visitors render as actual noun avatars while the existing aggregate count stays intact for older consumers"*
• TELL panel eyebrow updated: *"TELL THE PEOPLES · local first · live when connected"* — signals the new live-broadcast behavior

WHAT SHIPPED

• Deleted presence.ts +0 -124 (old DO)
• Created presence.ts +334 -0 (new DO with identity-enriched broadcast)
• Edited presence.ts +3 -0 (small follow-up adjust)
• Net: 1 file changed, +272 -59

WHAT SHIPPED

• Path: /Users/michaelhoydich/pointcast (explicit, so Codex doesn't default to the wrong repo)
• Brief reference: docs/briefs/2026-04-19-codex-presence-do-upgrade.md
• Context acknowledgment: STATIONS (#2) just shipped end-to-end; sandbox blocks .astro/ cache + git writes; cc handles build + deploy
• Key deliverables enumerated (architecture doc, DO upgrade, VisitorHereStrip render update, /tv constellation update, /for-agents + /agents.json docs)
• Privacy reminder: never broadcast session IDs, only derived noun IDs; agents broadcast no mood/listening/where
• Attribution: author codex, source cite the brief per VOICE.md
• Fallback: if sandbox blocks commits, leave staged + tell cc

WHAT SHIPPED

• /api/weather?station=malibu: returned {ok:true, station:"malibu", name:"Malibu", tempF:54, condition:"clear", sunset:"2026-04-20T19:29", updatedAt:"2026-04-20T01:15"} — live weather data from Open-Meteo via Codex's proxy. Works.
• /tv/malibu returns a 308 redirect to /tv/malibu/ (trailing-slash normalization), then serves a meta-refresh redirect HTML pointing at /tv?station=malibu. Works — but the backup JS <script>window.location.replace({JSON.stringify(target)});</script> has an unterminated template-literal bug (braces not interpolated at build time). Meta-refresh still fires so the redirect works; JS fallback is broken. Flagged below.
• /tv home: 21 STATIONS-markup references (stations-index / station-feed / STATION_SHORTCUTS / data-station) confirm the 3-mode integration rendered.
• Title: "STATIONS mode on /tv · first full Codex feature delivery"
• 9 highlight bullets enumerating the ship (3-mode UX, 15 per-station routes, weather proxy, enriched src/lib/local.ts, /local + /local.json updates, /for-agents doc update, architecture review, author: codex throughout)
• 4 links: STATIONS brief, architecture doc, live /tv/malibu route, weather API sample call
• endpoints.api.weather → https://pointcast.xyz/api/weather?station={slug} (the new edge-cached function)
• endpoints.perStation object with html, weather, and note fields explaining the 15-station geo-channel system + keyboard shortcuts (1-9 + Q-Y)

WHAT SHIPPED

• Approved Codex's 4 write dialogs via computer-use (local.ts, weather.ts, tv.astro, [station].astro, for-agents.astro)
• Ran the build Codex couldn't: npx astro build → 227 pages (up from 212, +15 station routes)
• Deployed: https://2eacfe0e.pointcast.pages.dev
• Retro'd
• 15 station subdirectories in dist/tv/: anaheim-oc, hermosa, long-beach, los-angeles, malibu, manhattan-beach, newport-laguna, north-san-diego, palm-springs, palos-verdes, pasadena, redondo-beach, santa-barbara, santa-monica, venice
• /tv/index.html carries 21 references to STATIONS markup (stations-index / station-feed / STATION_SHORTCUTS / data-station)
• Weather function bundled in _worker.js (confirmed via wrangler output: "✨ Uploading Functions bundle")
• Build clean, 227 pages, 19s build time

WHAT SHIPPED

• The 4.5h zero-artifact stretch earlier today → root cause (Codex project wired to wrong repo) → fix via computer-use path correction
• Current STATIONS progress (4/5 checklist items shipped, weather proxy in flight)
• 5 new briefs filed (#6-10) — queue now at 10
• Codex CLI has mcp-server subcommand → programmatic integration path named in docs/setup/codex-mcp-integration.md

WHAT SHIPPED

• Brief #6 — docs/briefs/2026-04-19-codex-presence-do-upgrade.md · Identity-enriched presence DO. Carries per-visitor {nounId, mood, listening, where, kind, joinedAt} over the WS so VisitorHereStrip + /tv constellation render real nouns instead of ghost slots. ~3-4h.
• Brief #7 — docs/briefs/2026-04-19-codex-here-congregation.md · /here full-page congregation view. Responsive noun grid, mood aggregate, live arrival feed. Builds on #6. ~2-3h after #6.
• Brief #8 — docs/briefs/2026-04-19-codex-multiplayer-primitive.md · Shared DO base for Pulse + YeePlayer v1 + future games. Extracts common code (pairing, broadcast, rate-limit, auto-close) into functions/api/_multiplayer.ts. ~2-4h.
• Brief #9 — docs/briefs/2026-04-19-codex-audio-input-yeeplayer.md · Mic-input YeePlayer. Web Audio API onset detection, clap-to-tap. Local-only processing (no upload). ~3-4h.
• Brief #10 — docs/briefs/2026-04-19-codex-analytics-share-cards.md · Cloudflare Web Analytics integration + per-block OG image generator. Infra for GTM launch. Analytics Part A ~1h, share cards Part B ~3-4h.
• Path 1: Codex MCP server (recommended) — codex mcp-server starts Codex as a stdio MCP server. Add to cc's MCP config, restart session, cc sees mcp__codex__* tools. Programmatic task queuing replaces manual app-clicks.
• Path 2: Codex CLI exec (simpler) — cc runs codex exec "..." via Bash. Works today, no MCP setup. Limitation: no status polling.
• Path 3: OpenAI API direct — full control, most work, loses the Codex agent loop. Not recommended.

WHAT SHIPPED

• Title: "Identity + broadcast + daily ritual — big Sunday"
• Summary paragraph: names the six arcs (mood primitive, broadcast mode, daily ritual, 100-mile lens, identity, Codex briefs) + flags the Codex artifact shipped via computer-use-assisted workspace correction as the day's big plot beat.
• 19 highlight bullets — each one names a concrete surface/file/ship, grouped roughly by arc:
• Mood primitive (schema + atlas + filters + JSON mirror)
• /today + /today.json (daily drop + past-7-days)
• /tv broadcast mode (ambient + polls + daily + presence)
• /local + /local.json (100-mile lens + stations + GeoCircle)
• /profile dashboard (identity + state + activity)
• VisitorHereStrip + TELL panel (per-visitor noun + self-report)
• FreshStrip (badges + CAUGHT UP routing)
• MorningPara (editorial-paragraph brief)
• Five Codex briefs (Pulse / STATIONS / YeePlayer v1 / TrackLab / VideoLens)
• TodayStrip + VoterStats experiments (shipped + removed — honest)
• /for-agents + /agents.json + /blocks.json + /b/{id}.json refreshes
• Email playbook for Manus ops
• 4 fresh polls
• Release sprint plan + GTM draft
• Codex workspace-path diagnosis via computer-use
• 35+ sprint retros authored
• Links: release sprint plan, GTM draft, Block 0320 (day-recap reflection), Block 0321 (sprint announcement).

WHAT SHIPPED

• docs/reviews/2026-04-19-codex-tv-stations-architecture.md (5947 bytes, 64 lines)
• A1 rendering: SSG + client-side mode switch. Pre-compute per-station block arrays at build time into HTML/data attributes. Ship /tv/[station] as real pages for castable/bookmarkable URLs. Stays aligned with /tv's edge-cache-friendly philosophy.
• A2 state: vanilla JS finite state machine. mode (global/stations-index/station-feed), globalSlideIndex, stationSlug, stationSlideIndex, weatherByStation, paused, autoReturnDeadline, autoTourEnabled. No framework.
• A3 keys: numeric 1-9 for nearest 9 stations, Q W E R T Y for remaining 6, visually printed on the index grid. Channel-surfing metaphor.

WHAT SHIPPED

• codex-project-first — "Which Codex project ships first?" (Pulse / STATIONS / YeePlayer v1 / TrackLab / VideoLens). Meta-poll directly on the queue's status. Coordination-purpose.
• sunday-es-move — "Sunday night in El Segundo — what's the move?" (ESB / Big Mike's / Vinny's / beach walk / stay in / movie). Uses the /local name-drops vocabulary. Coordination-purpose.
• april-register — "April 2026 is asking us to…" (build / rest / connect / travel / learn / mint / pause). Zeitgeist-purpose, sibling to the existing zeitgeist-april-2026 noun poll.
• sunday-soundtrack — "The soundtrack to your Sunday night?" (rain anthem / meditation / hip-hop / folk / electronic / jazz / silence). Editorial-purpose, ties to YeePlayer existing tracks.
• If tier/bandwidth is wrong → upgrade / diagnose
• If Codex is parked → explicitly kick it off
• If briefs are blockers → cc revises them (flagged as option in docs/briefs/2026-04-19-codex-check-in.md already)
• If still nothing by Tuesday AM → cc picks up STATIONS directly as fallback (smallest brief, highest-impact for /tv, best cc-fallback candidate)

WHAT SHIPPED

WHAT SHIPPED

• profile — /profile dashboard (shipped 20:58)
• family — /family Fukunaga Hoydich roster
• today — /today daily drop
• moods — /moods tonal atlas
• local — /local 100-mile lens
• tv — /tv broadcast mode
• family — /family.json
• today — /today.json (now including todayStrip with all 6 rotating picks)
• moods — /moods.json
• local — /local.json
• presence — wss://pointcast.xyz/api/presence (the WebSocket surface PresenceBar + VisitorHereStrip + /tv constellation all consume)
• perMood — /mood/{slug} + /mood/{slug}.json with brief algorithm note
• perYeeTrack — /yee/{id} with the "WATCH-type + media.beats" gating note

WHAT SHIPPED

• Phase 1 — Identity arc (Mon, gated on Mike's 4 decisions): PC_IDENTITY_KV namespace, /api/identity/log write endpoint, localStorage mirror to server on wallet-connect, /profile fetches remote on connect.
• Phase 2 — Codex delivery (Tue-Wed): check-in Tue AM on 5 briefs; merge what lands; re-prioritize if bandwidth-constrained (STATIONS → VideoLens → Pulse → YeePlayer v1 → TrackLab).
• Phase 3 — Manus reactivation (Mon-Thu): M-1 platform matrix completion, M-2 CF Email Routing, M-3 Resend setup, M-4 launch-day ops checklist.
• Phase 4 — GTM launch (Wed-Mon 04-22 to 04-27): Farcaster → X → Product Hunt → Nouns → HN → week retro.
• Phase 5 — Measurement (ongoing).
• Positioning: "first agent-native living broadcast"
• Audience ranked: AI builders → crypto-native → local ES → Farcaster → HN
• 5 wedges each backed by a shipped surface
• 7-day launch cadence with per-day channel tactics + success criteria
• Messages that work + messages to NOT lead with
• Open questions for Mike: PH maker strategy, Farcaster handle, GIF budget, pre-launch outreach, press pitching
• M-1: platform matrix completion (in-flight from AM brief)
• M-2: CF Email Routing dashboard setup (~10 min, due Mon EOD)
• M-3: Resend account + DNS verification + PAGES secret binding (due Tue EOD)
• M-4: launch-day ops checklist — GSC, Bing, IndexNow, Farcaster/X/iMessage unfurl verification, analytics (due Thu EOD)
• One-line status in chat
• Any architecture doc (even draft)
• Honest flag on briefs that are too vague

WHAT SHIPPED

• 140px noun avatar (gold-ringed, rounded) — deterministic from pc:session hash → noun id 0-1199
• Display name — preference order: pc:visitor:display override → short wallet address → known agent UA name → noun-NNN fallback → visitor
• Metadata line: "Noun № 421 · WALLET / AGENT / HUMAN · here since Mon Apr 19, 2026"
• Hint line: active wallet short-address if present + clarifying "anonymous identity — noun id is deterministic from this browser's session"
• Chips for each set field: mood (burgundy bold caps), 🎵 now playing, 📍 where
• edit ↗ link anchors back to /#here-tell-panel so the edit action lives on home where the panel actually is
• HELLO — count + last-earned date
• drops collected — count + current streak
• polls voted — unique count (walks all pc:poll:voted:* keys)
• voter level — from pc:voter:state JSON (level, XP, title)
• polls voted list — slug + picked option, each row linking to /poll/{slug}
• drops collected list — date + block id, each row linking to /b/{id}
• Empty states point at the appropriate home surfaces

WHAT SHIPPED

• YOU label in gold caps to match the strip's YOU slot.
• Mood rendered as a rounded dark pill.
• Song truncated at 50 chars with ellipsis.
• [edit] button reopens the panel pre-populated from storage.

WHAT SHIPPED

• cheapHash(s) — DJB2-style integer hash. Stable, not cryptographic.
• getVisitorNounId(identity) — maps any identity string (session id, wallet address, UA) to a Noun ID 0-1199. Deterministic.
• getVisitorNounUrl(identity) — convenience: full noun.pics URL.
• getVisitorDisplayName({ display, wallet, ua, sessionId }) — returns short name with preference order: user-set override → short wallet form → known agent name (GPTBot, ClaudeBot, etc.) → noun-NNN fallback → visitor.
• getVisitorKind({ wallet, ua }) — classifies as 'wallet' | 'agent' | 'human'. Used for glyph/color selection.
• VISITOR_LS_KEYS — the localStorage namespace: pc:session, pc:visitor:noun, pc:visitor:firstSeenAt, pc:visitor:display.
• YOU slot — your assigned noun (32×32 → 40×40 on desktop), gold ring with gentle pulse animation, "YOU" label below. First-visit assigns the noun and caches it; pc:visitor:firstSeenAt set so future /profile can say "here since Apr 19".
• 11 ghost slots — dotted-outline circles, faint purple. Light up (warm amber dot) as presence count climbs via the same /api/presence WebSocket PresenceBar uses. Staggered pop animation when they become lit.
• Overflow slot (+N) — appears when >12 visitors connect. Hides otherwise.
• "YOUR PROFILE →" link — anchors at /profile (the existing stub page). When the full /profile dashboard lands, this becomes the direct door.

WHAT SHIPPED

• 27 ticks shipped, 5 Codex briefs filed, new broadcast mode at /tv, /local at 100-mile radius, /today daily ritual, seven-chip TodayStrip
• Then Mike's two evening critiques:
• The diagnosis: pace outran coherence. Shipping surfaces ≠ shipping a coherent experience.
• The path forward: the three-zone consolidation is skin; identity + memory + response + /profile dashboard is the skeleton that needs to go in underneath.

WHAT SHIPPED

• Term interface (same shape as before: slug, term, definition, seeAlso, canonicalUrl, category).
• GLOSSARY: Term[] — the full 26-entry array, unchanged.
• Eye: TERM in green (#0F6E56, matches Garden channel register)
• Main: the term itself (e.g. "FA2", "Card of the Day", "/manifesto")
• Sub: {CATEGORY} · /GLOSSARY (primitive / surface / chain / mechanic / channel / role)
• Target: /glossary#{slug} → deep-links to the anchor

WHAT SHIPPED

• Video metadata (title, channel, description, tags, publish date)
• Engagement (views, likes, comment count, like-ratio, velocity trend)
• Audio features (tempo, key, energy, valence, danceability, speechiness, loudness — via Spotify match OR Meyda fallback)
• Transcript (YouTube auto-captions OR AssemblyAI)
• Sentiment arc (sliding-window sentiment over transcript, peaks, overall label)
• Topics (HuggingFace zero-shot classification)
• Visual (dominant palette, brightness, scene-change rate)
• Comment sentiment (sample of ~100, positive/neutral/negative breakdown, top themes)
• PointCast has ~15 WATCH-type YouTube embeds. All of them benefit from a lens.
• TrackLab is ONE consumer; /b/{id} WATCH pages are another; future /tv slides are a third.
• Separation of concerns: TrackLab = beats; VideoLens = signal. Neither needs the other to ship.
• A1: composition strategy (single fn vs streaming vs job-based — recommend streaming).
• A2: caching (30-day KV on youtubeId, new PC_VIDEOLENS_KV namespace).
• A3: rate limiting (Mike unlimited via wallet auth, anons 3/day/IP).
• A4: partial-success handling (every field nullable, warnings array).
• A5: consumer shape (TrackLab, /b/{id} LENS chip, future /tv slide).
• functions/api/videolens/analyze.ts — main endpoint
• src/lib/videolens.ts — client helpers + types
• src/components/VideoLensPanel.astro — UI panel
• src/pages/videolens.astro — standalone demo page
• YOUTUBE_API_KEY, SPOTIFY_CLIENT_ID + SPOTIFY_CLIENT_SECRET, ASSEMBLYAI_API_KEY, HUGGINGFACE_API_KEY.

WHAT SHIPPED

• Mood: sprint-pulse (the Codex-handoff + overnight-arc tag)
• Block: 0301 "Piet Mondrian"
• Station: Redondo Beach · 6mi S
• NameDrop: Pickleball League
• Channel: CH.FD · Front Door
• Noun: 1163

WHAT SHIPPED

• Step 1: Cloudflare Email Routing (free, 5-minute setup) — enables hello@, mike@, claude@ + optional catch-all, all forwarding to mhoydich@gmail.com.
• Step 2: Outbound provider — comparison table of Resend / Postmark / Mailgun / SendGrid / AWS SES, recommends Resend. Full Resend setup including DNS (MX + SPF + DKIM), API key, Pages secret binding.
• Step 3: cc wires the functions/api/send-note.ts outbound endpoint once RESEND_API_KEY is bound (stub shape documented, not yet written).
• Step 4: End-to-end verification commands (inbound curl test, outbound curl test).
• First content-generation primitive for Codex. Projects #1-#3 are interaction primitives (game, channel-flip, multiplayer rhythm). TrackLab creates new data.
• Scales YeePlayer v1. Codex's multiplayer rhythm mode is more interesting at 20 tracks than 4. TrackLab produces the 20.
• Unblocks a cc pain point. Hand-authoring beats for each new track is editorial time that doesn't scale. TrackLab flips it.
• A1: onset-detection library (recommend Meyda — acceptable accuracy, Mike edits anyway)
• A2: YouTube audio extraction (recommend in-browser Web Audio via IFrame Player — TOS-compliant)
• A3: file-size / bandwidth math
• A4: Mike-only gate (recommend Beacon wallet check — graceful degradation for visitors)
• A5: write path for save-as-block (recommend GitHub API with scoped PAT)

WHAT SHIPPED

• Comparison to v0: what stays, what changes. Solo mode at /yee/[id] is preserved; v1 is additive.
• Mechanics: session start on /tv/yee/[blockId], QR to /play/yee/[sessionId], video sync via TV broadcasting position to DO, beat-to-tap matching authoritatively on the DO.
• Six architecture questions (A1-A6): shared DO base with Pulse, beat-match logic, video playback sync, phone color palette (use the 7 bija colors deterministically from join-order), cross-player visual feedback, track-selection flow.
• Four deliverables: DO + fetch handler, TV session page, phone controller, multiplayer HUD component.
• Linkage: solo /yee/[id] gets a "PLAY ON TV" button; /tv rotation gets a YEE slide type.
• Budget: ~3-5 hours. The most interdependent of the three Codex projects.

WHAT SHIPPED

• UX shape: three modes (global → stations-index → station-feed), transitions via keyboard (S / Esc / numbers), touch (swipe up/down), or a dedicated "STATIONS" button. Auto-return after N minutes idle.
• Filtering: permissive substring match against meta.location. Special-case for "Los Angeles" station (matches every in-radius block since LA is the county-level anchor).
• Weather per station: Open-Meteo with a Cloudflare Function proxy + 10-min edge cache recommended.
• Five architecture questions (A1-A5): SSG-with-embedded-data vs SSR, state machine, key mapping, back-to-global timeout, KV-vs-cache.default.
• Four deliverables: add coords to src/lib/local.ts STATIONS, integrate modes into src/pages/tv.astro, optional /tv/{station} dedicated URLs, functions/api/weather.ts proxy.

WHAT SHIPPED

• Game mechanics — session lifecycle, pairing flow (QR on TV → phone scans → WS to Durable Object), tap broadcast, BPM computation, end-state.
• Five architecture questions (A1-A5) Codex answers in a doc: pairing flow ephemerality, DO state shape + broadcast cadence, anti-abuse rate limits, 3m-viewing-distance TV rendering, phone UI.
• Four implementation deliverables: DO + fetch handler (functions/api/pulse.ts), TV session page (src/pages/tv/pulse.astro), phone controller (src/pages/play/pulse/[sessionId].astro), ring component.
• Linkage into the existing site: add a "PULSE" entry on /tv, /for-agents update.
• Working style: ship to main, author: 'codex', don't scope-creep, ~2-4 hour budget.

WHAT SHIPPED

WHAT SHIPPED

WHAT SHIPPED

• 10 dot slots rendered server-side in the /tv top bar. Styling defaults to muted/empty.
• Client fills them from the existing /api/presence WebSocket broadcast. Count = humans + agents. First N dots toggle to --active (warm amber, glow, pulse).
• Staggered pulse animation: each dot has its own animation-delay (0s, 0.3s, 0.6s, …) so the row twinkles like a constellation, not a uniform blink. 3-second cycle per dot, ease-in-out. Reduced-motion users see the static filled state.
• Overflow handling: if total > 10, the number shows 10+ and all dots are active. The cap prevents the row from overwhelming the top bar on genuinely busy moments.
• YOU dot is always first in the row — slightly wider (11px vs 9px), gold 1.5px border, fills to solid gold when active. Its animation continues even when alone, so the bar doesn't ever feel dead.
• Base-state paint runs before the WS connects. Shows 1 + one active YOU dot immediately on page load, so the first viewport never displays —. WS success → refines the count; WS failure → we keep the base state rather than clobbering back to em-dash.

WHAT SHIPPED

WHAT SHIPPED

• data-daily-id — today's drop block id (shared with /today + /tv via src/lib/daily's pickDailyBlock)
• data-today — today's PT date string (YYYY-MM-DD)
• Unclaimed: "Caught up on the feed. Today's drop is still waiting — tap to collect."
• Claimed: "Caught up and claimed. Tap to revisit an older block."

WHAT SHIPPED

• Shared data source: /tv imports pickDailyBlock + todayPT from src/lib/daily.ts. The TV slide and /today page agree perfectly — both select the same block via the same deterministic daySeed function. No duplication, no drift.
• Slot 0 placement: the Daily Drop is always the FIRST slide a viewer sees when /tv loads. Cast to a TV → the daily drop is the opening hero. After its 20-second dwell, the rotation continues through blocks (with poll slides at every 5th position).
• No duplication in rotation: the interleave loop skips the daily block if it would otherwise appear in the "recent blocks" rotation. One appearance per cycle, in the featured slot.
• Visual distinction: gold-gradient "✦ DAILY DROP · SUN APR 19" pill (star rotates slowly, 5s per turn), oversized 72px title (vs. 64px on regular blocks — largest title in the rotation), amber glow on the thumbnail, 120px QR (larger than block/poll QRs), and a subtle radial gradient warm glow behind the active slide.
• QR target: https://pointcast.xyz/today (not /b/{id} — the daily drop flow goes through /today's collect button so the streak/stats register).
• Dwell extended: 20 seconds (BASE_DWELL + 8000). Tied with READ blocks for the longest dwell — it's the featured thing, give viewers time to scan + decide.
• Footnote: small "ONE BLOCK A DAY · ROTATES AT MIDNIGHT PT · COLLECT ON PHONE" strip below the body. Explains the mechanic for first-time casters.

WHAT SHIPPED

• Deterministic pick. src/lib/daily.ts exports pickDailyBlock(blocks, now) — sorts the block collection by id (stable regardless of caller), then indexes by daySeed(now) = (year * 1000) + dayOfYearPT(now) mod collection size. Same day, same block, for every visitor globally. El Segundo-anchored PT calendar.
• Today's pick for the launch: day-seed 2026109 → Block 0276 — "El Segundo name-drops". Editorially on-theme for the launch of a town-local ritual. Coincidence; good one.
• Collect button. Big dark panel, gold star, "COLLECT TODAY · TAP TO CLAIM". On click: pushes {date, blockId, at} to localStorage.pc:daily:collected, plays a two-note chime (720 Hz → 900 Hz), 20ms haptic buzz, shows a gold "+1 COLLECTED" floater, pulses the whole pick card with an amber ring. On repeat-press or already-claimed states, shifts to a green "✓ COLLECTED · COME BACK TOMORROW".
• Stats row: total ever collected (across all days) + consecutive-day streak ending today. Streak-computation walks backward day-by-day from today until it finds a gap.
• Additional surfaces: thumbnail (block's own noun or media), channel chip colored by CH, mood link (if the block carries one), QR code pointing at /b/{id} for phone-side deep-read, "OPEN BLOCK →" link, "COMES NEXT" note explaining the rotation.
• Schema.org: CreativeWork JSON-LD with mainEntity → canonical block URL. dateModified set to today's PT date. Agents following the LD get today's pick programmatically.
• No server writes. /today's collect button is a localStorage operation; no Cloudflare Function, no KV, no auth.
• Trivially reversible. A visitor can clear storage and re-claim — and that's fine for v0, because HELLO is held and there's no consequence to this counter other than a personal streak.
• When Mike greenlights the Tezos path (per Block 0280's wallet ladder Rung 5), the on-site collection becomes the claim whitelist. Until then, showing up + tapping = the entire UX.

WHAT SHIPPED

• Server interleave: the /tv frontmatter now builds a unified slides[] array of { kind: 'block', block } and { kind: 'poll', poll } items. Every 5th slot (positions 5, 10, 15, 20) becomes a poll slide, punctuating the block rhythm. Top 4 non-draft polls sorted by openedAt desc. Total slide count: 24 blocks + 4 polls = 28 slides.
• Poll slide layout: same 1.4fr / 1fr column split as block slides. Left column carries a purpose-colored LIVE POLL chip (utility green, coordination blue, editorial purple, decision orange, state oxblood), the slug kicker (/poll/{slug}), the question at 48px serif (smaller than a block title to leave room for bars), the bar list (up to 6 rows, one per option), and a tiny "— votes" total footer. Right column has the QR code pointing at /poll/{slug}?via=tv and the hint text → SCAN · TAP TO VOTE.
• Live tally: when a poll slide becomes active, the client fetches /api/poll?slug={slug} and paints the bars. A 5-second setInterval refreshes while the slide stays active. On slide exit, the timer clears — so at most one poll is polling the API at a time.
• Bar animation: transition: width 0.7s cubic-bezier so percentages ease to their values instead of snapping. Leader row gets a brighter amber fill + a subtle glow.
• Dwell extension: poll slides get +6s on top of the 12s base (= 18s total). Enough time for a viewer to scan the QR, open their phone, tap an option, and see the result on the TV before advancing.
• ?via=tv tag in QR URL: so server-side tallies can later separate TV-originated votes from site-direct votes if we ever want to analyze that.
• The existing /api/poll GET works today with zero new server code.
• A 5-second refresh feels live enough for a communal-watching context (users won't notice a 3-second delay between "tapped" and "TV updated"). Real-time is overkill.
• Upgrade path is open: a DO-based tally stream is a follow-up tick that can land without any client refactor — just swap the setInterval fetch for a WebSocket handler.

WHAT SHIPPED

• Stations carry a url field. Not-yet-authored per-station pages resolve to /search?q={name} so an agent always has a follow-up URL. When real station pages ship, the resolver moves to /local/{slug}.
• In-range blocks include mood + moodUrl. So an agent doing "give me all PointCast content tagged both 'quiet' and located within 100mi of El Segundo" can intersect the two lists with no extra fetches.
• Adjacent surfaces explicit. Seven cross-links baked into the payload — saves agents from scraping HTML or path-constructing.

WHAT SHIPPED

WHAT SHIPPED

• Grid shell: 70px top bar + 1fr hero + 90px ticker. Locked to 100vh × 100vw, no scroll.
• Auto-scroll hero: rotates through the 24 most recent blocks. Base dwell 12s; READ blocks get +8s, WATCH/LISTEN get +4s. Progress bar at the top tracks the current dwell in real time.
• Top bar: POINTCAST wordmark with CAST in accent gold, LIVE · TV red-pulse pill, presence readout ("WATCHING · N"), live PT clock with seconds, today's date.
• Slide layout per block: left column has channel chip (colored by channel), №{id} · TYPE kicker, huge serif title (64px desktop / 34px mobile), 22px dek, mood chip if present; right column has the thumbnail/noun art and a QR code linking to /b/{id} for phone-side interaction.
• Ticker footer: cycles the 60 most recent titles, 160s loop, reads like a Bloomberg crawler.
• Input: spacebar pauses, arrow keys step, touch-swipe works for mirrored-phone casts. No cursor, no menu — the TV is display, the phone is controller.
• Anti-burn-in: 42s gentle drift animation on the hero container (±3px translate), ticker never stops, LIVE dot pulses — no element stays pixel-static for more than a few seconds. OLED-safe.
• Presence: reuses the existing /api/presence Durable Object WebSocket. kind=tv param added so the server can distinguish TV sessions from regular browsers if it wants to.
• BC-1: review the /tv v0 route — dwell cadence, landscape typography at 3m, presence WS bottleneck at scale, burn-in risk, screen-reader behavior. Deliverable: docs/reviews/2026-04-19-codex-tv-v0.md.
• BC-2: platform-path architecture trade-off. Answer: what's the shared core, where do interactive primitives diverge (siri remote vs D-pad vs controller vs phone), recommendation on "phone as universal controller" pattern. Deliverable: docs/reviews/2026-04-19-codex-platform-architecture.md.
• BC-3: running review of each interactive primitive as cc ships them (live polls on TV, presence overlay, mini-game v0, daily-collection tie-in).
• PM-1: build the platform matrix — Apple TV / Roku / Google TV / Android TV / Fire TV / Samsung Tizen / LG webOS / Chromecast / AirPlay / game consoles. Columns: reach, native path, web-browser quality, dev lift, cost, monetization.
• PM-2: the casting path specifically — does Airplay preserve localStorage? Does Chromecast's sender/receiver model support phone-as-controller natively?
• PM-3: vendor-neutrality scan — any platform hostile to Good Feels content? PointCast carries cannabis-adjacent links.
• PM-4: location-API realities per platform for the 100-mile-radius feature.

WHAT SHIPPED

WHAT SHIPPED

• +1 HELLO per PT calendar day on first daily visit to any page bearing the strip (home today; extensible to other surfaces).
• Stored per-browser via localStorage.pc:hello:count and localStorage.pc:hello:lastDay.
• Visible at all times as a thin gold chip in the FreshStrip: ✦ HELLO · 7.
• Rewards the moment of earning: on first-visit-of-the-day, the chip fills to solid gold, the star spins 360° + scales, a "+1 HELLO" floater rises from the chip in oxblood, a11y announces via the existing aria-live region.
• Tooltip explains: "HELLO — presence points. +1 per day for showing up. Stored in this browser."

WHAT SHIPPED

• HELLO (first-time visitor, blue dot) — "start here →" CTA to the newest block
• N NEW (returning, newer blocks exist, warm oxblood background + pulsing amber dot) — "jump in →" CTA to the newest
• CAUGHT UP (returning, no new blocks, muted slate with green dot) — "revisit →" CTA to a random block from the last 20
• Reads localStorage.pcLastVisit (ms timestamp).
• Compares to the newest block's timestamp (server-embedded in the strip's data-newest-ms attribute).
• First-time → HELLO. Newer than last visit → N NEW (initially shown as "NEW", refined to precise count by a fetch of /blocks.json which happens in parallel and updates in place). Equal or older → CAUGHT UP.
• Writes localStorage.pcLastVisit = Date.now() AFTER rendering, so the current visit doesn't overwrite its own comparison baseline.

WHAT SHIPPED

• author — the VOICE.md authorship enum (cc / mike / mh+cc / codex / manus / guest). Now agents can filter or audit by voice attribution.
• source — the provenance string when present (required for mike/mh+cc/guest, optional for others). Surfaced as null when absent, preserving stable shape.
• mood — the slug. null when untagged.
• moodUrl — convenience field; pre-computed https://pointcast.xyz/mood/{slug} or null. Lets agents pivot without string-formatting.
• companions — the cross-link graph, surfaced as empty array [] when absent. Agents doing graph traversal now have the edges in the canonical feed.

WHAT SHIPPED

• $schema self-reference (handy for agents that catalog endpoints)
• generatedAt ISO timestamp
• 300s Cache-Control with Access-Control-Allow-Origin: *
• Stable field names; null over omit where a field is conceptually present but empty

WHAT SHIPPED

WHAT SHIPPED

• rainy-week · 4 entries (4B) — the set from sprint mood-primitive
• spirit · 1 entry (1G) — existing gallery mood
• quiet · 1 entry (1G) — existing gallery mood
• current-state · 1 entry (1G) — existing gallery mood (note: this one WANTS a matching block companion later — 0275's current-state framing is a natural cross-link)
• grounded · 1 entry (1G) — existing gallery mood

WHAT SHIPPED

• 0262 (Alan Watts · guided meditation)
• 0263 (November Rain · Guns N' Roses)
• 0264 (Purple Rain · Prince)
• 0275 (Wild Mountain Honey · a Mike playlist)

WHAT SHIPPED

WHAT SHIPPED

• src/lib/briefs.ts — import.meta.glob reader, pulls H1 as title, detects assignee from filename (codex / manus / cc / mixed), counts ## Task headers for task count, extracts one-line lede from the first non-meta paragraph, looks for status: complete marker anywhere in the body.
• /briefs page — groups by assignee. Codex section has blue accents (role: atomic review tasks, one PR per task). Manus section has orange (role: Cloudflare dashboard / DNS / GSC / IndexNow / objkt / social — anything behind a login). cc-internal section has purple. Each card: date, task count, COMPLETE chip when marked, title, lede, link to the raw GitHub file. "HOW THE HANDOFF WORKS" 4-step at the bottom.
• Stats strip: total briefs / total tasks / for-codex count / for-manus count — fed from the existing docs/briefs/ files (7 today).
• Agent adoption path: Codex reads /briefs, picks a task, opens a PR, tags Mike. Manus reads /briefs, runs the ops work, posts a screenshot in the recap. Status signal: append status: complete to the brief body → cc picks it up next build → COMPLETE chip renders.
• gallery content collection in src/content.config.ts. Schema: slug, title, imageUrl (relative or absolute), optional promptSummary (≤280), tool (midjourney/ideogram/sora/runway/nouns/other), optional mood (slug — feeds future /mood/{slug}), createdAt, author (default mike), source, draft.
• /gallery page — responsive grid of square tiles (minmax 220px), tap to open full-screen lightbox. Arrow keys + swipe navigate. ESC closes. a or ▶ toggles autoplay (6s/frame). Counter + caption (title, tool chip, mood, prompt summary, creation date).
• Four CC0 Noun seeds (noun.pics, licensed per nouns.wtf) at /content/gallery/noun-{0101, 0222, 0404, 0888}.json — proves the mechanics while empty of MJ. Mike adds real MJ via /drop or PR; new entries sort to top by createdAt.
• Authoring docs at src/content/gallery/_README.md — minimum shape + workflow ("drop URL → next tick files it → rendered").
• Discovery wiring: /briefs + /gallery added to agents.json human-endpoints map + home footer.
• Two build glitches caught mid-sprint: (1) gallery defineCollection silently dropped from the schema file — re-applied inline right before the export. (2) Caught via astro sync GenerateContentTypesError; fixed with a fresh .astro cache clear + re-land.

WHAT SHIPPED

• Block schema gains optional companions: Array<{id, label, surface?}> (max 8).
• /b/[id].astro renders a COMPANIONS strip when present — purple-accented, surface-colored chips (YEE/POLL/BLOCK/EXT).
• Block 0275 tagged with four /yee companions (Alan Watts, November Rain, Purple Rain, Chakra tune-up) — delivers the Q2 #1 default commitment: "Also playable on /yee cross-link chip".
• Bug caught mid-sprint: schema edit got silently reverted between ticks (auto-linter or editor sync). Re-applied, rebuilt, verified 0275 now shows all four /yee links in the companions strip.
• Per Block 0274 commitment: "if /poll/drum-rebuild-direction has no votes within 24h, cc defaults to Option A." Poll had no votes through the 10pm window.
• CSS-only changes to src/pages/drum.astro style block:
• 44×44 iOS tap-target floor on mobile (72×72 wrappers, 64×64 image minimums).
• Stronger press feedback via drop-shadow pulse on .drum-btn:active + .drum-tapped.
• Mid-width (641-900px) wrap fix so drums 4 + 5 don't squeeze against the edge.
• Desktop hover ring on badges so locked/earned states read as tappable rather than decorative.
• Ripple +1 fly-offs slightly larger on desktop (1.1rem).
• Zero mechanic changes. All 5 drums, counters, presence, audio, milestones, ripples — untouched.
• Sprint card drum-visual-refresh graduated to done.
• Mike's directive: make PointCast feel locally-rooted via real institution names. His verbatim list: "el segundo brewing, recreation park, pickleball league, standard station, big mikes, vinnys, gingers".
• Block 0276 (CH.ESC, mh+cc) — editorial frame: the list is a vocabulary, not a review. Naming these correctly in the right sentence is how a site sounds like the town.
• /poll/es-name-drops — Schelling-point editorial poll with the 6 places Mike named. outcomeAction: "Leader earns a dedicated /b/{id} block — cc-voice editorial profile with a visit writeup + /beacon cross-reference. Top-2 become candidates for a /local index page."
• Block 0276 has its own companions entries (the poll + /b/0254 + /beacon) to demonstrate the field working across block types.
• "Sasual" in Mike's list read as a typo. Omitted from poll options pending clarification; documented in the poll's source field so future cc knows.

WHAT SHIPPED

• Block 0274 (/b/0274) — cc-voice editorial (author=mh+cc, source cites the /sprint pick key) walking through all four options with tradeoffs:
• A · Visual refresh (~40 min) — CSS-only, keep every mechanic, tighter mobile, lowest risk.
• B · Game-ify (~75 min) — YeePlayer-style beat track layered on cookie-clicker mode.
• C · Room / jam (~120+ min) — multiplayer drum room with cursors, combined pattern via stubbed Presence DO.
• D · Token wiring (~60 min) — Claim DRUM button to FA1.2 contract; blocked on Mike's SmartPy compile.
• Poll: /poll/drum-rebuild-direction — Schelling-flavored editorial poll with the 4 options. purpose: 'editorial', outcomeAction names the concrete routing ("leader graduates from needs-input to ready in src/lib/sprints.ts within 24 hours").
• 4 new sprint cards added to the backlog as needs-input, each with needs pointing back to the poll OR a direct Mike /ping override.
• Queued pick deleted from KV after processing (the directive was processed by being scoped — the rebuild itself awaits the poll).

WHAT SHIPPED

• functions/api/feedback.ts extended — now accepts optional blockId field (4-digit string, ≤16 chars). Relaxed the "message required" gate so mood-only posts are valid (buttons without typed text). Email subject + body include the block id when present for fast grouping in Mike's inbox.
• FeedbackStrip.astro component — dashed-red-border strip below the block nav on every /b/{id} page. Three reaction buttons: RESONATED (green ✓) / CONFUSED (amber ?) / MISSED (rose ✗). Optional 280-char one-liner behind a + add a line disclosure. Kicker reads "FEEDBACK · PRIVATE TO MIKE · one tap, optional line" so the privacy commitment is visible at the surface.
• Wired into src/pages/b/[id].astro — renders between the related-blocks nav and the machine-readable strip. Every block page now has the feedback surface.
• localStorage dedup per browser per block (pc:fb:{id}) — if you've reacted on a block before, the UI paints the prior button as "voted" and says "you reacted: X · tap again to update". Server still accepts repeat submits (rate-limited to 5/min/IP via the existing feedback rate limit).
• Smoke-tested — POSTed a mood-only reaction with blockId=0273, got {ok:true}. The /admin/feedback viewer (already built) will group these by blockId for Mike.

WHAT SHIPPED

• 3 queued PICKs: feedback-block-strip (oldest), plus two custom directives — "yah polls on the home page" and "can you rebuild drum"
• 1 ping (the original 9:37pm @mike, already handled, kept for archive)
• 0 drops
• Purpose chip (color-coded coordination/utility/editorial/decision)
• Question (3-line clamp)
• Live leader tally — client-side fetch to /api/poll?slug=…, paints "LEADER · {label} · {pct}% OF {N} VOTES" or "0 VOTES · BE THE FIRST" if empty
• Purple "▶ VOTE" CTA → jumps to /poll/{slug} for the actual vote UI

WHAT SHIPPED

• New required field purpose: 'coordination' | 'utility' | 'editorial' | 'decision' (defaults to coordination).
• New optional field outcomeAction: string (≤280 chars) — one sentence describing what literally happens when the leader is decided.
• Inline doc comments cite the Mike directive + the "if the leader changes, what happens differently?" test.
• el-segundo-meeting-spot → coordination · "If a leader emerges (35%+ of votes), cc proposes the spot as default for spontaneous meetups."
• pick-a-chakra → editorial · "Leader becomes featured chakra on /yee/0236 next time."
• first-channel → editorial · "Top-2 channels get promoted in MorningBrief and FreshDeck weighting."
• south-bay-sunset → utility · "Leader becomes recommended sunset perch in a future CH.ESC editorial block."
• next-sprint → editorial · "Top-2 picks graduate from needs-input to ready in the backlog."
• weekday-pickleball → decision · "If converges with 40%+, the pickleball drop-in becomes a real standing event."
• Aggregate viz strip at the top: 4 metrics — POLLS LIVE / TOTAL VOTES / MOST ACTIVE / PURPOSE MIX (segmented colored bar). Client-side fetch sums every poll's tally, paints in. First time PointCast has cross-poll viz.
• Polls philosophy <details> callout under the viz strip — "WHAT MAKES A GOOD POINTCAST POLL" with the four-purpose definition list and the test sentence ("if the leader changes, what happens differently?").
• Purpose chip on each poll card — color-coded (coordination=blue, utility=green, editorial=purple, decision=orange).
• Outcome callout inline on each card — small purple-bordered "OUTCOME · {sentence}" panel, makes the downstream-use commitment visible to anyone scanning.
• Build glitch caught + fixed mid-sprint: p.data.purpose.toUpperCase() failed when Astro picked up old draft poll data before purpose default kicked in. Replaced with (p.data.purpose || 'coordination').toUpperCase() for safe access.

WHAT SHIPPED

• 1 queued PICK (feedback-block-strip)
• 2 pings (the original 9:37pm one already handled, plus a NEW anonymous one timestamped 00:17Z)
• /yee/0262 Alan Watts · Awakening The Mind — 12 meditation cues spaced 60-120s (ARRIVE, BREATHE IN, SOFTEN, LISTEN, PRESENT, RELEASE, WATCH, QUIET, FLOW, BEYOND, RETURN, THANK). Color-coded toward calm greens/blues with chakra-color accents on the deeper-pause cues.
• /yee/0263 Guns N' Roses · November Rain — 14 section markers across the 9:17 structure (PIANO IN, TURN, AROUND, RAIN, VERSE 2, WAIT, CHORUS, SLASH 1, BRIDGE, WEDDING, SOLO 2, STORM, RAIN AGAIN, OUT). Section names, not lyrics.
• /yee/0264 Prince · Purple Rain — 8 section markers (INTRO, VERSE, PURPLE, RAIN, VERSE 2, CHORUS, SOLO, OUTRO). Sparser pacing for the live-version length variance.

WHAT SHIPPED

• 5 new seed polls in src/content/polls/:
• pick-a-chakra — 7 chakra options with bija mantras + colors. Cross-references /yee/0236.
• first-channel — 7-of-9 PointCast channels. Onboarding signal.
• south-bay-sunset — 5 sunset perches between LAX and Palos Verdes. Local Schelling.
• next-sprint — 5 backlog candidates needing Mike review. Vote literally routes the autonomous loop.
• weekday-pickleball — Mon-Fri morning drop-in coordination. If converges, becomes a real meetup.
• /polls catalog now shows live tallies per card. Each card fetches /api/poll?slug=… client-side after page load, paints:
• "N VOTES" indicator (top-right of card, purple+bold when N>0)
• "LEADER · {label} · {pct}%" line at the bottom (only when there are votes)
• Card layout reorganized into top + bottom rows to accommodate the new chrome.
• Schema-org Question JSON-LD per poll already in place from v1 — agents that crawl the catalog see all options as suggestedAnswer.
• Sprint card more-polls-v1 added as done. Shifts the polls primitive from "one demo" to "small cluster" in one tick.

WHAT SHIPPED

• /api/ping payload extended with optional expand: boolean field. Stored in KV metadata + body. POST response now includes expand: true and a different note ("Topic received. Claude Code drafts + publishes as a block on the next tick.") when the flag is set.
• /ping form gains a purple-bordered "Topic — expand and publish" checkbox above the wallet-sign block. Default off — pings stay private. Status message on success becomes "Topic queued for expansion. cc drafts + publishes a block on the next tick."
• CSS for .expand block added to /ping page styles.
• AGENTS.md updated with the topic-expand processing rule for cc — when an /api/ping entry has expand: true, cc reads, drafts in cc-voice editorial (NOT Mike-voice), picks channel + type, sets author: 'mh+cc' (or 'cc'), source pointing back to the ping key, ships, deletes the processed ping. One ping → one block.
• Sprint card topic-expand-publish added to backlog as done. Status field documented.
• Block 0273 published as the meta-demo: cc-voice editorial expansion of Mike's exact chat message, author mh+cc, source field cites the chat exchange. The block is itself the round-trip the message describes.
• Smoke-tested end-to-end: POST with expand: true returned the new note string + expand: true in the response. Verified key in KV, then deleted the smoke entry.

WHAT SHIPPED

• PC_POLLS_KV namespace created + bound via wrangler CLI (id 7a49bba243c346068d9440122f79c4f1). Added to wrangler.toml with 180-day retention note.
• polls content collection in src/content.config.ts. Schema: slug, question (8-280 chars), 3-7 options (id + label + optional hint), dek, openedAt, closesAt, anonymous flag, author/source per VOICE.md.
• functions/api/poll.ts — POST vote (per-address dedup OR UA+IP fingerprint dedup) + GET tally (?slug=...) + GET protocol doc. KV layout: tally:{slug}:{optionId} for counts, voted:{slug}:{voterKey} for dedup with 180-day TTL. Returns 409 with the prior vote if a voter tries to revote.
• /polls catalog page — green-purple Schelling palette, "How it works" 4-step, machine-readable strip.
• /poll/[slug] — single poll page with vote UI. Tap an option, lock in the pick, see live distribution as bars (relative-to-leader scaling). Leader option highlighted in lavender. Voted option double-bordered. Distribution refreshes from /api/poll?slug=... after vote. Schema.org Question JSON-LD with all options as suggestedAnswer.
• localStorage vote-stick: voted? pc:poll:voted:{slug} remembers; UI loads pre-locked next time.
• Seed poll: el-segundo-meeting-spot — 5 options (Old Town Music Hall, El Segundo Beach pier, The Point, Smoky Hollow brewery, Library lawn). Classic Schelling coordination — meet someone in El Segundo with no other context, pick where they'll go too.
• OG card for /polls (purple ⊜ glyph).
• Discovery wired: /polls + /poll/[slug] in agents.json (human + json + api), home footer.
• Smoke-tested end-to-end: POST vote returned count: 1, GET tally returned total: 1, tally: {old-town-music-hall: 1}. Working.
• Mike's queued pick pick:...:shelling-point-poll deleted from KV after processing.

WHAT SHIPPED

• src/components/FreshDeck.astro — new component. Server renders only an empty placeholder (<aside hidden>); client JS waits for DOMContentLoaded, queries .grid .block-card[data-id], picks 3 random via partial Fisher-Yates, clones them with cloneNode(true), strips grid-span classes so they flow in the deck row, appends to the placeholder, and unhides. Zero extra fetch — uses the BlockCards already in the DOM.
• Inserted into src/pages/index.astro between MorningBrief and the channels chip bar. So the home now reads: masthead → MorningBrief → FreshDeck (3 random) → channels nav → HomeMajors → main grid.
• Mobile stacks single-column with the same airier vertical gap as the home grid mobile lighten. Sub-text "· 3 RANDOM PICKS · TAP TO READ" hides under 540px.
• Green left-border accent distinguishes the deck visually from the regular feed without screaming.

WHAT SHIPPED

• Three KV namespaces created via npx wrangler kv namespace create:
• PC_PING_KV → id adb2efa1fecb460d896a99f5a2a35fc8
• PC_QUEUE_KV → id 9f34cfebb2404343a008f999e08064e8
• PC_DROP_KV → id d4bf332ab3564664942970641e1e2aca
• Bindings added to wrangler.toml with comments + retention notes (90/30/60 days). The [[kv_namespaces]] mechanism in wrangler.toml is honored by Cloudflare Pages on the next deploy — no dashboard click required.
• Build + deploy via npx wrangler pages deploy dist. New deploy b86e3c9e. All three /api/{service} GET endpoints now return "kvBound": true.
• Smoke tests passed end-to-end:
• POST /api/ping with Mike's actual blocked message (the one from the 9:37pm screenshot) → 200, key ping:2026-04-18T21:37:00-08:00:9ad8bc52. His "hola / shelling points, feedback, emoji interactions, check-ins" note now lives in the real inbox in addition to /b/0272.
• POST /api/queue with a custom test directive → 200, key pick:2026-04-18T17:11:30-08:00:custom-735180ec.
• POST /api/drop with https://shop.getgoodfeels.com test URL → 200, key drop:2026-04-18T17:11:31-08:00:e409a391.
• Listing endpoints verified: GET /api/ping?action=list returns the message, GET /api/queue?action=list returns the pick. Loop is fully wired end-to-end.

WHAT SHIPPED

• 79 of 90 block files patched. Inserted "author": "cc" at the canonical schema position (after visitor, before meta). 11 files were skipped — those already carried explicit author fields from this morning's voice-audit (or the morning Mike-attributed footwork note 0270, or the cc-attributed 0271).
• Stable field order via a Node script that read each JSON, checked for existing author, and rewrote the file with a defined FIELD_ORDER so author lands consistently across the catalog. Field order: id, channel, type, title, dek, body, timestamp, size, noun, edition, media, external, readingTime, visitor, author, source, meta, draft.
• Schema validates cleanly — npx astro build produced 159 pages with zero warnings on the touched files. All 79 patched blocks now satisfy the VOICE.md author/source rule both implicitly (default=cc) and explicitly (the field is present in the JSON).

WHAT SHIPPED

• /subscribe agent-feeds dl expanded from 4 to 10 entries:
• DISCOVERY, SUMMARY, CANONICAL, STRIPPED — kept (existing).
• LIVE STATE — /now.json (60s cache, current state).
• WORK LOG — /sprints.json (autonomous sprint history, updates each cron tick).
• TEAM — /collabs.json (collaborators registry + 3-step federation spec).
• SHOP — /products.json (Good Feels SEO scaffold with schema.org Product).
• CONTROL — /sprint.json + reference to POSTing picks to /api/queue.
• INBOX — POST /api/ping (messages) + POST /api/drop (URLs).
• Three-tier footer note under the agent-feeds list:
• CSS for .agent-feeds__footer — dashed top rule, ink-soft body, accent on the italic phrase.
• Sprint backlog updated: subscribe-page-refresh now status: 'done'. The 1:11 refill's middle item shipped.

WHAT SHIPPED

• Four new endpoint entries added to the endpoint list on /for-agents, immediately after the existing /ping line:
• /sprint + /sprint.json + /api/queue (one-click directive picker)
• /sprints + /sprints.json (autonomous work log)
• /drop + /api/drop (paste-a-URL inbox with live URL classification)
• /products + /products.json + /products/{slug} (Good Feels SEO foothold)
• New <section> "Autonomous loop" between the endpoint list and the existing "Agent mode" section. Contents:
• One-paragraph lede: cc runs an hourly cron at minute :11 when REPL is idle.
• 5-step explainer: read inputs (queue + inbox + KV) → execute or substitute → ship safely → recap → idle.
• Safety-rail callout: schema-breaking changes, brand claims, false-Mike-voice, real-money txns, contract origination, permission grants — all held for Mike review.
• Footnote: CronCreate is session-only, 7-day auto-expire; if session dies, Mike chat-ticks once and the loop re-registers.
• CSS for the new .section__steps ordered list — gridded, ink-soft color, code/link styling consistent with the rest of the page.
• Sprint backlog updated: for-agents-page-refresh now status: 'done'. The 1:11 health-check refilled the backlog with three ready sprints; this is the first of those three.

WHAT SHIPPED

• Site health curls (6/6 pages 200): /, /sprint, /sprints, /products, /yee/0236, /b/0271. Live + healthy.
• R4-1 voice-audit grep (zero violations): the for f in src/content/blocks/*.json; jq author/source check from docs/briefs/2026-04-18-codex-round-4.md returns no violations. VOICE.md schema enforcement is working — every block in the catalog with author != cc has a source field.
• Backlog refilled with three new safe ready sprints so future ticks don't keep falling through to substitutes:
• for-agents-page-refresh (15m) — sweep /for-agents for v3 surface coverage.
• subscribe-page-refresh (12m) — cover new feed surfaces.
• block-author-backfill (20m) — explicit author: 'cc' on every legacy block file.

WHAT SHIPPED

• public/llms-full.txt — Quick index expanded. Added a "v3 surfaces (added 2026-04-17 → 2026-04-18)" subsection listing all 12 new pages + their JSON/API siblings. LLMs that pull the full surface now see /mesh, /yee, /dao, /yield, /publish, /beacon, /ai-stack, /collabs, /ping, /sprint, /sprints, /drop, /products in the index.
• public/llms-full.txt — new "Voice attribution" subsection. Documents the VOICE.md rule (default author: 'cc', mike byline requires source, Codex enforces) so any LLM citing PointCast knows the attribution gradient.
• public/llms-full.txt — new "Autonomous loop" section before "Last updated". Documents the hourly cron tick pattern: minute :11, reads docs/queue + docs/inbox + /api/queue, ships safely, recaps to docs/sprints/, idles. The doc is the LLM-facing explanation of why /sprint and /ping exist and how /sprints accumulates.
• Block 0271 (CH.FD READ) — clearly cc-attributed editorial summary of the autonomous loop's first morning. Five cron ticks, six sprints (one chat-driven), ~108 minutes. Documents what the loop will and won't do without Mike. Source field: "cc editorial recap of the autonomous loop's first morning, written during the 12:11 cron tick on 2026-04-18."
• Sprint backlog updated. check-in-primitive moved from ready → needs-input with explicit need: "Mike review on extending BLOCKS.md type enum from 8 to 9 types — schema-breaking change. DAO PC-0006 candidate." llms-full-refresh added as done.

WHAT SHIPPED

• src/lib/sprint-recap.ts — build-time reader of docs/sprints/*.md. Hand-rolled YAML frontmatter parser (no new dependency) + section extractor that splits markdown by ## Heading into a keyed map. Returns SprintRecap[] newest-first, plus a summary() helper aggregating count, total minutes, by-trigger and by-status counts.
• /sprints page — renders all recaps with: title (from H1), trigger pill (cron/chat/ping/queue), firedAt time in PT, duration, status pill, sprintId. "What shipped" expanded by default. "What didn't", "Follow-ups", "Notes" collapsed under <details> summary toggles. Mobile-friendly — single column, big tap targets on the toggles.
• /sprints.json — machine mirror, same data shape, CORS-open, 60-sec cache.
• OG card for /sprints (green accent matching /sprint).
• Discovery wiring: /sprints + /sprints.json added to agents.json (human + json) + home footer.
• Self-referential closure: /sprints renders this very recap as the newest entry the moment it deploys.

WHAT SHIPPED

• docs/briefs/2026-04-18-manus-kv.md — 3 atomic Cloudflare KV bindings: PC_PING_KV, PC_QUEUE_KV, PC_DROP_KV. Each task includes step-by-step Cloudflare dashboard navigation, curl smoke test, expected response, and a deliverable (screenshot + verification curl). Once Manus completes these, /sprint + /ping + /drop all stop returning 503 fallbacks and Mike can drive cc from his phone without committing repo files.
• docs/briefs/2026-04-18-codex-round-4.md — 5 atomic review tasks for Codex covering the morning's autonomous sprints:
• R4-1 Voice audit catalog grep (verify zero violations post voice-audit sprint).
• R4-2 /products schema.org sanity + Rich Results validation.
• R4-3 /sprint + /api/queue end-to-end pick flow walkthrough.
• R4-4 Mobile compact mode regression check (375px / 1024px / 1440px snapshots).
• R4-5 /drop URL classifier client/server parity test.
• Pre-existing brief noted: docs/briefs/2026-04-18-codex-voice.md (4 atomic V-tasks for VOICE.md enforcement) shipped in the voice-audit sprint earlier this morning.

WHAT SHIPPED

• BlockCard.astro mobile compact mode (@media (max-width: 639px)):
• Hide .block-card__body and .block-card__preview on grid mode (NOT on detail mode at /b/{id}). Title + dek + meta becomes the glance; tap to read body.
• Tighter card padding: 12px 14px (was default).
• Smaller noun illustration: 36×36 (was default ~44×44).
• Subtle → after the title on READ/NOTE/LINK/VISIT cards as a "more inside" hint, channel-colored.
• WATCH/LISTEN/MINT/FAUCET cards untouched — their facade chip IS the glance.
• index.astro grid spacing (@media (max-width: 639px)):
• Vertical gap: 16px (was 12px). Horizontal moot at single column.
• grid-auto-rows: minmax(120px, auto) — smaller floor since bodies are gone.
• MorningBrief.astro mobile (@media (max-width: 540px)):
• Bottom row becomes a horizontal-scroll strip (no wrap) with a thin scrollbar.
• Tap targets: 36px min-height, 7px×10px padding (was 3px×7px).
• Labels visible again (was hidden at this breakpoint — bigger targets gave the room back).
• Brief container itself gets 10px×12px padding for breathing room.

WHAT SHIPPED

• Schema: new products content collection in src/content.config.ts. Required: slug, name, description, url, addedAt. Defaults: brand=Good Feels, currency=USD, availability=in-stock, author=cc. VOICE.md rules apply (mike attribution requires source).
• /products catalog page. Renders an onboarding state when the catalog is empty (currently the case). Once products land, renders by category with hero image, price, availability tag.
• /products/[slug] per-product detail page. Schema.org Product top-level JSON-LD, gallery, facts strip (price/availability/category/effects/ingredients), big CTA → shop.getgoodfeels.com. Disclaimer: "POINTCAST DOES NOT SELL OR FULFILL".
• /products.json — machine mirror. Per-product schema.org Product blocks embedded inline so any agent can lift one entry without re-fetching the page.
• OG card for /products via scripts/generate-og-images.mjs. Pink-magenta accent matching the GF channel palette.
• src/content/products/_README.md documenting authoring conventions.
• Discovery wiring: /products added to agents.json (human + json), home footer, /sprint backlog marked done.

WHAT SHIPPED

• Schema change: added top-level author (enum: cc | mike | mh+cc | codex | manus | guest, defaults to cc) and source (optional string) to the block schema in src/content.config.ts.
• VOICE.md at repo root — formal rule: default cc; any block attributed to mike MUST include a source field pointing to Mike's actual words or directive. Codex enforces in PR review. AGENTS.md already references the inbox-on-session-start ritual; VOICE check is the parallel structural protection.
• 9 blocks audited and rewritten or retired:
• 0250 (YeePlayer launch) — rewritten as cc voice, removed ambiguous "I'm testing" framing.
• 0255 (AI stack) — rewritten as cc editorial, removed invented Mike-voice tool preferences.
• 0257 (4-corners dink drill) — rewritten as cc summary of widely-taught textbook drill, removed invented Mike personal-practice claims.
• 0258 (tide pools at 5am) — retired (draft: true). cc invented the experience; no Mike source.
• 0259 (jacaranda week) — rewritten as cc seasonal note, removed first-person framing.
• 0265 (coffee/jays/jasmine) — retired (draft: true). cc invented sensory observation.
• 0266 (shop opens at 9) — retired (draft: true). cc invented shop tasks.
• 0267 (morning rotation) — rewritten as cc editorial suggestion, not Mike's actual playlist.
• 0269 (Saturday match day) — retired (draft: true). cc invented Maria's third-shot scouting report. Schedule itself preserved in 0270 (Mike-sourced).
• 0270 schema cleanup — promoted meta.author/source to top-level author/source (Mike + chat 2026-04-18 mid-morning).
• Codex brief at docs/briefs/2026-04-18-codex-voice.md — 4 atomic tasks: full-catalog grep audit, CI gate, light voice review pass, doc-cross-references.