agentwheel 0.22.1 → 0.22.3

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 CHANGED
@@ -546,6 +546,23 @@ agentwheel ownership retire-stale \
546
546
  --fleet <fleet-id> --agent <agent> --json
547
547
  ```
548
548
 
549
+ To use a target configured in a nested workspace while retiring ownership into its containing
550
+ registered Fleet, run from that workspace and select the destination owner separately:
551
+
552
+ ```bash
553
+ agentwheel ownership retire-stale --local --agent service-agent \
554
+ --to-fleet <fleet-id> --to-workspace-root <fleet-root> \
555
+ --from-workspace-root <stale-owner-root> \
556
+ --source-state-key <stale-state-key> \
557
+ --destination-state-key <fleet-owned-state-key> --json
558
+ ```
559
+
560
+ `--to-fleet` qualifies the destination owner; `--local`, `--user`, or `--fleet` selects the target
561
+ workspace and its configured transport. The selected workspace must be within the registered
562
+ Fleet root, including after symlink resolution, and cannot identify a different Fleet.
563
+ The original `--fleet <id>` command remains supported for targets configured directly at that
564
+ Fleet root. Neither form changes agent configuration or relaxes contribution and revision guards.
565
+
549
566
  The dry-run still proves exact destination coverage and runtime bytes. Apply only its emitted command,
550
567
  which includes the plan, source, destination, and manifest-inventory revisions.
551
568
  For duplicate state owned by the same registered Fleet, set both workspace roots to the Fleet root