docs: document m2pack subcommands
Add a Phase 4 'm2pack commands' section to docs/cli.md with each subcommand's flags and a pointer at the m2pack-secure repo for installation. Update README.md with a short m2pack paragraph and append the Phase 4 entry to the Unreleased CHANGELOG section.
This commit is contained in:
14
README.md
14
README.md
@@ -32,6 +32,20 @@ Add `--json` to get a machine-parseable envelope on stdout. Exit codes:
|
||||
|
||||
See `docs/cli.md` for the full command reference.
|
||||
|
||||
## m2pack commands
|
||||
|
||||
Phase 4 adds a `metin-release m2pack …` command group that wraps the
|
||||
[`m2pack-secure`](https://gitea.jakubkadlec.dev/metin-server/m2pack-secure)
|
||||
binary for building, verifying, diffing, and runtime-key-exporting
|
||||
signed `.m2p` archives. The binary is not bundled — build it from the
|
||||
m2pack-secure repo and either put it on `PATH` or set `M2PACK_BINARY`
|
||||
to an absolute path.
|
||||
|
||||
```
|
||||
metin-release m2pack build --input ... --output a.m2p --key ck --sign-secret-key sk
|
||||
metin-release m2pack verify --archive a.m2p --public-key pk
|
||||
```
|
||||
|
||||
## MCP server
|
||||
|
||||
The `metin-release-mcp` console script (Phase 3) exposes each Phase 1
|
||||
|
||||
Reference in New Issue
Block a user