- add runnable examples for an unknown-name Tool, multi-export plugin, external kernel provider and same-name multi-version packages - add JSON Schemas for Analysis v1, Trace v1 and Tool v1 and validate them in CI - extend CI with protocol/consumer smoke tests and a Windows/macOS cargo check - add --kernel provider descriptors and R6 example integration tests - document the examples and update M0.6 status
20 lines
733 B
Markdown
20 lines
733 B
Markdown
# Unknown-name CLI tool example
|
|
|
|
This directory is a complete Tool Protocol v1 package. Nothing named
|
|
`benchmark` exists in the Marqdo CLI source; after installation the unknown
|
|
top-level command is dispatched by the registry.
|
|
|
|
```sh
|
|
marqdo tool install examples/tool-unknown-name/tool.json
|
|
marqdo tool list
|
|
marqdo benchmark run . --some-tool-option
|
|
marqdo tool remove benchmark
|
|
```
|
|
|
|
The executable receives the remaining arguments verbatim, inherits stdio/cwd,
|
|
and its exit code is propagated. `MARQDO_TOOL_PROTOCOL=1` and `MARQDO_BIN` are
|
|
provided for tools that need `check --emit`/`run --trace-file`.
|
|
|
|
A Tool is a user-run native process. It is **not** a C ABI plugin, a foreign
|
|
kernel, or a program inside the `.mq.md` sandbox.
|