feat: add reviews content collection

Move all 24 review entries from skills-review/catalog.js +
skills-review/submitted-catalog.js into a typed Astro content collection at
src/content/reviews/. Each entry is a Markdown file with frontmatter for the
review metadata (id, author, focus, wins, improve, extras, name, description)
and a body that holds the 'improved' SKILL.md content.

Re-point scripts/build-skill-review.mjs at the new collection. The generator
reads each .md file, parses its YAML frontmatter, and writes
skill-reviews/improved/{id}/SKILL.md in the same shape the legacy catalog
produced — verified byte-identical via 'git diff --exit-code skill-reviews/'.

The 'name' field is preserved separately from 'id' because two entries
renamed the skill during review (id angular-accessibility-root → name
angular-accessibility; id confectionary-skill-hub → name confectionery-orders).
Without it the generator output would drift on those two files.

Does not yet delete skills-review/catalog.js or submitted-catalog.js —
verify.mjs and the legacy review-desk page both still read them, so they
stay as a mirror until task 16 rewires the page to the collection. Adding a
new submission today requires editing both the .md file (new source of
truth) and the legacy catalog.js (until task 16).

Done-when:
- 24 entries under src/content/reviews/ ✓
- verify.mjs's id:' count assertion still passes ✓
- git diff --exit-code skill-reviews/ clean after regenerating ✓
- astro check passes (22 files: 0 errors, 0 warnings, 2 hints) ✓

Co-Authored-By: Claude Code <noreply@anthropic.com>

src/content/reviews/confectionary-skill-hub.md

@@ -0,0 +1,50 @@
+---
+author: 'Diego Moreira'
+description:
+  'Create or prepare a confectionery order from confirmed customer and item
+  details. Use when a user asks to register an order or counter sale; confirm
+  before sending it to an external system.'
+extras:
+  'Add `references/recipe-schema.md` and `references/order-schema.md`; test
+  invalid quantities and missing delivery details.'
+focus: 'Define recipe and order workflows for a confectionery domain.'
+id: 'confectionary-skill-hub'
+improve:
+  - 'This is a catalog of three capabilities, not one discoverable skill; split
+    recipe creation, recipe search, and order creation into packages.'
+  - 'Add valid frontmatter and state the system of record, validation rules, and
+    mutation approval boundary.'
+  - 'Move JSON schemas to focused references so only the relevant workflow
+    loads.'
+name: 'confectionery-orders'
+path: '../submitted-skills/Diego%20Moreira/skills/confectionary-skill-hub/SKILL.md'
+status: 'Split required'
+title: 'Confectionery skill hub'
+wins:
+  - 'Useful domain vocabulary and input shapes.'
+  - 'Concrete examples make the intent easy to understand.'
+---
+
+# confectionery-orders
+
+## Inputs
+
+Customer, pickup or delivery choice, items, quantities, prices, and optional
+discount.
+
+## Workflow
+
+1. Validate required fields and positive quantities.
+2. Calculate the proposed total and show a concise order summary.
+3. Ask for confirmation before creating or transmitting an order.
+4. Return the saved identifier or a clearly labeled draft.
+
+## Rules
+
+- Do not invent recipe availability, prices, addresses, or customer details.
+- Keep payment and personal data out of logs.
+- Read `references/order-schema.md` when mapping to the order system.
+
+## Output
+
+Return a valid order payload plus validation warnings and confirmation state.