[adamjohnwright]

Spec 016 User Story 4: an OpenAPI description generated from the contract, not maintained by hand. Java's own description lists most answers as a generic object.

• projects/contract/routes.ts: the route table, the interface Routes. It maps each "METHOD /path", as the service's registry has it, to its 200 answer: twelve search routes for now.
• tools/contract/generate.ts (ts-json-schema-generator 2.9.0, a dev dependency) writes projects/contract/openapi.json:
  • an OpenAPI 3.1 document of all 90 routes the content service serves;
  • the twelve the contract describes come with their answer schemas, and the other 78 are marked x-contract: "not yet";
  • the search entry is oneOf its six kinds (research R4: no single tag tells them apart), and a Java long is integer/int64;
  • a generic instance's name is made a valid component name (GroupedResult_SearchEntry);
  • it generates in about 1.7 s, the same bytes every run, and writes only when run as a script.
• tools/contract/generate.spec.ts:
  • T019: every contract route is one the service serves, and every served route is listed. Shown failing on a row for a route the registry lacks.
  • T020: the committed file equals what the generator writes. Shown failing on a contract field renamed without regenerating.
• Small changes: tools/load.spec.ts gains contract. The generated file is in .prettierignore, since the up-to-date check holds it instead.

Lock: it gains the generator, commander, safe-stable-stringify and a hoisted glob. With the hoisting, one transitive copy of brace-expansion goes from 5.0.9 to 5.0.12, within its range. Pushed with LOCKFILE_BUMP=1.

Preflight passes. The first push's smoke run had three diagram tests time out while other container builds loaded the machine; they pass on their own (9/9) and in this push.

🤖 Generated with Claude Code

[adamjohnwright]

Replaced by 708: path variables declared, clashing names refused, the counts corrected.