review-axiom-tasklisted

# Review Axiom Task Produce a compact retrospective from available evidence. This is not an instrumented execution trace: Axiom supplies routing and workflow instructions, while the host agent performs actions through its normal tools and authority. ## Scope Gate - Identify the review target before inspecting history. Use the current task segment preceding the review request, or one task or thread the user explicitly identifies. - Freeze the reviewed execution immediately before the triggering request. Record that request as review authority, and keep the review's own reads and reasoning outside the task being reviewed. - Ask one concise question only when the target or review window is ambiguous in a way that would materially change the report. - Start with the visible conversation. Inspect another task only when the user identified it and the host exposes a read-only task-inspection tool. - Record the target, first and last reviewed turns or events, and whether older history in that window is unavailable. Do not treat compaction summaries as full transcripts. - If no Axiom route applied, report the no-route result. Do not retrofit a route onto ordinary host-native work. ## Read-Only Boundary - Treat the request as authority to review the visible target-task context, not as authority to edit, commit, push, deploy, install, migrate, delete, retry, clean up, change configuration, or access credentials. - Use a fresh read-only observation only when it