playablelabs-playthrough-before-build
PlayableLabs: No Build Without a GREEN Playthrough, Visually Complete
Section titled “PlayableLabs: No Build Without a GREEN Playthrough, Visually Complete”Applies to every playable (Cocos, web, none) before ANY build or delivery: a PlayablePacker trigger,
t1k-playablelabs-ci-deliver, a pack meant for a network. Skill: t1k-playablelabs-base-playthrough.
Full text and rationale: that skill’s references/visual-completeness.md.
- GREEN on the commit being built, played against the original. RED: fix, rerun. UNVERIFIED is not a pass:
say so in the delivery post (with the gate’s
[playthrough-gate] ACCEPTED-UNVERIFIEDline) and build only if the user accepts it by name (--accepted-by). The report is committed and pushed, and is the one the game’spackage.jsonplaythroughdeclares.bun run check, smoke, unit gates andcompare-play.cjsscreenshots do NOT substitute. - No profile, no build. Write the game’s profile first (
references/profile-guide.md) and commit it. - Coverage is by state, level and time: every state and progression level, a frame strip (8+ frames) across each
animated state, per-frame invariants for the whole run. Declare
probe,invariants,strips,levelsin the profile (references/coverage.md); a profile declaring none is UNVERIFIED, not a waiver. - Visual completeness is its own bar: every effect, animation and colour treatment the ORIGINAL has must be in
the port. Before the first run, write
docs/FIDELITY-INVENTORY.md(orfidelity/inventory.json) from the original, one row per effect with a port status (present|missing|stand-in|unverified|waived:<reason>). The delivery gate refuses the build while any row is notpresent(or a same-tier README GAPS row stands); a waiver is per row, written, accepted by name. DeclarecolorandeffectPresencein the profile. A stand-in asset is a defect to fix. - Read the frames, record the verdict: per state / level / strip answer is the VFX there, is the animation
there, is the colour contrast the same (
playthrough/vision-review.json). A negative answer is RED; an unanswered item is UNVERIFIED. - A waiver is capped and evidenced.
visualWaiver/frame: falseskip a capture, never the requirement: name the state, why a comparison is impossible and what was looked at instead; a profile-level waiver cannot cover the whole profile. A negative vision verdict, or a failingcolourstate, needs a named waiver (waivers[],visual-completeness.md); the gate needs--accepted-byfrom itsacceptedBy: ACCEPTED-WAIVED, never GREEN. - Report in the delivery post and PR: profile, states and levels, invariants, inventory and waived rows, vision
verdicts, overall verdict, every UNVERIFIED item (link the committed
playthrough/report.md).
Related
Section titled “Related”t1k-playablelabs-base-clean-room (G4 gate), t1k-playablelabs-ci-deliver, playablelabs-cocos-zero-change.md.