Tabulated from three weeks of Claude Code session logs (2026-05-12 to 2026-06-02), Bram-driven.
| bucket | what it covers |
|---|---|
| Hunk-level staging / unstaging | -p / --patch work: add -p, checkout -p, restore -p, reset -p, stash push -p. Plus diff --cached / --staged to review the staging area hunk by hunk. |
| Staging surgery (non-hunk) | restore --staged <path> to unstage a single file, rm --cached, add --intent-to-add, any --index / --cached flag work. |
v0.1.31 closed eight issues — #84, #85, #86, #88, #91, #92, #93, #94 — touching the spinner lifecycle, JSONL turn-end detection, the in-flight feedback panel, iframe-cascade cost, PTY click delivery, and permission-menu interaction. None of the fixes were guesses. Each followed the same loop: propose a worklist item carrying an explicit hypothesis and validation plan, approve into an apply cycle that itself acted as the test stimulus, grep the trace for the predicted signal, and either commit or iterate. Wrong hypotheses (lastAssistantText panel as the cascade driver; sessionTurns parsing as the bottleneck) were caught quickly because each proposal named the specific trace pattern that would confirm or refute it.
Each round added a single layer that survived into the codebase: helper-call per-call timing for JSONL-walking helpers, heartbeat-batch and talk-session-batch for aggregate main-thread health, jsonl-fanout for
| <!-- | |
| B Square Bulletin — community calendar embed fix | |
| Problem: the current embed shows two scrollbars (page + iframe). The iframe | |
| has a fixed 1800px height with scrolling="yes", so when the event list is | |
| taller than 1800px it gets its own scrollbar inside the page's scrollbar, | |
| and when it's shorter you see a big gap. | |
| Fix: opt the iframe into auto-height mode (?autoheight=true), turn off its | |
| scrollbar, start it at height:0, and add a tiny postMessage listener that |
| #!/usr/bin/env bash | |
| # verify_edge_functions.sh — compare deployed edge function source against repo | |
| # | |
| # Usage: | |
| # export SUPABASE_ACCESS_TOKEN=sbp_... # from supabase.com/dashboard/account/tokens | |
| # export SUPABASE_PROJECT_REF=your_project_ref | |
| # bash verify_edge_functions.sh | |
| # | |
| # Requires: curl, diff, jq | |
| # Run from the root of your community-calendar repo clone. |
| -- Verify that a fork's Supabase database has all required objects. | |
| -- Paste this into the Supabase SQL Editor and run it. | |
| -- | |
| -- Each check returns '✅ OK' or '❌ MISSING' with the fix. | |
| -- | |
| -- Auto-generated from DDL files on 2026-04-24. | |
| -- Regenerate: python scripts/generate_verify_sql.py | |
| SELECT '── TABLES ──' AS section, '' AS status |
Five commits just landed upstream that reduce merge friction for forks. Here's what to do and why.
report.json and xmlui/version.txt are no longer tracked. These auto-generated files always diverge across forks, causing pointless merge conflicts.
xmlui/config.local.js is no longer tracked. It was already gitignored but still in the repo from an earlier commit. A config.local.js.example template is now shipped instead.
WFHB needs to edit certain events as they flow from the community-calendar database to the iframed viewer. The approach: add an eventOverrides object to the existing excluded.json file that WFHB already manages in GitHub. The community-calendar viewer already fetches this file via the ?exclude= query param; it just needs to apply overrides in addition to exclusions.
Two repos are involved:
community-calendar (Jon) — the shared viewer that any city can iframewfhb (Chuck) — the WFHB-specific moderator UI
The published blog at blog.xmlui.org is a standalone XMLUI app (xmlui-blog), separate from the main website. Its source lived in blog/src/ but has been removed from the working tree — only blog/dist/ remains.
The key file was blog/src/config.ts, which contains:
blogPosts array listing every post's metadata (title, slug, description, author, date, image, tags, draft).appGlobals.blog.posts.blog/public/blog/*.md via Vite glob import.Main.xmlui for the blog app used hardcoded Page routes with index-based references (posts[0], posts[1], etc.).Adding a new post to the published blog requires:
cities/*/events.json, cities.json, and version.txt to git after every build.ics files from scrapers/feeds are also committedload-events edge function fetches events.json from raw.githubusercontent.com to upsert into Supabasecities.json and version.txt ARE used by the frontend at load time (via GitHub Pages)
