Skip to content

t1k:playablelabs:ci:build-qa

FieldValue
Moduleci
Version1.17.3
Effortmedium
Tools—

Keywords: build qa, build report discord, latest build discord, qa build, quick play qa, tag discord build, test build, test quick play

/t1k:playablelabs:ci:build-qa
<discord channel/thread id or link> [--job <job path>] [--game <repo-dir>] [--ref-dir <dir>] [--dry-run]

Build QA from a Discord channel → reply with the verdict

Section titled “Build QA from a Discord channel → reply with the verdict”

Give it the Discord channel (or thread) a game’s builds are posted in. It finds the newest message carrying a Quick Play link, runs the build QA that pla-from-ref runs (stages 16–18) on that link, and replies to that same message with the verdict, tagging the game’s people.

Boundary. Never triggers a build and never edits a job (t1k-jenkins-build / t1k-jenkins-job). Pipeline params: t1k-playablelabs-ci-jenkins. The checks belong to their own skills; this skill picks the build, sequences the checks, collects receipts and delivers the report. A build only exists if the playthrough gate passed (t1k-playablelabs-ci-deliver step 3: a GREEN playthrough/report.json for the built commit, or a logged --accept-unverified --accepted-by, shown as ACCEPTED-UNVERIFIED and never as a pass): this QA never replaces that playthrough, and never reports a build as clean on smoke, flows and pla-qa alone.

InputSourceMissing means
Discord channel / threadarg: id or discord.com/channels/<guild>/<channel> linkask; never guessed
Job filter--job CocosPlayableLabs/<Job> when the channel carries several gamesnewest link of any job
People to taggame repo: discordTagUserIds in service-bindings.json, then discord.tagUserId in .claude/t1k-project-links.jsonAskUserQuestion for ids, offer to save them
Game repo dir--game, else cwdflows run the generic link flow (checks.md (references/checks.md) § 3)
Reference dir--ref-dir, else the pla-from-ref layout in the game repopla-qa check blocked

Tag ids are Discord snowflakes (17–20 digits), never inferred from a display name.

A Quick Play link has one layout, and the job path in it IS the Jenkins job: <cdn>/jobs/<job path>/<n>/Build/Client/<engine>/<Name>-<ver>-<n>/[<network>/]index.html (e.g. …/jobs/CocosPlayableLabs/PlayablePacker/133/Build/Client/Cocos/TimelineUp-1.0.1-133/common/index.html).

  1. Find the build. discord-mcp channels_get (must exist; record type and guild), then messages_read the recent messages to <scratch>/messages.json and run:
    Terminal window
    bun scripts/build-qa-report.cjs find-latest --messages <scratch>/messages.json [--job <job path>]
    Exit 1 = no Quick Play link in that page: read the next page (older) once, then STOP and say so. The hit carries messageId, playUrl, job, number, name, version, network. Show the user which build was picked (name, version, #number, message link) before testing.
  2. Build facts. Write <scratch>/build.json from the hit plus sizeBytes (step 3a) and replyTo (the build message’s jump link). For the size delta, Jenkins MCP getBuild on job / number - 1…: the previous successful build’s same file.
  3. Run the five checks (references/checks.md), one receipt each in <scratch>/receipts/<name>.json: artifact first, then smoke, flows, pla-qa in parallel, and playthrough (bun scripts/build-qa-report.cjs playthrough-receipt --game-dir <clone> --game-repo <ssh-url> [--branch <b>] [--commit <sha>] > <scratch>/receipts/playthrough.json). A check that cannot run writes blocked with the reason. Never skip, never eyeball instead of a gate.
  4. Render.
    Terminal window
    bun scripts/build-qa-report.cjs render --receipts <scratch>/receipts --build <scratch>/build.json \
    --tags <id,id> [--prev-size <bytes>] > <scratch>/report.json
    PASS only when all five pass; any fail → FAIL; else any blocked → BLOCKED.
  5. Deliver (references/discord-report.md): post report.json.message in the channel (discord-mcp cannot reply; the Re: line links the build message), read it back, then bun scripts/build-qa-report.cjs verify-mentions --message <posted.json> --tags <id,id>. Exit 0 is delivery; exit 1 means not delivered (fix, re-post, report the missing ids). --dry-run stops after step 4 and prints the message.
  6. Report to the user: the build tested, verdict, per-check table, the reply’s link, and any blocked reason they must act on.
CheckEvidence
Right buildfind-latest output: newest Quick Play message in the channel; user shown which one
Every check ranfive receipts; render shows no no receipt reason
Deliveredposted message carries the Re: link to the build message, verify-mentions exit 0
  • A build with no GREEN playthrough report is a gate bypass. The playthrough receipt (playthrough-receipt, the delivery gate with no escape) computes it: a missing receipt, a missing, stale, tampered or UNVERIFIED report is blocked and the verdict is BLOCKED; RED is fail. By hand, read playthrough/report.json and playthrough/accepted-unverified.jsonl in the game repo at the build’s commit: say in the reply which verdict the playthrough had and quote every logged --accept-unverified reason with who accepted it (only entries for that commit that name an accepter count). A build whose commit has neither is reported as BLOCKED: no playthrough evidence, not as a pass.

  • Newest link, not newest message. Chat after a build is normal; find-latest skips messages with no Quick Play link. A channel shared by several games needs --job, or the wrong game is tested.

  • Quick Play is the build, the editor is not. Flows run with --url <Quick Play>, never against the editor preview. A preview pass reported as a build pass sends a broken build to people.

  • Passing layout and top-face colours is not matching look. Add the per-region colour rows to the pla-qa receipt (mean HSV S̄ ±0.04, luma σ_L ±0.03, per-channel mean ±8/255 — references/checks.md § 4); an out-of-band row fails the verdict, and an unmeasured one is visual-parity: BLOCKED, never implied green. Colony Flow’s web port shipped less saturated and lower contrast than its Cocos original with smoke, flows and pla-qa all green.

  • A fast-looking build can still run at a third of the original’s frame rate. The packed artifact is what a phone runs: record the runtime-performance rows (JS ms/frame p50/p95, draw calls, triangles, alloc) and whether the engine half ships un-obfuscated (references/checks.md § 4). A fully obfuscated game.js was the measured cause of the ~2.3x slowdowns; an unmeasured row is runtime-performance: BLOCKED, never implied green.

  • One network page is not every network. A PlayablePacker link names one network dir (common); the smoke check covers the rest from the build’s artifacts.

  • Exit 2 is not a pass for smoke, preview-verify and pla-qa alike: it is blocked (tooling). Exit 137/124 means the run never finished.

  • No game flows is not a blocked flows check. The Quick Play link is always testable: run the generic link flow, plus one gameplay tap and the CTA tap. Only a dead link blocks it.

  • Mentions that did not land. A <@id> inside a code block, or an id not in the guild, posts without pinging. Only verify-mentions exit 0 on the read-back message counts.

  • CTA “fired” is not CTA fired at the right moment. Gate on the step index after the end-card tap and on the expected call count (lane-build-deliver.md Stage 17).

Reading the channel, running scripts/build-qa-report.cjs (find-latest, parse-url, render, verify-mentions), downloading the build and running the packer smoke / preview-verify are mechanical; judging whether a failed flow or a size delta is a real regression, and whether to post to a shared thread, is not. Routing SSOT: rules/orchestration-rules.md § “Task-Type → Agent Routing”.