Remove legacy infrastructure, keep only shared rule contracts

Deleted: demo app, designsync/exports bundle system, bible meta-docs,
theme CSS, scaffolds, examples, empty pattern placeholders, go.mod,
CHANGELOG, VERSIONING

Kept: kit/patterns/*/contract.md (all engineering rules),
kit/ai/claude/CLAUDE.template.md, CLAUDE.md, AGENTS.md, README.md

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

CLAUDE.md

@@ -1,17 +1,8 @@
-# UI Design Code — Instructions for Claude
+# Bible — Instructions for Claude
 
-Read and follow the project Bible before making any changes:
+This repository is the shared engineering rules library for all projects.
 
-**[`bible/README.md`](bible/README.md)**
-
-The Bible is the single source of truth for architecture, public integration contracts,
-bundle manifests, and reusable pattern conventions.
-
-Every significant architectural decision must be recorded in
-[`bible/decisions/10-decisions.md`](bible/decisions/10-decisions.md).
-
-If a change affects `kit/`, `exports/`, or `tools/designsync`, update the relevant Bible
-docs and `CHANGELOG.md` in the same change set.
-
-Do not expand the repository scope beyond the currently approved work area unless the user
-explicitly requests that expansion.
+Rules live in `kit/patterns/` as `contract.md` files. When adding or updating a rule:
+- Find the relevant existing contract and edit it, or create a new `kit/patterns/<topic>/contract.md`.
+- Do not create rules outside `kit/patterns/`.
+- Do not expand scope beyond engineering rules and patterns.