From 83242368196dc00ce7b35fe71012c8f893df9c10 Mon Sep 17 00:00:00 2001 From: Ben Stull Date: Thu, 4 Jun 2026 00:08:24 -0700 Subject: [PATCH] update ohm/0068/SESSION-0068.0-TRANSCRIPT-2026-06-03T23-55--INPROGRESS.md --- ...TRANSCRIPT-2026-06-03T23-55--INPROGRESS.md | 41 +++++++++++++++++++ 1 file changed, 41 insertions(+) diff --git a/ohm/0068/SESSION-0068.0-TRANSCRIPT-2026-06-03T23-55--INPROGRESS.md b/ohm/0068/SESSION-0068.0-TRANSCRIPT-2026-06-03T23-55--INPROGRESS.md index be9f6ad..b017c76 100644 --- a/ohm/0068/SESSION-0068.0-TRANSCRIPT-2026-06-03T23-55--INPROGRESS.md +++ b/ohm/0068/SESSION-0068.0-TRANSCRIPT-2026-06-03T23-55--INPROGRESS.md @@ -26,3 +26,44 @@ document library becomes real, per docs/design/multi-project-spec.md and the roadmap. ``` + +## Plan + +Session opened under wgl-session-ignore (quick "how do I create a document +library" question), then re-opened as a tracked coding session once it became +clear the real work is driving the §22 multi-project build. + +**Discovery (this session):** +- "document library" = a §22 project with `type: document`, declared in a + deployment's `projects.yaml` (REGISTRY_REPO), mirrored in by the framework. + It is NOT a code change to rfc-app; it's registry data — but the mechanism + itself is unreleased. +- benstull deployment exists (git.benstull.org: benstull/rfc-app @ 0.31.4 + + rfc-app-flotilla stub) but predates the registry feature entirely. main has + no registry.py. The registry spine lives only on this branch. + +**Session bookkeeping:** claimed ohm session 0068; closed out abandoned ohm +sessions 0026/0027/0045 (idle >4h, never finalized) — pushed to +wiggleverse/session-history. 0067 (~3.4h old) left in flight. + +**Repo state:** on `m3-backend-registry-spine`, 17 commits ahead of +origin/main, **never pushed (no upstream)**, tree clean. M3-backend Plan A +appears complete on-branch (registry mirror, runtime-config APIs, propose +initial_state, mark-reviewed, catalog unreviewed filter) plus an M3-frontend +design doc — further than memory recorded. + +**Frontier (per memory + branch):** +1. Push the m3 branch (protect 17 local-only commits); finalize Plan A + (CHANGELOG upgrade-steps block + VERSION bump per the per-breaking-slice + decision) and PR → main. +2. M3-frontend (the unclaimed slice; design doc just written): `/p//` + routing, 308 redirects off `/rfc/`, VITE_APP_NAME → runtime-config + cut, per-project theme overlay, deployment directory at `/`, project + switcher — consumes the two runtime-config APIs. This is what makes a + project (document library) actually navigable/usable. +3. Plan B (migration 028 PK rebuilds + project_id threading) — required before + a 2nd project (M4). +4. Deployment-side: stand up registry repo + project row + version pin; upgrade + benstull deployment off 0.31.4. + +(TODO: fill remaining transcript at finalize.)