fix(v2): E2E findings — iteration close status key, ANSI-safe CLI, SP rollup

[jurby]

Summary

Three fixes surfaced by a full real-GitHub end-to-end re-validation of EDPA v2 (2 Program Increments × 5 iterations, 24 PRs, 24/24 real CI runs, 560h derived, all invariants green — full report in docs/v2/e2e-real-github-run-2026-05-31.md).

1. Iteration close didn't set the lifecycle status key consumers read

edpa_iteration_close set only the nested iteration.status: closed, but pi_close.py (line 105), reports, the board lifecycle view, and the e2e verifier (12_verify_backlog.py) read the top-level status. An iteration closed via the MCP tool was therefore not seen as closed by those consumers (the e2e run had to patch PI-1's iteration YAMLs to make the verifier pass). Now sets both keys — nested (planning state, consumed by _pi_loader-lifted readers + capacity_override) and top-level (lifecycle). test_iteration_close_sets_status extended to assert the top-level key.

2. backlog.py add leaked ANSI codes into machine-readable output

The allocated item ID was printed with ANSI color even when stdout is piped/captured, which broke parent-ID parsing by tooling/CI (hit during E2E scaffolding). color()/bold() now honor NO_COLOR and non-TTY output via a _use_color() guard. Tests added.

3. Iteration/PI story-point rollup wasn't derived from items

velocity.py and pi_close.py read planning.planned_sp / delivery.delivered_sp from iteration YAMLs, which item-driven backlogs don't populate (SP live on Story/Defect js) → velocity 0, PI predictability None. New helper _sp_rollup.iteration_sp derives planned_sp (Σ js per iteration) and delivered_sp (Done only) from the backlog; both scripts fall back to it when explicit iteration SP is absent. Verified on the E2E sandbox: velocity avg 9.3, PI predictability 100%. Tests in test_sp_rollup.py.

Testing

• pytest -m "not e2e" tests/ → 551 passed (+5 new), 0 failures.

Follow-ups (not in this PR)

• R-2 (multi-role attribution): a multi-contract person (e.g. bob-pm sharing github: bob-arch-e2e with bob-arch) can't be credited distinctly — /contribute @handle resolves by GitHub login, so credit lands on the first contract. Manual attribution by EDPA id would close this. (/contribute itself is verified working end-to-end: a directive in a commit body credits a non-committer with derived hours.)
• E2E harness only: parallel work-creation can collide on shared synthetic file paths (add/add conflicts) — namespace paths per item if the parallel sim is kept.

🤖 Generated with Claude Code