I3324 — After every deploy the published homepage's hero choices are probed and found reachable

✕BLOCKED wave 2 · p2 · verification profile · parallel safe

Part of a-visitor-understands-and-checks-majordomus — A first-time visitor of majordomus.dev understands what Majordomus does and can check every claim it makes.

Objective

Extend scripts/pages verify --smoke so that, after a deploy, it reads the hero choices the published homepage offers and requests each one, failing when a choice's page is absent, with no route list kept by hand; no site feature is added.

Why

Split from I3223 (verification finding: one worker, one issue, one PR); I3223's acceptance line on scripts/pages verify --smoke is carried here. The intent is about a visitor of majordomus.dev, and the critique of a-visitor-understands-and-checks-majordomus found that no issue verified the published site; I1600 did that with scripts/pages verify --smoke for the earlier homepage. Sources: chatgpt-majordomus:c215#8.

Current state

Verified on master 707a04c7ce8: scripts/pages verify --url URL --commit SHA --smoke fetches every deploy.smoke route the deployment declaration lists and checks its marker; no hero choice is among them, and the choices do not exist until I3223 lands.

Desired state

The smoke verification derives the hero choices from the published page and probes each.

Scope

• scripts/pages

Out of scope

• Changing the homepage
• Probing pages other than the hero choices' targets

Dependencies

• I3223○READY The homepage hero lets a visitor switch between recorded scenarios, each ending in the refusal it proves

Acceptance criteria

• After a deploy, scripts/pages verify --url <site> --commit <sha> --smoke requests every hero choice of the published homepage and reports each
• A fixture homepage whose hero links a missing page fails the smoke verification
• The criterion a-visitor-understands-and-checks-majordomus#the-published-page-is-probed is switched to evidence: test, ref the case that holds the fixture, in the change that adds it

Validation

• majordomus plan validate
• bash test/run.sh 333_homepage_narrative

Evidence required

• case_the_published_hero_is_probed

Evidence

None recorded. Every token above needs a command or an artifact behind it before this issue can be completed; narrative is refused.

Timeline

started

—

verified

—

completed

—

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/I3324.yaml. Read it back with majordomus plan show I3324.