[Enhancement]: Kilo Code adapter: offer the terminal UI and ACP on the runtime's server #550

Affected area

Harness adapter; Schemas or configuration; Consumer integration; Documentation or examples

Problem or opportunity

Part of #547, which proposes one contract for serving harnesses' native interfaces.

The adapter starts one kilo serve process per runtime and talks to it over loopback HTTP through @kilocode/sdk 7.7.12. Fabric exposes none of the harness's own interfaces, so a consumer such as NVIDIA NemoClaw can't offer them.

Native interfaces:

• kilo: the terminal UI.
• kilo attach <url>: attaches the terminal UI to a running Kilo server.
• kilo acp: an ACP server.
• kilo serve: the headless server the adapter already runs, on 127.0.0.1 by default.

Proposed enhancement

Implement on #547's shared contract: opt-in harness.settings.interfaces.<name>, discovery of loopback ports and credential locations through the handle, owner-only credentials, the service lifecycle where an interface outlives a runtime, health checks, outbound requests off by default, and documented packaging.

• Add a terminal interface: the handle reports the runtime's kilo serve URL and credential location, so a consumer can run kilo attach against the server the adapter already owns, sharing the runtime's sessions.
• Optionally add an ACP interface.

Verify first:

• Whether kilo serve supports authentication; without it, any local process can drive the server.
• Whether kilo attach sees and continues the runtime's session.

Estimated effort: Small: the server already runs, as OpenClaw's Gateway does for #541.

Public contract and compatibility impact

• Schemas or adapter contract: the adapter's descriptor declares its interfaces, and its settings gain interfaces.
• Backward compatibility: additive; interfaces default to off.

Alternatives considered

• Consumer-side launching. A consumer could start the harness's interface beside Fabric, but it would duplicate configuration, credential and lifecycle handling outside Fabric, which [Enhancement]: Epic: serve harnesses' native interfaces through one adapter contract #547 avoids.

Acceptance criteria

• kilo attach with the reported URL and credential opens the terminal UI on the runtime's session.
• The interface is off by default, listens only on loopback, and uses [Enhancement]: Epic: serve harnesses' native interfaces through one adapter contract #547's discovery and credential handling.
• The README documents the interface, its packaging, and whether it shares conversations with Fabric invocations.

Additional context

Survey of Fabric main at 4fdf65a (2026-10-29); CLI options come from each CLI's --help in a disposable container. NemoClaw builds no Kilo image yet.

Duplicate check

• I searched the existing issues and did not find a duplicate.