feat: Claude for Unity-Builder — AI-assisted build configuration, debugging, and orchestration

[frostebite]

Summary

Add a minimal CLAUDE.md to unity-builder so Claude Code has the context it needs to assist with build configuration, debugging, orchestrator work, and contributions.

Scope

A single root-level CLAUDE.md covering:

• Quick reference — build, test, lint, format commands
• Architecture — entry point, execution paths, key modules, provider system
• Build system — tsc → ncc pipeline, dist/ committed, lefthook pre-commit hooks
• Code conventions — naming, formatting, linting rules
• Testing — Jest setup, test patterns, orchestrator integration tests
• Security — credential handling, input validation, injection risks
• CI workflows — what runs on push/PR

What this is NOT

• No .claude/agents/ definitions — keep it simple for now
• No per-directory CLAUDE.md files — one file at root
• No custom skills or workflows
• No auto-generated content

Why minimal

A focused CLAUDE.md is enough to unlock the core value: Claude can understand the project structure, follow conventions, run the right commands, and avoid security pitfalls. Agents, skills, and per-directory docs can come later as separate PRs once the foundation is validated.

Related

• tracking: Orchestrator LTS (v2.0.0) — Long-Term Support orchestrator release #794 (Orchestrator LTS)
• tracking: Orchestrator LTS Next-Gen — experimental features built on LTS foundation #795 (Orchestrator Next-Gen)

[frostebite]

No PR yet — this is a design-phase issue. Key architectural questions need resolution before implementation begins. Will be addressed after LTS and initial next-gen features ship.