Plan library-owned dispatch for host/token-daemon/ps/stop (6.1.1b)

[leynos]

Summary

• Drafts docs/execplans/6-1-1b-subcommand-dispatch.md, an ExecPlan
  for roadmap task 6.1.1b that extends the library-owned request
  boundary already established for run and exec to the remaining
  four operator subcommands (host, token-daemon, ps, stop).
• Pulls in the latest AGENTS.md guidance from upstream
  (memoryd@1-1-1-record-evidence-store-engine-and-migration-policy)
  so this branch picks up the observability, expanded testing-level,
  and documentation-update expectations before implementation starts.
• Plan only — no source changes yet. The plan must be approved before
  implementation begins.

What the plan covers

• New library-owned request types under podbot::api: HostRequest,
  TokenDaemonRequest, ListContainersRequest, and StopRequest,
  each mirroring the RunRequest template (private fields, validating
  constructor, accessor methods).
• Dispatch rewiring in src/main.rs and src/cli/mod.rs: every
  subcommand parses through Clap, constructs the library-owned
  request, and routes through the library API.
• A hard constraint that podbot host emits zero bytes on stdout from
  the moment Clap finishes parsing through library return, with a
  behavioural test that asserts the stdout-purity rule. Cited against
  the MCP stdio transport MUST and the project's developers' guide.
• Stage A-G work breakdown (orient, types, rewire, tests, docs,
  validation, CodeRabbit) with explicit Constraints, Tolerances,
  Risks, Progress, Surprises & Discoveries, Decision Log, and
  Outcomes & Retrospective sections. The plan is scoped narrowly to
  dispatch hardening; orchestration for each subcommand stays with
  roadmap steps 6.3.1, 6.4.1, and 6.5.1.

Prior art cited in the plan

• Jujutsu's "Separation of library from UI" architecture rule.
• The Model Context Protocol stdio transport spec ("MUST NOT write
  anything to stdout that is not a valid MCP message").
• Alexis Lozano's "Hexagonal architecture in Rust" series (Rust CLI
  as a thin adapter over a library-owned Request value).

Test plan

Plan-only PR. Validation performed locally on the draft:

• make markdownlint passes for the new ExecPlan and the
  refreshed AGENTS.md.
• make nixie passes (no Mermaid diagrams added).
• (Deferred until implementation) make check-fmt, make lint,
  and make test will be run after each implementation milestone, as
  required by the project's quality-gate policy.
• (Deferred until implementation) coderabbit review --agent
  will be run after each milestone.

Roadmap

This plan covers roadmap task 6.1.1b. Implement subcommand dispatch
for run, host, token-daemon, ps, stop, and exec. Scope
narrows to the four still-pending subcommands; run and exec are
already routed through library-owned request types. The plan does not
tick the parent 6.1.1 entry; it will tick only the four sub-checkboxes
on completion.

Issues referenced

• Issue Implement stub orchestration functions in api module #51 (host_agent_cli stdout purity) is resolved by the plan's
  Stage C: the dead-coded helper is replaced with a tracing-based
  diagnostic path, and the hard-coded ConfigError short-circuit
  goes away.

References

• Lody session:
  https://lody.ai/leynos/sessions/61a6d267-5083-4142-bae9-472e66457fe7

🤖 Generated with Claude Code

[sourcery-ai]

Sorry @leynos, you have reached your weekly rate limit of 2500000 diff characters.

Please try again later or upgrade to continue using Sourcery

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 3eee350e-82f2-4961-9275-e83c17739ed2

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch 6-1-1b-subcommand-dispatch

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}