[mrbobbytables]

Summary

Reworks /events so the index shows the latest year's events, newest first, and every event is listed in a year-grouped sidebar (newest year first, only the newest expanded), per the new ADR 0012, which this PR adds and marks Accepted.

Remit: end users of /events get one page per event, a year-ordered sidebar listing every event, and an index that always shows the most recent year rather than a hand-maintained Upcoming/Past split.

• Each event is its own page at docs/events/<year>/<slug>.md with an event: front matter block (start, end, location, url). KubeCon NA 2025 and 2026 move onto their own pages, taking the Michelin award photo and <EndUserTalkSchedule /> with them.
• scripts/lib/events-catalog.mjs is the one reader of those blocks: it validates them (ISO calendar dates, end >= start, year directory matches start, absolute http(s) url) and sorts latest first.
• sidebars.js builds the events sidebar from it; the Events navbar item becomes a docSidebar entry.
• scripts/lib/events-catalog-plugin.mjs publishes the same groups as global data (it lives beside the reader rather than under src/ because the browser coverage lane requires every src/** file to be measured in the browser, and the plugin runs only in Node). src/components/EventsIndex reads it and hands the years to a hook-free EventsCatalog, which renders the latest year with a decorative calendar block, <time> range and location, and links to earlier years.
• tests/e2e/fixtures/docs/events-catalog.mdx and a coverage-gated spec render EventsCatalog with the empty catalog and single-day, cross-month and cross-year events, shapes the published pages never hold; formatDateRange()'s unparseable-date guard is an accepted data-shape region (ADR 0007), since events-catalog.mjs rejects such pages at build time.
• formatDateRange() joins shared/formatDate.js; the events suites join the content-only CI focused list and docs/events/2026/kubecon-na.md the data-backed set (ADR 0011).

Based on #2035, which it includes; merge that first. The two PRs disagreed about tests/events-page.test.mjs (#2035 listed it in FULL_PATH_ONLY, this PR puts the events suites on the focused path); this branch now carries the focused-path choice and drops the FULL_PATH_ONLY entry.

• AGENTS.md and the doc-authoring skill describe adding an event by adding a page.

Verification

• npm run check:format, check:spelling, check:lint, check:unused, check:duplication, markdownlint on the changed documents
• npm run test:unit:coverage:check (all gates met; src 100% lines and regions)
• npm run test:mutation -- --mutate scripts/lib/events-catalog.mjs,src/plugins/events-catalog.mjs,src/components/EventsIndex/index.js,src/components/shared/formatDate.js: 92.31 initially, 95.36 after tightening; the remaining survivors are equivalent mutants (the Date round-trip subsumes the regex guard; < vs <= under a !== check). After the follow-up commit, --mutate scripts/lib/events-catalog-plugin.mjs,src/components/EventsIndex/index.js scores 100.
• npm run build:production, then events, events-catalog-fixture, end-user-talk-schedule, navigation, practitioners-home, accessibility, docs-routes and search e2e specs
• The full browser coverage lane locally (build:e2e:coverage, test:e2e:coverage, 439 pass, report:e2e:coverage with the CI thresholds and --require-source-files): source lines 100%, no stale accepted regions

Checklist

• Content speaks to end users (see
  CONTRIBUTING.md)
• Commits are DCO-signed (git commit -s)
• Site builds without new warnings

[netlify]

✅ Deploy Preview for endusers ready!

Name	Link
🔨 Latest commit	52d7e93
🔍 Latest deploy log	https://app.netlify.com/projects/endusers/deploys/6ae5f1802b59433f425384ea
😎 Deploy Preview	https://deploy-preview-2037--endusers.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[hivecommons-hive]

The required "End-to-end coverage" check fails deterministically at this head — source line coverage 99.92% against the 100% gate — and it will fail on every re-run, because two new lines are unreachable in any e2e build of the authored tree. From the run's own report (artifact e2e-coverage, run 41203899322, report.txt): src/components/EventsIndex/index.js | 97.67 | 94.12 | 21 63.

• src/components/EventsIndex/index.js:21 — the dayLabel ternary consequent String(from.getUTCDate()) is taken only for a single-day or cross-month/cross-year event. Both event pages on this branch (2025 Nov 10–13, 2026 Nov 9–12) are multi-day within one month, so no build executes that line.
• src/components/EventsIndex/index.js:63 — the empty-state return <p>No events have been announced yet.</p> can never run: the plugin reads docs/events/<year>/ from the real site dir, which is non-empty on this branch.

The ADR 0007 accepted-regions registry won't absolve these: tests/tools/e2e-coverage-report.mjs computes uncoveredLines directly from line counts (≈ lines 989–996) before accepted entries are matched — acceptance drops a span from the region denominator only, and the failing gate here is --check-source 100 (lines). The existing escape hatch for exactly this shape is the fixture machinery (E2E_FIXTURE_DOCS_PLUGIN / endusersE2EDataFixtures in docusaurus.config.js:211–237), but no fixture was added for EventsIndex; the alternative is to drop the unreachable branches (the single-day/cross-month collapse and the empty state) until content can exercise them. formatDateRange's single-day/cross-year arms (src/components/shared/formatDate.js regions 42, 43, 46) are similarly unexercised but only dent the region score, which still clears 96.

Everything else I read looks correct:

• scripts/lib/events-catalog.mjs validation is sound; the yaml package's default YAML 1.2 core schema keeps unquoted start: 2026-11-09 a string (unlike js-yaml's default), so isCalendarDate's typeof check and the string comparisons all hold against the actual front matter in docs/events/2025/kubecon-na.md and docs/events/2026/kubecon-na.md.
• The index and sidebar genuinely cannot disagree: sidebars.js and src/plugins/events-catalog.mjs both consume groupByYear(collectEvents(...)), and a malformed page throws EventPageError at config load, failing the build with the page named.
• tests/e2e/events.spec.js deriving expectations from the pages (with its own restated ordering rule) matches the awards.spec.js pattern and will cover new event pages on arrival.

The PR body's "e2e specs (165 pass)" is accurate for the test lane but doesn't extend to the coverage lane, which is what blocks the merge. Once lines 21/63 are either exercised by a fixture or removed, this looks ready to me. I have not approved or closed anything — flagging for the author.

— hive: agent=reviewer backend=copilot model=claude-fable-5 copilot=1.0.88

[mrbobbytables]

Rebased onto #2035 and pushed a follow-up commit (fef4128) addressing the failing "End-to-end coverage" check:

• src/plugins/events-catalog.mjs moves to scripts/lib/events-catalog-plugin.mjs; the lane requires every src/** file to be measured in the browser, and the plugin only runs in Node at build time.
• EventsIndex is split into the plugin-reading default export and a hook-free EventsCatalog, and a coverage-build-only fixture page (tests/e2e/fixtures/docs/events-catalog.mdx) renders the empty catalog and single-day, cross-month and cross-year events, which the published pages cannot reach. formatDateRange()'s unparseable-date guard becomes an accepted data-shape region (ADR 0007).
• The branch now includes ci: run every suite that reads an authored tree on the document-only path #2035's commit and resolves the one semantic conflict between them: tests/events-page.test.mjs is on the focused document-only path here rather than in FULL_PATH_ONLY. Merge ci: run every suite that reads an authored tree on the document-only path #2035 first; this PR then reduces to its own two commits plus the fix.

The full coverage lane passes locally with the CI thresholds (439 e2e tests, source lines 100%, no stale accepted regions); unit coverage, mutation (100 on the two touched files), lint, knip, duplication and the production build are green.

[hivecommons-hive]

Read the full tree at pr2037 (head 52d7e93), not just the diff. This looks correct to me; no defects found.

What I verified:

• Front matter contract holds end to end. scripts/lib/events-catalog.mjs reuses splitFrontMatter from architecture-frontmatter.mjs, which parses with the yaml package's default YAML 1.2 core schema — I confirmed parse('start: 2026-11-09') yields the string "2026-11-09", not a Date, so the lexicographic event.end < event.start check (events-catalog.mjs:97) and compareEvents()'s string ordering are sound. isCalendarDate()'s UTC round-trip correctly rejects 2026-02-30-style dates.
• Index and sidebar cannot disagree, as ADR 0012 claims: sidebars.js:40 and scripts/lib/events-catalog-plugin.mjs both consume collectEvents()/groupByYear() from the single reader, and tests/events-sidebar-contract.test.mjs pins the shape (index first, newest year expanded).
• Both event pages validate against the contract: year directories match event.start (2025/2026), URLs are absolute, end >= start.
• Heading-level change in EndUserTalkSchedule (h5→h3, h6→h4) is right in the new context: the schedule now renders under the event page's ## End User talks rather than the old index's deeper nesting, so h3/h4 restores a correct outline.
• Base #2035 has merged (main @ 01ceee8), so the "merge that first" note in the body is resolved; the branch carries the focused-path choice for tests/events-page.test.mjs as described, and docs/events/2026/kubecon-na.md joins DATA_BACKED_DOCUMENTS (content-only-ci.mjs:23).

One dev-ergonomics note, not a defect: getPathsToWatch() reloads the plugin's global data when an event page changes, but the sidebar in sidebars.js is computed at config load, so a newly added event appears in the dev-server index before it appears in the sidebar until restart. Production builds are unaffected.

All checks are green (unit coverage, mutation, e2e, e2e coverage). Approval itself is a maintainer's signature — leaving that to a human.

— hive: agent=reviewer backend=copilot model=claude-fable-5 copilot=1.0.88