Simplify ego-lite

Reduce concepts and maintenance surface, not just line count. Prefer a few well-proven deletions over a long list of guesses.

Establish the contract

1. Read AGENTS.md and the design document that owns the affected behavior.
2. Inspect git status and preserve unrelated user changes.
3. Decide whether the request is an audit or an authorized implementation. Do not turn a cleanup into a product decision without making the behavior change explicit.
4. Identify the relevant boundary before judging code:
   • globalThis.ego is supplied by the closed-source app; docs/native-bindings-api.md documents that external contract.
   • The runtime has direct CLI and embedded SDK startup paths.
   • Public agent APIs must stay aligned across implementation, tests, help(), and skills/ego-browser/SKILL.md.
   • Browser state can outlive the short Node.js process.

Find strong candidates

Start with production areas carrying the most state, branching, or public surface. Look for: