agentwheel 0.16.6 → 0.18.0

package/install.md

@@ -28,16 +28,17 @@ agentwheel --version
 agentwheel --help
 ```
 
-If it is missing, install it with the package manager already available on the host:
+If it is missing or older than the config requires, install the current CLI with the package
+manager already available on the host:
 
 ```bash
-npm i -g agentwheel
+npm i -g agentwheel@latest
 ```
 
 Prefer pnpm only when the host already uses pnpm for global tools:
 
 ```bash
-pnpm add -g agentwheel
+pnpm add -g agentwheel@latest
 ```
 
 Verify after installation:
@@ -47,6 +48,11 @@ agentwheel --version
 agentwheel doctor --help
 ```
 
+Named fleets require a schema-v3-capable CLI. Upgrade Agentwheel first, verify
+`agentwheel --version` and `agentwheel fleet --help`, then create, register, inspect, or plan fleet
+state. Do not rewrite the config to an older schema or remove named-fleet data to make an old CLI
+accept it.
+
 ## Install The Companion Skills
 
 Pick the adapter that matches the active runtime:
@@ -87,7 +93,7 @@ If the user wants to preview first, add `--dry-run` to the `install` command.
 Browse the public catalogue:
 
 ```text
-https://nestdevlab.github.io/agentwheel/catalogue.html
+https://www.nestdev.it/agentwheel/catalogue.html
 ```
 
 Install an OpenPack package:
@@ -112,7 +118,7 @@ If a fleet profile declares runtime `reloadCommands`, run reloads or service res
 explicitly approved:
 
 ```bash
-agentwheel install --profile extra-message-policy --execute-plugins --reload-runtimes
+agentwheel install --fleet example-fleet --profile extra-message-policy --execute-plugins --reload-runtimes
 ```
 
 Draft a catalogue submission for a public repository:
@@ -128,4 +134,5 @@ npx agentwheel@latest registry publish https://github.com/owner/repo
 - The management skill is installed if the user requested it.
 - The discovery skill is installed only if the user requested proactive suggestions.
 - Any catalogue resource install uses the adapter and installation type the user intended.
+- Desired-state scope is explicit when it matters: `--user`, `--local`, or `--fleet <fleet-id>`.
 - Catalogue submissions use `agentwheel registry publish` unless the user explicitly wants a manual registry PR.

package/llms.txt

@@ -7,7 +7,8 @@
 - README: https://github.com/NestDevLab/agentwheel#readme
 - AI install handoff: https://github.com/NestDevLab/agentwheel/blob/main/install.md
 - AI agent guide: https://github.com/NestDevLab/agentwheel/blob/main/AGENT.md
-- Public catalogue: https://nestdevlab.github.io/agentwheel/catalogue.html
+- Public site: https://www.nestdev.it/agentwheel/
+- Public catalogue: https://www.nestdev.it/agentwheel/catalogue.html
 
 ## Specs And Design
 
