Recover a Claude Code task correctly after a compaction or restart

This session's context was compacted, resumed from a saved transcript via --continue or --resume, or otherwise interrupted partway through a task. Do not continue as though every earlier decision is still fully remembered, and do not fill a gap with a plausible-sounding guess. Reconstruct the actual current state from ground truth before writing or changing anything else.

ORIGINAL GOAL
Migrate the reports module off the legacy REST client onto the new typed API client, one file at a time, keeping every existing test green throughout.

WHERE A PRIOR PLAN MIGHT ALREADY EXIST
A PLAN.md should exist at the repo root, written at the start of this task, listing files in migration order.

HOW THIS SESSION WAS RESUMED
This session was resumed with claude --continue after an unplanned terminal restart, not through a manual compaction.

EXPECTED TEST STATE BEFORE THE INTERRUPTION
The full reports test suite was green the last time it ran before the interruption, per the PLAN.md notes.

RECONSTRUCT BEFORE DOING ANYTHING ELSE
1. Run git status and git diff to see exactly what is currently uncommitted right now. List every added, modified, and deleted file, and summarize what each specific change does in one line.
2. Run git log to see what has already been committed toward this goal, if anything, on the current branch, and how recently.
3. Read, in full, any plan, todo list, or design note that exists at the location named above.
4. Compare the current diff and commit history against the original goal stated above: state which parts are done, which are in progress, and which have not started, citing the specific file or commit that proves each of those three claims.
5. Run the actual test suite now and compare the result against The full reports test suite was green the last time it ran before the interruption, per the PLAN.md notes. above. A currently failing test where the plan says everything was green last time is new information that needs its own explanation, not something to route around silently while continuing the original task.
6. Write one paragraph stating the current understanding of exactly where this task stands, based only on what steps one through five actually show, not on an inference about what probably happened during the gap.

IF SOMETHING DOES NOT ADD UP
If the current diff contains a change that cannot be explained by the goal or the plan artifact, name it explicitly as unexplained rather than building on top of it or assuming it was intentional. If an earlier decision appears to have been made that is not written down anywhere verifiable, say plainly that the reasoning behind it is unrecoverable from available evidence, and ask — do not invent a plausible-sounding rationale to fill the gap just because one would be convenient to have.

ONLY THEN
Propose what happens next, in concrete terms, naming the very next file or command involved, and wait for explicit confirmation before resuming any edit — a proposal is not itself permission to proceed, even when it seems like the only reasonable next step.