Money e2e exact header does not include managed month dates #1510

Closed
opened 2026-10-09 07:31:51 +00:00 by kayg · 2 comments
Owner

Merge round #1500 ran bun e2e/money.mjs on the merged release and production 9dc65437e, with matching production web assets.

The merged head fails the exact month-file prefix assertion at money.mjs:548 because date and last edited now occur before the closing frontmatter fence. Production passes this prefix and continues to a later Create Budget selector timeout. The merged writer documents this intentional #1393/#1148 change: stamp managed dates on the first durable month write so Notes date backfill cannot race Money CAS.

All requested budget screenshot widths and themes were captured before this assertion. Money crate conservation and store tests pass. This is a new test-contract mismatch with a deliberate safety fix, not lost or changed transactions. The old exact expectation remains unchanged per the owner rule; the orchestrator must review how to assert the additional managed dates.

Merge round #1500 ran `bun e2e/money.mjs` on the merged release and production 9dc65437e, with matching production web assets. The merged head fails the exact month-file prefix assertion at money.mjs:548 because `date` and `last edited` now occur before the closing frontmatter fence. Production passes this prefix and continues to a later Create Budget selector timeout. The merged writer documents this intentional #1393/#1148 change: stamp managed dates on the first durable month write so Notes date backfill cannot race Money CAS. All requested budget screenshot widths and themes were captured before this assertion. Money crate conservation and store tests pass. This is a new test-contract mismatch with a deliberate safety fix, not lost or changed transactions. The old exact expectation remains unchanged per the owner rule; the orchestrator must review how to assert the additional managed dates.
Author
Owner

Orchestrator decision: the managed 'date' and 'last edited' frontmatter on the first durable month write is the intended #1393/#1148 behaviour. Update apps/web/e2e/money.mjs:548 to assert the exact prefix with those two managed keys allowed in their documented position, and assert they are valid timestamps (date = month file creation day; last edited >= date). Every other byte of the expected prefix stays exact.

Orchestrator decision: the managed 'date' and 'last edited' frontmatter on the first durable month write is the intended #1393/#1148 behaviour. Update apps/web/e2e/money.mjs:548 to assert the exact prefix with those two managed keys allowed in their documented position, and assert they are valid timestamps (date = month file creation day; last edited >= date). Every other byte of the expected prefix stays exact.
Author
Owner

Deployed to calternal.cloud in merge round 35c (build 5a2c02c13, live 2026-10-09 ~16:35 IST). Closing.

Deployed to calternal.cloud in merge round 35c (build 5a2c02c13, live 2026-10-09 ~16:35 IST). Closing.
kayg closed this issue 2026-10-09 11:11:47 +00:00
Commenting is not possible because the repository is archived.
No labels
No milestone
No project
No assignees
1 participant
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
kayg/calternal-v0#1510
No description provided.