[Myothas]

Bead: ankra-rjzybk

Documents ankra cluster agent upgrade --version <release> [--allow-downgrade] and the matching version / allow_downgrade parameters of the MCP tool upgrade_cluster_agent.

• reference/cli/cluster.mdx: the agent upgrade section, written in the exact shape tools/gendocs renders from the command's Long/Example/flags, so the release-time regeneration produces the same text.
• concepts/cluster-agent.mdx: a "From the CLI" subsection under Upgrading the Agent: without --version an upgrade never moves an agent backwards; an older --version needs --allow-downgrade; an unknown release is refused.

Code: ankraio/ankra-cli (flags) and ankraio/cluster#5043 (MCP tool). The API side shipped in ankraio/cluster#5040.

🤖 Generated with Claude Code

[ankra-platform]

✅ Run #260 succeeded

Run #260 for commit 0d66b5a (pull request #593).

Stage	Step	Outcome	Duration
build	build	success	1m 26s
checkout	checkout	success	25s
gate	gate	success	0s
publish	publish	skipped	-
scan	scan (tool=checkov)	success	1m 18s
scan	scan (tool=semgrep)	success	36s
scan	scan (tool=trivy)	success	1m 7s

Open this run in Ankra

_{🔗 Details ↗ · Updated Oct 20, 2026, 5:15 AM UTC}

---

Ankra AI review

Verdict: looks good.

Docs-only change documenting the new --version and --allow-downgrade flags for ankra cluster agent upgrade, plus the matching MCP tool parameters. The concepts page and CLI reference are consistent with each other on the downgrade-refusal semantics, and the flag table matches the prose. No correctness or security concerns in the content itself.

---

Reviewed commit 0d66b5a. This review is read-only and advisory.

[Myothas]

growth lane read (round r-20261020T053649Z, calibrate), head 0d66b5a. HOLD until the two unserved sources land; nothing in the text needs changing.

Audited sentence by sentence against what is served, not against the merge list:

• API behaviour (never backwards without --version; an older --version refused unless --allow-downgrade; a release neither published nor running refused): cluster#5040 merged 03:49:07Z = Build & Deploy run 4973 = hel1 ankra-cluster-api-go 1.0.9973, progressed 03:54:51Z. SERVED. The PR's refusal wording matches #5040's (409 on the downgrade; "is not a published stable release or the version this agent runs").
• upgrade_cluster_agent with version / allow_downgrade: cluster#5043 (80aa0d5c) OPEN, Ankra pipeline still running at 05:4xZ. NOT SERVED.
• CLI --version / --allow-downgrade: ankra-cli#583 (55849217) OPEN. Latest tag v0.43.1 (2d5dc045) and master 1bb51fe9 carry neither flag, and the live reference page is pinned to v0.40.0 (docs#590 raises it to v0.43.1). Until a tag carries docs(security): every standard change is now recorded in the audit log #583, this section would describe flags the released CLI does not have.
• Text parity: the Long, Example and flag strings match cli#583 verbatim, and gendocs code-spans bare --flag tokens (flagToken), so the backticks match a regeneration too. docs#590's hunks in reference/cli/cluster.mdx do not touch the agent sections, so there is no textual conflict with the pending regen. The page header still says it is generated by tools/gendocs and not edited by hand; the regeneration at the tag that carries docs(security): every standard change is now recorded in the audit log #583 is the real source of this section.
• Copy checks: em dashes 0 in all three spellings. Checks on 0d66b5a all green (Prose lint, Broken links, Structure checks, Ankra pipeline, build-and-push).
• Overlap with docs#594: both add to the same Upgrading the Agent section of concepts/cluster-agent.mdx (docs(audit): agent settings changes are on the audit log, with a reason (ankra-8tbujq) #594 a bullet at :210, this PR a subsection at :215). Non-overlapping hunks; the second to merge may need a rebase.

Gates to merge: (1) cluster#5043 served on hel1 (app.kubernetes.io/version = its Build & Deploy run + 5000); (2) an ankra-cli tag that carries #583, at which point #590's regeneration and latestStableCli move with it.

Rider in the same section (one word, two places): concepts/cluster-agent.mdx:8 and :206 say agent releases are on the 2.0.x track. Releases are 2.1.x (this PR's own examples 2.1.1250 and 2.1.1247, cluster#5040's tests, the fleet on 2.1.12xx). Filed as ankra-ccxkvv (P4 docs bug) so it does not rot; folding the fix into this PR closes it.

Posted by the Ankra growth lane (an Ankra AI agent).

[Myothas]

Growth lane round r-20261020T070430Z (Ankra AI agent), the record after this PR landed.

It landed at the audited head 0d66b5a (squash d6a8fda, 05:54:14Z, 10 s after cluster#5043) and is live on https://docs.ankra.ai. As of 07:1xZ 10-20:

• API and MCP sentences: TRUE. cluster#5043 = B&D run 4975, served in hel1 cluster-api-go 1.0.9978 (progressed 06:48:13Z).
• CLI sentences: ahead of the released CLI. cli#583 is on master (squash c067070b), no tag past v0.43.1 exists, and v0.43.1 (2d5dc045) is 7 commits behind c067070b. ankra cluster agent upgrade --version and --allow-downgrade are documented at concepts/cluster-agent.mdx:218-224 and reference/cli/cluster.mdx:747-752 but not installable until the next cli tag; the hand edit to the generated reference page is replaced by the regen at that tag.

Tracked as ankra-s9kkja (a CliVersion badge on the concepts block and the regen audit, at the first tag past v0.43.1). ankra-ccxkvv (:8 and :206 still say 2.0.x) was not folded in and stays open. Nothing to change on this PR.