feat: add standalone Rust CLI binary (awn) for agent-native AWN interface

[Jing-yilin]

Summary

Adds a standalone Rust CLI binary (awn) under packages/awn-cli/ that provides an agent-native interface to the Agent World Network. Following the CLI-Anything philosophy: CLI is the most universal entry point for AI agents.

Why

• Current AWN is deeply coupled to OpenClaw's plugin API — only OpenClaw users can use it
• CLI is universally accessible: any agent framework (Claude Code, Codex, Droid, opencode) can call it via shell exec
• Single binary, zero runtime dependencies (no Node.js required)
• --json flag for structured output makes it agent-native

What's included

Modules (all with full test coverage)

• crypto.rs (18 tests) — Ed25519 signing, agentId derivation, canonicalize, domain-separated signatures. Byte-for-byte compatible with TS SDK (4 cross-language compatibility tests with identical seed/output).
• identity.rs (7 tests) — Load/create Ed25519 keypair, persist to disk. File format compatible with TS identity.json.
• peer_db.rs (14 tests) — JSON peer store with TOFU trust model, capability search, camelCase field names matching TS format.
• daemon.rs (5 tests) — Axum IPC server on localhost with /ipc/status, /ipc/peers, /ipc/worlds, /ipc/ping endpoints.

CLI Commands

awn daemon start [--data-dir ~/.awn] [--gateway-url ...] [--port 8099]
awn daemon stop
awn status                          # agent ID, transport, joined worlds
awn peers [--capability world:]     # list known peers
awn worlds                          # list from Gateway + local cache

All commands support --json for structured output.

Version sync

• Cargo.toml version synced from root package.json via sync-version.mjs
• PROTOCOL_VERSION derived from Cargo.toml at compile time (major.minor)
• AGENTS.md updated to document Cargo.toml as version-bearing file

SKILL.md

CLI-Anything format skill definition for agent discovery.

Test Results

test result: ok. 44 passed; 0 failed; 0 ignored

Atomic Commits

1. feat: add Rust awn CLI skeleton with wire-compatible crypto module
2. feat(awn): add identity module with TS-compatible key persistence
3. feat(awn): add peer DB with TOFU, capability search, and TS-compatible persistence
4. feat(awn): add daemon with IPC + clap CLI (status, peers, worlds)
5. docs(awn): add CLI-Anything style SKILL.md for agent discovery
6. chore: add changeset for Rust awn CLI

[Jing-yilin]

Codex Review

[Medium] CLI commands cannot reach daemons started on a non-default IPC port

daemon start accepts --ipc-port, but status, peers, and worlds always resolve the daemon address from AWN_IPC_PORT or the hard-coded default 8199. If the daemon is started on any other port, the follow-up commands still call 127.0.0.1:8199 and report that the daemon is not running unless the caller also exports AWN_IPC_PORT out of band. I reproduced this with cargo run -- --json daemon start --ipc-port 8207 followed by cargo run -- --json status, which failed until AWN_IPC_PORT=8207 was set. That makes the advertised --ipc-port flag effectively unusable across normal CLI invocations.
Refs: packages/awn-cli/src/main.rs:52, packages/awn-cli/src/main.rs:74, packages/awn-cli/src/main.rs:119, packages/awn-cli/src/main.rs:148, packages/awn-cli/src/main.rs:190, packages/awn-cli/src/daemon.rs:222

[Medium] awn daemon stop reports an error but still exits 0

The stop subcommand currently prints daemon stop not yet implemented and then returns success. That is particularly risky here because the bundled skill explicitly tells agents to treat exit code 0 as success and non-zero as failure, so scripts will happily continue under the false assumption that the daemon has been stopped. Until the stop path is implemented, this branch should return a non-zero exit code.
Refs: packages/awn-cli/src/main.rs:110, packages/awn-cli/src/main.rs:112, packages/awn-cli/src/main.rs:113, packages/awn-cli/skills/SKILL.md:73

Validation: cd packages/awn-cli && cargo test