bug: CI jobs Python SDK + SDK Conformance point at clients/python, archived in 106f90446

[dasTholo]

Summary

Python SDK (leanctx) and SDK Conformance Matrix fail on every run, including on main, because both point at clients/python, which no longer exists. 106f90446 moved it to _archive/clients-python/ and the workflow references were not updated. That commit says so itself:

CI note: publish-clients.yml and ci.yml reference archived paths (will be updated when new SDK is ready).

Filing it so the breakage is tracked rather than carried silently — with CI Green depending on these jobs, every PR now shows a red check set regardless of its own content.

Symptom

Both jobs fail within seconds, at their first working-directory step:

##[error]An error occurred trying to start process '/usr/bin/bash' with working directory
'/home/runner/work/lean-ctx/lean-ctx/clients/python'. No such file or directory

Confirmed on run 32403748709 (job Python SDK (leanctx), step Install) and on the main run 32392749871.

git ls-tree -d --name-only upstream/main:clients returns only rust.

Affected references

File	Line	Step
.github/workflows/ci.yml	364	python-sdk → Install
.github/workflows/ci.yml	367	python-sdk → Test
.github/workflows/ci.yml	426	sdk-conformance → Install Python SDK
.github/workflows/publish-clients.yml	66	PyPI publish

ci.yml:386 carries a comment referring to "conftest from clients/python" as well.

The publish-clients.yml reference has not fired yet, but would break a PyPI release the same way.

Options

Whichever fits the plan for the new SDK:

1. Point at the archived copy — _archive/clients-python. Restores the gate immediately, but pins CI to code that was deliberately archived.
2. Point at the successor — packages/python-lean-ctx/ exists and carries a pyproject.toml. If that is the intended replacement, the three working-directory values plus publish-clients.yml can move there.
3. Skip the jobs until the new SDK lands — an if: guard or removing them from the CI Green dependency list, so unrelated PRs stop inheriting a red status.

Option 3 seems closest to the intent recorded in 106f90446 ("will be updated when new SDK is ready"), and would make CI results meaningful again in the meantime.

Not related to #1496

Separate cause and separate fix: #1496 is Rust 1.98.0 turning eleven pre-existing findings in rust/src into hard errors. This one is a workflow path that outlived the directory it points to. Between them they account for six of the failing jobs on any current PR.

[yvgude]

Status update: the CI references were corrected as part of the archived-client cleanup and the issue is integrated on main. Please report back with the affected workflow URL if it still fails on current main.