Skip to content

merge-first-gate-once

Path-scoped: loads only when editing merge-tree machinery. Lanes stay cheap; the engine’s heavy run happens once, at the tree root.

TierWho runs itWhat
Laneevery leaf and nodesyntax/lint, static checks, the node’s own targeted tests.command
Rootthe merge-tree root, oncethe engine’s full compile and suite (verificationTiers.heavyRun), in root-regen, before the PR
  • A node’s tests.command must not equal the heavy run. tree-check rejects it (testsNotHeavyRun).
  • mergeUpTree.rootHeavyGate: auto (default: off for kit source, required when an engine declares heavyRun, otherwise off with the reason printed), required (missing heavyRun exits 2), off.
  • Briefing a lane: “targeted tests and static checks only; the root runs the full suite once.”
  • Build and test are separate commands: declare ordered heavyRun.steps (one gate slot, stop at the first failing step, passExitCodes for a build that exits non-zero on success):
    "heavyRun": { "steps": [
    { "name": "build", "argv": ["cocos", "build"], "passExitCodes": [36] },
    { "name": "test", "argv": ["bun", "test"] }
    ], "summary": { "kind": "junit", "path": "out.xml" } }
    argv OR steps, never both. Every step’s argv is worker-capped. Detail: skills/t1k-cook/references/merge-up-tree-execution.md (step 5), skills/t1k-team/references/node-file-contract.md § “Lane tier vs root tier”.