mirror of
https://github.com/callstack/agent-device.git
synced 2026-09-14 20:06:34 +08:00
Michał Pierzchała
819d7dc8aa
* feat: expose semantic MCP tools * docs: remove semantic mcp prd * refactor: deepen semantic command surface * refactor: add mcp execution seam * refactor: deepen command grammar * refactor: remove legacy command definitions * refactor: collapse semantic cli wrappers * refactor: remove local mcp placeholders * refactor: derive semantic cli routing * refactor: trim mcp status metadata * refactor: derive semantic input contracts * refactor: split semantic grammar modules * refactor: derive batch input schema * refactor: centralize cli command schema catalog * refactor: share semantic cli output projections * refactor: remove legacy cli output paths * refactor: consolidate command interface surface * docs: align command contract wording * refactor: split command projection from cli grammar * refactor: trim projection exports * fix: satisfy fallow command contract audit * refactor: structure public batch steps * chore: clean batch architecture references * fix: keep legacy cli batch steps working * fix: serialize mcp batches * chore: tighten command surface cleanup * fix: serialize mcp stdin requests * chore: keep mcp config out of command contracts * fix: project structured batch targets * chore: harden command input typing * fix: project maestro backend for replay tests * fix: preserve session mcp request options
2.0 KiB
2.0 KiB
Agent Device Domain Context
Terms
- Provider-backed integration scenario: device-free integration test that runs the real daemon request path and replaces only external device or host tool execution.
- Provider: request-scoped adapter interface for external device, runner, or host tool execution.
- Provider transcript: exact record of provider calls used when a test must verify platform command translation.
- Scenario transcript: command-level integration flow that describes user-visible behavior through daemon commands.
- In-process provider scenario harness: integration runner that invokes the daemon request handler directly without opening an HTTP listener.
- HTTP contract test: narrow test that verifies JSON-RPC transport, auth, and response finalization over the daemon HTTP boundary.
- Interactor: semantic interface between command dispatch and platform behavior.
- Platform module: platform-specific implementation behind the Interactor.
- Target: selected automation destination, such as mobile, tv, or desktop.
- Modality: broad supported device family, such as mobile, tv, or desktop.
- Session: daemon-owned state for a selected target and opened app or surface.
- Command surface: catalog of public command identity, interface exposure, adapter policy, and shared command metadata across CLI, Node.js, MCP, and batch entrypoints.
Testing Principles
- Provider-backed integration scenarios should exercise the public daemon path whenever practical.
- Prefer the in-process provider scenario harness for broad scenarios; keep HTTP contract tests narrow and transport-specific.
- Provider seams sit below platform modules so integration tests still cover platform command translation.
- Provider transcripts are for exact external command contracts.
- Scenario transcripts are for broad, user-rooted workflows that should replace mocked handler unit tests.
- Unit tests stay for pure logic, parser matrices, selector matching, capabilities, and important edge cases.