Add minimal Runtime inspection commands

[V3RON]

Summary

Adds a new runtime command family so tool users can evaluate live expressions, inspect returned remote object handles, and explicitly release preserved Runtime references on Chrome, Node.js, and React Native targets.

Context

This change introduces a focused src/runtime/ module and keeps the scope intentionally small: runtime eval, runtime props, runtime release, and runtime release-group. The default behavior preserves remote object handles in the agent-cdp-runtime object group so an agent can evaluate first and inspect properties in a follow-up step before releasing the handle.

Backward-compatibility: existing command families, daemon lifecycle, and default output formats remain unchanged. This only adds a new top-level command family, new packaged skill guidance, and README coverage for Runtime inspection.

Risks

• Runtime evaluation is intentionally powerful and can cause side effects if the expression mutates target state.
• Runtime object handles are preserved by default, so callers need to release them in long-lived sessions when they are no longer needed.
• Property/value previews depend on what the target runtime exposes through CDP, so Chrome, Node.js, and React Native may differ slightly in descriptions even though the command surface is shared.

Fixes #8

Manual testing

1. Start the daemon and select a Chrome, Node.js, or React Native target that exposes CDP.
2. Run agent-cdp runtime eval --expr "process.version" or another read-only expression appropriate for the target, and verify primitive values print compactly.
3. Run agent-cdp runtime eval --expr "globalThis" and verify the output includes an objectId for follow-up inspection.
4. Run agent-cdp runtime props --id <OBJECT_ID> --own and verify returned properties include concise summaries and nested object handles when present.
5. Run agent-cdp runtime release --id <OBJECT_ID> or agent-cdp runtime release-group and verify cleanup succeeds without changing other command workflows.