ego-lite-simplify

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:

• Exports, helpers, events, options, fallbacks, packages, or state fields with no production consumer.
• Tests or documentation that are the only consumers of behavior that is no longer required.
• Multiple representations of the same page, task-space, session, ref, lifecycle, or output state.
• Pass-through layers that add vocabulary but no policy, isolation, or test seam.
• Compatibility code that is unnecessary on an explicitly breaking branch.
• Generality with no current product use, such as unsupported concurrency modes or unused extension points.
• Special cases, rollback paths, or validation that exist only to protect a removable surface.
• Hand-written parsers, queues, retry logic, or utilities that a Node.js built-in or healthy dependency can replace with less total code.

Do not count moving logic into a wrapper as simplification. Estimate the net result: implementation, tests, docs, public names, state transitions, and special cases removed minus new glue and dependencies added.