B-X0EC-sdf-stale-sdlc-cli
SDF shells out to one sdlc CLI checkout for the whole machine
(solutions/ontological/desktop/src-tauri/src/actions/sdlc_cli.rs). When that checkout is older
than the project it is pointed at, actions fail with an error about the project, not about the
CLI.
What happened
Section titled “What happened”On 2026-10-03, POST /api/actions/project-setup-status returned 500 for this repository:
sdlc.yaml is not a valid sdlc.yaml ... Unrecognized keys: "workflows", "hooks"The sdlc.yaml is valid for the current CLI. SDF had resolved the checkout recorded in
~/Library/Application Support/sdlc/home, a clone several hundred commits behind main, whose
config schema predates those keys.
What is wanted
Section titled “What is wanted”- SDF shows which checkout it resolved and that CLI’s version, in Settings and in the error.
- When the CLI rejects a project’s
sdlc.yamlfor unknown keys, the message says the CLI may be older than the project and how to repoint it (sdlc dev link, orSDLC_HOME). - A status read that fails this way is reported as a CLI mismatch, not a 500.
Found while serving SDF for M-YX34. It is one of the conditions the startup check should report (B-CSHR-sdf-startup-check).