In brief
The new project analysis turns the research queue into a public, searchable report. The same generator that refreshes the homepage and library progress displays now builds the report and refuses a stale release.
One source for the count
The article programme has changed as pages were published and one case study was retired. A hand-written total on a public page could quietly diverge from the queue that controls the work. The analysis report reads that queue directly. It shows 230 active commissions, 12 published enrichments, 218 available editorial pages and 12 planned additions as recorded in the 30 September release. Those figures describe different things: a current page is not necessarily a completed enrichment.
The report lists all 21 work blocks and every commission. Search and combined filters help readers inspect what is available, what is planned and which records have completed the current source-led review. Its publication history shows dated releases; it does not turn a planned record into a published page.
Evidence and presentation stay connected
The report also shows the source library's recorded 60 holdings and 17,165 extracted pages. Those are holdings and extraction counts, not proof that each historical claim has been verified. The source register and each study remain the places to inspect a work's role and a claim's evidence.
The page reuses the site's pyramid instrument, progress styles and established type. Its searchable queue progressively enhances a readable page rather than making the record depend on a script. The Case Studies, Temples and Units retain their own paths into the same programme.
A release gate for the public report
The progress command now regenerates the analysis page alongside the homepage and library plates. Its check mode fails when the published view is stale against the queue. The 30 September release checked counts, links, structured data, source extraction and article prerequisites, then tested desktop and narrow screens, search, filters, empty state and reset before confirming source-to-mirror parity and the public route.
The result is a more useful progress measure: a visitor can inspect each claim behind a headline count, while the next Build Log entry can report a later release without rewriting this one.