mirror of
https://github.com/morluto/rea.git
synced 2026-10-31 11:56:12 +00:00
morluto
63220edcc3
Keep missing or ambiguous scenario request durations unknown, retain learned clock rules, and withhold plans that cannot generate an observed clock. Refuse such writes in older imported states before changing state or generators. BREAKING CHANGE: The write-plan reason can now be unknown-clock; strict clients must accept the new output value. Validated state, CLI and advertised MCP workflows, documentation, and focused clock and cleanup regressions.
1.4 KiB
1.4 KiB
Plan
- Schema: optional
observed_at(ISO date-time) onrequestevents, andstarted_at(ISO date-time) andelapsed_ms(non-negative number) onrequest-finishedandrequest-failedevents. - Collector: stamp
observed_atwhen a request is observed and copy the browser'stiming().startTimeandresponseEndintostarted_atandelapsed_mswhen it reports them, admitting the strings with the other metadata. - Records: index each transaction's single finished or failed start and
duration and give each attributable record
startedDateTimeandtime; add a limitation when any record is timed. - Comparison: drop both fields from network evidence before fingerprinting and commit the rule in the built-in list and the comparison limitation.
- Docs: the scenario contract's network evidence and the environment docs' browser scenario section.
- Tests: the collector stamps both fields, records take them, the state learns the HAR's clock and verdicts from a timed scenario and none from an untimed or partly untimed one, a request that never ended or ended twice falls back to its observation with unknown duration omitted, an explicit zero remains observed, comparisons ignore the times (also against an untimed capture), and the real-Chrome network lane checks every request is observed and every finished request carries the browser's start and duration.