Add per-recipe crash-loop launch budget

[OnlyTerp]

Problem

Repeated failed launches are not tracked or quarantined, so a bad recipe/backend can be launched repeatedly with no per-recipe failure budget or clear crash_loop state.

Evidence

• controller/src/modules/engines/engine-coordinator.ts:18-20 has no failure counter/quarantine state.
• controller/src/modules/engines/engine-coordinator.ts:66-87 emits launch-progress error but does not record/count failures.
• controller/src/modules/engines/routes.ts:142-202 calls setActiveRecipe once per request and has no budget check.
• controller/src/modules/system/event-manager.ts:132-151 can already carry optional metadata on launch_progress.
• frontend/src/lib/types/recipes/recipes.ts:152-153 already accepts recipe status: "error".

Proposed direction

Add an in-memory per-recipe crash-loop budget in the controller. After N launch failures in a time window, mark the recipe/runtime as crash-looped, stop additional launch attempts until manual retry/config change, and expose optional state via existing status/recipe/SSE payloads.

Acceptance criteria

• Controller tracks repeated launch failures per recipe over a bounded time window.
• After threshold, launch returns a clear crash-loop response without spawning a new process.
• Successful readiness or recipe config change resets the budget.
• /recipes, /status, or launch_progress exposes optional crash-loop state without breaking existing clients.
• Focused tests simulate repeated immediate-exit/failed launches without starting real model servers.

Non-goals

• No auto-retry scheduler.
• No persistent SQLite crash-loop state.
• No process-manager launch rewrite.
• No frontend redesign in the first slice.

[OnlyTerp]

Prepared for review in PR #155: #155

Branch: OnlyTerp:terp/wp-003-crash-loop-budget
Commit: 04211fd feat(controller): add launch crash-loop budget

Verification already run:

• bun test ../tests/controller/integration/runtime-recipe-contracts.test.ts -t "crash-loop budget"
• bun test ../tests/controller/integration/runtime-recipe-contracts.test.ts
• bun run typecheck in controller
• npm run typecheck in frontend

Known baseline: npm run check:contracts still fails on duplicate AggregatedSession exports outside this WP-003 change.