Add the mock endpoints a new screen needs as scenarios
Fake data for a new screen added as scenarios in the mock server, never as branches inside the app.
The ticket
Add the mock endpoints a new screen needs as scenarios in the mock server, with no conditional branches in application code.
Acceptance criteria
- Every endpoint the screen consumes is implemented in the mock
- No mock branch is added to application code
- A conformance run asserts each mock response matches the API contract
- The scenario is selectable without editing code
What lands as proof
A conformance run listing each consumed endpoint as implemented, and an application diff with no mock branch in it.
Why teams defer it
- A conditional in the component takes two minutes and a scenario takes an hour, so the conditional wins under deadline.
- Those conditionals are invisible until somebody ships one to production.
Questions
- What does the agent actually change?
- The ticket is scoped to one outcome: add the mock endpoints a new screen needs as scenarios in the mock server, with no conditional branches in application code. Work that serves that outcome is in scope, and anything outside it is left for a separate ticket, so the pull request stays reviewable.
- How do I know the work is done?
- The pull request carries the evidence, not only the diff. Here that means every consumed endpoint implemented, asserted by a conformance run, so a reviewer can confirm the result without reproducing the work locally.
- How much oversight does this need?
- None is required before the run starts. Every claim this ticket makes can be checked by machine, so the agent works straight through and a person reviews the finished pull request like any other.