Skip to content

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.

  1. Gate new behaviour on web / none. Cocos output stays byte-identical to ci/engine-matrix/baselines/; the parameter publish sends engineType for web only. The page splash (PlaybleEngine PR #265, unmerged) is the worked case: on by default for web and none, and --engine-host cocos-3.8 gets nothing and refuses --splash-config / --splash-params.
  2. Engine seam. cc / window.cc / legacyCC / Cocos chunk or build-path names live only in the files tests/engine-seam-gate.test.js allows (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.
  3. History. Never force-push or rebase PlaybleEngine, PlayableLabs or ParamTool: merge origin/master, push normally, commit by pathspec, never git stash.
  4. Engine fork last. Order: per-project module switch, then packer code (src/runtime/, src/adapters/), then a minimal studio/3.8.7 fork patch, listed in the PlaybleEngine repo patch ledger (its PATCHES file, not a rule). Need the third? Stop and report.
  5. master is 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, never origin/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.