## ADDED Requirements

### Requirement: Graded context recovery from audit trails
The system SHALL support context recovery at 5 graded levels (L0-L4), each returning progressively more detailed context from persistent audit trail files.

#### Scenario: L0 recovery loads index summary
- **WHEN** user invokes `/recover` with no arguments
- **THEN** system reads `index.json` and returns the last 5 index entries (id + task + status) at approximately 200 tokens

#### Scenario: L1 recovery loads current task state
- **WHEN** user invokes `/recover` with `level: 1`
- **THEN** system reads `.current_session` for session ID, then reads `{session_id}/session.json` for task + start_time, then reads the last 3 audit_trail.jsonl records

#### Scenario: L2 recovery loads user corrections
- **WHEN** user invokes `/recover` with `level: 2`
- **THEN** system searches all `audit_trail.jsonl` files for `user_correction` records and returns them alongside L1 context at approximately 1000 tokens

#### Scenario: L3 recovery loads full session
- **WHEN** user invokes `/recover` with `level: 3` or `/recover full`
- **THEN** system returns complete `audit_trail.jsonl` and `audit_pending.jsonl` at approximately 3000 tokens

#### Scenario: L4 recovery loads cross-day history
- **WHEN** user invokes `/recover` with `level: 4`
- **THEN** system returns cross-day comparison of manifests and historical daily reports at approximately 5000+ tokens

#### Scenario: Session start auto-recovery
- **WHEN** `/start` creates a new session and historical audit data exists
- **THEN** system SHALL load L0 + L2 context automatically (index summary + user corrections) before the new session begins

### Requirement: User correction priority in context loading
The system SHALL mark `user_correction` records with highest priority in all context recovery operations. Corrections SHALL always be loaded before task state or any other context.

#### Scenario: Corrections surfaced first on recovery
- **WHEN** `/recover` loads context
- **THEN** any `user_correction` records in the audit trail SHALL appear before task summaries and SHALL be clearly labeled as "User Corrections — Review These First"

### Requirement: Structured recovery report
The system SHALL output a structured recovery report containing: current task, user corrections found, key conclusions from context, unresolved issues, and recent actions.

#### Scenario: Recovery report includes all sections
- **WHEN** context recovery completes
- **THEN** output SHALL contain: `**Current Task**`, `**User Corrections**`, `**Conclusions**`, `**Open Issues**`, `**Recent Activity**`