docs/getting-started.md tells new contributors to build the native CLI with:
cd oss
cargo build --manifest-path crates/Cargo.toml -p runx-cli
There is no oss/ directory in this repository — the checkout root is already the OSS workspace, so the very first command in the walkthrough fails with cd: no such file or directory: oss on a fresh clone.
The same stale path assumption appears in:
docs/reference.md line 15 (cd oss) and line 673 (cd oss/packages/cli)docs/skill-to-graph.md line 107 (cd oss)
These look like leftovers from a layout where the repo lived under an oss/ subdirectory. Dropping the cd oss step (or replacing it with a note that the clone root is the workspace) would make the walkthrough runnable as written.
Verified against a fresh shallow clone today. Happy to send a small PR removing the stale lines if that is preferred.
docs/getting-started.mdtells new contributors to build the native CLI with:There is no
oss/directory in this repository — the checkout root is already the OSS workspace, so the very first command in the walkthrough fails withcd: no such file or directory: osson a fresh clone.The same stale path assumption appears in:
docs/reference.mdline 15 (cd oss) and line 673 (cd oss/packages/cli)docs/skill-to-graph.mdline 107 (cd oss)These look like leftovers from a layout where the repo lived under an
oss/subdirectory. Dropping thecd ossstep (or replacing it with a note that the clone root is the workspace) would make the walkthrough runnable as written.Verified against a fresh shallow clone today. Happy to send a small PR removing the stale lines if that is preferred.