@@ -25,3 +26,8 @@ npm i -g agentwheel
 agentwheel doctor --adapter codex --local
 agentwheel install github:NestDevLab/agentwheel --adapter codex --local --skill agentwheel
 ```
+
+Named fleets are optional and require a schema-v3-capable Agentwheel CLI. Select exactly one
+desired-state scope when it matters: `--user`, `--local`, or `--fleet <fleet-id>`. Upgrade and
+verify `agentwheel fleet --help` before creating, registering, or reading fleet state; see the fleet
+configuration guide for registration, plan-digested normalization, and journal recovery.

package/openpack.json

@@ -1,7 +1,7 @@
 {
   "schemaVersion": 2,
   "name": "NestDevLab/agentwheel",
-  "version": "0.16.6",
+  "version": "0.18.0",
   "provides": [
     { "type": "skills", "path": "skills" }
   ]

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "agentwheel",
-  "version": "0.16.6",
+  "version": "0.18.0",
   "description": "Weave skills, rules, and instructions across every AI agent.",
   "type": "module",
   "license": "MIT",
@@ -8,7 +8,7 @@
     "type": "git",
     "url": "git+https://github.com/NestDevLab/agentwheel.git"
   },
-  "homepage": "https://github.com/NestDevLab/agentwheel#readme",
+  "homepage": "https://www.nestdev.it/agentwheel/",
   "bugs": {
     "url": "https://github.com/NestDevLab/agentwheel/issues"
   },
@@ -42,9 +42,9 @@
   },
   "scripts": {
     "build": "tsup && chmod +x dist/index.js",
-    "check-release-version": "node scripts/check-release-version.mjs",
     "prepack": "pnpm build",
-    "sync-site-version": "node scripts/sync-site-version.mjs",
+    "release:check": "node scripts/release-check.mjs",
+    "release:prepare": "node scripts/release-prepare.mjs",
     "test": "vitest run",
     "typecheck": "tsc --noEmit"
   },

package/skills/agentwheel/SKILL.md

@@ -5,7 +5,7 @@ allowed-tools: [Bash]
 license: MIT
 metadata:
   author: NestDevLab
-  version: "0.16.6"
+  version: "0.18.0"
 ---
 
 # agentwheel
@@ -19,6 +19,7 @@ Mental model:
 - `add` records desired packages.
 - `install` makes the declared state true in the target runtime.
 - `update` re-resolves tracking packages, then applies.
+- `skill update <name>` maps a configured skill to its owning package and reconciles only that skill plus its genuine transitive composition inputs; sibling artifacts keep their runtime bytes and manifest/lock state.
 - `uninstall` removes configured packages and their managed runtime output.
 
 ## Safety Rules
@@ -53,9 +54,10 @@ To add and install in one step:
 agentwheel install github:owner/repo --adapter codex,claude
 ```
 
-Explicit source installs with explicit adapters default to user-level artifacts. Use `--local` for
-the current directory or `-t/--target-root <project>` for project/workspace installs. Use `--user`, `--local`, or
-`-i/--installation-type <type>` when scope should be explicit.
+Explicit source installs with explicit adapters default to user-level artifacts. Use exactly one of
+`--user`, `--local`, or `--fleet <fleet-id>` when desired-state scope matters. Use
+`-i/--installation-type <type>` for the runtime layout inside that scope and
+`-t/--target-root <project>` for an explicit target root. Named fleets are optional.
 
 ## Workspace Setup
 
@@ -276,9 +278,10 @@ agentwheel install github:owner/repo --adapter codex,claude
 ```
 
 Explicit source installs with explicit adapters default to documented user-level installs. Pass
-`--local` for the current directory or `-t/--target-root <project>` for project/workspace installs, and use `--user`, `--local`,
-or `-i/--installation-type <type>` when scope should be explicit. If a package can be installed in
-more than one type and no CLI/context default applies, agentwheel fails instead of guessing.
+`--user`, `--local`, or `--fleet <fleet-id>` to select one desired-state scope, and use
+`-i/--installation-type <type>` for the runtime layout inside that scope. If a package can be
+installed in more than one type and no CLI/context default applies, Agentwheel fails instead of
+guessing.
 
 Target selection order is `--target-root`, then `--agent`, then runtime auto-detection from the current directory, then the current directory.
 
@@ -293,32 +296,46 @@ agentwheel status --all
 agentwheel status --profile daily
 ```
 
-For profile-managed fleets, prefer `agentwheel status --profile <name>` over
+For a named fleet, prefer `agentwheel status --fleet <fleet-id> --profile <name>` over
 direct agent status; profile status uses the same runtime resolution, adapter
 config, installation type, and graph lock fingerprinting as
-`install --profile <name>`. If a workspace defines a profile named `all`,
-`agentwheel status --all` checks that profile.
+`install --fleet <fleet-id> --profile <name>`. If that fleet defines a profile named `all`,
+`agentwheel status --fleet <fleet-id> --all` checks that profile.
 
-## Named Agents And Profiles
+## Named Fleets, Agents, And Profiles
 
