Audit: cross-package contract fidelity (askr-schema codec round-trip, askr-server response shape)

[smiggleworth]

Purpose

Audit task, not a bug report — produces a contract table, doesn't fix anything.

Procedure

1. Verify that this package's content() codec output/input actually matches what askr-schema validators (if used to define the codec's schema) produce and expect end to end — not just that both compile against each other's types.
2. Verify this package's assumptions about a @askrjs/server app's response shape (status codes, header conventions, error-response format) against a real running askr-server app, not just against the DSL's own type definitions.
3. File a gap issue for any mismatch.

Definition of Done

• Table: contract point | consumer/producer | ✅ verified end-to-end match / 🔗 gap filed.
• askr-schema codec round-trip and askr-server response-shape assumptions both explicitly checked.
• No row left unmarked.

[smiggleworth]

Cross-package contract audit complete via PR #35 validation. Current clean sibling mains were rebuilt before probing.

Contract point	Consumer / producer	Result
json(schema) request encode and response decode	askr-fetch / real askr-schema.safeParse	✅ Valid { name: "Ada" } round-tripped with application/json and schema validation on both sides
Success status/header/body	askr-fetch / actual createServerApp application	✅ 200 application/json decoded to the declared object
Validation error status/header/body	askr-fetch / actual askr-server OpenAPI route	✅ 422 application/problem+json decoded with source-prefixed issues[0].path = ["body", "name"]

The initial audit assumption used errors; live output established the normative server field is issues, and the corrected contract passed. No mismatch or gap issue remains.