48 of 63 generators do not render the SF 005 layout (SF 006 not implemented) #199

Only 15 of the 63 generators render the SF 005 index layout (ol.post-list > li.post-item > h2.post-item-title > a[href]). The other 48 ship the 005 assets (assets/ssgberk.css, assets/ssgberk.png) but not the 005 page markup. Nothing catches this, because the SF 006 conformance checker (tools/check_conformance.py) is not implemented yet: results record conformance: unchecked.

This came up in BenchCommons/tools-benchmark#25 (spec 009, output quality pass). For those 48 generators, the pass now picks the audited post from output_glob instead (postSource: "glob"). Their Lighthouse, SEO and accessibility numbers therefore describe each generator's own templates, not the shared reference layout.

Generators on the 005 layout (15)

bridgetown, cryogen, docfx, franklin, hakyll, jbake, laika, lume, lustre-ssg, nesta, plenti, publish, soupault, statiq, tableau

Generators not on the 005 layout (48)

• SF 006 tasks 10–26 (the 17 originals): hugo, gatsby, jigsaw, nikola-mako, jekyll, nanoc, middleman, metalsmith-handlebars, metalsmith-nunjucks, zola, astro, eleventy, hexo, nextjs-export, vitepress, pelican, mkdocs.
• Spec 007 waves 1–4, not covered by SF 006 (31): analog, antora, cecil, cobalt, docmd, docusaurus, dumi, emanote, iles, ink, lektor, marmite, mdbook, nextra, nimib, nuxt-content, observable-framework, quarkdown, quarto, quartz, rspress, sculpin, sphinx, starlight, sveltekit, tanstack-start, vike, vite-ssg, vuepress, zensical, zine

Tasks

• Implement SF 006 tasks 1–9: the checker and its build.sh integration.
• Migrate the 17 originals: SF 006 tasks 10–26.
• Add the spec 007 generators above to SF 006 (or a follow-up spec), one task per generator, so the conformance enforcement in SF 006 task 27 covers all 63.
• Re-run BT spec 009's quality pass once each generator emits the 005 layout (postSource should become index).

Detected with grep -rl --exclude='*.css' post-item <generator dir> on master 0012b37. A generator that builds the markup in code without the literal class name would be miscounted, so check each one when migrating.