Extract CLIProxy renderer into its owner repository

[NWYLZW]

The CLIProxy renderer and provider adapter were maintained inside CordisX Host, which mixed plugin product changes with Host lifecycle and UI work. This moves the renderer, styles, CLIProxy method declarations, response projection, lifecycle, and approval adaptation into the standalone plugin repository.

The branch now publishes a schema-valid plugin-package/runtime-manifest v9 candidate and a bundled platform-provider Node service. The service consumes only the public Protocol broker and ctx.platformProviders.register; it receives closed Host-issued provider configuration and opaque workspace handles. Endpoint and credential resolution, process startup, raw transport, configuration persistence, method/schema policy, and the single ProviderFleet remain Host-owned.

Validation:

• npm run check
• 7 focused artifact, renderer, public-boundary, service, operation, lifecycle, and approval tests
• package/runtime v9 AJV validation and exact runtime digest
• npm pack --dry-run includes renderer graph, stylesheet, dist/service.mjs, package manifest, and runtime manifest
• clean install of exact Git head 6cd0713f52c2090eb43bffaaeb40854e9420cd2e produced the 126,832-byte renderer and 25,445-byte service through prepare
• all new service modules are 47–276 lines

This PR remains open. It must not merge until Host #340 is formally merged and pinned. The branch consumes the formal Protocol v2 safe model-mapping projection at cbfd15ef4d2f51bcffa659f393cd65730bbe5f0d. The matching Host v2 implementation must still be formalized and pinned before this plugin can merge or the Host-built consumer can be deleted.

No live Codex Desktop launch or user acceptance was performed.