Browser QA playbook
This page packages the QA method as a public artifact: open the live route, verify state through the DOM or source-visible hooks, check desktop and mobile layouts, confirm discovery wiring, read cache state, and keep public claims inside what the live URLs can support.
QA Loop
A technical reader should be able to understand how the portfolio surfaces are checked. These steps are the public-facing version of the run loop used around Aimaxin proof pages.
Live route first
Each proof claim is tied to a public Aimaxin route. The check begins by opening the direct URL, reading the visible page state, and confirming the artifact does not depend on a private repo, hidden credential, or unpublished screenshot.
State readback
The Arcane Harmonizer build exposes stable controls and source-visible readback hooks, so future checks can inspect game state, advance time, exercise buttons, and verify local save/export behavior with less manual ambiguity.
Responsive readback
Portfolio routes are checked at desktop and narrow mobile widths so proof cards, buttons, nav links, and long technical labels do not overlap or force horizontal scrolling before a link is promoted.
Discovery wiring
A shipped proof page is stronger when it is wired into portfolio cards, the content map, shared discovery data, RSS, sitemap, and deploy manifests. That makes the work easier to audit and less dependent on one manually pasted URL.
Cache-aware proof
Broad pages can lag behind direct routes when an edge cache is stale. The playbook keeps public posts on hold when plain canonical reads do not expose the newest proof wiring, and uses direct fresh routes for Featured or Projects instead.
Claim boundaries
This artifact supports claims about implementation, QA, routing, publishing operations, and public proof packaging. It does not claim traffic, revenue, user counts, clients, rankings, certifications, adoption, or hiring outcomes.
LinkedIn Use
Featured title
Direct proof page for the verification loop behind Codex-built Aimaxin work: live route checks, state readback, responsive QA, cache-aware promotion decisions, RSS, sitemap, and claim boundaries.
Project description
Documents how live Aimaxin artifacts are checked before public promotion: direct URL readback, DOM/state hooks, desktop and mobile layout checks, discovery-file wiring, and cache-sensitive posting rules.
Post boundary
This route can support a profile proof link immediately after deployment. A broader public post should wait until plain portfolio, compact proof, all-content, RSS, and sitemap reads expose the new playbook.
Proof Boundary
Supports
This page supports claims about browser QA, live route readback, responsive checks, source-visible hooks, discovery plumbing, deploy verification, and LinkedIn-safe proof packaging.
Does not support
This page does not claim traffic, revenue, users, engagement, rankings, clients, certifications, employer approval, hiring results, or product adoption.
Safest use
Use the direct route when the reader needs to see how the public artifacts are verified, not just that a portfolio page exists.
Next check
Public posts should stay tied to routes that open cleanly on plain live reads. If broad pages remain stale, point profile surfaces at direct proof routes instead.