Validate Context Rules

Check .claude/rules/subsystem-*.md files match current codebase.

Workflow

For each subsystem-*.md rule file:

1. Read the rule — Extract type names, module paths, function names, error variants
2. Grep the codebase — Verify each reference exists
3. Check for new additions — Find new public types/modules not in rule
4. Report — List stale references + missing additions

Subsystem Rules to Check

Verification Commands

bash
1# Check if a type still exists
2grep -r "pub struct TypeName" crates/
3grep -r "pub enum TypeName" crates/
4
5# Check if a module still exists
6ls crates/ocx_lib/src/module_name/
7
8# Check for new public types not in the rule
9grep -rn "^pub struct\|^pub enum\|^pub trait" crates/ocx_lib/src/subsystem/ | grep -v test

Output Format

markdown
1## Context Validation Report
2
3### subsystem-oci.md
4- OK: IndexImpl, SelectResult, RemoteIndex, ...
5- STALE: [type] — renamed to [new_name] or removed
6- MISSING: [new_type] — not documented in rule
7
8### subsystem-file-structure.md
9...

When to Run

• After big refactors
• Before major feature branches
• Part of /code-check audits
• Monthly