chore: update cursor rules and fix quote characters

- Sync .cursor/rules with merged date prefix convention
- Fix curly quote characters in AOP and spec template

Author: adamwdraper

.cursor/rules/directive-core-protocol.mdc

@@ -11,16 +11,22 @@ Authoritative sources (read first):
 
 🚨 FIRST STEP — FEATURE BRANCH (BEFORE ANYTHING ELSE):
 - Check current branch: `git branch --show-current`
-- If not on a feature branch, create one from main: `feature/<spec-name>` (must match spec folder)
+- If not on a feature branch, create one from main: `feature/YYYYMMDD-feature-name` (must match spec folder)
 - NEVER work directly on main or master
 
+**Naming Convention**:
+- All new specs use date-based prefixes: `YYYYMMDD-feature-name/`
+- Use the current date when creating the spec (e.g., `20251105-cursor-rules-alignment/`)
+- If multiple specs created same day, use distinct feature names to differentiate
+- Example: For a spec created on November 5, 2025 → `/directive/specs/20251105-feature-name/` → branch `feature/20251105-feature-name`
+
 Pre‑implementation gates (must exist and be approved before any code):
-1) Spec → `/directive/specs/<feature>/spec.md`
-2) Impact Analysis → `/directive/specs/<feature>/impact.md`
-3) TDR (high‑level, decisive about interfaces) → `/directive/specs/<feature>/tdr.md`
+1) Spec → `/directive/specs/YYYYMMDD-feature/spec.md`
+2) Impact Analysis → `/directive/specs/YYYYMMDD-feature/impact.md`
+3) TDR (high‑level, decisive about interfaces) → `/directive/specs/YYYYMMDD-feature/tdr.md`
 
 Location for new feature docs:
-- Create all new Spec, Impact, and TDR files under `/directive/specs/<feature>/` (one subfolder per feature).
+- Create all new Spec, Impact, and TDR files under `/directive/specs/YYYYMMDD-feature/` (one subfolder per feature).
 
 Collaboration and approval:
 - Draft each document (Spec, Impact, TDR) collaboratively with the engineer.

directive/reference/agent_operating_procedure.md

@@ -54,7 +54,7 @@ This is the **standard workflow** the agent must follow for every new feature sp
 ---
 
 ## Step 1 — Repo Recon (Codebase Map)
-Produce a short “you are here” map:
+Produce a short "you are here" map:
 - Entry points, services, key modules
 - Current data models and important tables/collections
 - External interfaces (APIs, events, webhooks, queues)

directive/reference/templates/spec_template.md

@@ -16,7 +16,7 @@ What should exist when this is done? (concise outcome statement)
 
 ## Success Criteria
 - [ ] Clear, measurable user outcome or KPI  
-- [ ] Qualitative improvement if metrics aren’t available  
+- [ ] Qualitative improvement if metrics aren't available  
 
 ## User Story
 As a [user type], I want [capability], so that [benefit].  
@@ -40,4 +40,4 @@ Links to designs, copy, or prototypes (e.g., Figma files, screenshots, docs).
 - Include at least one negative case  
 
 ## Non-Goals
-What’s explicitly out of scope for this PR.  
+What's explicitly out of scope for this PR.