track-project-progresslisted

# Track Project Progress Preserve only the state needed to resume reliably. Keep detailed requirements, designs, architecture, tests, and runbooks in their existing sources of truth. ## Reconcile before updating 1. Read applicable project instructions and `THE-FIRST.md`. 2. Inspect actual Git state, relevant commits, linked documents, tests, and external tracker items available in the current environment. 3. Separate verified facts from plans, user proposals, AI assumptions, and stale status. 4. If sources conflict, report the conflict and its impact. Do not overwrite one source merely to make the index appear consistent. 5. Never put credentials, secrets, personal data, or long conversation transcripts into the index. ## Maintain the state contract Keep these frontmatter keys and enum values stable: ```yaml --- the_first_schema: 1 phase: requirements status: in_progress documentation_mode: index_only dialogue_mode: deep active_slice: null updated_at: YYYY-MM-DD --- ``` Allowed phases: - `requirements` - `experience` - `technical` - `development` - `deployment` - `complete` Allowed statuses: - `not_started` - `in_progress` - `awaiting_user_acceptance` - `accepted` - `blocked` - `complete` Allowed documentation modes: - `index_only` - `normalize_in_place` - `structural_migration` Allowed dialogue modes: - `fast` - `deep` Treat a missing `dialogue_mode` in an older index as `deep`. Persist a change only when the user explicitly selects a different dialogue depth;