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
Context\n\nDetected by nightly doc-sync run 2026-05-09.\n\nPR #123 (merged 2026-05-09) updated public/version-history.html to reflect 16 releases and 29 days elapsed, but left the velocity banner headline unchanged:\n\nhtml\n<!-- Headline — still says 25 -->\n<div class=\"headline\">v0.1 to v0.9 in 25 days</div>\n\n<!-- Sub-headline — correctly updated -->\n<div class=\"sub\">Sixteen releases. Blathers can't keep up.</div>\n\n<!-- Stat counter — correctly updated -->\n<div class=\"num\">29</div>\n<div class=\"label\">days elapsed</div>\n\n\nThe headline and counter now disagree on the same page ("25 days" vs 29).\n\n## Why this needs a human decision\n\nThe right correction isn't obvious:\n\n- Option A — update headline to match counter: Change to "v0.1 to v0.9 in 29 days." But 29 is "days elapsed since v0.1 to today (May 9)", not how long the v0.1-to-v0.9 arc actually took. v0.9.0 shipped May 3, which is 23 days from Apr 10. Saying "29 days" is technically inaccurate as a historical claim.\n- Option B — treat headline as a fixed historical tagline: Keep "25 days" as a snapshot from when it was written (around v0.9.2 / May 5) and update only the counter going forward. But a reader seeing both numbers on the same page will be confused.\n- Option C — reword the headline to avoid a specific number: e.g. "v0.1 to v0.9, one sprint" or omit the day count from the headline entirely.\n\n## Acceptance\n\n- The headline and days-elapsed counter on public/version-history.html tell a consistent story.\n- No reader is left wondering which number is correct.\n\n## References\n\n- PR #123 — doc-sync run that updated the counter but missed the headline\n- public/version-history.html velocity banner block
Context\n\nDetected by nightly doc-sync run 2026-05-09.\n\nPR #123 (merged 2026-05-09) updated
public/version-history.htmlto reflect 16 releases and 29 days elapsed, but left the velocity banner headline unchanged:\n\nhtml\n<!-- Headline — still says 25 -->\n<div class=\"headline\">v0.1 to v0.9 in 25 days</div>\n\n<!-- Sub-headline — correctly updated -->\n<div class=\"sub\">Sixteen releases. Blathers can't keep up.</div>\n\n<!-- Stat counter — correctly updated -->\n<div class=\"num\">29</div>\n<div class=\"label\">days elapsed</div>\n\n\nThe headline and counter now disagree on the same page ("25 days" vs 29).\n\n## Why this needs a human decision\n\nThe right correction isn't obvious:\n\n- Option A — update headline to match counter: Change to "v0.1 to v0.9 in 29 days." But 29 is "days elapsed since v0.1 to today (May 9)", not how long the v0.1-to-v0.9 arc actually took. v0.9.0 shipped May 3, which is 23 days from Apr 10. Saying "29 days" is technically inaccurate as a historical claim.\n- Option B — treat headline as a fixed historical tagline: Keep "25 days" as a snapshot from when it was written (around v0.9.2 / May 5) and update only the counter going forward. But a reader seeing both numbers on the same page will be confused.\n- Option C — reword the headline to avoid a specific number: e.g. "v0.1 to v0.9, one sprint" or omit the day count from the headline entirely.\n\n## Acceptance\n\n- The headline and days-elapsed counter onpublic/version-history.htmltell a consistent story.\n- No reader is left wondering which number is correct.\n\n## References\n\n- PR #123 — doc-sync run that updated the counter but missed the headline\n-public/version-history.htmlvelocity banner block