Runtime decision record

Retain and complete this file when the selected profile needs a maintained runtime, command, package, service, or deployment authority. It is required for packaged-cli, mcp-enabled, browser-interface, and headless-service, and optional for script-assisted when helper-runtime decisions need a separate record.

Caller-visible CLI behavior belongs in CLI_INTERFACE.md; caller-visible MCP behavior belongs in MCP_INTERFACE.md; browser-visible behavior belongs in WEB_INTERFACE.md. This file remains authoritative for implementation runtime, exact commands, package and distribution choices, protocol and transport selections, and deployment lifecycle.

Status

Selection status: UNSELECTED

Change the status to SELECTED only after completing the common fields and every section activated by Selected profiles:. Unselected profile sections may retain template guidance. A selected section must contain no unresolved TODO or UNSELECTED values.

Profile applicability

A script-assisted skill may retain only the common runtime identity, applicable shared commands, environment, distribution, and rationale. It does not need to resolve packaged CLI, MCP, browser, or service fields.

Primary implementation

Select one implementation ecosystem actually used by the skill. Use an explicit value such as NONE or NOT APPLICABLE only when absence is semantically valid; do not add competing manifests or lockfiles for unused runtimes.

Commands

Every command must state or imply an exact working directory. Rows activated by an unselected profile may remain NOT APPLICABLE or NOT SUPPORTED; rows activated by a selected profile must be concrete.

Shared development commands

Packaged CLI commands

Complete only when packaged-cli is selected. The canonical command must agree with CLI_INTERFACE.md.

MCP commands

Complete only when mcp-enabled is selected. Public behavior and compatibility remain in MCP_INTERFACE.md.

Browser-interface commands

Headless-service commands

MCP protocol support

Complete this section only when mcp-enabled is selected. Verify the current official MCP specification and selected SDK before completing it. MCP_INTERFACE.md defines caller-visible negotiation, fallback, result, interaction, and compatibility behavior without duplicating these exact selections.

Protocol lifecycle, cancellation, interaction, subscriptions, logging, and task behavior differ between revisions. Prefer an SDK-supported negotiation path over handwritten probing. Tests must cover every revision and fallback the concrete skill claims.

MCP variants

Use standard MCP transport names. Do not describe a raw socket protocol as “TCP MCP” unless the project intentionally implements a non-standard custom transport.

stdio variant

When supported, stdout is protocol-only, diagnostics use stderr, the launcher is trusted and bounded, and shutdown escalation is deterministic.

Streamable HTTP variant

Host, Origin, authentication, authorization, size-limit, and protocol-header decisions are request-scoped. A valid first request must not authorize later requests on the same keep-alive or multiplexed connection. Every present disallowed Origin must produce HTTP 403 for that request.

When 2026-07-28 is supported, also complete:

The stdio and Streamable HTTP variants must expose equivalent domain operations under the same revision, identity, authorization, configuration, and workspace policy unless a documented protocol limitation prevents parity.

Bundled ad hoc MCP tool client

Complete this section only when the skill bundles a command that discovers or invokes MCP tools.

The bundled launcher must not expose arbitrary shell commands or caller-selected JSON-RPC request IDs. Preserve every raw tools/list page and complete tool-call result in lossless modes; flattened views are derived presentations.

Optional human verification Web interface deployment

Complete this section when browser-interface is selected. This section is the sole source of truth for process, listener, port, container, service, gateway, external-origin, and deployment-selection capabilities. WEB_INTERFACE.md defines browser-visible behavior.

The final deployment topology may remain deployment-selected, but routing, authentication, authorization, health checks, and failure boundaries remain explicit. Disabling a debug UI must avoid loading UI-only assets or state on non-UI startup paths.

Headless service deployment

Complete this section when headless-service is selected. It applies to an independently reachable non-browser service, whether or not that service also exposes MCP.

Define how another node reaches the service, which identities may invoke it, how readiness differs from liveness, how in-flight requests terminate during shutdown, and which tests establish those guarantees.

Distribution

Resolve the common rows for every retained runtime record and the profile-specific rows activated by Selected profiles:.

Environment and configuration

Document required environment variables without placing secrets in this repository. Replace the example row with concrete variables or an explicit NONE record.

Network-server configuration should normally permit explicit bind address, port, endpoint path, authentication material location, log level, and optional Web-interface enablement. Secret values must not be committed or passed through public process listings when a safer mechanism exists.

Decision rationale

Explain why the selected runtime, package manager, commands, public-interface support, protocol revisions, transport variants, distribution, and deployment choices fit this skill better than credible alternatives. Address only activated profiles, but include how adapters share implementation and tests when several interfaces expose the same operations.

TODO