reportlisted

# Pi Report Skill Use this skill for Pi-native report requests: ```text /skill:report <circuito> /skill:report <circuito> <fecha_inicio> <fecha_fin> ``` This is a thin Pi adapter over the shared report contract. It preserves el Gentleman orchestration discipline while keeping report behavior in the canonical Python pipeline. ## Source of truth - `src/chec_local_interpreter/report_pipeline.py` owns report-domain behavior. - `src/chec_local_interpreter/report_contract.py` owns normalized request/outcome serialization. - `.claude/skills/report/SKILL.md` remains the canonical end-to-end report runbook. ## Argument rules - `circuito` is required. - Dates are optional as a pair. - Reject a lone date immediately; never infer the missing bound. ## Run sequence **Environment bootstrap (mandatory).** Run every report-contract and role CLI command from the repository root with `PYTHONPATH=src .venv/bin/python`. Do not try bare `python`/`python3` first and do not declare the environment unavailable merely because they cannot import `chec_local_interpreter`; this repository's supported local command is the virtualenv-prefixed form. 1. Read `.claude/skills/report/SKILL.md` before running the workflow. 2. Preflight through the shared contract: ```bash PYTHONPATH=src .venv/bin/python -m chec_local_interpreter.report_contract preflight <circuito> [fecha_inicio fecha_fin] --runtime pi ``` 3. State the resolved circuit/date window once and ask the user to confirm. 4. After