Mission will expose adapter readiness probes as class-level Agent Entity commands rather than as ad hoc Open Mission app routes, raw terminal checks, or managed AgentExecution instances.

Context

Mission already treats Entity commands as the canonical operator mutation surface under daemon entity.command transport, and it treats AgentExecution as the canonical model for long-lived managed execution state. Adapter readiness probing sits between those seams: operators need a one-shot way to validate login, launch configuration, model selection, and provider CLI health before or instead of starting a managed AgentExecution.

That probe is not a durable AgentExecution. It should not allocate AgentExecution ids, register runtime ownership, publish AgentExecution events, or write audit material that claims a real execution existed. At the same time, it must reuse Mission-owned adapter launch semantics instead of inventing a second launch path in Open Mission or in a surface-specific helper.

Decision

Mission will introduce an Agent connection test as a class-level Agent Entity command named testConnection.

The command payload identifies the target Agent plus optional launch parameters such as repository root, working directory, model, reasoning effort, launch mode, and prompt override. The command result is a typed Agent connection diagnostic. The command travels through the existing daemon entity.command transport and is implemented by the owning Agent Entity class.

The Agent Entity class delegates the runtime work to a daemon-owned one-shot Agent connection tester. That tester reuses the resolved Agent adapter, validates launch configuration through the existing adapter preparation path, spawns the adapter with a bounded smoke prompt, and classifies the result without creating a managed AgentExecution.

Agent adapters may provide adapter-specific connection diagnostics for known failure shapes such as login-required or proxy-auth mismatches. Those diagnostics are local to connection testing and are not automatically promoted into AgentExecution signal vocabulary.

Ownership

AgentContract owns the remote command metadata and schemas.

Agent owns the public Entity command implementation and repository-scoped Agent resolution.

The daemon-owned Agent connection tester owns one-shot launch probing, timeout handling, stdout/stderr capture, parser reuse, and generic result classification.

AgentAdapter owns provider-specific failure interpretation through an optional diagnostic hook. Adapter diagnostics report launch readiness through the Agent connection diagnostic result and leave Entity command semantics with the Agent Entity command.

Agent connection testing belongs to Agent-owned diagnostics because the probe does not create or manage AgentExecution state. AgentExecutionRegistry remains active execution lookup and process-handle plumbing.

Consequences

  • Open Mission and other surfaces call one canonical Agent.testConnection command through the existing remote Entity surface.
  • Mission keeps one authoritative adapter launch path while avoiding fake AgentExecution records for readiness probes.
  • Adapter-specific auth and launch guidance can improve incrementally behind the adapter boundary.
  • Agent connection diagnostics stay typed and bounded instead of leaking raw terminal material as canonical operator output.

Implementation Rules

  • Do not expose Agent connection testing as a normal REST route when the Entity command surface already exists.
  • Do not create managed AgentExecution records, runtime supervision edges, or AgentExecution journal entries for one-shot connection tests.
  • Do reuse the configured Agent adapter and its launch preparation path.
  • Do keep the result schema separate from AgentExecution signal schemas unless a future decision deliberately converges them.
  • Do keep adapter-specific failure classifiers optional and bounded.