Session 0068.0 — Transcript

App: ohm Start: 2026-06-03T23-55 (PST) End: 2026-06-04T00-42 (PST) Status: FINALIZED — stood down (no code work; goal already met by 0067).

Launch prompt

Drive the §22 multi-project ("document library") work forward.

Motivating example: make it possible to create a benstull document library
called `human-filter-experiment` (type: document) in the benstull deployment.

(Opened first under wgl-session-ignore for a quick "how do I create a document library" question; re-opened as a tracked coding session — wgl-coding-session-init, this transcript — once it became clear the real work was driving the §22 build.)

Pre-state

Framework main did NOT yet contain the §22 registry feature (registry.py absent on main); the registry spine lived on branch m3-backend-registry-spine.
benstull deployment (git.benstull.org: benstull/rfc-app) at v0.31.4, predating the registry feature entirely.
Four ohm sessions still --INPROGRESS: 0026/0027/0045 (last week), 0067 (~3.4h).

Arc

Reframed the ask. "Document library" = a §22 project with type: document, declared in a deployment's projects.yaml (REGISTRY_REPO) and mirrored in by the framework — registry data, not an rfc-app code change. "Domain" is not a framework primitive (deployment → projects is the whole hierarchy).
Discovered the feature is unshipped. benstull runs 0.31.4 (no registry), main had no registry.py, the spine was only on the in-progress branch. So no live projects.yaml exists to add an entry to. Confirmed a benstull deployment DOES exist (benstull/rfc-app + stub rfc-app-flotilla).
Operator chose to drive the M3+ work (the library being the motivating example), so opened a tracked coding session.
Session init. Claimed ohm 0068. Closed out abandoned ohm sessions 0026/0027/0045 (idle >4h, never finalized) → finalized as abandoned (end=start) + manifest titles, pushed to wiggleverse/session-history. Left 0067 (~3.4h) in flight. Installed the CLAUDE.md org-context import (later found already committed by 0067). Seeded + checkpoint-published this transcript.
Baseline check exposed a live collision. Mid-session, the shared canonical checkout was switched off m3-backend-registry-spine onto main by the concurrent session 0067, which had finalized Plan A and merged it via PR #11 (6c2bdb3, v0.33.0) and moved on to feat/m3-frontend (isolated worktree rfc-app-m3-frontend). My in-progress CLAUDE.md edit was wiped by the branch switch — the §5.4 shared-checkout hazard, live.
Stood down. The session's stated goal (finalize + push Plan A) was already accomplished by 0067. No code work remained for 0068.

Cut state

origin/main == local main == 6c2bdb3, clean. Plan A merged (PR #11, v0.33.0: registry mirror + /api/deployment & /api/projects/:id + review semantics; META_REPO→REGISTRY_REPO hard cut). feat/m3-frontend (PR #10, design doc only) is the live frontier in worktree rfc-app-m3-frontend.
0068 produced no framework commits. Its only mutations were to wiggleverse/session-history (close-outs + this transcript). Memory updated: appended a 0068 note (document-library/benstull context + worktree lesson) to project_rfc_app_multiproject.md.

Operator decisions

Claim 0068 concurrently AND close out sessions idle >4h. → done.
Given Plan A already merged by 0067: stand down 0068. → done.

Next-session prompt

Resume the §22 multi-project ("document library") build. Read memory
project_rfc_app_multiproject.md first (Plan A merged = PR #11, v0.33.0; M3-frontend
designed = PR #10). The live frontier is M3-frontend, already in the isolated
worktree ~/git/wiggleverse.org/ben.stull/rfc-app-m3-frontend on branch
feat/m3-frontend — DO NOT share the canonical checkout (the §5.4 collision bit
session 0068). First move: write the M3-frontend implementation plan against the
now-merged API shapes (/api/deployment, /api/projects/:id) on the M3-0 Tier-1
harness, then execute via subagent-driven-development. Toward the benstull
`human-filter-experiment` document library specifically, the remaining chain after
M3-frontend is: Plan B (if it's a 2nd project), stand up a benstull REGISTRY_REPO +
projects.yaml, and upgrade the benstull deployment off 0.31.4 to >=0.33.0.

Lesson

Parallel sessions on rfc-app MUST use isolated git worktrees. 0068 and 0067 shared the canonical checkout and the tree was reset mid-session — exactly what §5.4 warns about. 0067 did this right for the frontend (own worktree); the backend Plan A finalize/merge happened in the shared checkout and is what collided.

4.7 KiB Raw Blame History