Skip to content

Probe P4c — v1 of the contract broken consistently, examples and producer's tests included - #39

Closed
napkinstack-agent[bot] wants to merge 1 commit into
mainfrom
probe/p4c-consistent-break
Closed

napkinstack-agent[bot] wants to merge 1 commit into
mainfrom
probe/p4c-consistent-break

Conversation

@napkinstack-agent

Copy link
Copy Markdown
Contributor

A probe of NapkinStack M10h — never merged. M9's P4 (#24, replayed as #38) left the contract's examples invalid, and that is how it was caught on v0.3.1: by the producer's own e2e. M9 wrote that had the probe updated them too, nothing would have refused. This is that change: approximateLocation renamed whereabouts everywhere in catalog-api v1 — the property, required, the examples — and in catalog, its code and its tests. loans, which consumes v1 and reads approximateLocation, is not touched, so no job of its own runs.

Expected on v0.4.0: Module checks — V1 alone, oasdiff naming the property; contracts' check and test, catalog's check, test and e2e, Fitness functions all green.

It is closed as soon as its outcome is logged in the validation log, #1.

🤖 Generated with Claude Code

…ucer's tests included

M9's P4 left the examples invalid, which is how it was caught; M9 noted that had they been
updated too, nothing would have refused. This is that change: approximateLocation renamed
whereabouts everywhere in catalog-api v1 — property, required, examples — and in catalog,
its code and its tests. loans, the consumer, is not touched. A probe, never merged.

Agent-Session: 26f79b64-9fc9-4b2b-9354-485dcc9cda58
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
@napkinstack-agent

Copy link
Copy Markdown
Contributor Author

Outcome logged in the validation log: #1 (comment)

@napkinstack-agent
napkinstack-agent Bot deleted the probe/p4c-consistent-break branch September 19, 2026 20:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

0 participants