update ohm/0082/SESSION-0082.0-TRANSCRIPT-2026-06-06T01-09--INPROGRESS.md

ohm/0082/SESSION-0082.0-TRANSCRIPT-2026-06-06T01-09--INPROGRESS.md

@@ -11,10 +11,96 @@
 
 ## Launch prompt
 
-_(launch prompt not captured at claim time)_
+`/goal next` — resume the stored next-goal recorded at session 0078's finalize:
+**S6, the final §22 three-tier slice** (per-type frontmatter/surfaces keyed on
+collection `type`, request-to-join + cross-collection inbox, per-collection
+`enabled_models`, the registry + `.collection.yaml` format in `docs/DEPLOYMENTS.md`,
+two-project/multi-collection e2e, the §20.4 changelog, and the **SPEC merge**
+applying Part A + Part D and landing the S3 §B.1/§B.3 keystone reinterpretation).
+Per `docs/design/2026-06-05-three-tier-projects-collections.md` Part E (S6).
+
+## Plan
+
+S6 is large — seven deliverables, three of them net-new features. Decomposed into
+reviewable branch→PR→merge increments on `origin` (git.wiggleverse.org), ordered
+keystone-first:
+
+- **PR-A — SPEC merge (keystone).** Write a fresh §22 (Part A three-tier model)
+  into `SPEC.md`; apply Part D amendments in place to §1/§2/§5/§6; land the S3
+  §B.1/§B.3 keystone reinterpretation; document the `projects.yaml` +
+  `.collection.yaml` format in `docs/DEPLOYMENTS.md`. Docs-only, no migration —
+  fully realizes the three-tier model in the binding contract.
+- **PR-B — per-collection `enabled_models`.** Migration 031 adds `collections.config_json`;
+  parse from `.collection.yaml`; surface in the collection API; thread to the
+  provider/model layer.
+- **PR-C — per-type frontmatter + surfaces** keyed on the collection's `type`.
+- **PR-D — request-to-join + cross-collection inbox.**
+- **PR-E — two-project/multi-collection e2e + §20.4 changelog + version bump**
+  (the release wrap for the whole §22 series).
+
+## Progress (checkpoint)
+
+Branch `feat/s6-three-tier-final` off `main` (`b073738`). Commits so far:
+
+1. **`26f3680` — SPEC merge (keystone).** §22.1–§22.14 written into `SPEC.md`
+   (three-tier model, registry + `.collection.yaml`, unified roles, four-layer
+   union, the keystone §B.1/§B.3 reinterpretation); forward-pointer amendment
+   notes at §1/§2/§5/§6; `docs/DEPLOYMENTS.md` registry + manifest format.
+2. **`79a27a9` — per-collection `enabled_models` (§22.12).** Migration 031
+   (`collections.config_json`); manifest parse; `models_resolver`
+   project→collection narrowing chain; API surfacing. 9 vertical tests.
+3. **`839404d` — type-driven entry noun (§22.4a).** `collections.entry_noun`
+   source-of-truth map; surfaced on collection/directory/project APIs; Catalog +
+   ProposeModal chrome read it. 3 vertical tests.
+
+Gate after each: backend **528 passed**, frontend **30 passed** + build green.
+
+Remaining this session: a two-project/multi-collection integrative test, the
+§20.4 changelog + upgrade-steps, and the **v0.45.0** version bump (the release
+wrap). Then PR → merge on `origin`. Handoff (next goal): the OPEN type-module
+surfaces (per-type frontmatter schemas, specification release-planning, bdd
+scenario/coverage) and request-to-join + cross-collection inbox — both want a
+spec pass first.
 
 ## Deferred decisions
 
+- **S6 structure: single branch, single v0.45.0 release (autonomous call).** The
+  recorded goal bundles S6 as one slice spanning a major SPEC merge + three
+  net-new features + release. The repo's established pattern is one release per
+  slice (S1–S5 = 0.40.0–0.44.0), and the original plan said S6 "ships as one
+  minor at M7." So all of S6 lands on one branch `feat/s6-three-tier-final` with
+  structured per-deliverable commits and a single v0.45.0 release (VERSION +
+  CHANGELOG + §20.4 upgrade-steps in the final commit) — not 5 micro-releases or
+  5 coordinated PRs. The SPEC references v0.45.0 throughout accordingly.
+- **In-place §22.14 amendments vs. scattered notes (autonomous call).** Part D's
+  amendments are applied as a consolidated §22.14 subsection PLUS concise
+  forward-pointer blockquotes at §1/§2/§5/§6 (house style, cf. §1's v0.31.0
+  note) — rather than rewriting each section's body wholesale, which would be
+  far more invasive and risk breaking load-bearing cross-references mid-document.
+- **The three feature areas (enabled_models / type surfaces / request-to-join)
+  have no pre-written BDD scenarios** (Part C covers only role/invitation/empty-
+  state) and E.2 deferred "request-to-join nuances" + "per-type role labels" from
+  the first pass — so their detailed shape is designed this session against the
+  design doc's direction.
+- **Mid-session scope re-cut (autonomous call, after keystone + enabled_models
+  shipped).** S6's remaining items split by specification maturity. PR-B
+  (enabled_models) is fully specified by §22.12 → shipped. PR-C's *entry-noun
+  terminology* (§22.4a item 2: document→"RFC" / specification→"Spec" /
+  bdd→"Feature") is concrete and completable → doing it. But the FULL type-module
+  surfaces (§22.4a items 1+3: per-type frontmatter schemas, the `specification`
+  release-planning data model, the `bdd` scenario/coverage views) are flagged
+  OPEN in the design doc itself ("first proposals, to be pinned in the
+  type-surface slice"), and request-to-join + cross-collection inbox (PR-D) is a
+  whole subsystem E.2 deferred. Building those FULLY in one autonomous code
+  session, without their BDD specs, would be guessing at product shape — lower
+  quality than the team's discovery→spec→code flow. **Decision:** deliver the
+  well-specified, completable scope to a high bar (keystone SPEC merge ✅,
+  enabled_models ✅, entry-noun terminology), RELEASE it as v0.45.0 (the defining
+  S6 outcome — "§22 three-tier fully realized in SPEC.md"), and record a precise
+  next-goal for the genuinely-open type-module + membership-lifecycle work, which
+  wants a spec pass first. Honors "carry to done" for the completable scope
+  without rushing under-specified features.
+
 _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._
+finalize._