The site now publishes two weekly data pages from versioned data files. This entry records the change from the assigned issue record only.
Motivation
Readers comparing models need current prices and scores without chasing vendor pages. Versioned data files with a source on every row keep the numbers checkable, and a weekly refresh keeps them honest. The new pages reuse the established legal-page pattern so they feel native to the site.
What changed
Two versioned data files now hold the tables, and every row carries its own source link and check date. The builder renders the prices page and the benchmarks page from shared templates with last-updated stamps, and both pages join the footer navigation and the sitemap. A refresh script validates the files, flags anything older than ten days, and prints the digest line the morning digest copies into its release note. The digest for the day links to the prices page and the benchmarks page.
How it was done
The work ran on a short branch cut from the main line. Data files were added first with a builder gate that fails the build on a missing source or a bad date, then templates were added reusing the shared table styles with no page-specific scripting, then the refresh script and tests were added. The change ships with this log entry in the same pull request.
Verification evidence
The site build exits success, the full test suite is green, and the presence gate prints success. Both pages render tables with source links and last-updated stamps, both appear in the sitemap, and the refresh script prints the digest line on fresh data while exiting nonzero on stale fixture data.
How this entry was built.
Each step ran through the company pipeline on the assigned issue.
- The remote and the login checked out, and a fresh branch was cut from the main line.
- The data files, templates, builder wiring, and refresh script landed together.
- The pull request opened with the change and the log entry.
- Security and quality reviews passed the shipment.
Pipeline.
Each stage ran in order; blocked stages looped back through fix and re-review.
the pull request · merge pending · the branch
- done — Preflight and branchDEV · — Validated the remote and the login, then cut a fresh branch from the main line.
- done — Data pagesDEV · — Shipped data files, templates, builder wiring, refresh script and tests with a green build.
- done — Main syncDEV · — Synced main share-meta plus daily digest into the branch, resolved the artifact budget cap, and rebuilt green.
Verdict trail.
| Stage | Agent | Verdict | SHA | Why |
|---|---|---|---|---|
| Preflight and branch | DEV | done | commit | Validated the remote and the login, then cut a fresh branch from the main line. |
| Data pages | DEV | done | commit | Shipped data files, templates, builder wiring, refresh script and tests with a green build. |
| Main sync | DEV | done | commit | Synced main share-meta plus daily digest into the branch, resolved the artifact budget cap, and rebuilt green. |
Why each step ran.
- DEV
- The data pages reuse the established legal-page pattern with the shared table styles, so no new visual language was introduced. The builder validates every row before rendering and fails the build on a missing source or a bad date. The refresh script enforces the ten-day staleness rule and prints the digest line on success.
- Director
- This change adds routine data pages inside the cleared design pattern with no new components. Security and quality reviews are pinned to the exact pull-request head in parallel child issues. Release approval fires only when both verdicts pass that exact head.
Receipts.
●●●