I3094 — The Pages build and check hold a site built in every language

✓DONE wave 0 · p0 · implementation profile · parallel safe

Part of architecture-is-enforced — A violated invariant fails a gate, and green means every required check ran.

Objective

The build and check steps of the Pages workflow are bounded for the site as it is now built, in every language site/i18n/languages.json declares, so a correct site is published rather than stopped by a bound sized for one language.

Why

On 2026-10-20 the first Pages run of the alpha.1 master (39392245576, 82ac259d0ae) built 5100 routes in English and Czech and then stopped at `scripts/pages check` after its 3-minute step bound, so nothing was published and /cs/ stayed a 404 on majordomus.dev. The bound had been sized for the ~2550 routes of one language; the build step of the same run took 172 of its 180 seconds.

Current state

pages.yml bounds `build` and `check` at 3 minutes each.

Desired state

Both are bounded at 10 minutes, with the reason and the run that showed it beside them.

Scope

• .github/workflows/pages.yml
• .ai/repo/project/issues/I3094.yaml

Dependencies

None. This issue is a root of the graph.

Acceptance criteria

• The build and check steps of .github/workflows/pages.yml carry timeout-minutes: 10
• The first Pages run of master after this lands publishes the site, both languages, without a hand deploy

Validation

• majordomus plan validate
• actionlint .github/workflows/pages.yml

Evidence required

• landed_change

Evidence

Timeline

started

2026-10-20T14:25:53Z

verified

2026-10-20T14:26:04Z

completed

2026-10-20T14:26:20Z

Those three fields, the evidence above and the state of the dependencies are all the status is made of. There is no status field to disagree with them.

Canonical record: .ai/repo/project/issues/I3094.yaml. Read it back with majordomus plan show I3094.