§22 S2: release v0.41.0 — create & navigate a second collection (@S2)

Minor, non-breaking: named collections via .collection.yaml, create-collection
endpoint, collection-scoped serve/propose, and the /p/<project>/ collection
directory. Completes acceptance @S2 (C3.6). 478 backend + 26 frontend green.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

docs/design/2026-06-05-three-tier-projects-collections.md

@@ -549,7 +549,8 @@ means the deployment runs and either gains a capability or provably loses none
   exactly as before, now with a real collection layer and one extra path segment.
   **Completes:** `@S1` (the single-collection / single-project redirect skips).
 
-- **S2 — Create & navigate a second collection.** Teach the registry mirror to
+- **S2 — Create & navigate a second collection.** *(Shipped v0.41.0.)* Teach the
+  registry mirror to
   read `.collection.yaml`; add the bot-commit-wrapped **create-collection**
   endpoint (authorized by existing deployment owner/admin for now — the scoped
   role surface lands in S3); the project collection-directory at `/p/<project>/`;