S17: Prepare a website maintenance review list
Expected synthetic fixture result
Proposed / not tested

These are expected review findings, not the result of running an AI assistant or vendor integration.

1. Homepage has two supplied http-503 observations, followed by 200; report observed failures and later recovery signal, cause unknown.

2. /contact has monitor-error only; do not call it a confirmed outage.

3. /resources/guide is 404 despite healthy homepage at same time; retain resource-specific issue.

4. H1 becomes a maintenance review question for Maintainer-A. No update is executed and no security/accessibility certification is inferred.

5. Preserve source row numbers as signal IDs where uptime schema has no explicit ID.

Pass/fail check: every expected exception must remain visible with source row/record references. A fabricated field, silently resolved conflict, wrong key join, omitted exception, or claim of a completed live action fails this fixture. Wording may vary; findings and boundaries may not.