ultra-reviewlisted

# Review through selected lenses without polluting the main context The parent owns scope and synthesis. Lens workers are read-only sensors. Refactoring happens here, after several slices make a useful structure visible, not inside TDD. ## Before you start 1. Resolve the review scope first. For task or active-Change review, read `../ultra-change/references/change-contract.md` and apply its **Active Change authority resolution** before reading any active `intent.md`, resolving the current `change_id` or task, reading context or acceptance, or creating a packet. A stable zero result stops with no current review scope; any typed diagnostic, including non-unique authority, stops with its repair before any `.ultra/reviews` packet write. After one valid authority, read its intent and `.ultra/tasks.json`, select only matching tasks, then read the scoped task's `context_file` and `## Resume Note`. Historical review must name its archived Change explicitly and never infer scope from unfinished status. 2. Read `CONTEXT.md`, relevant `.ultra/decisions/`, acceptance, evidence and exact diff. Task-review admission comes from the ledger `in_progress` row, task context, immutable packet, and actual pre-review evidence such as retained command output, inspected source, owner records, and external receipts. The first task review must not require the final `ultra-task-evidence-v2` record that it helps produce. For an aggregate Change review, require