Release v4.51.1

Fixed

• A scene element querying a read model that backs more than one modeled query (for example AllWorkItems and WorkItemById, both returning WorkItemSummary) now resolves to the correct route. Previously, StageSceneRoutes matched candidates by the read model's type name alone and broke the tie by shortest route text; Arc names the conventional argument-less collection endpoint from the read model's pluralized name, which can be textually longer than a by-id route, so the by-id route was sometimes picked for a table that needs the collection. The element's own modeled query name (now carried in SceneElementProperties.Query) is tried first, and when that does not resolve, a by-id lookup is excluded from the remaining candidates before falling back to the shortest route. (part of #236) (part of #237)

This was found live: the screens-release browser acceptance harness showed the WorkItemList screen's AllWorkItems table bound to /api/workspaces/tracking/work-item-by-id instead of /api/workspaces/tracking/all-work-item-summaries, so the list rendered no rows against the public CLI/Stage vector.

All Host (416), Contracts (623) and the Scene-scoped Rendering.Cratis specs pass; a regression spec reproduces the exact ambiguous-readmodel shape.