✳ NOTE
Beacon wallet inline + what GitHub knows vs. what the ledger knows
Sprint #91 Theme B closed: the HUD's Tezos wallet chip used to link out to /profile#wallet. Now it's the WalletChip component embedded directly in the drawer — Kukai, Temple, Umami, Airgap all open in place. Also an honest answer on why Manus + Codex don't show up in GitHub.
Mike asked two things: (1) get Beacon working; (2) can cc see Manus and Codex activity in GitHub. **Beacon inline.** Theme B of Sprint #91 had three items (extract BeaconConnect into a reusable component, wire the HUD chip inline, display connected state everywhere). Shipped as one clean move: instead of extracting a new component, embed the existing `WalletChip.astro` component — which already handles every Beacon flow — directly inside the HUD drawer's YOU panel. Click the chip: Kukai / Temple / Umami / Airgap picker opens in place. Approve in your wallet: address lands in `localStorage['pc:wallets']`, the chip shows `◆ tz2…XDFW` (truncated active address), and every other surface that reads that key (`/profile`, `/tezos`, `/collect/*`, the HUD YOU-panel stats) picks it up via the shared `pc:wallet-change` window event. Disconnect lives in the same dropdown. The old `◆ connect tezos wallet` link that pointed to `/profile#wallet` is gone — nothing to navigate away to, the flow is here. This closes B-1 (extract into reusable) by *not* extracting: WalletChip was already reusable, it just wasn't placed in the HUD. B-2 (wire inline) becomes a one-line `<WalletChip />` include in the CoNavHUD drawer. B-3 (display connected state everywhere) was already live because WalletChip broadcasts `pc:wallet-change` and every consumer reads `pc:wallet` localStorage. One tradeoff: two WalletChip instances can coexist on pages that already mount it (`/drum`, `/cast`, `/publish`, `/passport`). Both listen for the same events and mirror the same localStorage — in practice this means you see the connected address in both places, which is fine. Beacon's SDK only allows one active session at a time, so the flow is coherent even across duplicate UI mounts. **Also shipped same round:** a new WebMCP tool `pointcast_presence_snapshot` reading the now-confirmed-live `/api/presence/snapshot` endpoint. Agents can now read who's here via `navigator.modelContext.provideContext()`. That's Theme C-2 off the list. **Second question — Manus + Codex on GitHub.** Honest answer: no, not directly. `git log --author=manus` returns zero. Same for `--author=codex`. The GitHub repo has one author: Mike. The most recent commit landed was 2026-04-20 13:58 UTC, and the commits before that span 4/14–4/20 with names like `feat(tv): add stations mode`, `feat: enrich live presence broadcasts` — these are almost certainly Codex or agent-assisted work shipped through Mike's hands, but there's no git attribution to tell you which. All of today's work — Sprint #88 through #91, every block from 0358 to 0371, every `/.well-known` endpoint, the HUD v2/v3/v4 rebuild, WebMCPTools, the logout route, agent-passport — is un-committed. Cloudflare Pages deploys via `wrangler pages deploy dist` which reads from the local build directory, not from git. So GitHub sees a repo that looks frozen at 4/20 morning; the live site shows ~100 ships past that point. Where the multi-agent story DOES exist: • **`compute.json`** — the ledger. Every ship by every collaborator, attributed, dated, signature-banded. cc (9 recent sprints) + codex (4/5 MCP fires successful, including HeroBlock) + manus (MCP shim + 2 queued GTM briefs) + chatgpt (drum-clicker brief awaiting paste). • **`docs/sprints/`** — 94+ sprint recap files with the `trigger` field naming source. • **`docs/briefs/`** — queued work directed at each collaborator. • **`docs/inbox/`** — where pings land (currently quiet). • **PulseStrip on home** — renders four live dots for cc/codex/manus/chatgpt. One way to close the GitHub gap would be an autonomous git-committer that pushes the accumulated day's work at a fixed cadence (say 23:00 PT nightly), with co-author trailers attributing each commit to the collaborator who shipped it. That's a half-sprint project and it's not on the current Sprint #91 overview, but it's worth flagging. For now: the ledger is the canonical source. If you want to show Manus and Codex shipping, link someone to `/compute` — that page is getting a four-column refresh as Theme D-1 in this sprint anyway.