[barbatos2011]

Two mistakes in #224, found reviewing it after it had already merged.

The partial-success guidance was wrong in the direction that matters

#224 added this to AGENTS.md:

Re-running the whole command is usually wrong: the nodes that succeeded are already in the requested state.

Only one command emits PARTIAL_SUCCESS — network destroy — and for that one the reasoning is backwards. Its message is state cleaned up regardless (cmd/network/destroy.go:189): trond has already dropped every node from state before returning. So:

• a retry returns NETWORK_NOT_FOUND, not a partial re-run;
• the entries in failed are containers or systemd units still running on the target with nothing tracking them.

An agent following the old text would retry, get NETWORK_NOT_FOUND, and reasonably conclude the teardown had completed — while the containers kept running. That is a worse failure than the missing-code gap #224 set out to fix.

It now says: do not retry, surface the failed list for manual cleanup. It also records what the other multi-node commands do instead, so "multi-node" is no longer implied to mean "partial-reporting":

command	on per-node failure
network destroy	exit 1, error_code: PARTIAL_SUCCESS, removed + failed arrays, state already clean
network create	stops at the first failed node, DEPLOY_ERROR, exit 1
network upgrade	UPGRADE_FAILED, exit 1

The same over-generalisation is corrected in internal/output/exitcode.go and contracts/cli-contract.md, which #224 worded the same way.

The changelog's 40-command list sat under the wrong heading

#223 split ### Added into Foundation (what the never-published alpha section described) and Since (everything after). #224 replaced Foundation's 32 CLI commands bullet with an enumeration of all 40 — including recipe, schema, mcp, doctor, verify-config, build and shadow-fork, every one of which is itemised again below under Since.

Release notes that say "Foundation: everything" and then "Since: some of that again" are worse than the wrong count they replaced. The total is now a lead paragraph under ### Added, where it describes the release; Foundation goes back to naming the command groups the project launched with.

Checked while reviewing, no change needed

• Only the root command defines PersistentPreRunE, so nothing shadows fix: reconcile the docs with what trond actually does #224's new --output validation or paths.SetBaseDir.
• SchemaVersion governs the output-JSON schema manifest, not the CLI flag surface, so removing --config needs no version bump — cmd/schema_coverage_test.go and version_test.go agree.
• shadow-fork mutate --config binds its own local flag and still works. Removing the root persistent --config in fact took away a latent shadowing hazard between the two.
• trond completion bash is fine — an earlier report of exit 1 was my own shell quoting, not a regression.

No behaviour change here; docs plus one code comment. make test 25/25, gofmt and vet clean, knowledge/ and internal/knowledge/files/ still byte-identical.