chore: update ant-node to 0.9.0 and migrate skills

.claude/commands/e2e-node-management-test.md → .claude/skills/e2e-node-management-test/SKILL.md

@@ -1,3 +1,9 @@
+---
+name: e2e-node-management-test
+description: Run a comprehensive end-to-end test of all node management features against a real testnet. Builds the binary and exercises every implemented command and API endpoint.
+allowed-tools: Bash, Read, Glob, Grep, AskUserQuestion
+---
+
 # End-to-End Node Management Test
 
 This command runs a comprehensive end-to-end test of all node management features against a real

.claude/skills/update-ant-node-ref/SKILL.md

@@ -0,0 +1,69 @@
+---
+name: update-ant-node-ref
+description: Update the ant-node dependency version in ant-core/Cargo.toml, regenerate lockfile, verify the build, and commit the change. Use when asked to update ant-node or /update-ant-node-ref.
+allowed-tools: Bash, Read, Edit, Glob, Grep, AskUserQuestion
+---
+
+# Update ant-node Reference
+
+This skill updates the `ant-node` dependency version in `ant-core/Cargo.toml`, regenerates the
+lockfile, verifies the build, and commits the change.
+
+## Procedure
+
+### Step 1: Prompt for target version
+
+Ask the user: **What version of `ant-node` should we update to?** (e.g., `0.9.0`)
+
+Do not proceed without a version string.
+
+### Step 2: Update the dependency
+
+Edit `ant-core/Cargo.toml` and change the `ant-node` version to the one the user provided. The line
+to change looks like:
+
+```toml
+ant-node = "X.Y.Z"
+```
+
+### Step 3: Update the lockfile
+
+Run:
+
+```bash
+cargo update
+```
+
+This regenerates `Cargo.lock` to reflect the new version.
+
+### Step 4: Verify the build
+
+Run:
+
+```bash
+cargo build
+```
+
+Do **not** use `--release` — it is too slow for a validation build.
+
+If the build **succeeds**, proceed to Step 5.
+
+If the build **fails**, stop and report the error to the user. Explain what breaking changes were
+detected and what code modifications would be needed to get the build to compile. Do not attempt to
+fix the code automatically — let the user decide how to proceed.
+
+### Step 5: Commit the change
+
+Stage `ant-core/Cargo.toml` and `Cargo.lock`, then create a commit:
+
+```
+chore: update ant-node to <version>
+```
+
+### Step 6: Ask about PR
+
+Ask the user: **Would you like to create a pull request for this change?**
+
+If yes, create a PR with:
+- **Title:** `chore: update ant-node to <version>`
+- **Body:** A brief summary noting the version bump and that the build was verified.

CLAUDE.md

@@ -135,7 +135,7 @@ cargo run --bin ant -- --help  # Run the CLI
 
 ## E2E Test Skill
 
-The project includes an E2E test command at `.claude/commands/e2e-node-management-test.md` that tests all node management features against a real testnet (invoked via `/e2e-node-management-test`). When adding new `ant node` subcommands or changing existing node management behavior, update this command to cover the new or changed functionality.
+The project includes an E2E test skill at `.claude/skills/e2e-node-management-test/SKILL.md` that tests all node management features against a real testnet (invoked via `/e2e-node-management-test`). When adding new `ant node` subcommands or changing existing node management behavior, update this command to cover the new or changed functionality.
 
 ## Linear Project
 

ant-core/Cargo.toml

@@ -35,7 +35,7 @@ tracing = "0.1"
 bytes = "1"
 lru = "0.16"
 rand = "0.8"
-ant-node = "0.8.0"
+ant-node = "0.9.0"
 saorsa-pqc = "0.5"
 tracing-subscriber = { version = "0.3", features = ["env-filter"] }