Init Script Contract

Every coding session in a multi-session project starts by bringing the dev server up. If the entry point is named differently each time, or takes four minutes, or prompts for input, you burn tokens and wall-clock on every single session. The fix is a fixed set of script names at the project root with a hard contract. The initializer agent writes them once; every downstream session relies on them.

The names are load-bearing — [[shift-notes]] and [[broken-window-check]] both refer to them by name. Do not invent your own.

When to apply

• You are the initializer agent scaffolding a fresh project.
• You just discovered setup exceeds 120s and need to split cleanly.
• You are auditing an existing project whose sessions keep re-discovering how to launch the app.

The five scripts