Skip to content

Refresh CLI commands from the deployed API and prepare 8.5.753 - #8

Merged
zeekay merged 1 commit into
mainfrom
fix/cli-live-spec
Oct 20, 2026
Merged

zeekay merged 1 commit into
mainfrom
fix/cli-live-spec

Conversation

@zeekay

@zeekay zeekay commented Oct 20, 2026

Copy link
Copy Markdown
Member

The shared CI checks the deployed API document, while the CLI generation helper still used an older private repository document. CI therefore rejected the command tree as stale even though the functional tests passed.

Regenerate the command definitions and live evidence from API v8.5.844, record that document's digest, and make the local spec check use the same public source as CI. Prepare CLI v8.5.753.

Validation: workspace suite passed except the initial evidence-version mismatch; after recapturing with the updated lock, CLI integration and all three spec regression tests passed. Strict clippy and spec-check passed. Live probes found no absent coordinates; 53 results remain inconclusive. Production cloud, local dev, token login, branch delivery, follow-up, and teleport were verified on the preceding CLI commit.

CI reads the deployed public API document, but the local helper still fetched a private pinned YAML file. Generate from the public document consistently and refresh its digest, commands, and live evidence together.

Testing: workspace suite; corrected evidence provenance and reran CLI/spec regression tests successfully; strict clippy; spec-check; 1025 live probes found no absent coordinates, with 53 inconclusive responses.
Risk: medium; generated commands follow current API shapes and remove retired routes.
How to revert: revert this commit and install v8.5.752.
@zeekay
zeekay merged commit db59227 into main Oct 20, 2026
2 of 3 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant