add ohm/0083/SESSION-0083.0-TRANSCRIPT-2026-06-06T01-49--2026-06-06T07-59.md + replace placeholder/variant SESSION-0083.0-TRANSCRIPT-2026-06-06T01-49--2026-06-06T02-17.md

ohm/0083/SESSION-0083.0-TRANSCRIPT-2026-06-06T01-49--2026-06-06T02-17.md

@@ -1,140 +0,0 @@
-# Session 0083.0 — Transcript
-
-> App: ohm
-> Start: 2026-06-06T01-49 (PST)
-> End: 2026-06-06T02-17 (PST)
-> Type: coding
-> Mode: autonomous (yolo)
-> Driver: Ben Stull (+ Claude Opus 4.8)
-
-## Launch prompt
-
-```
-Finish §22 S6 remainder: request-to-join + cross-collection inbox (§22.8), then
-per-type surfaces (§22.4a items 1&3). Build by analogy to shipped §28
-contribution_requests + S4 memberships.grant.
-```
-
-## Outcome
-
-The §22 S6 remainder is complete; the deployment→project→collection three-tier
-model is now realized in both code and `SPEC.md`. Two landings:
-
-1. **§22.8 request-to-join + the cross-collection inbox — shipped v0.46.0**
-   (PR #24, `origin/main` = `1c17fec`).
-2. **Per-type surfaces (§22.4a items 1 & 3) — spec pass done** (PR #25,
-   `origin/main` = `b7e23a0`), the discovery/spec pass the goal called for,
-   leaving implementation to slices S7a–S7c.
-
-## Pre-state
-
-- `origin/main` = `0140150` (S6 core, v0.45.0): the SPEC merge, per-collection
-  `enabled_models` (mig 031), the type-driven entry noun (§22.4a item 2).
-- Two S6 items were deferred at v0.45.0 as "wanting a discovery/spec pass first":
-  the per-type surfaces (§22.4a items 1 & 3) and request-to-join (§22.8).
-- Clean tree on `main`, fully pushed. Three other ohm sessions (0079/0080/0081)
-  in flight (unfinalized placeholders) — noted, proceeded concurrently per the
-  autonomous default. (A concurrent session's `e86fc65 Discovery spec:
-  configurable collection metadata` landed on `main` mid-session; merges stayed
-  clean.)
-
-## The arc
-
-**1. Understand (read the spec + the analogues).** Read `SPEC.md` §22.8 / §22.11
-(request-to-join surfaces to "the scope's Owners across the subtree", accepting
-writes the `memberships` row; one deployment-wide inbox) and the design doc Part
-E S6 framing. Mapped the two analogues: §28 `contribution_requests`
-(`api_contributions.py`, migration 024, the per-owner notification fan-out +
-accept/decline lifecycle) and S4 `memberships` (`api_memberships.py` /
-`memberships.py` — `grant` + the broader-scope-supersedes prune, the
-`can_invite_at_{project,collection}` gates). Confirmed the engine seam: a join
-request targets a `(scope_type, scope_id)` pair (the `memberships` vocabulary
-minus `global`), and accept grants a scope role instead of minting an RFC invite.
-
-**2. §22.8 implementation (backend).**
-- Migration `032_join_requests.sql` — additive table (no rebuild), `scope_type ∈
-  {project, collection}`, `requested_role`/`granted_role`/`status` enums, a
-  one-open-per-`(scope, requester)` partial unique index.
-- `auth.effective_role_at_scope(user, scope_type, scope_id)` — the scope-grain
-  twin of `effective_scope_role` (which only keys on a collection), folding
-  global→project for a project target. Drives the dup-member gate + the
-  `can_request_join` flag.
-- `notify`: `_scope_owner_user_ids` (upward Owner enumeration = the
-  cross-collection inbox), `fan_out_join_request`, `notify_join_decided`, three
-  `render_summary` cases.
-- `api_join_requests.py` — `GET join-target` / `POST join-requests` / `POST
-  {id}/accept` / `{id}/decline` under `/api/scopes/{scope_type}/{scope_id}/`.
-  Key decision: the request POST does **not** require the scope be readable —
-  that is precisely how one joins a *gated* scope they were told about (§22.8).
-  Registered the router in `api.py`.
-
-**3. §22.8 implementation (frontend).** `api.js` join verbs; `JoinRequestModal`;
-the `viewer.can_request_join` flag added to the project + collection viewer
-blocks in `api_collections.py`; a "Request to join" affordance in
-`CollectionDirectory` (project scope) and the `Catalog` footer (collection
-scope); the actionable `JoinRequestRow` in `Inbox.jsx` (the cross-collection
-inbox surface, which is automatic once the fan-out reaches the right Owners).
-
-**4. Tests + release.** `test_join_requests_vertical.py` (11: cross-collection
-fan-out, project vs collection reach, accept-writes-membership, role-narrowing,
-decline, dup-409, existing-member-409, non-owner-403, sibling-collection-403,
-unknown-scope-404, eligibility) + `test_migration_032_join_requests.py` (5).
-Frontend `api.joinrequests.test.js` (4) + two `CollectionDirectory` cases.
-**Backend 546 / frontend 36 green; frontend build clean.** Bumped VERSION +
-`package.json` → 0.46.0, CHANGELOG 0.46.0 entry ("no upgrade steps" — additive).
-Branch `feat/s6-join-requests` → Gitea-API PR #24 → merged → `main`.
-
-**5. Per-type surfaces — the spec pass.** The goal flagged these as wanting a
-discovery/spec pass first (no BDD scenarios existed in Part C, which is
-role-focused). Grounded in the current type plumbing (`registry.VALID_TYPES`,
-the lenient type-agnostic `entry.py`) and wrote
-`docs/design/2026-06-06-per-type-surfaces.md`: Part A (item 1 — the per-type
-frontmatter schema via a new `entry_schema.py` validator), Part B (item 3 — the
-`specification` Releases view + the `bdd` scenario/coverage views), Part C (BDD
-acceptance scenarios `@S7a/@S7b/@S7c`), Part D (a 3-slice additive,
-engine-preserving delivery plan + open product questions). Added a
-forward-pointer + shipped/spec'd status to the three-tier doc's S6 bullet.
-Branch `spec/s7-per-type-surfaces` → Gitea-API PR #25 → merged → `main`.
-
-## Cut state
-
-- `origin/main` = `b7e23a0`; local `main` clean and synced; no open PRs; both
-  feature branches deleted on merge.
-- VERSION 0.46.0 (mirrored in `frontend/package.json`).
-- Backend 546 / frontend 36 green; frontend build clean.
-
-## Deferred decisions
-
-Low-confidence / autonomous calls made without operator input:
-
-- **Request POST is not readability-gated.** Deliberate per §22.8 ("a user who
-  knows a *gated* scope exists requests to join it") — you cannot require read on
-  a scope that is invisible to the requester. Guarded instead by signed-in +
-  granted + not-already-a-member + dup-pending. Alternative considered: require
-  readability (would make gated joins impossible via the API). Confident.
-- **`join_requests.scope_type` excludes `global`.** A deployment isn't a thing
-  one "discovers and joins" (§22.8 names a project/collection). Confident.
-- **Route shape `/api/scopes/{scope_type}/{scope_id}/…`.** Clean and mirrors the
-  `memberships` scope vocabulary; §17 is illustrative and doesn't pin the
-  contribution/membership routes, so no SPEC change. Reasonable.
-- **Accept may narrow the requested role** (optional `role` body, default =
-  requested). Gives the Owner control rather than forcing the asked-for role;
-  within the Owner's grant reach. Minor.
-- **Treated the per-type surfaces as a *spec-doc* deliverable, not code.** The
-  goal said they "want a discovery/spec pass first"; I produced the spec pass
-  (design doc + BDD scenarios + slicing) and left implementation to S7a–S7c
-  rather than coding surfaces that still carry open product questions. This is
-  the call most worth the operator's eye — if the intent was "implement them
-  too," S7a (schemas) is unblocked and ready; S7b/S7c need the D.1 questions
-  settled first (a discovery session may fit).
-
-## Next session
-
-```
-/goal implement S7a — per-type frontmatter schema (§22.4a item 1), per docs/design/2026-06-06-per-type-surfaces.md Part A + Part C @S7a: a backend/app/entry_schema.py validator, the new optional Entry fields (specification: spec_version/lifecycle/supersedes; bdd: feature/verifies), write-boundary enforcement on propose/edit/PR-merge, and the §7 catalog "malformed frontmatter" flag — additive, non-breaking, document/N=1 unchanged.
-```
-
-S7b (specification releases) + S7c (bdd surfaces) follow once their Part D.1 open
-questions (release identity vs `spec_version` pinning; `verifies` ref grammar /
-anchors; whether `lifecycle` enters the state machine) are settled — possibly a
-discovery session.

ohm/0083/SESSION-0083.0-TRANSCRIPT-2026-06-06T01-49--2026-06-06T07-59.md

@@ -0,0 +1,143 @@
+# Session 0083.0 — Transcript
+
+> App: ohm
+> Start: 2026-06-06T01-49 (PST)
+> End: 2026-06-06T07-59 (PST)
+> Type: coding
+> Mode: autonomous (yolo)
+> Driver: Ben Stull (+ Claude Opus 4.8)
+
+## Launch prompt
+
+```
+Finish §22 S6 remainder: request-to-join + cross-collection inbox (§22.8), then
+per-type surfaces (§22.4a items 1&3). Build by analogy to shipped §28
+contribution_requests + S4 memberships.grant.
+```
+
+## Outcome
+
+The §22 S6 remainder is complete; the deployment→project→collection three-tier
+model is now realized in both code and `SPEC.md`. Then two follow-up tasks at the
+operator's direction: a roadmap question, and a roadmap cleanup.
+
+1. **§22.8 request-to-join + the cross-collection inbox — shipped v0.46.0**
+   (PR #24, `origin/main` = `1c17fec`).
+2. **Per-type surfaces (§22.4a items 1 & 3) — spec pass done** (PR #25,
+   `origin/main` = `b7e23a0`) — *subsequently superseded* (see §Follow-ups).
+3. **OHM roadmap Phase G refreshed** (ohm-rfc PR #12, `b4a6943`).
+
+## Pre-state
+
+- `origin/main` (rfc-app) = `0140150` (S6 core, v0.45.0): the SPEC merge,
+  per-collection `enabled_models` (mig 031), the type-driven entry noun.
+- Two S6 items deferred at v0.45.0 as "wanting a discovery/spec pass first": the
+  per-type surfaces (§22.4a items 1 & 3) and request-to-join (§22.8).
+- Clean tree on `main`, fully pushed. Three concurrent ohm sessions
+  (0079/0080/0081) in flight (unfinalized placeholders) — noted, proceeded.
+
+## The arc — §22.8 (the shipped feature)
+
+**1. Understand.** Read `SPEC.md` §22.8 / §22.11 and the design-doc Part E S6
+framing; mapped the two analogues — §28 `contribution_requests`
+(`api_contributions.py`, mig 024) and S4 `memberships` (`api_memberships.py` /
+`memberships.py`, the `grant` + broader-scope-supersedes prune + the
+`can_invite_at_{project,collection}` gates). Engine seam: a join request targets
+a `(scope_type, scope_id)` pair (the `memberships` vocabulary minus `global`),
+and accept grants a scope role instead of minting an RFC invite.
+
+**2–3. Build (backend + frontend).**
+- Migration `032_join_requests.sql` (additive; one-open-per-(scope,requester)).
+- `auth.effective_role_at_scope` — scope-grain twin of `effective_scope_role`,
+  folding global→project for a project target.
+- `notify`: `_scope_owner_user_ids` (upward Owner enumeration = the
+  cross-collection inbox), `fan_out_join_request`, `notify_join_decided`, 3
+  `render_summary` cases.
+- `api_join_requests.py` — `/api/scopes/{scope_type}/{scope_id}/` (join-target /
+  request / accept / decline). The request POST is **not** readability-gated
+  (that's how one joins a *gated* scope). Registered in `api.py`.
+- Frontend: `api.js` verbs; `JoinRequestModal`; `viewer.can_request_join` on the
+  project + collection viewer blocks; "Request to join" in `CollectionDirectory`
+  + the `Catalog` footer; the actionable `JoinRequestRow` in `Inbox.jsx`.
+
+**4. Tests + release.** `test_join_requests_vertical.py` (11) +
+`test_migration_032` (5); frontend `api.joinrequests.test.js` (4) + two
+`CollectionDirectory` cases. **Backend 546 / frontend 36 green; build clean.**
+VERSION + package.json → 0.46.0; CHANGELOG 0.46.0 ("no upgrade steps"). Branch
+`feat/s6-join-requests` → Gitea-API PR #24 → merged.
+
+## The arc — per-type surfaces (spec pass, then superseded)
+
+The goal flagged these as wanting a discovery/spec pass first. Wrote
+`docs/design/2026-06-06-per-type-surfaces.md` (per-type frontmatter schema via a
+new `entry_schema.py` validator; `specification` Releases view; `bdd`
+scenario/coverage views; BDD scenarios `@S7a/@S7b/@S7c`; a 3-slice plan).
+Branch `spec/s7-per-type-surfaces` → PR #25 → merged.
+
+**Superseded same day.** A parallel session (0079–0081) was concurrently writing
+`docs/design/2026-06-06-configurable-collection-metadata.md`, which **explicitly
+supersedes** the per-type-surfaces draft (its D9/D11): the schema model moves from
+*type-driven* to **collection-configured `fields:`** + per-entry `.meta.yaml`
+**sidecars** + faceted filtering. So the per-type-surfaces direction (and the
+`Next /goal: implement S7a` I recorded) is now void; the successor's SLICE-0
+will mark `per-type-surfaces.md` superseded + amend SPEC §22.4a.
+
+## Follow-ups (post the first finalize)
+
+The session was finalized once at 02:17, then continued at the operator's
+direction:
+
+- **Q: "what are all items on the roadmap?"** Read the canonical
+  `ben.stull/ohm-rfc/ROADMAP.md` (43 numbered items, Phases A–G + a version-targets
+  table). Reported: ~32/43 shipped; what remains is item 22 (consent copy,
+  operator-blocked), the §22 per-type surfaces (then being reworked), and the
+  v1-gated deploy-safety arc (37–43), plus operational cleanup (33–35). Flagged
+  the **Phase G section as stale** (didn't reflect S1–S6 or §22.8 shipping).
+
+- **Roadmap cleanup (ohm-rfc PR #12, merged `b4a6943`).** Per the operator —
+  *"there won't be types; there will be configurable metadata per collection …
+  do NOT add to roadmap yet, but clean up based on it being the most up-to-date
+  plan."* Four surgical Phase-G edits, **no new items added**, items 1–43 +
+  version-targets table untouched: (1) a 2026-06-06 status note (series continued
+  past v0.39.0 → three-tier, re-sliced S1–S7); (2) slice-status refresh (S1–S6 +
+  §22.8 shipped; old M6 = invite + request-to-join; old M7 = enabled_models +
+  SPEC merge; M4 effectively covered by ohm+ecomm + the two-project test); (3)
+  old **M5 → SUPERSEDED** by configurable collection metadata (successor draft
+  *in flight, not yet roadmapped*; bdd coverage = future `ref` surface); (4)
+  cutover block fixed (0.31.5→0.39.0 cutover done, OHM pinned 0.39.0; new gap =
+  v0.40–v0.46 undeployed). Opened for review, then merged on operator request.
+
+## Cut state
+
+- **rfc-app:** my work fully landed — `origin/main` = `b7e23a0` (v0.46.0 + the
+  per-type-surfaces doc), branches deleted. ⚠️ At finalize the shared checkout's
+  `main` was **ahead-2 + untracked `corpus-tree` spec files** — that is the
+  **parallel session's** WIP (the §5.4 worktree hazard); **left entirely
+  untouched** (not mine to commit/push).
+- **ohm-rfc:** clean on `main` = `b4a6943` (roadmap PR #12 merged), branch deleted.
+- VERSION 0.46.0. Backend 546 / frontend 36 green.
+
+## Deferred decisions / autonomous calls
+
+- **§22.8 request POST not readability-gated** — deliberate (§22.8: you join a
+  *gated* scope you were told of). Confident.
+- **`join_requests.scope_type` excludes `global`** — a deployment isn't "joined."
+- **Route shape `/api/scopes/{scope_type}/{scope_id}/…`** — §17 is illustrative,
+  doesn't pin these routes; no SPEC change.
+- **Per-type surfaces delivered as a spec doc, not code** — the goal said "want a
+  spec pass first." (Now moot — superseded by configurable metadata.)
+- **Declined to finalize session 0081** when a finalize-on-goal hook misfired onto
+  it — 0081 is a *different* (live/parallel) discovery session; finalizing it
+  would fabricate or clobber another driver's record. Left 0079/0080/0081 alone;
+  operator later confirmed ≥1 is the live session they're co-writing with.
+- **Roadmap PR opened for review (not auto-merged)** then merged on operator's
+  "Merge it" — the supersession wording was theirs to steer.
+
+## Next session
+
+The per-type-surfaces plan is superseded; the next move is gated on the parallel
+session's configurable-collection-metadata spec settling.
+
+```
+/goal await the configurable-collection-metadata spec landing (parallel session finishing docs/design/2026-06-06-configurable-collection-metadata.md), then implement SLICE-0 — amend SPEC §22.4a so the entry schema is collection-configured .meta.yaml sidecar fields not type-driven frontmatter; defer item-3 type surfaces (record bdd coverage as a future ref surface); mark 2026-06-06-per-type-surfaces.md superseded; §20 changelog (doc-only) — then SLICE-1 (sidecar storage + dual-read parser + idempotent frontmatter→sidecar migration + malformed-metadata catalog flag). NOTE: that spec is parallel-owned and shares this checkout — use an isolated worktree (§5.4) before starting code.
+```