-Global config is `~/.agentwheel/config.json`. Project config is `.agentwheel/config.json`; project values win.
+Named fleets are optional control-plane configurations. Select one explicitly with
+`--fleet <fleet-id>`; ordinary user and local work does not require fleet registration. User,
+local, and fleet scopes are isolated desired state: Agentwheel does not merge them, and no fleet
+has global priority.
+
+Named fleets require a schema-v3-capable Agentwheel CLI. Upgrade first, verify
+`agentwheel --version` and `agentwheel fleet --help`, then create or register fleet state. Do not
+downgrade the config, strip named-fleet data, or run an old CLI against it.
 
 Current config shape:
 
 ```json
 {
-  "schemaVersion": 1,
-  "packages": [],
-  "registry": {},
+  "schemaVersion": 3,
+  "fleetId": "example-fleet",
+  "packages": [
+    {
+      "name": "core-agent-pack",
+      "source": "github:example-org/core-agent-pack",
+      "driver": "git",
+      "adapter": "codex",
+      "installationType": "local",
+      "mode": "tracking"
+    }
+  ],
   "agents": {
-    "lab-codex": { "adapter": "codex", "installationType": "local", "root": "$HOME/project" },
-    "lab-claude": { "adapter": "claude", "installationType": "local", "root": "$HOME/project" }
+    "lab-codex": { "adapter": "codex", "installationType": "local", "root": "/workspace/project" }
   },
   "profiles": {
     "daily": {
       "runtimes": [
-        { "agent": "lab-codex" },
-        { "agent": "lab-claude" }
+        { "agent": "lab-codex" }
       ]
     }
   }
@@ -328,14 +345,30 @@ Current config shape:
 Use named targets:
 
 ```bash
-agentwheel install --agent lab-codex --dry-run
-agentwheel install --agent lab-codex
-agentwheel install --all --dry-run
-agentwheel install --all
-agentwheel install --profile daily --dry-run
-agentwheel install --profile daily
+agentwheel fleet register example-fleet --root /srv/agentwheel/fleets/example-fleet --required-package core-agent-pack
+agentwheel fleet list
+agentwheel fleet show example-fleet
+agentwheel install --fleet example-fleet --agent lab-codex --dry-run
+agentwheel install --fleet example-fleet --all --dry-run
+agentwheel install --fleet example-fleet --profile daily --dry-run
 ```
 
+An intended runtime path owned by another scope is a blocking conflict even when the bytes match.
+Use the dedicated fleet normalization workflow: preview the transfer, review its exact plan digest,
+then apply only the unchanged plan. Never remove the source declaration first or hand-edit runtime
+output to manufacture a clean plan.
+
+```bash
+agentwheel fleet normalize example-fleet --from user --package core-agent-pack --json
+agentwheel fleet normalize example-fleet --from user --package core-agent-pack \
+  --plan-digest <reviewed-sha256> --apply
+agentwheel fleet normalize example-fleet --from user --recover
+```
+
+`fleetId` in the fleet config must match the registry key. Every repeatable
+`--required-package` must name a package declared by that fleet. Recovery is only for a pending
+journal and must fail if recorded configs, manifests, or graph locks changed externally.
+
 ## Adapters
 
 Built-in adapters:
@@ -381,9 +414,9 @@ agentwheel update --all --dry-run
 agentwheel update --profile daily --dry-run
 ```
 
-For profile-managed fleets, use `agentwheel update --profile <name>` before
-`install --profile <name>` when tracking packages should move forward. If a
-workspace defines a profile named `all`, `agentwheel update --all` checks that
+For a named fleet, use `agentwheel update --fleet <fleet-id> --profile <name>` before
+`install --fleet <fleet-id> --profile <name>` when tracking packages should move forward. If that
+fleet defines a profile named `all`, `agentwheel update --fleet <fleet-id> --all` checks that
 profile.
 
 Limit an update to one configured package:
@@ -395,6 +428,15 @@ agentwheel update team-agent-pack
 
 Named package updates preserve artifacts owned by other configured roots, including unrelated drift.
 
+For one configured skill, resolve its owner and reconcile only that skill plus genuine transitive composition inputs:
+
+```bash
+agentwheel skill update code-review --fleet example-fleet --profile daily --dry-run
+agentwheel skill update code-review --fleet example-fleet --profile daily
+```
+
+Pinned owners use install semantics; tracking owners re-resolve. Sibling artifacts from the same package retain their runtime bytes and manifest/graph-lock entries; only composition inputs actually used by the requested skill join the update scope. Unrelated configured packages are not resolved. If ownership is ambiguous, pass `--package <name>`. Use `--adopt` only after explicit approval of the dry-run's unmanaged destinations.
+
 Advance one tracking dependency while unrelated graph nodes remain locked:
 
 ```bash
@@ -468,6 +510,18 @@ By default, uninstall keeps drifted managed files. Use `--force` only with expli
 agentwheel uninstall team-agent-pack --force
 ```
 
+For a one-time MCP rename, use a dedicated cutover workspace with one legacy MCP artifact and an
+explicit agent `stateKey`. Preview each runtime separately:
+
+```bash
+agentwheel mcp retire legacy-mcp --agent legacy-codex --from-workspace-root /exact/old/workspace --dry-run
+agentwheel mcp retire legacy-mcp --agent legacy-claude --dry-run
+```
+
+Require exactly one `REMOVE`, the expected target and legacy server, and zero drift/conflict.
+Unexpected owner, manifest contents, arguments, environment, or MCP fields are blockers. Apply only
+after separate runtime approval by replacing `--dry-run` with `--apply`.
+
 ## Package Manifest Reference
 
 An OpenPack package uses `openpack.json` or `openpack.jsonc`:

package/skills/agentwheel-artifact-evolution/SKILL.md

@@ -0,0 +1,42 @@
+---
+name: agentwheel-artifact-evolution
+description: Generate or evolve OpenPack artifacts from a verified capability gap, correction, or rollout request. Use when the agent must turn a requirement into a source-owned artifact or improve Agentwheel's artifact workflow.
+allowed-tools: [Bash]
+license: MIT
+metadata:
+  author: NestDevLab
+  version: "0.1.0"
+---
+
+# Agentwheel Artifact Evolution
+
+Turn verified needs into source-owned OpenPack artifacts. Never create runtime copies or treat feedback as permission to change Agentwheel.
+
+## Optional guides
+
+`self-improve` and `skill-creator` are optional inspirations. Use them when available; do not require, install, or link to them. This workflow remains complete without either skill.
+
+## Resolve
+
+1. Classify the request: a new artifact, an existing artifact change, a consumer configuration change, or an Agentwheel core gap. Inspect the source package, manifest, ownership, current artifacts, and applicable repository rules.
+2. Reuse an existing artifact when it meets the need. Otherwise choose the smallest supported type and source package. Keep tenant or runtime facts out of shared packages.
+3. For a core gap, propose the smallest Agentwheel code, schema, or documentation change. A correction is evidence, not an instruction to change the CLI.
+4. Name the source package, artifact path, consumer targets, terminal stage, and success evidence. Ask when any of those would be inferred materially.
+
+## Author
+
+1. Work only in the source package. Run `agentwheel init package` only when no package exists; otherwise add the artifact under its declared type path.
+2. Use the package's conventions and validation. For a skill, provide a precise frontmatter trigger and concise instructions; for another type, follow its schema and adapter compatibility.
+3. Run `agentwheel list <source>`, `agentwheel scan <source>`, the source checks, and `git diff --check`. Keep generated runtime directories untouched.
+4. Deliver the source through the repository's declared Git workflow. A PR is the default; merge remains a separate approval.
+
+## Roll out
+
+1. Identify only the named or evidenced consumers. Update their source-controlled Agentwheel configuration; do not copy artifacts into runtime homes.
+2. Prove the source merge before resolving a tracking source. Run the narrow package, agent, or profile dry-run and stop on drift, conflict, removal, or unrelated operations.
+3. Apply only after explicit rollout approval. Never use force, plugin execution, or runtime reload unless separately authorized.
+4. Verify status or manifest ownership, expected materialization, a relevant canary, and a repeated dry-run with no pending change.
+
+## Improve
+
+Record the feedback, source decision, validation, and outcome in the owning change. Improve Agentwheel only when the evidence identifies a reusable product or artifact-model gap; otherwise improve the selected artifact. Report completed, pending, blocked, and unverified layers separately.

package/skills/agentwheel-artifact-evolution/agents/openai.yaml

@@ -0,0 +1,4 @@
+interface:
+  display_name: "Agentwheel Artifact Evolution"
+  short_description: "Generate and evolve OpenPack artifacts"
+  default_prompt: "Use $agentwheel-artifact-evolution to create or evolve an OpenPack artifact and plan its safe rollout."

package/skills/agentwheel-discovery/SKILL.md

@@ -5,7 +5,7 @@ allowed-tools: [Bash]
 license: MIT
 metadata:
   author: NestDevLab
-  version: "0.16.6"
+  version: "0.18.0"
 ---
 
 # Agentwheel Discovery

package/skills/agentwheel/references/ct111-selfhost-instruction-activation.md

@@ -1,24 +0,0 @@
-# CT111 self-hosted instruction activation
-
-Use when adding a small always-loaded behavior rule to YehonalBot/Drassil on CT111 without importing unrelated core-private skills.
-
-Facts/pitfall:
-- CT111 (`ct111-openclaw`) owns its own AgentWheel plane under `/root/src/nestdevlab/fleet-control/profiles/ct111-selfhost`; do not install to CT111 from CT107.
-- OpenClaw instruction artifacts often target the same runtime file: `/root/.openclaw/workspace/AGENTS.md`.
-- Adding a second selected `instructions/<rule>.md` artifact from `agent-core-toolkit-private` can create duplicate instruction targets with different content. AgentWheel may skip one duplicate or report drift on the managed block.
-
-Preferred pattern:
-1. Keep the broad source package selected narrowly; do not add all of `agent-core-toolkit-private` just to deliver one rule.
-2. If the target already has a domain/persona `instructions/AGENTS.md` artifact, compose the new small behavior fragment into that existing artifact instead of adding a separate instruction artifact to the same destination.
-3. Put the behavior text in the domain toolkit, e.g. `agent-drassil-toolkit-private/fragments/self-improve-activation.md`.
-4. Add one compose include near the top of the domain `AGENTS.md` composition, usually immediately after `core:fragments/core-base.md` and before role overlays:
-   ```json
-   { "include": "fragments/self-improve-activation.md" }
-   ```
-5. Validate JSON/OpenPack selection, then run CT111 dry-run in place:
-   ```bash
-   ssh ct111-openclaw 'cd /root/src/nestdevlab/fleet-control/profiles/ct111-selfhost && npx --yes agentwheel@latest install --profile ct111-selfhost --dry-run --yes'
-   ```
-6. Treat `UPDATE instructions/AGENTS.md -> .openclaw/workspace/AGENTS.md` as the expected dry-run signal. Do not apply if unrelated drift/plugin operations are present unless the user approves that exact scope.
-
-This pattern preserves narrow delivery: the future runtime receives the behavior inside its existing AGENTS managed block without importing unrelated core-private skills or creating competing instruction blocks.

package/skills/agentwheel/references/fleet-control-cleanup-ct107-node-and-effective-adapters.md

