> For the complete documentation index, see [llms.txt](https://jordan-7.gitbook.io/jordan-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://jordan-7.gitbook.io/jordan-docs/internal/run-b-verification/outstanding.md). # Outstanding Every known-broken item, open decision and deferred thing, reconciled against `OPEN-ISSUES.md` entry by entry (every `###` heading and every "open" bullet there was read for this page). Each row says where it is blocked and what would unblock it. Items that `OPEN-ISSUES.md` records as RESOLVED, RETRACTED or SUPERSEDED are not repeated here; the [work history](/jordan-docs/internal/run-b-verification/work-history.md) carries them. Blocked-on codes: **owner** (a credential, an account, a dashboard toggle, a decision), **broadcast** (needs a real stream with the operator present), **engineering** (nothing external needed), **decision** (a product call). ## On the owner | Id | Item | Where it is blocked | What unblocks it | Source | | --- | -------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------- | -------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | | O1 | **CLOSED 2026-09-16 (Pass C).** Run against the production volume over `railway ssh`, report mode then `--write`: both printed "Nothing to migrate — no guest list at /data/guest-whitelist.json". The store has never been written on prod, so nothing was pinned and nothing was unresolvable; the volume was byte-identical afterwards. Any entry added from now on pins `identityKey` at add time. | — | — | `_migrate-whitelist-identity.mjs`; [Guest whitelist](/jordan-docs/features/features/guest-whitelist.md) | | O2 | **CLOSED — verified 2026-09-16 (Pass C).** `BOUNTY_ADMIN_KEY` IS set on the production service (`railway variables`, names only). `OPEN-ISSUES.md` still records it as unset, which was true when written and is not now. | — | — | `OPEN-ISSUES.md` (stale); Railway service variables | | O3 | Configure LiveKit Cloud webhooks (`participant_joined`, `participant_left` → `/api/livekit/webhook`); the burn breaker meters zero and is inert without them | owner | Cloud dashboard step | `OPEN-ISSUES.md` L3 (2026-07-25); real delivery was verified once on 2026-07-26 — confirm the setting still holds. Also N11 (2026-10-23): a Call in campaign counts nothing without them | | O4 | Confirm Railway's app-sleep toggle is OFF; a slept container drops `participant_left` and leaves sessions open in the breaker's ledger | owner | dashboard check | `OPEN-ISSUES.md` L7 | | O5 | Paste a real `OPS_ALERT_WEBHOOK` and fire `POST /api/livekit/burn/test-alert` | owner | one variable, one request | `OPEN-ISSUES.md`, 07-27 "Owner-blocked" | | O6 | Decide the sub-3 s residual (options written) | decision | the owner's call | `docs/decisions/sub3s-residual.md`; `OPEN-ISSUES.md` P2 | | O7 | Decide whether MegaChat wants coin-keyed (pump.fun mint) payouts at all | decision | product call | `OPEN-ISSUES.md`, "pump.fun ownership is unsolved" (3) | | O8 | Decide the two `.claude/worktrees/` scratch branches (one commit ahead each), and the stash `f7219f416b99e59e9188b1cf1e9a988fa6e6fc73` that is not mine | owner | inspect, then keep or drop | `OPEN-ISSUES.md`, "STASHED EDITS" | | O9 | The bounty admin `/bounty/admin` and its policy table are behind the flag; before any public flag-on, O2 and the retest checklist | owner | [Launch readiness](/jordan-docs/internal/run-b-verification/launch-readiness.md) | — | | O10 | **ALREADY FLIPPED — verified 2026-09-16 (Pass C):** production runs `OBS_ONECLICK=1`. What remains is the checklist it was meant to wait for: rows 8–14 of `docs/obs-oneclick-checklist.md` still need a real OBS on the owner's machine, and B1 below is the same gap. | owner | `node _verify-obs-oneclick.mjs` rows 8–14 | Railway service variables; `OPEN-ISSUES.md` (stale) | | O11 | **CLOSED — verified 2026-09-16 (Pass C).** Both `MODERATION_API_KEY` and `CONTACT_URL` are set on the production service. `OPEN-ISSUES.md` still lists them as needed. | — | — | `OPEN-ISSUES.md` (stale); Railway service variables | | O12 | Two stale worktree registrations (`create-room-ui`, `mc-guest-whitelist`) print `Permission denied` on every commit because OneDrive holds the files | owner | pause OneDrive sync for the folder, then `git worktree prune` | Pass A report; `REPORT-DOCS.md` | | O13 | **The bounty program is LIVE on production** — `BOUNTY_CLAIM=1` on the service, so every `/api/bounty/*` route is mounted and `/bounty` renders the board. The handbook and the launch-readiness page describe it as off-by-default; that is the code default, not the deployed state. Nothing has run through it (no evidence chain, no captures on the volume) and settlement is the ledger-only stub on production (real money is built behind `BOUNTY_FUNDING`, `OPEN-ISSUES.md` BM), so no money can move — but the surface is reachable by anyone who finds it. Decide whether it should be on in stealth. | decision | one variable | Railway service variables; `bounty-claim.config.js` | | O14 | **An SSH key now exists for the production container.** Pass C created `~/.ssh/railway_megachat_ed25519` (a scoped key, not your default identity) and registered its public half with your Railway account as `claude-passc-megachat-migration`, because `railway ssh` is the only sanctioned path to the volume and O1 required it. It is how the launch-readiness retest will reach prod data. Remove it with `railway ssh keys remove claude-passc-megachat-migration` and `rm ~/.ssh/railway_megachat_ed25519*` if you would rather it not exist. **2026-10-24:** migrations now run at boot, applied only when `MIGRATE_AT_BOOT` names them (`DECISIONS.md`, the audit fix round: stores), so a migration no longer needs `railway ssh`; the key's remaining use is reading production data. | decision | your call | Pass C Session 1 report | | O15 | **Who pays the streamer for credit- and points-funded seats?** The viewer's credit lives in the reward pool; the platform wallet never receives it, so E38 retains every intent for those seats rather than invent a payer. Options: the reward pool pays the streamer's share (signer `rewardPool` at the door — a one-line change), the platform funds it, or those seats stay unpaid by design. | decision | your call | `settlement.js` (E43); register L39 | | O16 | **Small rooms cannot escalate.** With three distinct flaggers required, a one- or two-viewer session never extends its hold. Acceptable for launch (the streamer refund covers the honest case; escalation only delays), or close it with unanimity when a session has fewer than `minFlaggers` depositors — four lines, the depositor count is already tracked. | decision | your call | `docs/internal/escrow-contract.md`, the small-room question | | O17 | **CLOSED 2026-09-19.** Set on the service as `ESCROW_OPERATOR_KEY` (funded 3.00 USDC.e by the owner) and `ESCROW_ATTEST_KEY` (funded 0.10 by `scripts/fund-escrow-roles.mjs`), both stored without the `0x` prefix, which the loader accepts. | — | — | `escrow-chain.js`, `normalizeKey` | | O18 | **The classifier's thresholds, and what any of it should unlock.** The numbers are reasoned guesses with no users behind them (register L48), and no feature reads them. Before one does: are these the right bars, and what does each tier get — zero friction, a prompt, a refusal? | decision | your call | `classifier.js`, `THRESHOLDS`; `docs/internal/account-model.md` | | O19 | **Rotate the breached secrets (K1–K3, K6):** the five wallet keys, the provider secrets, the stream keys, and the two campaign keys minted fresh (`CAMPAIGN_SPENDER_KEY`, `X_TOKEN_KEY`). K1 is a hard gate before real bounty settlement and real campaign payouts | owner | new keys off Railway, move funds, update the variables | `OPEN-ISSUES.md` K1–K3, K6 | | O20 | **Railway account follow-up (K4):** GitHub is reconnected and autodeploy is back (2026-10-24). Left: recreate the API tokens; review the audit log for Oct 20–22 | owner | two dashboard steps | `OPEN-ISSUES.md` K4 | | O21 | **Node and Next (K5):** this machine's Node 24.12.0 → 24.22.1; `web/` next 16.2.6 → 16.4.2; until then the local server is never exposed through cloudflared | owner | two upgrades | `OPEN-ISSUES.md` K5 | | O22 | **Set `AUTH_SECRET` on Railway (K7).** Everyone is signed out once (sessions minted before this round carry no `iat` and are refused anyway); overlay URLs become keyed, so streamers re-copy the OBS URL | owner | one variable, said to streamers in advance | `OPEN-ISSUES.md` K7; [Launch readiness](/jordan-docs/internal/run-b-verification/launch-readiness.md) row 65 | | O23 | **Two present-but-empty variables (K8):** delete or fill `PLATFORM_SETTLEMENT_KEY` and `ESCROW_CONTRACT_ADDRESS`. Before the key is filled, audit the PENDING buried-seat refunds the old refund bug may have inflated (U2) | owner | an audit of `data/settlement.jsonl`, then one variable each | `OPEN-ISSUES.md` K8, U2; launch-readiness row 63 | | O24 | **Bounty claims on production (R3):** confirm `BOUNTY_IDENTITY_STUB` is unset, run the claim retest, and void or rebind every stub-era claim (`stubbed: true` ledger rows) | owner | a names-only variable check; `/api/bounty/admin/override` | `OPEN-ISSUES.md` R3; launch-readiness rows 66, 68 | | O25 | **Cash watch-to-earn:** set `REWARDS_CASH_ALLOWLIST` and the reward bounds before the pool is funded; until then cash is off | owner | name the creators | `OPEN-ISSUES.md` U1; `rewards.js`; launch-readiness row 69 | | O26 | **The default room's password (stores-15):** try `changeme` on production's default room dashboard; set a real password if it opens | owner | one manual check, never from an agent | `rooms-store.js`; launch-readiness row 72 | | O27 | **Apply the account migration?** It reports at every boot and applies only under `MIGRATE_AT_BOOT=accounts,whitelist-identity` | owner | one variable | `OPEN-ISSUES.md` T1; launch-readiness row 71 | | O28 | **Sign-ahead dust runs (N18, U7):** `_gate-escrow-seat` and `_gate-tempo-phase2`, after both send the seat token | owner | mainnet dust, the owner's call | `OPEN-ISSUES.md` U7, N18; launch-readiness row 73 | | O29 | **Where Holler refunds come from (U5):** the platform wallet, as today, or held at the door until the upload lands | decision | your call | `OPEN-ISSUES.md` U5; `letters.js` | | O30 | **Where bounty forfeits go, 7(c) (R4):** the withheld half goes to the streamer who rejected; options written | decision | your call | `OPEN-ISSUES.md` R4 | | O31 | **The capture disk budget (R5),** before real playbacks freeze | decision | a retention period or a byte cap on `bounty-captures/` | `OPEN-ISSUES.md` R5 | | O32 | **X account switching (Q2):** needs a replace-link flow and a rule for campaign claims bound to the old X id | decision | your call, then engineering | `OPEN-ISSUES.md` Q2 | | O33 | **Campaign claims at scale (S2):** per-campaign claim files or SQLite (the audit's owner decision 5) | decision | your call | `OPEN-ISSUES.md` S2; `campaign-store.js` | | O34 | **`design-assets/` ignore rules (P9),** candidate rules written | decision | your call | `OPEN-ISSUES.md` P9 | | O35 | **`git gc` for four `tmp_obj` files (P11)** | owner | pause OneDrive, then gc | `OPEN-ISSUES.md` P11 | | O36 | **Reserved names for launch (M):** compile the list; decide bounty-backed reservations or a plain reserved list in `accounts.js` | decision | the list, then one call | `OPEN-ISSUES.md` M | | O37 | **Real campaign payouts (N1)** need K1 and the owner's word in person; `CAMPAIGN_FUNDING=1` stays unset until then | owner | K1, then the owner's say-so | `OPEN-ISSUES.md` N1; launch-readiness, "Switching on real-money campaigns" | | O38 | **`X_BEARER_TOKEN` (N5):** a campaign check refreshes old X links with it; without it the person reconnects X once | owner | X billing, one variable | `OPEN-ISSUES.md` N5 | | O39 | **Does a funded campaign waive the room's Holler price? (N6)** | decision | your call | `OPEN-ISSUES.md` N6 | | O40 | **LiveKit webhook freshness (N15):** after the next deploy, check the log for "webhook token carries no issue time" on real deliveries | owner | one log read | `OPEN-ISSUES.md` N15; `livekit-webhooks.js` | | O41 | **A seat join that cites no approve still opens on the allowance alone (N16)** | decision | your call | `OPEN-ISSUES.md` N16; `server.js` `verifyPasskeyStreamAllowance` | | O42 | **Fund the campaign spender's address for its fees (N17)** | owner | a little USDC | `OPEN-ISSUES.md` N17 | | O43 | **One Railway replica (N21, S7):** the campaign pull lock and the Call in seat check are both per process | owner | a dashboard setting | `OPEN-ISSUES.md` N21, S7 | | O44 | **A custom-token campaign on chain before custom tokens are advertised (N9)** | owner | a small funded campaign in that token | `OPEN-ISSUES.md` N9 | | O45 | **Liveness tiers for bounties and campaigns (O):** the owner's idea; the badge, where the label lives, whether a backer can require a tier | decision | your call, then engineering | `OPEN-ISSUES.md` O | | O46 | **Stuck fundings that need a person (N12, N22):** write the "needs a person" runbook, and decide whether an admin "close and refund what was received" route should exist | owner | the runbook, then one call | `OPEN-ISSUES.md` N12, N22; launch-readiness, cold-review item 9 | | O47 | **The paid halves of web-2 and web-4 (V12):** one MPP join through a dropped socket, one paid Holler whose first upload fails, then retries | owner | mainnet dust, the owner's call | `OPEN-ISSUES.md` V12; launch-readiness row 81 | | O48 | **Privy on our viem (V5):** force Privy's pinned viem and noble onto ours with `overrides`, or keep two copies | decision | a Privy sign-in, embedded signing and an MPP join to prove it (dust) | `OPEN-ISSUES.md` V5 | | O49 | **`font-mono` inside the bounty shell (V10):** exempt it from the `.mc-product` font rule or not | decision | your call | `OPEN-ISSUES.md` V10; `web/app/product.css` | | O50 | **Say " UTC" on the `/c/` deadline (V16)** | decision | a copy change | `OPEN-ISSUES.md` V16; `web/components/campaign-offer/offer-copy.ts` | | O51 | **Sign off the Space Mono readouts** at 375 px | owner | screenshots from the fresh build | launch-readiness row 83; `web/app/globals.css` | | O52 | **Should a listed guest be seated with Join Stream off? (Y3)** The code and the 2026-09-05 decision say yes, on purpose; the old pages said no | decision | your call; if no, the switch runs before the whitelist | `OPEN-ISSUES.md` Y3; `server.js` `tryWhitelistJoin` | | O53 | **Restate U1 and close U4 in** [**the status-call page**](/jordan-docs/internal/internal/needs-a-status-call.md) **(Y6):** U1's premise (the join page calls only `/api/join/passkey`) is false, and U4's two fixes both shipped in Pass C | owner | two edits there, yours to make | `OPEN-ISSUES.md` Y6; `web/lib/join-page.ts` | | O54 | **Read production's bounty ledger for pools paid under the old arithmetic (W6)** before Run B: they read `overdrawn: true` and pay nothing more | owner | one read of `data/bounty-ledger.jsonl` on the volume | `OPEN-ISSUES.md` W6; `bounty-escrow.js` | | O55 | **The first owner run of each gate changed by reading only (X8)**, which is its proof | owner | mainnet dust, the owner's call | `OPEN-ISSUES.md` X8; launch-readiness row 88 | | O56 | **The SIGTERM flush (W2):** after a deploy that had held store writes, check the log for `[shutdown] wrote N held store change(s)`; Windows cannot prove it | owner | one log read | `OPEN-ISSUES.md` W2; `server.js`; launch-readiness row 86 | ## Needs a real broadcast | Id | Item | What would settle it | Source | | --- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | --------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- | | B1 | obs-websocket path against a real OBS during a real broadcast, with verification reading the result | operator live with OBS, `--skip-push`, `_smoke-obs-overlay.mjs` | `OPEN-ISSUES.md`, "The obs-websocket path is still untested against real OBS"; R8 | | B2 | Kick re-measured on the 75 s / 51 s freeze window | a Kick rehearsal (`_rehearsal-kick.mjs`) — needs `KICK_STREAM_KEY`, `KICK_RTMP_URL` locally | `OPEN-ISSUES.md`, "KICK IS STILL UNPROVEN" → run #5 PASS predates `b3ccf8b` | | B3 | Twitch "every SECOND code of a window misses" (T5b) — likely subsumed by the overlay polling fix, **to be confirmed, not assumed** | a fresh Twitch broadcast with the refreshed overlay; the 2026-08-30 run (det 1.000) is consistent with it being fixed | `OPEN-ISSUES.md` T5b, "ROOT CAUSE FOUND" | | B4 | Does pump.fun's playlist outlive the broadcast? Verification runs after the fact | measure after a stream ends | `OPEN-ISSUES.md` T8 | | B5 | pump.fun self-capture vs external on one broadcast, after the coin-page fix (both columns were the same capture on 08-29; genuinely different on 08-30 — confirm it holds) | re-run `_rehearsal-pumpfun.mjs` | `OPEN-ISSUES.md`, pump.fun P2, "BOTH READ PATHS PROVEN" | | B6 | Rumble end to end — needs a fresh livestream slot and the watch URL from the address bar while live | operator | `OPEN-ISSUES.md` R5, "Rumble: ingest PROVEN" | | B7 | `timelineSpreadMs` across several real broadcasts, to decide R1/R2/R3 | several broadcasts on any platform; the value is recorded on every verification now | `OPEN-ISSUES.md` R1–R3 | | B8 | Kick calibration close to a reliability boundary — how often does an honest Kick streamer land in manual review? | operational tracking | `OPEN-ISSUES.md`, "golden loop" retest, Kick run #5 | | B9 | A Call in across a deploy: the rejoin reserves, 61 s on camera on air makes the claim owed with one payout intent; with the stream ended before the rejoin, the old seat's slot is back | the owner on air with live LiveKit webhooks, pushing mid-call | `OPEN-ISSUES.md` S1; launch-readiness row 79 | | B10 | A Call in from the preview: nothing is owed until GO LIVE, then owed after `minSeconds` on camera | the owner on air with live LiveKit | `OPEN-ISSUES.md` S1; launch-readiness row 80; `web/lib/join-page.ts` `publishLivekitTracks` | ## Engineering, no external dependency | Id | Item | Source | | ---- | --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------ | | E1 | **CLOSED 2026-09-16 (Pass C).** The badge now takes the corner diagonally opposite where the stack actually lands, and a layout that would still reach it at the ten-tile ceiling is refused on the write path with a reason. `_gate-overlay-layout.mjs` 33/0 measures a real browser across all sixteen origin/direction combinations. | `public/overlay.html`, `applyBadgeAnchor`; `rooms-store.js`, `layoutCollision` | | E33 | **The layout editor was inert — the overlay never received a layout at all.** CLOSED 2026-09-16 (Pass C): `server.js` sent `resolveRoomConfig(id)?.config?.layout`, and that function returns a flat object with no `config` key, so the value was always `undefined` and every room rendered the built-in default. The same expression fed the seat cap the literal 3. Admission was never affected. | `OPEN-ISSUES.md`, "THE LAYOUT EDITOR WAS INERT" | | E34 | **`direction: left`/`right` was never implemented.** CLOSED 2026-09-16 (Pass C): `relayout()` only wrote `box.style.top`, so a horizontal stack rendered as a downward column while the editor previewed a row. | `OPEN-ISSUES.md`, "DIRECTION WAS NEVER IMPLEMENTED" | | E35 | **Five browser gates assert against a UI that was replaced.** `_gate-polish`, `_gate-browse-deck`, `_gate-browse-thumb`, `_gate-cam-autoswitch` and (partly) `_gate-free-megachat` were last touched in July and assert on markup and copy the 2026-08-29 → 09-06 overhaul deliberately rebuilt — `#price`, the landing "equation" line, a zero-git-diff check against a pre-overhaul commit. They have been red and unwatched ever since, which is T2 with a cost attached. Re-pointing them is real work and deserves its own pass. **Until it happens, "the browser gates are green" is not a claim anyone can make, and the retest checklist depends on it.** | `OPEN-ISSUES.md`, "THE ELEVEN BROWSER GATES WERE NOT GRADING THE PAST" | | E37 | **CLOSED 2026-09-17.** No path put an approved pledged clip on air the first time. The cause was three missing joins, not one: `markPlayed` had no caller, the air session was never bound to a room (the claim page called `startAirSession` without one, so every production session carried `roomId: null` and the letters hook could never match), and the claim page handed out the by-id overlay URL that the overlay's own source describes as rotting. First airings and replays now share one dispatcher, one rate limit and one bridge; a session always binds to a room; `markPlayed` is called where a playback starts. `_gate-first-airing.mjs` 31/0, including a real browser overlay rendering a clip that was only ever approved. | `OPEN-ISSUES.md`, 2026-09-17 | | E41 | **CLOSED 2026-09-18 (E38): the gate clears the seeded board before it measures, 41/0.** Was: `_gate-bounty-program.mjs` red since 2026-09-01 — the demo board seeded on first boot adds 900 of escrow and the gate expected its own 110. Not a product defect; a stale expectation. | `OPEN-ISSUES.md`, 2026-09-17; `_gate-bounty-program.mjs` | | E40 | **Queue ORDER is oldest-approved-first, and nobody has decided whether it should be the streamer's to change.** Skip, hold and reorder are unbuilt; the E37 pass made the simplest defensible choice rather than inventing a product surface. Worth deciding before launch: a streamer with a large queue and no control over it is a support problem. | `bounty-bank.js`, `firstAiringCandidates` | | E38 | **CLOSED 2026-09-18.** The seat pending bucket is real money now: ticks pull into the platform wallet and every escrow intent goes through `settlement.js`, paid by the flush once `PLATFORM_SETTLEMENT_KEY` is set (unset on prod, so PENDING). Funded run: Part 4. | `settlement.js`; `_gate-money.mjs` | | E39 | **MPP seats do not pause while the overlay is hidden.** Their ticks are client vouchers; refusing one trips the stale-kick and ends the seat. Only the server-driven meters skip ticks. Since E38 they DO feed the seat bucket (`seatEscrow.accrue` on every paid voucher), so their buried seconds are refunded; the pause itself is still open (L34). | `server.js`, `tickAllMeters`; register L34 | | E36 | **CLOSED 2026-10-24: the script is deleted** (`web/package.json`; eslint is not installed and no config exists), and `_gate-typecheck.mjs` is the check (`OPEN-ISSUES.md` V11). Was: **`npm run lint` has never been runnable.** `web/package.json` runs `eslint .` and no ESLint config has ever been committed on any branch; ESLint 10 requires a flat config and exits 2. Three run prompts have now listed "lint" as a verification step. Add a config (choosing the rule set is a real decision) or drop the script. | `web/package.json`; `OPEN-ISSUES.md`, "npm run lint HAS NEVER BEEN RUNNABLE" | | E42 | **CLOSED 2026-09-18.** A points-funded seat carried the room's USDC tick price in 6-decimal atomic units against a whole-point balance, so every points seat was kicked `out_of_funds` on its first tick and refunded. Found by building the L35 fixture. The credit join now passes point-denominated atomics. | `server.js`, `createSeat`; `_gate-meter-pause.mjs` | | E43 | **CLOSED 2026-09-18.** Credit- and points-funded seats opened escrow buckets carrying the USDC address, so once the door existed their sweeps and refunds would have become real platform-wallet intents for money that never entered the platform wallet. Their buckets now carry no token address and the door RETAINS such intents. | `server.js`, `createSeat`; `settlement.js`; `_gate-money.mjs` T1 | | E44 | **Two sweeps still open from the E38 audit:** Arc-era references outside the deleted page (comments and helpers that still say Arc), and testnet framing in prose that describes a mainnet app. Neither changes behaviour; both mislead the next reader. | `OPEN-ISSUES.md`, 2026-09-18 | | E45 | **CLOSED 2026-10-24.** `_gate-phase1`, `_gate-phase2` and `_gate-ui-part-a` are deleted (harness lane; `DECISIONS.md`, the audit fix round: harness), and `_gate-dashboard-phase1` boots through `startGateServer` and asserts the 404. Was: **Five gates assert the deleted passkey bundle is served** — `_gate-phase1`, `_gate-phase2`, `_gate-dashboard-phase1`, `_gate-ui-part-a` (all four already red here for W5) and `_gate-auth` (re-pointed at the join page 2026-09-18). Re-point the four when they are ported to `startGateServer`. | `_gate-money.mjs` P (the 404 is now the asserted behaviour) | | E46 | **Resolved 2026-11-04 (owner): the legacy Gateway seat mode is removed.** `tickPrepaidSeat`, the `'gateway'` default, the shadowed `/api/join` stub and the Arc/Circle config went with the Arc cleanup; every seat names its own payment mode. U1 (MPP) is untouched. | `server.js`, `tickPrepaidSeat`; `_gate-money.mjs` P | | E47 | **CLOSED 2026-09-19 (Session 2).** Mainnet deployment `0x432bb6c62503711ad4e70a91247a110e61779213`; deposit at join; the ledger's figures into `attest`; `tickPasskeyStreamSeat` pays nobody for an escrow seat; the direct fallback rewritten with the payout address as the only recipient; a room without one refused. `_gate-escrow-seat.mjs` 29/0 on mainnet dust. | `docs/internal/escrow-contract.md`, Session 2 | | E48 | **Privy users — the wallet layer — still pay into MPP channels whose payee is the platform wallet.** `joinSeat` in `web/lib/join-page.ts` sends a Privy wallet to `/api/join/mpp` whenever `meterMode` is `mpp_session`, which production is; only MetaMask reaches the escrow. The scoping pass's claim that MPP was unreachable from the UI was wrong (a `head -5` on a grep). One client condition routes Privy through the metered join; whether to, or to point the channel payee at the streamer instead, is a decision. | `web/lib/join-page.ts`; register L44 | | E49 | **CLOSED 2026-09-19 (Session 2).** Every door transfer since E38 would have failed on mainnet: the server's hand-rolled chain object dropped `feeToken`, writes went out as EIP-1559, and fees defaulted to pathUSD, which no wallet of ours holds. Found when the escrow deposit and then the fallback's first pull both died with `insufficient funds … have 0`. Every server signer is now on viem's Tempo chain and every transfer names its fee token. | `server.js`, `tempoViemChain`; `settlement.js`; register L47 | | E50 | **Gate H should assert that every server-side `createWalletClient` is built on viem's Tempo chain**, so the next signer added on a bare chain object fails the gate instead of its first mainnet send. | `_gate-money.mjs`; register L47 | | E51 | **Nothing consumes the classifier.** It is built, gated and shown to the account holder; rewards, gating and anything else that might read it are unwritten, and what each tier should unlock is undecided. | `classifier.js`; `docs/internal/account-model.md` | | E52 | **Opacity and Reclaim are stubs.** Each file is the whole SDK boundary and returns `not-configured`. Wiring either is filling in one file — but Opacity's documentation site was returning a Cloudflare DNS error, so its contract could not be read from the source of truth. | `attestation/opacity.js`, `attestation/reclaim.js` | | E53 | **A Privy-reported social cannot be upgraded automatically.** Privy gives a username but no platform id, so the only way to turn one into a real link with attributes is for the person to connect that platform through our own OAuth. Whether Privy's `linked_accounts` carries an id we could use was not investigated. | `privy-identity.js`; register L50 | | E2 | A1: bind X's client-supplied self-capture URL to the X identity; the comment above `captureSourceUrl` saying those platforms "are not claimable yet" is false and load-bearing | `OPEN-ISSUES.md`, adversarial review A1 (high) | | E3 | A2: one degraded Privy fetch permanently deletes `platformLogins` — the merge must be additive and an empty fetch must never be written | `OPEN-ISSUES.md` A2 (high); `privy-identity.js` | | E4 | A3: no round-trip test for the widened `recordVerification` whitelist (`detectionRate`, the `timeline*` fields) — partially covered by `_gate-confidence-split.mjs` H after the regression came back once | `OPEN-ISSUES.md` A3; "golden loop" retest | | E5 | A4: gate E4 asserts against its own copy of the pump.fun live-narrowing; export the real function | `OPEN-ISSUES.md` A4 (low) | | E6 | `verifiedClips` counts scaffolding (canary, setup) windows — inflates the payout unit | `OPEN-ISSUES.md`, pump.fun P1; "STILL OPEN" under the dead-recorder entry | | E7 | An open review keeps its original reason and never learns the newer one; reasons should append | `OPEN-ISSUES.md`, P1 (07-29) | | E8 | `NO_VOD_COVERING_TS` reported for an offline channel in live mode — the wrong classifier branch matches first | `OPEN-ISSUES.md`, P1 (07-29) | | E9 | Capture storage has no global ceiling across concurrent sessions | `OPEN-ISSUES.md`, repeated since 08-24 | | E10 | pump.fun manifests (\~320 kB, append-only) re-fetched every 2 s poll — size for it or poll slower before enabling the platform | `OPEN-ISSUES.md` P3 (08-25) | | E11 | Placeholder-stream detection on pump.fun (T6) — the cheap, fail-safe option chosen, not built | `OPEN-ISSUES.md` T6 | | E12 | Overlay renders "server unreachable" instead of blanking; setup helper prints a countdown (T7) | `OPEN-ISSUES.md` T7 | | E13 | Log discarded calibration probes and cluster size on every calibration | `OPEN-ISSUES.md`, "Calibration once swallowed an injected DISAGREEMENT" | | E14 | The stub calibration fixture cannot construct offsets ≥ \~30 s; rebuild by concatenating per-badge segments | `OPEN-ISSUES.md`, calibration P1 | | E15 | `_rehearsal-run-b.mjs` exits with a libuv assertion after its report | `OPEN-ISSUES.md`, calibration P1 | | E16 | Contributions with no uploaded clip are refundable (`CLIP_NEVER_UPLOADED`) but nothing sweeps them | `OPEN-ISSUES.md`, 07-27 "Still open" | | E17 | The platform match has no reversal story; no post-release clawback for BOUNTY releases. **Partly reused 2026-09-16:** the designed holdback (option B) is now built for live seats (`seat-escrow.js`); bounty releases still pay in full with a bookkeeping-only dispute window. | `OPEN-ISSUES.md`, 07-27; `docs/decisions/post-release-clawback.md` | | E18 | `_gate-mpp-clientpath.mjs` still mirrors the payment path (drift-checked, not converted) | `OPEN-ISSUES.md`, 07-27 | | E19 | Port the fixed-sleep gates to `startGateServer` (list recorded in W5); lift G0 into the helper and adopt it in eleven browser gates | `OPEN-ISSUES.md` W5; 2026-09-16 | | E20 | One runnable entry point for the gate suite, with isolation or retry (T2) | `OPEN-ISSUES.md` T2 | | E21 | `_gate-theme.mjs` reported red for dark mode on 2026-08-26 (T1); not re-checked since the Nerve skin — [U3](/jordan-docs/internal/internal/needs-a-status-call.md) | `OPEN-ISSUES.md` T1 | | E22 | The three bounty components (`my-pledges`, `record-flow`, `streamer-page`) render in the pre-Nerve skin; reapply the restyle on top of the lockdown, contributor from the session only | `OPEN-ISSUES.md`, "THE BOUNTY COMPONENTS LOST THE NERVE SKIN" | | E23 | **CLOSED 2026-09-16.** `_gate-bounty-claim.mjs` section G now spawns through `startGateServer` (port precheck, readiness poll, stderr kept, nonce); it had reported `0,0,0` twice in a row under build load on the fixed 9 s sleep, and passed 102/0 on the harness immediately after. The other fixed-sleep gates in W5 remain open (E19). | `OPEN-ISSUES.md`, "SECTION G IS A FIXED-SLEEP RACE" | | E24 | Handles are reassignable by design at the identity layer; every consumer that stores a handle must pin the identity — the durable fix belongs in `identity-store.js` | `OPEN-ISSUES.md`, "A HANDLE IS NOT AN AUTHORIZATION TOKEN" | | E25 | G4/G5: competing claimants not modelled; MegaChat handles are 3–20 chars against Twitch's 3–25 | `OPEN-ISSUES.md`, "Known gaps still open" (Run A) | | E26 | Kick OAuth registration validity unproven (a rendering login page proves nothing); needs a full round trip with a real Kick account | `OPEN-ISSUES.md`, P1 (07-29) | | E27 | The Safari manual fallback for OBS one-click (no loopback mixed-content exemption) is by design; the monitoring toggle applies to the input named *MegaChat Overlay* only | `OPEN-ISSUES.md`, OBS one-click "Open" | | E28 | Rumble: the harness must read `server_url`/`stream_key` from the live-status API, never env; no Rumble rehearsal harness exists | `OPEN-ISSUES.md`, "Rumble: ingest PROVEN" | | E29 | `docs/design/copy-bank.md` retired the `/bounty` disclosure; `web/components/bounty/record-flow.tsx` and `web/components/bounty/claim-flow.tsx` still carry sibling preview notices | `docs/ui-overhaul/copy-principles.md`, line 265 | | E30 | Delete a room from the UI (`deleteRoom` has no caller) | `docs/ui-overhaul/baseline/ideal-paths-local.md` T8 | | E31 | LiveKit capacity figures remain models, not measurements (L4); no programmatic access to Cloud usage numbers (L2) | `OPEN-ISSUES.md` L2, L4 | | E32 | `/api/join/mpp` is mounted and gated but unreachable from the join page — retained code or a live mode? ([U1](/jordan-docs/internal/internal/needs-a-status-call.md)) **2026-10-24 (docs pass):** the premise is stale. The join page does call it (Privy wallets when the MPP meter exists, free rooms, whitelisted guests), as E48 says; U1 needs restating (O53) | `web/lib/join-page.ts`; `server.js`; `OPEN-ISSUES.md` Y6 | | E54 | The 6 h held-clip TTL (`LETTER_HOLD_TTL_MS`) is a guess at a broadcast's length, never measured against a real show | `OPEN-ISSUES.md` P1 (producer mode) | | E55 | `ready` has no cap of its own; only `GLOBAL_MAX_BYTES` and the hold TTL bound a producer's bench | `OPEN-ISSUES.md` P2 | | E56 | Restart recovery mid-playback (`playing` → held, never replayed) is gated against a seeded `meta.json`, not against a deploy landing mid-clip | `OPEN-ISSUES.md` P3 | | E57 | Producer mode was driven through the dashboard with no OBS overlay connected; "Air it" and the overlay-offline banner are asserted from one side only — same gap as row 25a | `OPEN-ISSUES.md` P4 | | E58 | The join page's suggested guest name is not selected on focus, so a fan who clicks and types appends to it | `OPEN-ISSUES.md` P5 | | E59 | `_gate-cohost-booth.mjs` unlocks through a form that is no longer mounted and types into the pre-filled `#username`; its arm, re-arm, auto-off and denied sections are uncovered until it is re-pointed | `OPEN-ISSUES.md` B2 (booth picture) | | E60 | **CLOSED 2026-09-24.** The guest's echo: the booth now plays the guests (the canceller's reference) and the overlay mutes them while it does — `_gate-booth-audio.mjs` 13/0. What remains is E64. | `OPEN-ISSUES.md` E3 | | E61 | The booth's still-picture watch pauses while its tab is hidden, and reads a deliberate still scene as "still picture" | `OPEN-ISSUES.md` B3, B4 | | E62 | The guest page's fallback for a booth that predates `mc.picture` (show the host after 2s with no attribute) is reasoned, not gated — no harness can run the old booth against the new join page | `OPEN-ISSUES.md` B6 | | E63 | A picture that turns into OBS's placeholder MID-session is visible for up to \~1s (`OBS_AFTER` samples) before both sides hold it | `OPEN-ISSUES.md` B7 | | E64 | The echo fix depends on OBS capturing Desktop Audio on the booth's output device, and whether Chrome's canceller cleanly removes a loud speaker is unmeasured — both need a live session | `OPEN-ISSUES.md` E4 | | E65 | Live check: does This tab now sound clean to the streamer? The double-copy defect is fixed and gated; nothing recorded the old sound | `OPEN-ISSUES.md` W1 | | E66 | **CLOSED 2026-09-25** — the operator is on OBS 32.2.2. (OBS 31 doubled guests and stingers on stream in either OBS booth mode.) | `OPEN-ISSUES.md` W4 | | E67 | Through OBS (formerly OBS · speakers) gates the streamer's voice for guests under loud playback (10–24% of speech) and adds \~170 ms, unmeasured in conversation | `OPEN-ISSUES.md` W2, W5 | | E68 | Operator-side: start OBS Virtual Camera; remove or shut down the second "Browser" overlay source; fix the dead "Audio Input Capture" and check Mic/Aux is unmuted | `OPEN-ISSUES.md` W7 | | E69 | Live check: the first real broadcast after this deploy gets a picture from its previews (12 KB floor, a short seat) | `OPEN-ISSUES.md` R6 | | E70 | The bounty capture frame lands on the room's newest airing, untested and unmakeable in production (no ffmpeg) | `OPEN-ISSUES.md` R7 | | E71 | Airings of deleted rooms stay in `airings.json` (their files are cleaned) | `OPEN-ISSUES.md` R8 | | E72 | **CLOSED 2026-09-25** — confirmed by the owner: no "Which extension?" chooser opening a room with MetaMask and Phantom installed. | `OPEN-ISSUES.md` D5 | | E73 | The big-stream threshold (100) is a guess; the owner can now tune it live on `/dev` once real streams use the board | `DECISIONS.md`, "The board's featured tier and its density" | | E74 | Injected wallets other than MetaMask are registered for watch time at Connect, not at load | `OPEN-ISSUES.md` D6 | | E75 | Live check: a Recently aired card opens the owner's 2026-09-24 broadcast in the Twitch player on the page | `OPEN-ISSUES.md` P1, P6 | | E76 | No dashboard button yet for removing a kept MegaChat (the route exists) | `OPEN-ISSUES.md` P4 | | E77 | A deliberately deleted VOD and an expired one both fall back to the kept clip | `OPEN-ISSUES.md` P5 | | E78 | Live check: the owner opens `/dev` on megachat.fun signed in with Twitch, which pins their account (a 404 means the account's Twitch link is missing) | `OPEN-ISSUES.md` S2, S10 | | E79 | A quiet broadcast that ended while the server was down, with no preview kept, can look shorter than 5 minutes | `OPEN-ISSUES.md` S9 | | E80 | Live, off air: the booth on the ASUS speakers at stream volume with real guests — This tab, then Through OBS — no siren, no ring, and the howl guard's cuts counted | `OPEN-ISSUES.md` F7 | | E81 | The streamer's own voice returned by a guest's leaky device or a Discord call on the same speakers is not something the booth can cancel | `OPEN-ISSUES.md` F6 | | E82 | Echo reports ride the seat id (public to the room): a forger can put a wrong "sending your voice back" line on the booth (throttled); a per-seat secret would stop it | `OPEN-ISSUES.md` J7 | | E83 | A stream tab more than 30s behind the host is not found by the guest-page echo detector | `OPEN-ISSUES.md` J7 | | E84 | **CLOSED 2026-10-24 (integration pass).** All four answer 403 `seat_token_mismatch` without the seat's token, and the join page sends it (`_gate-integration.mjs` A8). Was: **HIGH — every seat-id-only HTTP route is the N1 hole again (U3):** `POST /api/leave/:seatId`, the LiveKit publisher token, `/api/seat/quality`, `/api/seat/echo` must require the seat token; seat ids are public | `OPEN-ISSUES.md` U3; `server.js` `seatTokenMatches` | | E85 | **Escrow seats live during a redeploy are never attested (U4);** the contract pays the streamer the whole cap. Needs seat persistence or a boot-time attest from the seat ledger | `OPEN-ISSUES.md` U4; `escrow-chain.js` | | E86 | **Checksum v2 writer flip, the deploy after this round (U6)** | `OPEN-ISSUES.md` U6; `bounty-ledger.js` | | E87 | **CLOSED 2026-10-24 (integration pass).** Releases are allocated pro rata and a refund returns only the unreleased remainder (`bounty-escrow.js`; `_gate-integration.mjs` M3); pools paid before it read overdrawn (O54). Was: **A bounty pool can pay out more than it holds (R19, money-9):** latent while settlement is a stub; must land before Run B | `OPEN-ISSUES.md` R19; `bounty-escrow.js` | | E88 | **CLOSED 2026-10-24 (integration pass): every item landed**, each with a dated note under its entry in `OPEN-ISSUES.md`; `_gate-integration.mjs` 52/0, `_gate-identity-account.mjs` 65/0. P1 leaves five reads (E125). Was: **This round's integration-list remainders, open when this was written:** P1 (`server.js` env reads), Q6 (`_gate-x-claims`), R20 (frames parser), R21 (stub flag in gates), R22 (admin session), S9 (exact campaign amounts), T6 (accounts and campaign store on the helper; watermark), U12 (credit-join ownership, key guard, rewards payout config, `/api/health` ledgers, one parse per message), the classifier change. Close each as it lands | `OPEN-ISSUES.md` P1, Q6, R20–R22, S9, T6, U12; `DECISIONS.md` (identity) | | E89 | **Config built at import misses `.env` (P2);** production unaffected | `OPEN-ISSUES.md` P2 | | E90 | **Twelve server fetches have no timeout (P3)** | `OPEN-ISSUES.md` P3 | | E91 | **The sliding-window limiter, written twice, prunes its whole Map per call above 5,000 keys (P4)** | `OPEN-ISSUES.md` P4; `dashboard-routes.js` `unlockAllowed` | | E92 | **Duplications (P5–P7):** three JSON request helpers in `web/lib`, two relative-time forms, the address and 64-hex regexes inlined 26 times | `OPEN-ISSUES.md` P5–P7 | | E93 | **Pages and files that say something false after this round:** `docs/legacy/README.md` on the /index.html route (P10), the pruner and `MIGRATE_AT_BOOT` lines (T8), "no X token is stored" (Q8); cc-42 and cc-43 (P11). **2026-10-24:** P10, T8 and Q8 landed (docs and integration passes) and the dead client public/rewards.js is deleted; left: `fixtures/bounty-partial.json` (cc-42) and `MORNING_CHECKLIST.md`'s `npm run gate:tokens` (cc-43) | `OPEN-ISSUES.md` P10, P11, T8, Q8 | | E94 | **Gates out of date with the product:** `_gate-phase4-handles`, `_gate-first-airing` B3, `_verify-bounty-oauth` K, the gates that send no seat token, `_gate-dashboard-phase1` (writes the repo's real `data/rooms.json`), `_gate-lk-phase2` and `_gate-phase2-hostfeed` (`#manage-room-id`), the unkeyed rehearsal overlay URLs, `_gate-privy-auth`'s forged shape, `_gate-obs-protocol`'s libuv exit at teardown. **2026-10-24 (integration and harness passes):** fixed: `_gate-first-airing` B3, `_verify-bounty-oauth` K, the seat token in every listed gate (the dust ones edited, not run), `_gate-dashboard-phase1` on a scratch server, `_gate-privy-auth`'s shape. Left: `_gate-phase4-handles`'s browser section (refused a stale build), the room-unlock form (E120), the rehearsal URLs, the libuv exit | `OPEN-ISSUES.md` T7, P12, R16, Q9, N25 | | E95 | **Gates boot `server.js` with the local `.env`'s real keys (U11):** points-only today; a money case there would sign mainnet transfers. **2026-10-24 (harness lane):** closed for every `startGateServer` gate (`SENSITIVE_ENV`, `keepEnv`); open for the self-booting files (E119) | `OPEN-ISSUES.md` U11; `_gate-helpers.mjs` `startGateServer` | | E96 | **Identity remainders:** the account page is silent on `?link_error=` (Q3), no "log out everywhere" (Q4), `/api/account` merges attributes across platforms (Q7). **2026-10-24:** Q3 landed (web lane: `web/components/account/account-page.tsx`) | `OPEN-ISSUES.md` Q3, Q4, Q7 | | E97 | **YouTube, Rumble and pump.fun ownership proofs (R2):** their handles cannot be claimed until each exists | `OPEN-ISSUES.md` R2; `bounty-routes.js` | | E98 | **Bounty deferrals:** `spawnSync` tools on the event loop (R6), caller strings reaching ffprobe (R7), capture not stopping when the channel goes offline (R8), released clips never purged (R9) | `OPEN-ISSUES.md` R6–R9 | | E99 | **Bounty smaller items:** the O(n²) `/program` fold (R10), seeded flags (R11), the `handleKey` allowlist's home (R12), cleanups (R13), the lapsed-claim wedge (R14), two claims in one room (R15), the approval queue's account ids (R17), the in-memory pledge dedupe (R18) | `OPEN-ISSUES.md` R10–R18 | | E100 | **Campaign remainders:** the engine split (S3), ci-16 (S4), the `findFundingTransfer` cache (S5), one throwing campaign aborts the sweep (S6), a stuck funding's elapsed time unshown (S8), the `attestation/index.js` comment (S10) | `OPEN-ISSUES.md` S3–S6, S8, S10 | | E101 | **Store remainders:** a hard kill inside the 1 s window reads `evidence_diverged` (T2), memory ahead of disk after a failed write (T3), bounty archiving (T5), two latch lines for one damage (T9). **2026-10-24:** T9 landed (integration pass, money H13) | `OPEN-ISSUES.md` T2, T3, T5, T9 | | E102 | **Money remainders:** the send lock's gaps (U8), serialized direct-mode pulls (U9), the rewards socket after a sign-in (U10). **2026-10-24:** U10 landed (web lane: `web/lib/join-page.ts`) | `OPEN-ISSUES.md` U8–U10 | | E103 | **The backer's bounty page (L1–L4):** a per-bounty view, re-up after a claim, top up, clip retention under L2 | `OPEN-ISSUES.md` L | | E104 | **Campaign v1 gaps:** the reference-set root on chain (N2), a FAILED payout has no in-app resolution and no "mark paid", on purpose (N4), free joins depend on the MPP meter (N7), `/c/[slug]` copy for an honoured claim (N13); Reclaim and Opacity for inbound follows stay stubs (N3, as E52) | `OPEN-ISSUES.md` N2–N4, N7, N13; `campaign-merkle.js` | | E105 | **The campaign dashboard's type errors (N8):** `tsc --noEmit -p web` was clean at the audit (2026-10-24) and `_gate-typecheck.mjs` T1 now asserts it; close N8 once the gate passes on the merge build | `OPEN-ISSUES.md` N8; `_gate-typecheck.mjs` | | E106 | **N14 residuals:** the overlay key cannot be rotated per room (rotating the sign-in secret rotates every key and signs everyone out); the legacy `/r//overlay` redirect drops the query | `OPEN-ISSUES.md` N14; `overlay-key.js` | | E107 | **The drop rule cannot decide a Tempo nonce-key transaction (N23);** it leaves the campaign to a person | `OPEN-ISSUES.md` N23; `settlement.js` | | E108 | **The product header is hand-built 8 times (V2);** one ``, with computed-style diffs at 4 widths × 2 themes | `OPEN-ISSUES.md` V2 | | E109 | **The join page runs on module globals (V3):** a second mount revives the first one's sockets. Until fixed, never link to /join with `next/link` | `OPEN-ISSUES.md` V3; `web/lib/join-page.ts` | | E110 | **Merge the rewards socket into the seat socket (V4),** unblocked now that the server parses each message once | `OPEN-ISSUES.md` V4, U12 | | E111 | **Every full page load by a signed-in user re-posts the Privy token (V6)** | `OPEN-ISSUES.md` V6; `web/lib/identity.ts` | | E112 | **The /legacy drawer dialogs do not move, trap or restore focus (V7)** | `OPEN-ISSUES.md` V7 | | E113 | **Web leftovers:** the campaign client's dead branches, duplicated formatters and `` (V8); legacy contrast, `web/app/product.css` patch rules, six switches, `!important` patches, the minified `web/components/create-room/create-room.css` (V9) | `OPEN-ISSUES.md` V8, V9 | | E114 | **The Holler attempt dedupe is in memory (V13):** a restart inside 10 minutes lets one repeat pay; the upload sweep refunds it | `OPEN-ISSUES.md` V13; `letters.js` | | E115 | **Gate coverage and stale premises (V14, V15):** the campaign approve step is by hand; `_gate-lk-phase1/2/3` spend dust (owner-run); `_gate-overlay-first-guest`'s premise and `_gate-booth-audio` S13 hold trivially since NEW-1 | `OPEN-ISSUES.md` V14, V15 | | E116 | **Integration residuals:** a cooperative MPP close after the seat is gone is refused (W3); a USDC-reward credit in a non-6-decimal room is mispriced (W4); the Windows-only `airings.json` rename race (W7) | `OPEN-ISSUES.md` W3, W4, W7 | | E117 | **A room saved with rewards on at the old 0.1 / 5 answers 400 on every dashboard save (W8)** until lowered | `OPEN-ISSUES.md` W8; `dashboard-routes.js` | | E118 | **Gates owed a run on the fresh build (W9):** `_gate-board-fold` B0–B2, `_gate-campaigns` D7, `_gate-bounty-claim` G, `_gate-phase4-handles`, `_gate-web-fixes`, `_gate-record-flow` | `OPEN-ISSUES.md` W9, R20 | | E119 | **Self-booting harness files bypass `startGateServer` (X2):** no key blanking, fixed sleeps; continues E19 | `OPEN-ISSUES.md` X2; `_gate-helpers.mjs` | | E120 | **Three browser gates drive a room-unlock form that is gone (X3, P12)** | `OPEN-ISSUES.md` X3, P12; `web/components/room-recovery.tsx` | | E121 | **`_gate-stale-capture` is red by design (X4)** until a real stalled capture is kept under the repo | `OPEN-ISSUES.md` X4; `_gate-capture-stall.mjs` | | E122 | **Harness deferrals (X6)** (X6); X7 closed 2026-11-04 (the Circle passkey source was deleted) | `OPEN-ISSUES.md` X6, X7 | | E123 | **Ending a room (Y2):** `deleteRoom` guards only the default room while the route says the demo room is permanent too, and the route removes and refunds live seats before the refusal | `OPEN-ISSUES.md` Y2; `rooms-store.js` `deleteRoom`; `dashboard-routes.js` | | E124 | **The glossary's "capped at ten" is the `MEGACHAT_MAX_SEATS` default (Y4)** | `OPEN-ISSUES.md` Y4; `rooms-store.js` `maxEffectiveSeats` | | E125 | **Five `server.js` env reads still skip `envNum` (P1 residual):** `PENDING_CAMERA_TIMEOUT_MS` reads a non-number as NaN; `FOLLOW_POLL_MS`, `FOLLOW_OFF_CONFIRM_MS`, `POSTER_SWEEP_MS`, `SEAT_RECONNECT_GRACE_MS` read it as the default | `OPEN-ISSUES.md` P1; `server.js` | ## Reconciliation note `OPEN-ISSUES.md` has 76 `###` entries across 16 runs (as of `03aabc0`). Every open bullet found in it maps to a row above or to a `RESOLVED`/`RETRACTED`/`SUPERSEDED` marker in the file itself. Two items in the file are recorded with both an "open" and a later "resolved" form (L1, L5, L6, G9, P6, the Twitch self-capture claim); the resolved form governs and they are omitted here. New in this pass: E1. E38 (2026-09-18): E42–E46 and O15 added; E38, E41, E42, E43 closed. Escrow Session 1 (2026-09-18): E47, O16, O17 added. Session 2 (2026-09-19): E48–E50 added; E47, E49, O17 closed. Identity layer (2026-09-19): E51–E53 and O18 added. MegaChat producer mode (2026-09-19): E54–E58 added; booth picture (2026-09-24): E59–E68 added, E60 closed; board order and pictures (2026-09-25): E69–E71 added; density, featured tier and wallet popup (2026-09-25): E72–E74 added; replays (2026-09-25): E75–E77 added; owner settings page (2026-09-25): E78–E79 added; the siren (2026-09-26): E80–E81 added; echo found and named (2026-09-28): E82–E83 added, B1 closed in the same pass (and its first form superseded — B5); P6 in that run is a gate-diagnostics fix, closed in the same pass and not carried here. The audit fix round (2026-10-24): sections K–O (2026-10-22/23) were not carried until now and are reconciled here with this round's K4 and K7 updates, K8, and P–U: O19–O46, B9–B10 and E84–E107 added; O3 and O14 annotated. Not carried, because the file records them closed: N10, N14 (its residuals are E106), N19, N20 (closed by U1), and the "fixed this round" records Q1, Q5, R1, S1, T1, U1. N24 is closed in effect: launch-readiness's "The cold review's own list" reconciles the reviewer's list. N11 joins O3, N18 joins O28, N21 joins O43. The record addendum (2026-10-24, later): sections V (web), W (integration), X (harness) and Y (the docs pass) reconciled: O47–O56 and E108–E125 added; E36, E45, E84, E87 and E88 closed; E32, E93–E96, E101 and E102 annotated. Not carried, because the file records them fixed: V1, V11 (closes E36), W1, X1, Y1, and the landed notes under P1 (its residue is E125), P10, Q3, Q6, Q8, Q9, R19–R22, S9, T6, T8, T9, U3, U10–U12; T7's residue is E94. W5 is the money lane's recorded decision; Y5 joins O23 and O29; X5 is register L40. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://jordan-7.gitbook.io/jordan-docs/internal/run-b-verification/outstanding.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.