Task: File the credit loose ends

The three credit gaps are tracked work with owners and acceptance criteria, instead of three captures that no sprint carries.

• Each of the three captures is a BACKLOG task on this story, with its UUID unchanged, and the bucket index no longer lists it.

(Implementation strategy. Written when work starts; key decisions are distilled into the parent story's * Decisions at close, but the plan itself stays — it is the historical record of what we did.)

Every number this task claims about a tree, with the command that produced it and the commit it was measured at. A number without both is not a measurement, because a clean-up record describes a tree and trunk moves under a branch: a consumer count, a gate's component count and a suite's size all change with no code changing, and the reader of a bare number cannot tell which tree it came from. Where the raw output matters, put it in an evidence/ file beside the task and name that file in the Command column.

Manual QA scenarios (scaffolded via compass add test_scenario) that verify this task. Link new ones here as they're created; the scenario doc itself links back via its "Verifies task" field.

The three captures are the story's tasks. Promotion kept each UUID, so every existing id: link still resolves, and the inbox and next indexes no longer list them. The story sits in Sprint 28 as BACKLOG, with the three tasks in the same state.