Skip to content

t1k:unity:base:lane-kernel-unity

FieldValue
Modulebase
Version5.116.6
Effortlow
Tools—
/t1k:unity:base:lane-kernel-unity

Preloaded into Unity lanes. Each line names a failure an earlier lane already paid for.

Batch gate (t1k unity test, unity-batch-gate.sh)

Section titled “Batch gate (t1k unity test, unity-batch-gate.sh)”
  • Exit 75 is a gate failure (no slot in the bounded wait). Retry later. It is not a result.
  • Exit 77 proves nothing (no results, zero tests, or all skipped). It is never a pass.
  • Exit 2 on EditMode: read the results XML first. Skipped:Ignored is not a pass.
  • Full suite: T1K_UNITY_BATCH_TIMEOUT_SEC=6000 (default 1800; longer exits 124).
  • Never wrap the gate in timeout, or open a second Editor on one project.
  1. C# parse check on every changed .cs file.
  2. Offline compile, when present in the kit (unity-offline-compile.cjs).
  3. Static-ref check (t1k:unity:base:static-ref-check) for prefab, scene or Addressables edits.
  4. Blind-edit validate (t1k:unity:blind-edit:assets) for YAML edits.
  5. THEN one Unity round: t1k unity recompile, then t1k unity test.

unity-t0.sh runs steps 1 to 4 in one call, when present. A green T0 is necessary, not sufficient.

  • Commit after every green T0, pathspec form: git commit -m "..." -- <files>. A reboot kills uncommitted work.
  • Push only your own topic branch. Never push main.
  • Catch up with git rebase origin/<branch>, never git reset --hard (the pin guard blocks it).
  • Mutate the consumer, never the constant a test reads back: that test cannot go red.
  • A RED you did not observe is not a RED: revert the fix in a scratch copy and watch the test fail.
  • Count the results. Zero tests or all skipped is exit 77, not green.
  • A surviving mutation is a finding (t1k:gamedev:testing:red-proof).
  • Mutate with a wrong value, not by deleting a readonly assignment (CS0171; t1k:unity:testing:workflow).
  • Source-text pins strip comments and slice the method body (same skill).
  • 12 px text floor, 8 px text pad, 4.5:1 small-text contrast, thumbnail minimums.
  • When a pin fails, fix the layout. Do not lower the pin.
  • Harness px = used px x scale. Compare both in one unit.
  • Missing FTUEConfig means a bad Library copy, not a code bug. Rebuild the copy from a clean source; never name a donor worktree.
  • Skills are READ, never spawned: Read the SKILL.md or use the Skill tool.
  • UI lane: Read t1k:unity:ui:hud-layout, then t1k:unity:ui:ugui.
  • New Unity API member: doc XML line first (t1k:unity:base:preflight); headless green proves nothing.
  • A pgrep -f wait loop matches its own shell: wait on a sentinel (t1k:unity:testing:workflow).
  • Prefab, scene or .meta edit: Read t1k:unity:blind-edit:assets first.
  • Bash refuses git inside a URL or heredoc, even in non-git commands: use the Write tool.
  • A sibling’s unmerged stub (Mathf): private copy plus a PS row, switched back after merge.
  • dotnet missing from this shell’s PATH does not mean no SDK: probe $HOME/.dotnet before writing “no C# compiler” (trap 12).
  • A cleanup trap deletes only its own files, never a live client’s /tmp/Unity-LicenseClient-* socket (trap 13).
  • Stacked-lane traps (items 1-13): references/stacked-lane-traps.md.

End every report with these three lines, verbatim, even when each says none:

Skills read: <skill names read this run, or none>
Skill gaps: <a skill that lacked what you needed, or none>
Lesson candidates: <one line each, or none>

A kit skill that was wrong, missing or misleading also gets an anchored marker in message text, not in a file: [t1k:skill-bug kit="unity" skill="<name>" bug="<one line>" evidence="<path or id>"] or [t1k:lesson kit="unity" skill="<name>" fragment="<file or section>" reason="<one line>"].