agentwheel 0.21.5 → 0.21.7
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +17 -0
- package/dist/index.js +772 -607
- package/openpack.json +1 -1
- package/package.json +1 -1
- package/skills/agentwheel/SKILL.md +1 -1
- package/skills/agentwheel-discovery/SKILL.md +1 -1
package/README.md
CHANGED
|
@@ -139,6 +139,23 @@ refused unless `--carry-drift` is passed: the dry-run prints the runtime hash, t
|
|
|
139
139
|
`--expected-runtime-hash <sha256>`, and the manifest keeps the recorded hash so the next install
|
|
140
140
|
still reports the drift. Merge and managed-block entries never carry drift.
|
|
141
141
|
|
|
142
|
+
Use `--source-state-key <exact-key>` when an existing source manifest must be selected explicitly.
|
|
143
|
+
This is a command-local equivalent of a named agent's `stateKey`; it does not edit agent configuration,
|
|
144
|
+
move state files, or reconstruct graph locks. The key must be canonical and match the selected adapter
|
|
145
|
+
and installation type. The existing target identity, source owner, exact merge contribution, hash,
|
|
146
|
+
revision, pending-journal and migration guards still apply. For example:
|
|
147
|
+
|
|
148
|
+
```bash
|
|
149
|
+
agentwheel ownership handoff mcp/example.json --local --agent local-codex \
|
|
150
|
+
--source-state-key codex.user.existing-state \
|
|
151
|
+
--from-workspace-root /old/workspace --to-workspace-root /new/workspace --dry-run
|
|
152
|
+
```
|
|
153
|
+
|
|
154
|
+
Apply only the same reviewed selection with `--expected-hash` and `--expected-revision`. An explicit
|
|
155
|
+
key is never inferred from other claims and does not allow incomplete merge ownership or drift to
|
|
156
|
+
be carried for merge artifacts.
|
|
157
|
+
|
|
158
|
+
|
|
142
159
|
For a one-time MCP rename, keep the legacy artifact in a dedicated cutover workspace rather than
|
|
143
160
|
the canonical desired-state profile. Set the legacy manifest `stateKey` on its named agent, then
|
|
144
161
|
preview one runtime at a time:
|