Skip to content

Move cmd-mox behind a CommandRunner port (#62) - #76

Merged
leynos merged 4 commits into
mainfrom
issue-62-move-cmd-mox-integration-behind-a-commandrunner-port
Jun 8, 2026
Merged

Move cmd-mox behind a CommandRunner port (#62)#76
leynos merged 4 commits into
mainfrom
issue-62-move-cmd-mox-integration-behind-a-commandrunner-port

Conversation

@lodyai

@lodyai lodyai Bot commented Jun 1, 2026

Copy link
Copy Markdown
Contributor

Summary

This branch moves the cmd-mox IPC integration for issue #62 out of production modules and behind a CommandRunner port selected at the CLI boundary.

Closes #62.

Production code now depends on the runtime command-runner protocol and default subprocess adapter, while the cmd-mox adapter lives under lading.testing and is loaded only when LADING_USE_CMD_MOX_STUB is enabled.

Review walkthrough

Validation

  • make check-fmt: passed.
  • make lint: passed with Ruff clean and Pylint at 10.00/10.
  • make typecheck: passed with ty check clean.
  • make test: passed, 465 tests and 14 snapshots.
  • grep -R "cmd_mox" -n lading: passed with hits only under lading/testing/cmd_mox_runner.py.
  • coderabbit review --agent: passed with zero findings after follow-up fixes.

Loading
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Move cmd-mox integration out of production modules behind a CommandRunner port

1 participant