docs: restructure into rfc-app 'docs' collection (Maker Collective)

Move the two Maker Platform memos into docs/rfcs/ with minimal entry
frontmatter (slug/title/state) and add docs/.collection.yaml (type:
document, public) so the rfc-app registry mirror surfaces them as the
'docs' collection of the new maker-collective project.

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

docs/.collection.yaml

@@ -0,0 +1,4 @@
+# §22.4a collection manifest — read by the registry mirror.
+type: document
+visibility: public
+name: Docs

docs/rfcs/maker-platform-pr-faq.md

@@ -1,3 +1,19 @@
+---
+slug: maker-platform-pr-faq
+title: "Maker Platform — PR-FAQ"
+state: super-draft
+id: null
+repo: null
+proposed_by: ben.stull@wiggleverse.org
+proposed_at: '2026-06-15'
+graduated_at: null
+graduated_by: null
+owners:
+- ben.stull
+arbiters: []
+tags: []
+---
+
 # Wiggleverse Maker Collective - A Platform for Makers to Connect — PR-FAQ
 
 > **What this doc is.** An Amazon-style **PR-FAQ** ("working backwards") version of

docs/rfcs/maker-platform-strategy.md

@@ -1,3 +1,19 @@
+---
+slug: maker-platform-strategy
+title: "Maker Platform — Strategy & Architecture"
+state: super-draft
+id: null
+repo: null
+proposed_by: ben.stull@wiggleverse.org
+proposed_at: '2026-06-15'
+graduated_at: null
+graduated_by: null
+owners:
+- ben.stull
+arbiters: []
+tags: []
+---
+
 # Maker Platform — Strategy & Architecture
 
 A working memo distilling the thinking so far. It serves makers in general, but launches into one dense community first (the *beachhead*, §2/§5). The aim is to keep two doors open — a paid consultancy that's real today, and an option on a larger network play — without over-committing to the second before the evidence justifies it.