v0.10.2

Summary

0.10.2 fixes the Edge batch-claim flow and tightens the operator UX around long-running CLI work.

The main behavioral change is in edge claim-batch: rows that require connectivity verification now run the Edge ping inside the batch before startClaim. That makes the batch path match the intended claim flow instead of assuming a separate prior ping command proved connectivity.

Edge Claim Batch

• edge claim-batch now runs a pre-claim ping for blank skip_connectivity_check rows and explicit skip_connectivity_check=false rows.
• Rows with skip_connectivity_check=true skip the batch-owned ping and send skip_connectivity_check: true to startClaim.
• New edge claim-batch --skip-connectivity-check applies skip mode to blank rows. Rows that explicitly say skip_connectivity_check=false are treated as conflicts and rejected instead of being silently overridden.
• Batch output now distinguishes ping failures from claim failures with ping-failed, preClaimPing, and totals.pingFailed.
• Resume now skips prior succeeded and already-claimed rows before skip-connectivity conflict checks, so completed rows stay completed on rerun.

Flow And Utility UX

• Flow summaries now include nextAction for non-completed runs, giving agents and operators the next safe command/artifact to use.
• flow list --format text|json improves flow discovery and exposes required context plus safe first commands.
• Flow resume commands now preserve custom --out-dir values and use platform-appropriate quoting.
• Missing or malformed flow resume metadata now fails closed instead of falling back to invocation defaults.
• Utility dry-runs now count validated rows under totals.planned; totals.succeeded is reserved for applied rows.
• util prepare notes now include clearer column guidance, reject taxonomy, JSON shape examples, and safe next commands.

Logs, Config, And Docs

• logs show can look up exact entries by --entry <sessionId>:<seq> or --request-id <id> without being limited to the recent tail.
• Global --output now works consistently with flow list and logs when local --format is not explicitly provided.
• config tenant remove now requires --confirm and reports removed profile/key-slot metadata.
• Edge claim docs and the shipped xyte-cli skill guidance now describe plan-first batch claiming, resume artifacts, skip-connectivity precedence, and the resume artifact limitation.

Validation

• npm run release:check passed locally.
• GitHub CI passed on main.
• Publish workflow passed and published @xyteai/cli@0.10.2.
• Release assets workflow passed and uploaded the package tarball, SBOM, and checksums.

Full changelog: v0.10.1...v0.10.2