playablelabs-cocos-zero-change
PlayableLabs Packer: Cocos Customers See Zero Change
Section titled “PlayableLabs Packer: Cocos Customers See Zero Change”Advisory: a kit ships no hooks, and a skill-local script is not an enforcedBy: surface
(accepted: hook: / gate: / cli: + advisory). The real gate is PlaybleEngine’s own CI.
Caveat: paths: loads this rule on the first READ of a matching file, not at session start.
Editing the packer (The1Studio/PlaybleEngine)? Existing Cocos customers must see ZERO behaviour
change; only the web and none engine hosts may change. Prove it on BOTH engines.
- Gate new behaviour on
web/none. Cocos output stays byte-identical toci/engine-matrix/baselines/; the parameter publish sendsengineTypeforwebonly. The page splash (PlaybleEngine PR #265, unmerged) is the worked case: on by default forwebandnone, and--engine-host cocos-3.8gets nothing and refuses--splash-config/--splash-params. - Engine seam.
cc/window.cc/legacyCC/ Cocos chunk or build-path names live only in the filestests/engine-seam-gate.test.jsallows (src/engine/cocos38/**,src/runtime/engine-host-cocos38.ts,scripts/lib/engine-probes-cocos38.cjs). Never widen that list: move the code behind the seam. - History. Never force-push or rebase PlaybleEngine, PlayableLabs or ParamTool: merge
origin/master, push normally, commit by pathspec, nevergit stash. - Engine fork last. Order: per-project module switch, then packer code (
src/runtime/,src/adapters/), then a minimalstudio/3.8.7fork patch, listed in the PlaybleEngine repo patch ledger (its PATCHES file, not a rule). Need the third? Stop and report. masteris unprotected and Jenkins packs from it: a merge is a production deploy. A PR-branch canary never publishes; baselines compare to a LITERAL base SHA, neverorigin/master.
Proof: skill t1k-playablelabs-base-change-proof; run
bun scripts/verify-both-engines.cjs --pr <n> --base-sha <40-hex> (skill dir); exit 0 only when
the 9 engine-matrix shards and, if the PR touches the Jenkinsfile paths, jenkins-pair are green on
the PR head SHA.