@@ -1,39 +0,0 @@
-# Fleet control cleanup: CT107 node vs runtime targets, and effective adapters
-
-Use this reference when cleaning or explaining an AgentWheel fleet-control `.agentwheel/config.json` that targets multiple runtimes/profiles.
-
-## Durable lessons
-
-- Do not model CT107/nestdev as `ct107-openclaw` unless there is an explicitly declared, full OpenClaw runtime home to manage. In Joseph's current CT107/CT110 layout, CT107 is a local node/workspace with Claude/Codex homes; OpenClaw gateway/profile targets live on CT110 or profile-specific users.
-- If a target name implies a real runtime install that does not exist, remove it from `agents` and from every `profiles.*.runtimes[]` entry rather than leaving it as a misleading alias.
-- For profile installs, AgentWheel chooses the effective adapter from each runtime target in the selected profile. The package entry's `adapter` field can be source/default metadata and is not a reliable answer to “which adapters are targeted by this pack under profile all”.
-- When the user asks “per pack, which adapters are targeted?”, compute it as: selected profile runtimes → each runtime's adapter or adapterConfig name → package roots fanned out to that set. Then separately note artifact-type limitations, especially plugin targets.
-
-## Safe cleanup shape
-
-1. Read `.agentwheel/config.json` and list:
-   - `agents` entries,
-   - each profile's runtime list,
-   - any `adapterConfig` paths.
-2. Identify misleading/nonexistent runtime targets by user/domain knowledge first. Ask or preserve if unsure; do not rename targets silently.
-3. Remove the bad agent entry and all profile runtime references to it.
-4. Remove only generated lock directories for the removed target, e.g. `.agentwheel/locks/<removed-agent>/`; do not bulk-delete unrelated locks.
-5. Update `docs/fleet.md` with:
-   - canonical meaning of the fleet,
-   - current agents table,
-   - profile membership,
-   - effective adapter-targeting table per profile and per package.
-6. Validate with JSON parsing and a grep that the removed target no longer appears in config/docs.
-7. Run `agentwheel install --profile <profile> --dry-run` when credentials/cache allow. If a private GitHub fetch blocks dry-run, report it as a credential/cache blocker, not as proof the config is bad.
-
-## Reporting style for Joseph
-
-Keep it short and operational:
-
-- what was removed/changed,
-- exact files touched,
-- current profile membership,
-- validation result,
-- any dry-run blocker.
-
-Avoid over-explaining AgentWheel internals unless he asks; he wants the concrete fleet shape and whether it is clean.

package/skills/agentwheel/references/fleet-plugin-rollouts.md

@@ -1,69 +0,0 @@
-# Fleet plugin rollouts with AgentWheel
-
-Use this when a fleet-control repository manages plugin installation across multiple runtime harnesses.
-
-## Pattern
-
-1. Add the plugin package to `.agentwheel/config.json` as a normal package.
-2. Select every runtime-specific artifact exposed by the OpenPack package, for example:
-   - `plugins/extra-message-policy`
-   - `plugins/hermes-extra-message-policy`
-   - shared `rules/...`
-   - runtime settings such as `settings/hermes-extra-message-policy.json`
-3. Add a dedicated rollout profile instead of immediately folding it into `all`, for example:
-
-```json
-"extra-message-policy": {
-  "runtimes": [
-    { "agent": "ct110-openclaw" },
-    {
-      "agent": "ct110-hermes",
-      "adapterConfig": "/absolute/path/to/fleet-control/adapters/hermes-with-plugins.jsonc"
-    },
-    { "agent": "ct110-tirrenia" }
-  ]
-}
-```
-
-4. Run a dry-run first:
-
-```bash
-npx --yes agentwheel@latest install --profile extra-message-policy --dry-run
-```
-
-5. Apply only after reviewing drift/conflict/plugin operations. For OpenClaw semantic plugin installs, include:
-
-```bash
-npx --yes agentwheel@latest install --profile extra-message-policy --execute-plugins
-```
-
-6. Verify the dry-run uses copy/materialized OpenClaw plugin commands, not symlinks:
-
-```bash
-agentwheel install --profile extra-message-policy --dry-run | tee /tmp/plugin-dry-run.txt
-! grep -q -- '--link' /tmp/plugin-dry-run.txt
-```
-
-Fleet-managed OpenClaw plugins should plan `openclaw plugins install <staged-plugin-path>`. If the plan contains `openclaw plugins install --link ...`, stop and update AgentWheel/OpenClaw plugin command generation before applying.
-
-## Profile scoping pitfall
-
-AgentWheel profiles select runtimes, not packages. If a fleet-control repo's root `.agentwheel/config.json` contains many packages and you need a narrow plugin-only rollout, create a separate workspace/profile directory with its own `.agentwheel/config.json` containing only those plugin packages. Then run the dry-run from that profile workspace.
-
-## Important pitfall: custom adapter config placement
-
-For profile installs, `adapterConfig` must be on the profile runtime entry, not only on the named agent. The current workspace agent schema may not preserve `adapterConfig` under `agents.*`, while profile runtimes do support it.
-
-Use an absolute adapter config path when the runtime is remote/SSH or when relative resolution might happen from the target root rather than the fleet repository.
-
-## Hermes plugin artifacts
-
-If the built-in Hermes adapter does not install plugin artifacts, keep a declarative adapter config in the fleet repo, e.g. `adapters/hermes-with-plugins.jsonc`, with a `plugins` target pointing at `.hermes/plugins`.
-
-## Verification checklist
-
-- `agentwheel list <source>` shows all expected runtime-specific artifacts.
-- Direct Hermes dry-run with the custom adapter creates `.hermes/plugins/<plugin>`.
-- Fleet profile dry-run creates the Hermes plugin, rule, and settings.
-- OpenClaw profile dry-run shows `PLUGIN ... semantic plugin install planned`.
-- Do not restart runtimes as part of the AgentWheel install unless the user explicitly asks.

