add ohm/0090/SESSION-0090.0-TRANSCRIPT-2026-06-08T20-30--2026-06-09T03-29.md + replace placeholder/variant SESSION-0090.0-TRANSCRIPT-2026-06-08T20-30--INPROGRESS.md

ohm/0090/SESSION-0090.0-TRANSCRIPT-2026-06-08T20-30--2026-06-09T03-29.md

@@ -0,0 +1,132 @@
+# Session 0090.0 — Transcript
+
+> App: ohm
+> Start: 2026-06-08T20-30 (PST)
+> End: 2026-06-09T03-29 (PST)
+> Type: brainstorming
+> Driver: Ben Stull + Claude (Opus 4.8 1M)
+
+## Launch prompt
+
+Brainstorm and spec a scoped Admin information architecture for the three-tier
+model (deployment → project → collection), and the collection-management surfaces
+that hang off it. §22 delivered scoped roles ({owner, contributor} at {global,
+project, collection}) but the admin *page* IA never followed: `/admin` is mounted
+only at deployment scope (App.jsx:348) and mixes grains (retired RFCs, graduation
+queue at the wrong scope); create-project/collection work but are unreachable on
+N=1 deployments; in-app metadata field-schema config is deferred (D8). Goal:
+produce a Solution-Design spec for a coherent Site/Project/Collection Admin IA.
+Don't write code this session.
+
+## Pre-state
+
+- rfc-app on clean `main` (`afa8d26`, v0.52.3-era at session open; later observed
+  live OHM at v0.52.3 then v0.53.0).
+- OHM live deployment at `rfc.wiggleverse.org`. Registry `wiggleverse/rfc-registry`
+  declared two projects: `ohm` (content_repo `ohm-content`) + `ecomm`
+  (`ecomm-content`). `GITEA_ORG=wiggleverse`.
+- Concurrent in-flight sessions: 0080, 0089, later 0092.
+
+## Arc (turn-by-turn, uncurated)
+
+1. **Init.** Classified brainstorming; claimed session 0090 (warned about in-flight
+   0080/0089, proceeded per autonomous default). Clean pushed-main baseline.
+2. **Explore.** Fanned out 5 Explore agents over routing/landing, the Admin page +
+   re-home targets, §22 roles/composition, create-project/collection surfaces, and
+   the D8 metadata config. Built a precise map of the four defects (DEF-1..4) and
+   the existing `auth.py` permission primitives.
+3. **Product stories.** Operator supplied 15 product user stories (US-1..15)
+   mid-explore. Asked 4 design decisions (Private model, slug editing, collection
+   storage, collection retire) → all recommendations accepted: Private=gated +
+   request-access page; create-time slug only; path-in-project-repo + auto-create;
+   distinct `retired` collection state.
+4. **Approaches + design.** Proposed 3 IA approaches; operator chose C (per-scope
+   routes + scope-switcher + gear). Presented the full design; approved with the
+   graduation-canonical-at-collection + project-rollup, audit/permission-events
+   left deployment-wide.
+5. **Wrote the spec** → `docs/design/2026-06-08-scoped-admin-ia.md` (v0.1.0): §1
+   context/4 defects, §2 15-story traceability, §3 IA, §4 data/API + SPEC
+   amendments, §5 decisions, §6 OOS, §7 8-slice delivery, §8 gap analysis (12 gaps).
+6. **G-3 + type + LLM-context.** Operator: G-3 → warn+allow; corrected the "no
+   types" premise (type retained as terminology-only per §22.4a; kept admin
+   surfaces type-agnostic, G-11). Operator raised LLM authoring-context → split:
+   §9 config surfaces here, consumption to a separate spec (G-12); store-once /
+   compose-at-read-time. Spec → v0.1.1.
+7. **Dogfood pivot.** Operator: host the design docs as an RFC collection to review
+   in the tool. Investigated: app.json content=`ben/ohm-rfc` (dev archive) vs live
+   render repos (`ohm-content`/`ecomm-content` via rfc-registry). First attempt: a
+   `specs` collection under the `ohm` project in `ohm-content` (commit 85edd17),
+   reconciler picked it up (~140s) → all 7 docs live, flipped public. Added §4.5
+   D-DISCOVER (content-repo webhook → refresh_registry) at operator request →
+   v0.1.2. Decision #1: in-tool (then ohm-content) canonical; removed local copy.
+8. **"Not seeing it" → separate project.** Operator wanted specs separate from OHM.
+   Constraint: content_repo must be in `wiggleverse` org. Created
+   `wiggleverse/rfc-app-content` (Gitea API — token now has org scope), seeded all
+   7 docs as its default collection, registered `rfc-app` project in rfc-registry
+   (00aa0be), hid the nested ohm/specs (unlisted). Re-synced canonical to
+   rfc-app-content. Spec → v0.1.4 (added G-13 no-prune, G-14 webhook-non-default,
+   **G-15 blocking: branch/edit subsystem not three-tier-aware**).
+9. **G-15 discovery (headline).** "Left blank by the proposer" + blank canonical
+   body traced to `api_branches.py` `_repo_for`/`_file_path_for` hardcoding the
+   default project's `rfcs/<slug>.md`. §22 migrated reads, not writes. Captured as
+   blocking; handed off a fix prompt. Operator paused session.
+10. **Resumed: G-15 fixed.** Operator fixed in a separate session → v0.53.0 (PR #47)
+    + deployed to OHM. Verified: collection-scoped body routes render (rfc-app
+    40221 chars; ohm/specs 36979).
+11. **Start Contributing → "Branch not found."** Diagnosed: slug-only
+    `start-edit-branch` + `_require_rfc(slug).fetchone()` picks arbitrarily among
+    the **duplicate** slug (ohm/specs + rfc-app). Fix = remove the duplicate.
+    No in-app prune (G-13) → did a guarded prod-DB prune over IAP SSH (VM has no
+    sqlite3; used `sudo python3`), backed up to `ohm-app.db.bak-prespecs`, deleted
+    7 `cached_rfcs` + 1 `collections` row; removed ohm-content/specs git (8d7e974).
+    Verified slug unique, OHM dir back to `default`, Start Contributing works
+    (logs: edit branch cut in rfc-app-content, 200).
+12. **Highlight→Ask does nothing.** Traced to RFCView rendering RFCDiscussionPanel
+    (not ChatPanel) on canonical `main` → AI "Ask" has no surface (RFCView.jsx:911-915);
+    logs confirm no chat turn fired. Not collection-specific. Proposed Option B
+    (Ask auto-starts contributing then chats); operator chose B → handed off a prompt.
+13. **Finalize.**
+
+## Cut state
+
+- **Spec canonical & live:** `rfc-app-content/rfcs/2026-06-08-scoped-admin-ia.md`
+  v0.1.4 — https://rfc.wiggleverse.org/p/rfc-app/c/rfc-app/e/2026-06-08-scoped-admin-ia
+- **Live infra (kept):** `rfc-app` project (registry 00aa0be) + `wiggleverse/rfc-app-content`
+  repo (7 docs). Nested ohm/specs fully removed (git + DB). OHM untouched otherwise.
+- rfc-app session repo: clean `main`, nothing to land.
+- OHM live at v0.53.0 (G-15 deployed).
+
+## Deferred decisions / notable autonomous actions
+
+- **Prod DB surgery (live write):** pruned the ohm/specs duplicate directly on the
+  VM with a prior backup. Reversible (re-seedable) but flagging as a prod write.
+- **Created live infra** (rfc-app-content repo + rfc-app project, public). Kept.
+- **submit-spec to ohm-rfc/specs/ intentionally SKIPPED** to honor decision #1
+  (rfc-app-content is the single source of truth; submitting would diverge). The
+  spec is published canonically in-tool, not left local. Operator can request the
+  pipeline archive copy if wanted.
+
+## Brainstorming artifact
+
+Spec produced ✅ — published canonically to `rfc-app-content` (live-rendered),
+NOT to `ohm-rfc/specs/` (decision #1). Artifact guard satisfied; submit-spec
+deliberately skipped (recorded above).
+
+## Coding follow-ups handed off (separate planning-and-executing sessions + deploy)
+
+1. **Option B** — canonical-view "Ask" auto-cuts an edit branch then runs the
+   question there (RFCView; reuse handleStartContributing). Full prompt delivered.
+2. **G-5 write-family residual** — `start-edit-branch`/`promote-to-branch` still
+   slug-only; finish §22 write-family collection-scoping.
+
+## Next-session prompt
+
+```
+/wgl-brainstorming Resume the Scoped Admin IA spec (canonical: rfc-app-content/
+rfcs/2026-06-08-scoped-admin-ia.md, live at rfc.wiggleverse.org/p/rfc-app/c/rfc-app/
+e/2026-06-08-scoped-admin-ia). Fold in in-tool review feedback and work the open
+threads: split out the §9 LLM-context *consumption* design (retrieval + permission/
+exfiltration model) as its own spec; decide collection `type` elimination (§22.4a).
+Then kick off S0 (SPEC §22 amendments) when ready to build. The Option B (canonical-
+view Ask) and G-5 write-family fixes are queued as separate coding sessions.
+```

ohm/0090/SESSION-0090.0-TRANSCRIPT-2026-06-08T20-30--INPROGRESS.md

@@ -1,48 +0,0 @@
-# Session 0090.0 — Transcript
-
-> App: ohm
-> Start: 2026-06-08T20-30 (PST)
-> Type: brainstorming
-> Status: **PLACEHOLDER — claimed at session start; finalized at session end.**
->
-> This file reserves session ID 0090 for ohm. The driver replaces this
-> body with the full transcript and renames the file to its final
-> SESSION-0090.0-TRANSCRIPT-2026-06-08T20-30--<end>.md form at session end.
-
-## Launch prompt
-
-```
-Brainstorm and spec a scoped Admin information architecture for the
-three-tier model (deployment → project → collection), and the
-collection-management surfaces that hang off it.
-
-Problem: §22 delivered scoped roles ({owner, contributor} at {global,
-project, collection}) but the admin *page* IA never followed. Today
-/admin is mounted only at deployment/site scope (App.jsx:348), and it
-mixes grains that don't belong together:
-  - Retired RFCs (a collection-grained concept) live in the global,
-    site-owner-only admin (Admin.jsx:49–54, §13.7) — wrong scope.
-  - Graduation queue is already project-flavored (useProjectId()) yet
-    also sits at site level.
-  - Create-project / create-collection actions exist and work
-    (POST /api/projects, POST /api/projects/<id>/collections; modals in
-    CreateProjectModal.jsx / Directory.jsx) but are only reachable via
-    the multi-item directories, which the N=1 landing logic
-    (DeploymentLanding, App.jsx:448) redirects past — so an Owner on a
-    single-project/single-collection deployment has no UI path to manage
-    or create siblings. Effectively API-only today.
-  - In-app metadata field-schema config is deferred (decision D8 in
-    docs/design/2026-06-06-configurable-collection-metadata.md): a
-    collection's `fields:` are edited in .collection.yaml in git, with
-    no in-app surface. This is logically a Collection-Admin capability.
-
-Goal: produce a Solution-Design spec for a coherent Site Admin / Project
-Admin / Collection Admin IA. Don't write code this session.
-
-```
-
-## Deferred decisions
-
-_Autonomous-mode low-confidence calls the driver made and would have
-liked operator input on. Appended as the session runs; surfaced at
-finalize. Empty if none._