Placeholder adapters

Two adapter names appear in the registry but are mock-only and produce no real side effects:

• ssh is registered as a mock adapter for forward compatibility. There is no real SSH client backing it. A flow that references adapter: "ssh" runs, but the executed node returns a synthetic succeeded payload rather than the result of a remote command.
• zosmf is registered as a mock adapter. Instead, use the cli adapter with bin: "zowe" and a z/OSMF-backed Zowe profile.

Caution

The flow generator must not emit adapter: "ssh" or adapter: "zosmf" in production output.

If you need real SSH today

Use adapter: "shell" with actionId: "run-command" and a command: "ssh ..." value. The local sandbox layer applies as it would to any shell invocation.

remote[action: "Remote uptime"] {
  adapter: "shell"
  actionId: "run-command"
  command: "ssh user@host uptime"
}

If a future release replaces a placeholder with a real implementation, that adapter’s descriptor will start returning a non-empty action list and the spec pipeline will generate a real reference page next to the others.