Type
test
Priority
P2 medium — recurring launch checks should be repeatable without touching live systems.
Summary
Create a read-only script that checks the public site's key surfaces: homepage, about, press, sitemap, YouTube iframe presence, and expected shop slot count.
Why This Matters
The roadmap research identified weekly health checks as useful. NEXT already mentions a read-only Launch Monitor, but the repo has no reusable local command for those checks.
Evidence
Fact:
NEXT.md says a read-only launch monitor exists and forbids mutations.- README documents public URLs and deploy/admin state.
.github/workflows/ci.yml runs local preview smoke, not production health.- Existing launch checks in docs are manual and scattered.
Scope
In scope:
- Public HTTP/HTML checks only.
- No auth, no Vercel mutation, no Shopify mutation, no cart/checkout actions.
- Document command and expected output.
Out of scope:
- Automated scheduling.
- Posting comments.
- GA/Search Console API checks.
- Store-admin checks.
Proposed Approach
Add a Node script under scripts/ that fetches public URLs, validates status codes and simple content markers, and prints pass/fail evidence.
Acceptance Criteria
Tests Required
- Manual test steps: run script against production and, if supported, preview/base URL override.
- Regression tests: verify script exits non-zero against an invalid URL.
Evals Required
Evals required: none, because this issue does not affect AI/agent behavior.
Definition of Done
A future agent can run one read-only command and get a clear health report.
PR Readiness Gate
Before this issue can become a PR, the implementing agent must provide:
- Command output
- Files changed
- Validation target URL
- Known limitations
Dependencies
Commerce truth issue should define expected slot count first.
Risks
- False positives from external embed changes.
- Scope creep into authenticated APIs.
Agent Suitability
Safe for agent after commerce truth is settled.
Suggested PR Title
Add read-only Skywhale launch health check
Suggested PR Body
Summary
Adds a local public-site health script.
Why
Launch checks should be repeatable and non-mutating.
Changes
Adds script and docs.
Tests
Run against production and invalid URL.
Evals
None.
Risks
External embeds may change.
Follow-up
Optional weekly automation can call this later.
Type
test
Priority
P2 medium — recurring launch checks should be repeatable without touching live systems.
Summary
Create a read-only script that checks the public site's key surfaces: homepage, about, press, sitemap, YouTube iframe presence, and expected shop slot count.
Why This Matters
The roadmap research identified weekly health checks as useful. NEXT already mentions a read-only Launch Monitor, but the repo has no reusable local command for those checks.
Evidence
Fact:
NEXT.mdsays a read-only launch monitor exists and forbids mutations..github/workflows/ci.ymlruns local preview smoke, not production health.Scope
In scope:
Out of scope:
Proposed Approach
Add a Node script under
scripts/that fetches public URLs, validates status codes and simple content markers, and prints pass/fail evidence.Acceptance Criteria
/,/about.html,/press.html, and/sitemap.xml.npm run buildpasses.npm run lintpasses.Tests Required
Evals Required
Evals required: none, because this issue does not affect AI/agent behavior.
Definition of Done
A future agent can run one read-only command and get a clear health report.
PR Readiness Gate
Before this issue can become a PR, the implementing agent must provide:
Dependencies
Commerce truth issue should define expected slot count first.
Risks
Agent Suitability
Safe for agent after commerce truth is settled.
Suggested PR Title
Add read-only Skywhale launch health check
Suggested PR Body
Summary
Adds a local public-site health script.
Why
Launch checks should be repeatable and non-mutating.
Changes
Adds script and docs.
Tests
Run against production and invalid URL.
Evals
None.
Risks
External embeds may change.
Follow-up
Optional weekly automation can call this later.