docs(fr-044): Plan 3 — generated read routes, typed rows and docs pages for reports

The implementation plan after Plan 2 (report view lowering and reads in
every port). It covers a generated list route for a view-backed
object.report in five ports, the api-contract report/ sub-corpus, the
TypeScript, Java and Python generators no longer skipping reports, and
model and API pages for reports in meta docs.

A report is served as a keyless read-only projection is served today:
each port hands the read model it already has to its existing read-only
generators. The contract is stated as tables the ports copy: which
reports are served, the REST surface, what may be filtered and sorted,
the wire encoding of each derived subtype, what each port generates, the
corpus (model, seed, twelve scenarios in full) and the docs pages.

The corpus model was loaded with the real loader and its three views and
every query behind an expected row were run on Postgres 16. Two
throwaway spikes fed the read model through every TypeScript and Python
generator, and what they emitted and what broke is what the tasks are
written from. HTTP bodies were not executed: no port serves a report
yet. Cited paths and names were read in the tree; what could not be
confirmed is marked UNVERIFIED and listed. Seven questions for the
maintainer are at the end.

Found while verifying, and folded into the tasks: TypeScript and Python
mount item routes for a keyless projection against the documented
contract, and TypeScript types a decimal in a view read schema as a
number while the value is a string.

Author: dmealing