You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
* docs: design spec for working aimock drift detection
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* docs: implementation plan for aimock drift detection
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
* feat(examples-chat): record mode for the aimock e2e runner
* feat(examples-chat): AIMOCK_MODE=record wiring in e2e global-setup
* feat(examples-chat): tag the contract-only @drift e2e subset
* feat(examples-chat): structural fixture differ replacing the broken drift script
* feat(ci): weekly aimock drift run — record-proxy e2e subset + structural diff
* feat(examples-chat): differ reports incomplete recordings separately from drift
The aimock recorder emits { content: '' } with a 'fixture may be
incomplete' warning when it cannot parse tool-call deltas from a stream.
Observed live: both tool-calling entries in the first record run collapsed
to empty text while the @drift specs passed. A recorder artifact, not
model drift — reported in its own category so it cannot masquerade as a
kind change.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
---------
Co-authored-by: Claude Opus 5 <noreply@anthropic.com>
0 commit comments