Repository navigation
Conversation
…nged, so a second change on the same day is a newer date The edge serves a page and its Markdown copy with the date the content last changed as their Last-Modified. The copy stated that date as a day (`Updated: 2026-11-17`), and a page first published and last changed on the same day stated it the same way in its footer, so both were served as of midnight. Two changes made on one day then had the same Last-Modified: a client that revalidated with If-Modified-Since after the first got a 304 after the second and kept the old text. Every copy of the site was dated this way, and seven pages besides; getting-started.mdx, for one, changed twice on 2026-11-14. `isoInstant` in date-rules.mjs states the content date to the second in UTC (`2026-11-17T10:30:31Z`). The footer's last `<time datetime>` carries it, including on a page published and last changed on the same day, whose one date stands for both, and the copy's `Updated:` line carries the same value. The sitemap's <lastmod> and the structured data keep the day. check-markdown-twins holds `Updated:` to an instant to the second, on the day the sitemap gives, and equal to the date the page's footer states. The llms generator measures the longer `Updated:` line as a dated line, so where a shard is cut still does not depend on the dates; `make llms` writes the same files.
|
No actionable comments were generated in the recent review. Walkthrough
Merge Risk:
|
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## main #1152 +/- ##
=======================================
Coverage 97.35% 97.35%
=======================================
Files 477 477
Lines 97722 97722
=======================================
Hits 95136 95136
Misses 2586 2586 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
Numerical conformance1899/1899 checks pass across 111 domains, against 230 normative designations and 121 further published sources. Used in the tables below is how much of that clause's published tolerance the deviation consumes: 100 % sits exactly on the limit, 5 % uses a twentieth of the allowance, and a dash means the clause states no two-sided tolerance for the quantity, so there is no budget to spend. It is reported and never used to decide a verdict, which is settled at full precision before any rounding. Nothing moved: same 1899 checks, same verdicts, same numbers. Closest to their published limit (top 5) The rows with the least room left, so the ones a change is most likely to push over.
|
|



The edge serves each docs page and its Markdown copy with the date their content last changed as Last-Modified. The copy stated that date as a day (
Updated: 2026-11-17), and so did the footer of a page first published and last changed on the same day, so both were served as of midnight UTC. Two changes on one day then shared one Last-Modified: a client that revalidated with only If-Modified-Since after the first change got a 304 after the second and kept the old text. That covered every copy on the site and seven pages, and same-day changes do happen (start/getting-started.mdxchanged twice on 2026-11-14).What changes:
isoInstantinsite/src/lib/date-rules.mjswrites the content date to the second in UTC (2026-11-17T10:30:31Z).LastUpdated.astro: the last<time datetime>of the footer carries that instant. A page published and last changed on the same day shows one date as before, and that date'sdatetimeis now the instant of the change instead of the day.Updated:line carries the same instant, so the page and its copy get the same Last-Modified. The sitemap's<lastmod>and the structured data keep the day.check-markdown-twinsrefuses anUpdated:that is not an instant to the second, one on another day than the sitemap gives, and one that differs from the date the page's footer states.generate_llms.pymeasures the longerUpdated:line as a dated line, so where a shard is cut still does not depend on the dates.make llmswrites the same files as before.The docs-edge Worker already reads a full ISO date-time from both places, so it needs no change.
Checks run locally:
test:agent-md281/281 andtest:scripts695/695 (with a test ofisoInstant), the newcheck-markdown-twinscases (which fail against the old checker: 43 of 51),pytest tests/test_generate_llms*.py52/52,make llmswith no drift, ruff, and a full site build followed bycheck:markdown-twins,check:crawlandcheck:structured-data.Summary by CodeRabbit