fix(levelup): remove remaining .cdrs.json references

- Update specify.md to use .specify/memory/cdr.md
- Update README.md with new CDR flow and status values
- Update config-template.yml and extension.yml locations

Author: kanfil

extensions/levelup/README.md

@@ -37,7 +37,7 @@ Scan your codebase for patterns that could become team-wide directives:
 /levelup.init
 ```
 
-This creates proposed entries in `{TEAM_DIRECTIVES}/.cdrs.json` with status "proposed".
+This creates proposed CDRs in `{PROJECT}/.specify/memory/cdr.md` with status "Discovered" or "Proposed".
 
 ### 2. Clarify and Accept CDRs
 
@@ -71,22 +71,25 @@ This creates a draft PR with all accepted contributions.
 
 ## Context Directive Records (CDRs)
 
-CDRs are tracked in `{TEAM_DIRECTIVES}/.cdrs.json` and define:
+CDRs are stored in markdown format:
+
+- **Local**: `{PROJECT}/.specify/memory/cdr.md` - Working copy during discovery/clarification
+- **Approved**: `{TEAM_DIRECTIVES}/CDR.md` - Approved contributions tracked in team-ai-directives
+
+CDRs define:
 
 - **Target Module**: Where the contribution goes in team-ai-directives
 - **Context Type**: Rule, Persona, Example, or Skill
-- **Status**: discovered → proposed → accepted → active
-- **Evidence**: Links to code, commits, and discussions
+- **Status**: Discovered → Proposed → Accepted | Rejected
 
 ### CDR Status Values
 
 | Status | Description |
 |--------|-------------|
-| **discovered** | Inferred from codebase during brownfield analysis |
-| **proposed** | Suggested for review, awaiting validation |
-| **accepted** | Approved for implementation |
-| **active** | Merged to team-ai-directives and ready for use |
-| **deprecated** | No longer recommended (kept for history) |
+| **Discovered** | Inferred from codebase during brownfield analysis |
+| **Proposed** | Suggested for review, awaiting validation |
+| **Accepted** | Approved for implementation |
+| **Rejected** | Not approved (reason documented in CDR) |
 
 ## Configuration
 
@@ -105,8 +108,8 @@ Optional configuration in `.specify/extensions/levelup/levelup-config.yml`:
 ```yaml
 cdr:
   heuristic: "surprising"  # surprising | all | minimal
-  # CDR manifest location (relative to team-ai-directives root)
-  location: ".cdrs.json"
+  # CDR file location (local project)
+  location: ".specify/memory/cdr.md"
 
 skills:
   drafts_location: ".specify/drafts/skills"

extensions/levelup/commands/init.md

@@ -242,7 +242,7 @@ Run `{SCRIPT}` to set up the infrastructure:
 - Creates skills drafts directory at `.specify/drafts/skills/`
 - Returns JSON with `TEAM_DIRECTIVES`, `REPO_ROOT`
 
-The `.cdrs.json` file should already exist in team-ai-directives (created during init).
+The `.specify/memory/cdr.md` file will be created in the project directory.
 
 ### Phase 4: Load Existing Directives
 

extensions/levelup/commands/specify.md

@@ -34,11 +34,11 @@ Extract **Context Directive Records (CDRs)** from the **current feature specific
 **Input**:
 - Current feature spec, plan, tasks (from `specs/{feature}/`)
 - Optional: `trace.md` if generated by `/levelup.trace` (enriches CDR extraction)
-- Existing modules from `{TEAM_DIRECTIVES}/.cdrs.json` (if any)
+- Existing CDRs from `{REPO_ROOT}/.specify/memory/cdr.md` (if any)
 
 **Output**: 
-- New proposed modules added to `{TEAM_DIRECTIVES}/.cdrs.json` with status "proposed"
-- Enriched existing modules with feature-specific evidence
+- New proposed CDRs added to `{REPO_ROOT}/.specify/memory/cdr.md` with status "Discovered" or "Proposed"
+- Enriched existing CDRs with feature-specific evidence
 
 ## Role & Context
 
@@ -113,9 +113,9 @@ If artifacts are missing, note which are unavailable.
 
 **Objective**: Load modules to refine
 
-Read `{TEAM_DIRECTIVES}/.cdrs.json` and filter:
-- Status = "discovered" or "proposed"
-- Match user-specified module IDs if provided
+Read `{REPO_ROOT}/.specify/memory/cdr.md` and filter:
+- Status = "Discovered" or "Proposed"
+- Match user-specified CDR IDs if provided
 
 ### Phase 3: Enrich CDRs
 
@@ -182,12 +182,12 @@ Append evidence to CDR:
 - [ ] No issues reported
 ```
 
-### Phase 4: Update Modules
+### Phase 4: Update CDRs
 
-**Objective**: Write enriched modules to `.cdrs.json`
+**Objective**: Write enriched CDRs to `.specify/memory/cdr.md`
 
-Update `{TEAM_DIRECTIVES}/.cdrs.json`:
-- Add evidence metadata to module entries
+Update `{REPO_ROOT}/.specify/memory/cdr.md`:
+- Add evidence metadata to CDR entries
 - Update enrichment timestamp
 - Add enrichment source reference
 
@@ -231,11 +231,11 @@ Consider adding more context:
 
 | File | Description |
 |------|-------------|
-| `{TEAM_DIRECTIVES}/.cdrs.json` | Enriched Context Directive Records |
+| `{REPO_ROOT}/.specify/memory/cdr.md` | Enriched Context Directive Records |
 
 ## Notes
 
-- This command enriches modules, it doesn't change their status
+- This command enriches CDRs, it doesn't change their status
 - Status changes happen in `/levelup.clarify`
 - Works best with complete feature implementation
 - Can be run multiple times to add more evidence

extensions/levelup/config-template.yml

@@ -20,9 +20,9 @@ cdr:
   # - minimal: Only high-value/novel patterns
   heuristic: "surprising"
 
-  # Location of CDR file (relative to team-ai-directives root)
-  # The CDR manifest tracks context module contributions
-  location: ".cdrs.json"
+  # Location of CDR file (local project)
+  # CDRs stored in markdown format
+  location: ".specify/memory/cdr.md"
 
 # Skills Settings
 skills:

extensions/levelup/extension.yml

@@ -102,7 +102,7 @@ tags:
 defaults:
   cdr:
     heuristic: "surprising"  # surprising | all | minimal
-    location: ".cdrs.json"
+    location: ".specify/memory/cdr.md"
   skills:
     drafts_location: ".specify/drafts/skills"
   team_directives: