#tooling

The architecture for letting an agent (or CI) drive the live s&box editor: compile-gate, spawn, play, inject input, read telemetry, screenshot, assert, and gate a merge on the numbers, with no human at the keyboard.

The build order for a fresh s&box project a coding agent can actually work in without corrupting itself on day one: skeleton, globals, compile gate, and the ownership discipline that keeps parallel agents from clobbering each other.

Disjoint file ownership, serialize hot files, report-don't-fix foreign errors, resume after interrupts: the concurrency rules that keep agent waves shippable.

MP3 + JSON .sound beside it: no wav/ffmpeg; Distance is in inches; copy schema from addons/menu box_open.sound.

Headless dotnet build is green while the in-editor compiler emits SB1000: Environment/IO/Process/reflection are banned in game code.

Razor HUD emoji and dashes die under Get-Content/Set-Content: edit with byte-safe UTF-8 APIs or a real editor.

Failed package compile leaves the editor running the last-good hotload: multi-symptom 'regressions' are often stale code.

Folders → sbproj → Assembly.cs → 4-object scene → green dotnet build → tagged logs on Play, then optional art tools.

.sbproj + Assets/Code/ProjectSettings/tools layout, 4-object scene + Bootstrap, dotnet build before anything else.

dotnet build reports 0 errors on .razor files the in-editor compiler rejects: the headless build doesn't surface the Razor errors the live editor's Roslyn compiler flags.

Top model plans and reviews; cheaper agents execute on disjoint files; telemetry-driven feel tuning: whitelist and stale-assembly traps included.

If sbox-launcher.exe stays open during a Steam update, files vanish mid-install. Validate via steam://validate/590830.

C# hotloads on alt-tab in ms; scene changes and new Input.config actions need Play/editor restart; failed compile keeps the last-good assembly.

Get-Content/Set-Content re-encodes BOM-less UTF-8 as ANSI; CRLF files break \n-only search-replace: use byte-safe APIs.