t1k:unity:web:validate
| Field | Value |
|---|---|
| Module | web |
| Version | 2.32.3 |
| Effort | high |
| Tools | — |
Keywords: browser, deployment, device-matrix, headers, integrity, smoke-test, validate, web, webgl
How to invoke
Section titled “How to invoke”/t1k:unity:web:validateValidate a Unity Web Deployment
Section titled “Validate a Unity Web Deployment”Validate the live deployment, not only the local build directory. This command is read-only.
Preconditions
Section titled “Preconditions”- A deployment manifest produced by
/t1k:unity:web:buildis available. - The candidate is served through the same HTTPS origin, CDN, redirects, and embedding topology intended for release.
- Target browsers and representative desktop/mobile devices are named.
Workflow
Section titled “Workflow”-
Validate the live HTTP contract:
Terminal window bun .claude/skills/t1k-unity-web-validate/scripts/validate-web-deployment.cjs \https://example.test/game/ --manifest ./deployment-manifest.jsonWhen running from this source repo, use the module-local path under
.claude/modules/web/skills/t1k-unity-web-validate/.Add
--integrityto download raw artifact bytes and compare SHA-256 digests. This is stronger but may transfer the complete build. Cross-origin redirects are blocked by default; use--allow-cross-origin-redirectonly for an intentional HTTPS CDN handoff. HTTPS downgrades remain blocked.--timeout-msis a wall-clock deadline per resource, and integrity downloads are capped at the artifact byte count recorded in the manifest. Use--format markdownfor a reviewable report. -
Run the cold-cache and warm-cache browser smoke paths.
-
Capture console errors, failed/blocked requests, loader progress, time to first interaction, and the first playable frame.
-
Validate input, audio unlock, persistence, resize/orientation, fullscreen, iframe behavior, offline/reconnect handling, and a representative long session.
-
Repeat the agreed browser/device matrix and classify gaps as release blockers, accepted exceptions, or follow-up work.
Read references/browser-validation-matrix.md before claiming release readiness.
Required output
Section titled “Required output”- Candidate URL, source revision, manifest digest, timestamp, and cache state.
- HTTP contract result per document/artifact, including redirects and mismatched headers.
- Optional artifact integrity result.
- Browser/device/version matrix with pass, fail, blocked, or not-run status.
- Console/network evidence and observed runtime metrics.
- Release verdict with explicit exceptions and reproduction steps for every failure.
Executed by
Section titled “Executed by”The matrix sweep delegates to cheap-tier agents; only the release verdict stays on a reasoning
tier (routing SSOT: rules/orchestration-rules.md § “Task-Type → Agent Routing”):
| Step | Agent |
|---|---|
| Read each HTTP response header / artifact SHA off the manifest and the live responses | t1k-fact-fetcher |
| Compare artifact digests against the manifest and quote the mismatch | t1k-data-verifier |
| Poll each browser-matrix run to a terminal pass/fail state and report per cell | t1k-ci-watcher |
| Label each matrix cell / console finding against the skill’s pass conditions | t1k-list-classifier |
| Aggregate the matrix rows into the pass/fail/blocked/not-run table | t1k-metrics-reporter |
| Classify gaps as release blockers, accepted exceptions, or follow-up work | reasoning tier — a release call, not a label |
| Write reproduction steps for every failure and the release verdict | reasoning tier — decoding a failure is diagnosis (t1k-debugger), deciding what to do about it is t1k-code-reviewer |
The pass conditions are stated item-by-item in the validation protocol, so labeling a run against
them is fully specified before the agent starts — that is what makes the sweep cheap-tier work
rather than triage. The moment a console error is handed to t1k unity console output and the question
turns from which cell fails? to why does it fail here and not on desktop?, it has changed tier,
and that is a different agent rather than a bigger model on the same one. This command is
read-only, so no executor step holds write tools
Safety boundaries
Section titled “Safety boundaries”- Never mutate CDN, hosting, browser, or project configuration during validation.
- Never send credentials, production user data, or destructive game actions through a smoke test.
- Never treat an HTTP-only pass as proof that gameplay works.
- Never generalize one Chromium desktop run to Safari, Firefox, mobile, iframe, or private mode.
- Run
--integrityonly when downloading the full candidate build is acceptable.