Task: Point the web reads at the feed catalogue

The web target builds and its catalogue reads answer from the feed catalogue.

• The official rates and subscriptions routes read feeds and answer the shape their screens already take
• The web target builds, typechecks and passes its tests

Only the two BFF routes import the deleted module; the rest of the web surface reaches the catalogue through them, so the change stays inside the BFF and its two tests.

The renamed row is not a rename of a field: the feed carries publisher_code in place of provider_code, and a service where the source carried a kind. The reply keeps the shape each screen already takes, so the screens do not move, and the mapping is stated where it happens: a source's kind is now the feed's service, which is the only fact of that shape the feed has.

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 web target builds again: the two BFF routes read the feed catalogue, the Official rates and subscriptions screens answer from it unchanged, and the suite passes. The route inventory main carries is regenerated in the same commit, because ten routes it answers were missing from the table.