package/skills/agentwheel/references/harness-path-map-rules-2026-06-13.md

@@ -1,98 +0,0 @@
-# Harness path-map rules pattern — 2026-06-13
-
-Use this when Joseph asks to make CT107/CT110 workspace/harness topology visible to all agents through AgentWheel.
-
-## Durable pattern
-
-- Put detailed machine-readable topology in the shared docs root:
-  - `/home/administrator/env/workspace/itermodus/brain-shared/mappings/harnesses.yaml`
-- Put the short, always-installed instruction in the private core toolkit:
-  - `/home/administrator/env/workspace/itermodus/nestdevlab/agent-core-toolkit-private/rules/harness-path-map.md`
-- The `agent-core-toolkit-private` package exposes `rules/` via `openpack.json`, so any new file under `rules/` is discoverable by `agentwheel list .` and installable by configured runtimes.
-
-## Content split
-
-- Rule file: concise operational policy and pointers. Avoid a huge topology dump.
-- YAML file: detailed host/path/mount map, legacy path status, canonical runtime homes.
-
-## Current canonical layout
-
-```text
-/home/administrator/env/workspace/itermodus/brain-shared   # shared docs/memory/maps/runbooks
-/home/administrator/env/workspace/itermodus/nestdevlab     # AgentWheel/OpenPack/plugin/source repos
-/home/administrator/.hermes                                # Hermes harness home
-/home/administrator/.openclaw                              # OpenClaw harness home
-/home/administrator/.codex                                 # Codex harness home
-/home/administrator/.claude                                # Claude harness home
-/home/administrator/.agentwheel                            # AgentWheel home
-```
-
-CT107 `/home/administrator/env/ai-agents` is a technical SSHFS view of `CT110:/home`, not the canonical docs root. Do not propose active CT110 harness state under `/root`; treat `/root` paths as legacy/backup/compatibility until audited.
-
-## Verification
-
-From the package root:
-
-```bash
-agentwheel list .
-```
-
-Expected: it lists both existing and newly added `rules/*.md` artifacts.
-
-Before applying to runtimes, prefer:
-
-```bash
-agentwheel install --dry-run
-```
-
-Apply only after Joseph approves runtime/generated-file changes.
-
-## Completion pattern for fleet propagation
-
-When Joseph approves completing propagation of this rule, do not only run a source-scoped install. Make the package part of durable AgentWheel desired state, then apply both configured remote agents and locally detected runtimes.
-
-1. Add the private core toolkit rule to AgentWheel global config once:
-
-```bash
-sudo -u administrator -H bash -lc 'agentwheel add /home/administrator/env/workspace/itermodus/nestdevlab/agent-core-toolkit-private \
-  --name NestDevLab/agent-core-toolkit-private \
-  --driver local \
-  --adapter openclaw \
-  --mode tracking \
-  --select rules/harness-path-map.md'
-```
-
-2. Preview/apply configured named agents, including SSH targets such as CT110 OpenClaw/Hermes/Tirrenia:
-
-```bash
-sudo -u administrator -H bash -lc 'agentwheel install --all --dry-run'
-sudo -u administrator -H bash -lc 'agentwheel install --all'
-```
-
-3. Separately preview/apply runtimes auto-detected on the current host. `--all` only covers configured agents; it does not cover local auto-detected `.openclaw`, `.claude`, or `.codex` directories unless those are named agents.
-
-```bash
-sudo -u administrator -H bash -lc 'agentwheel install --all-detected --dry-run'
-sudo -u administrator -H bash -lc 'agentwheel install --all-detected'
-```
-
-4. Verify with checksums against the package source and final dry-runs. A clean completion has identical hashes for source/generated rule files and summaries with `drift 0, conflict 0`.
-
-```bash
-sha256sum /home/administrator/env/workspace/itermodus/nestdevlab/agent-core-toolkit-private/rules/harness-path-map.md \
-  /home/administrator/.openclaw/rules/harness-path-map.md \
-  /home/administrator/.claude/rules/harness-path-map.md \
-  /home/administrator/.codex/rules/harness-path-map.md
-
-ssh root@192.168.1.110 'sha256sum \
-  /home/administrator/env/workspace/itermodus/nestdevlab/agent-core-toolkit-private/rules/harness-path-map.md \
-  /home/administrator/.openclaw/rules/harness-path-map.md \
-  /home/administrator/.hermes/rules/harness-path-map.md \
-  /home/openclaw-tirrenia/.openclaw/rules/harness-path-map.md'
-```
-
-## Pitfalls
-
-- Use `--only-source` when doing an ad-hoc source-scoped dry-run; otherwise AgentWheel may try to apply the current workspace's configured packages and report irrelevant selected-artifact errors.
-- A failed apply may leave a pending journal that AgentWheel can recover on the next run. Fix the underlying issue and rerun `agentwheel install`; do not hand-edit generated files unless ownership/permissions block AgentWheel itself.
-- If remote Hermes rule directories are owned by `root`, fix ownership of the directory and rerun AgentWheel instead of copying the file manually, e.g. `chown administrator:administrator /home/administrator/.hermes/rules` on CT110.

