BlogProPresenter
Corex\Config\Blog\BlogProPresenter · class · Config layer
One shape for an editorial item and a comment, wherever they leave the server (spec 075). BlogProScreen localises the first paint and BlogProController answers every refetch after it. They were projecting the same two objects into the same two array shapes independently, so a field added to one path silently did not exist on the other — and the client cannot tell which path a given item arrived by. That is the same “two derivations, one eventual divergence” this project has now written down twice (DECISIONS #157, #160), so here it is derived once. Pure apart from the permission checks, which are deliberately here: a control is decided by the same {@see BlogProPermissions} the route asks, not guessed at by the client (DECISIONS #159, spec 112).