Start the rebuild: note schema, vault kit and data migration

Phase 1 of the functional design plan.

- Move the old site into legacy/, unchanged, for reference. It still
  builds from there until cutover.
- Add packages/schema: the one definition of all 20 note types, with
  field titles and descriptions, note and vault checks, and JSON Schema
  export so later editing tools and the MCP server share it.
- Add vault-kit: Obsidian templates generated from the schema, and the
  Site guide for 24.01_PersonalWebsite.
- Add tools/migrate: turns the legacy JSON, collections, store data and
  page text into 545 Site folder notes and 84 images, and checks the
  result with the schema.

Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_012aSbo2D1qP8cMFQCykf7kx

vault-kit/24.01_PersonalWebsite/Site guide.md

@@ -0,0 +1,19 @@
+# Site guide
+
+Everything in the `Site` folder can appear on GregKilmer.com. Nothing outside
+it ever can.
+
+- **Going live.** A note is on the site only when its `publish` property is
+  true. Turn it off and the page comes down; nothing is deleted.
+- **New notes.** Use a template from `Site/_templates`. Each note type has its
+  own folder; the template's comments list the allowed values.
+- **Links.** Link notes the usual way, `[[Note name]]`. A post that links to
+  a make shows up on that make, its craft and the Workshop page.
+- **Status updates.** Add a note in `Now/` with a kind from `Now/_kinds`, a
+  date and the `[[note]]` it is about. The newest one per note wins.
+- **Images.** Put them in `Site/_attachments/` and link them by file name.
+- **Settings.** `_site.md`, `Now/_kinds.md` and `Store/_settings.md`.
+  Opening and closing store orders is one property in `Store/_settings.md`.
+
+If a change has a problem, the site keeps showing the last good version and
+the admin page explains what to fix.