v0.12.3 — Recorded repeats replay in order

Recording the same request more than once used to leave disconnected duplicate stubs. Following the reference oracle's behavior, repeats are now chained into a generated scenario.

Recorder

• Repeated requests become a scenario chain: the first capture serves at Started and advances, each later capture serves from the prior state — a replay returns the recorded responses in recorded order
• An upstream whose answer changed between repeats now replays faithfully; distinct requests stay scenario-free
• Repeat identity is method + URL + request body — exactly what the generated request pattern matches on

Oracle-verified

The initial plan was to deduplicate; the real reference oracle refuted it and showed the scenario-chain shape instead, which Mockifyr now generates identically. Pinned by Recording_RepeatedIdenticalRequests_CaptureLikeTheOracle (structural bundle comparison on both sides), with the chain rules unit-tested and mutation-tested to 100 % (32/32).

Validation: 194 oracle-backed differential tests (one new), 292 unit tests, all green.

Docs: record & playback guide updated; docs/parity/g12-transport.md records the learned behavior and closes the G9-era "repeats → scenarios" deferral.

🤖 Generated with Claude Code