#4471 review: dates and timing are not one problem

This review covers the support knowledge-base export dated 4 October 2026, not the current support queue. The original incident page marked the whole ticket as known with one parser fix queued. Its table groups by tenant locale and booking form, so it cannot distinguish a timing report from a month/day swap. This review reads the report bodies as well.

Engineering update after the export

DennyRedeye supplied the following engineering update from the course challenge page on 1 November 2026:

#4471 · closed 05 oct
parser fixed
fix(dates): parse dd/mm for eu locales
hint won't fix booking-v3 form retired

The parser ticket is completed, and the hint ticket is closed as not planned. The timing ticket stays open because the update gives no resolution for its reports. Closing the merged desk ticket does not prove that every problem merged into it was fixed.

This update changes ticket dispositions, not the historical report membership. The counts below still describe the 4 October export. No later report export, commit hash, rollout details or timing reproduction has been independently verified.

Exported desk view

412 reports merged into #4471 · 2 causes

5 reports read as a one-day move; filed under parser by tenant.

The desk counts the parser and hint groups using its exported component. Its one-day notes are included and footnoted under parser, not subtracted from that group.

Engineering status and timing investigation

The export contains 427 rows and 412 unique reports merged into #4471. 15 overlapping rows do not represent additional reports. The exported parser and hint groups count each report ID once. The timing row is an overlapping investigation subset within parser, not additional reports; do not add it to the exported total.

Intake labels are not cause evidence

Timing reports kept separate

The desk's oneDayMove notes flag these report IDs. Their bodies do not describe the month/day swaps used to support the parser and hint groups. This is an investigation ticket, not proof that all these reports share one timezone or delivery bug. The exported desk view counts them under parser and footnotes them there; this review preserves that count while making the uncertainty visible.

R-41202 · kettle.books · email

Invite says Tuesday 12 May. Calendar says Monday 11 May. My client turned up on the Monday. We had coffee.

R-41209 · alder.physio · app

Every booking in June is one day off. Only June. Why only June.

R-41236 · nine.lanterns · app

The invite arrived before I made the booking. I would like to know how.

R-41344 · pale.harbour · email

Client in Lisbon got Tuesday. Client in Toronto got Monday. Same meeting. We held it twice.

R-41620 · lantern.row · email

Tuesday 6 October showed as Monday. I moved it myself. I have stopped reporting these but my colleague says it helps you.

Exported groups and overlapping investigation audit

Shared parser: month-first interpretation

The shared parser reads dates month first, but the tenant directory identifies day-first locales. The exported desk classifier counts app and email reports, and booking-v2 form reports, under parser. It also counts the timing cases there, with a footnote; the count is not proof that the parser explains those bodies. Browser locale and intake tags are not substitutes for the tenant’s configuration.

R-41200 describes 7 April becoming 4 July. R-41205 comes from Morrow Tax, whose tenant locale is fr-FR, even though intake saw an en-US browser and tagged it as a hint problem. The engineering update reports that the parser now parses dd/mm for EU locales, so the parser ticket is completed. The export explains the original failure; it does not prove the implementation details, regression coverage or rollout of the reported fix.

booking-v3: the form tells people the wrong date order

The booking-v3 form prints MM/DD/YYYY under its date field. Alder Physio, Copper Studio and Pale Harbour use that form with day-first tenant locales. People follow the month-first hint, but the form reads their input in the tenant’s day-first order. This is a separate interface contract problem, not the shared parser fix.

R-41230 is a Copper Studio form report: 6 January becomes 1 June. Engineering retired booking-v3 and marked the hint as won’t fix, so the hint ticket is closed as not planned, not completed by a date-hint patch. The historical reports remain in the audit.

Timing: keep the uncertainty visible

The desk notes identify reports with adjacent-day or other timing symptoms. The tenant-only classifier files them under parser, but a month/day swap does not explain their reported behavior. R-41236 says an invite arrived before its booking; that observation is not enough to prove a one-day shift.

The investigation must retain the original booking date, timezone, serialized timestamp, recipient timezone and delivery logs. Test a single event across Lisbon and Toronto and check date-only values around midnight and daylight-saving boundaries. These are diagnostic checks, not a claim that a timezone bug has already been reproduced.

Why the merge hid separate problems

Decision 0001 permits merges on normalized subject alone, without reading the body. The accepted triage page still repeats that rule, even though its interactive example computes cause using tenant locale and channel. Neither subject equality nor that helper alone proves that the bodies describe the same failure.

Match tenant configuration, input path, observed date transformation and reproduction evidence before merging. Keep unresolved timing reports separate. Do not rewrite the accepted decision: propose a new decision that replaces subject-only merging after desk approval.

What the desk must check next

The engineering update supersedes the export’s queued-parser and active-booking-v3 status. The support desk keeps working: check for later reports, changed merge assignments, parser rollout details, and the retirement’s scope. Recompute counts from unique IDs if a new report export becomes available. Do not present this export’s counts as live totals or close the timing investigation merely because #4471 was closed.

Reproducing this page

The words live in this page. The tables and report IDs are computed by IncidentReview from the unchanged report export, tenant directory and desk notes. The review helper removes overlapping report IDs and keeps the existing cause groups intact. It flags the notes’ timing cases as an overlapping investigation subset, without subtracting them from the desk’s parser count. It does not invent a timezone root cause or change the original export.

The public repository contains the source page and a prerendered HTML copy under docs. The HTML uses these components at build time, so it includes the tables and desk reference, not only the Markdown source.

desk ref DR-8Q7Z-1VS3