package/skills/agentwheel/references/hermes-profile-scoped-skill-rollout.md

@@ -1,43 +0,0 @@
-# Hermes profile-scoped skill rollout
-
-Use when adding one new shared toolkit skill to Hermes default/Karan plus a Hermes profile such as `odino` without reconciling the whole generated skill tree.
-
-## Pattern
-
-1. Put the skill in the class-level toolkit source, e.g. `agent-core-toolkit-private/skills/<skill>/SKILL.md`.
-2. In that toolkit `openpack.json`, restrict the skill item to Hermes if it must not install to OpenClaw/Codex/Claude:
-   ```json
-   {
-     "type": "skills",
-     "path": "skills",
-     "items": {
-       "<skill>": { "runtimes": ["hermes"] }
-     }
-   }
-   ```
-3. Add `skills/<skill>` to the relevant fleet selector.
-4. Dry-run with a scoped source install so AgentWheel does not try to adopt/reconcile every existing runtime skill:
-   ```bash
-   AGENTWHEEL_NO_UPDATE_CHECK=1 npx --yes agentwheel install \
-     /path/to/toolkit --driver local \
-     --agent ct110-hermes \
-     --select skills/<skill> \
-     --only-source --dry-run
-   ```
-5. For a Hermes profile target such as Odino, pass the custom profile adapter config explicitly; otherwise the built-in Hermes adapter may reject `profile-odino` for skills as unsupported:
-   ```bash
-   AGENTWHEEL_NO_UPDATE_CHECK=1 npx --yes agentwheel install \
-     /path/to/toolkit --driver local \
-     --agent ct110-hermes-odino \
-     --adapter-config adapters/hermes-odino.jsonc \
-     --select skills/<skill> \
-     --only-source --dry-run
-   ```
-6. Apply the same commands without `--dry-run` after the plan shows only the intended `CREATE`/`UPDATE` and `conflict 0`.
-7. Verify on the remote host by checking both paths and hashes, then optionally `hermes skills list` and `hermes --profile odino skills list`.
-
-## Pitfalls
-
-- A broad `agentwheel install --agent ct110-hermes` can surface many unrelated conflicts for existing unmanaged skills. Use scoped source install for one-skill rollouts.
-- `--agent ct110-hermes-odino` may not automatically apply the profile adapter config in all CLI shapes; pass `--adapter-config adapters/hermes-odino.jsonc` explicitly for profile skill installs.
-- Keep source ownership and deploy ownership separate: toolkit repo owns the skill; fleet-control owns selectors/locks/deploy docs.