ct-analysis-looplisted

# /ct-analysis-loop - Source Code Analysis (Phase 4) **Primary request**: Use this skill when repeating configuration fixes and re-analysis after an analysis failure, or when recording `functions_found` in state. **Entry**: `status` is `project_created` **Input**: `state.json` -> `ct_resources.*` + (for `conversion`, top-level `conf_path`; keep `artifacts.conf_path` as a mirror) **Output**: `state.json` (`status=analysis_success`) **Execution mode**: In-memory state when called through `ct-orchestrator` / one-time `state.json` read in standalone mode **Standalone guard**: In standalone mode, read `state.json` and confirm that `status` is `project_created`. - If `state.json` is missing or `status` is not `project_created` -> **stop immediately** and tell the user to run `ct-init-project` first to complete project preparation - If Phase 3 outputs (`ct_resources.project_name`, `ct_resources.working_directory`) are missing, analysis cannot proceed - In `conversion`, if top-level `conf_path` is missing or the `artifacts.conf_path` mirror is not kept with it, treat it as a Phase 2/3 regression target **conf path contract**: - The canonical input in the cross-phase state contract is top-level `conf_path` - Under the current runtime or validator contract, `artifacts.conf_path` must also be kept, and both values must point to the same absolute path **Precondition**: Use the bootstrap variables acquired in Phase 0. In end-to-end entry, `ct-init-project` prepares them. In resume entry