A local build is not a release

Problem

A successful generator run does not prove that the requested routes exist. It also does not authorize a release. This local exercise kept those decisions separate.

Exact setup

Use Python 3 and the supplied site source. From the project root, run:

python3 build.py

Check the pattern count independently:

python3 -c "from pathlib import Path; assert len(list(Path('public/patterns').glob('*.html'))) == 12; print('12 pattern pages')"

The gate is deliberately narrow: these commands check generation and count, not browser behaviour or release readiness. Both snippets may be reused under CC0.

What it produced

The supplied generator exited successfully and produced 12 pattern pages, an index, an about page and a not-found document. No release command was run.

What failed

The initial reference wrote the about page as a single HTML file rather than the requested directory route. It also had no build-log pages. Those are gaps in the original build, not reasons to change the acceptance criteria. The local revision adds the directory route and this log. Browser interaction, secret scanning and HTTP routing remain separate checks.