perf: add documentation review configuration

Author: zircote

.claude/documentation-review.local.md

@@ -0,0 +1,92 @@
+---
+# Documentation Review Configuration
+# Generated by /doc-setup on 2026-02-22
+
+doc_paths:
+  - spec/specification.md
+  - spec/assistant-adoption.md
+  - spec/schemas/assistant-adoption.schema.json
+  - spec/schemas/manifest.schema.json
+  - spec/assistants/*.json
+  - src/content/docs/**/*.mdx
+  - docs/plans/*.md
+  - blog/*.md
+
+ignore:
+  - node_modules/
+  - dist/
+  - .astro/
+  - "*.lock"
+  - "*.min.*"
+
+standards:
+  require_description: true
+  max_heading_depth: 4
+  require_code_examples: true
+  check_links: true
+  check_spelling: true
+  strictness: strict
+
+cross_validation:
+  spec_to_astro_sync: true
+  sync_pairs:
+    - source: spec/specification.md
+      targets:
+        - src/content/docs/specification/overview.mdx
+        - src/content/docs/specification/archive-format.mdx
+        - src/content/docs/specification/manifest.mdx
+        - src/content/docs/specification/component-types.mdx
+        - src/content/docs/specification/install-lifecycle.mdx
+        - src/content/docs/specification/lockfile.mdx
+        - src/content/docs/specification/portability.mdx
+        - src/content/docs/specification/lazy-loading.mdx
+        - src/content/docs/specification/appendices.mdx
+    - source: spec/assistants/*.json
+      targets:
+        - src/content/docs/assistants/*.mdx
+  schema_prose_validation: true
+  schema_pairs:
+    - schema: spec/schemas/manifest.schema.json
+      prose: spec/specification.md
+    - schema: spec/schemas/assistant-adoption.schema.json
+      prose: spec/assistant-adoption.md
+
+site_generator:
+  type: astro-starlight
+  config_path: astro.config.mjs
+
+api_docs:
+  openapi_path: null
+  asyncapi_path: null
+  generate_from_code: false
+
+output:
+  verbosity: detailed
+  format: markdown
+---
+
+# Project Documentation Notes
+
+## Architecture
+
+ccpkg documentation follows a three-layer pattern:
+
+1. **Canonical source**: `spec/specification.md` and `spec/assistant-adoption.md` are the normative specs. All prose authority lives here.
+2. **JSON schemas**: `spec/schemas/*.json` provide machine validation. Properties and types must match the prose spec.
+3. **Astro site**: `src/content/docs/` pages are generated/synced from canonical specs via `scripts/generate-spec-pages.mjs` and `scripts/generate-assistant-pages.mjs`. These should never diverge from the canonical source.
+
+## Generated files (review for freshness, not authoring)
+
+- `src/content/docs/assistants/*.mdx` — generated by `npm run generate:assistants` from `spec/assistants/*.json`
+- `src/content/docs/specification/*.mdx` — synced from `spec/specification.md` sections
+
+## MDX Compatibility
+
+Angle brackets (`<`, `>`) in spec markdown must be escaped as `&lt;`/`&gt;` for MDX compatibility, even inside code blocks within numbered lists.
+
+## Review priorities
+
+1. Spec-schema consistency: Do JSON schema fields match what the prose documents?
+2. Spec-Astro sync: Have Astro pages been regenerated after spec changes?
+3. Cross-references: Do internal links between spec sections resolve correctly?
+4. Data accuracy: Do assistant adoption specs match official host documentation?