docs: remove stale 'oss/' paths from build walkthroughs

docs/getting-started.md

@@ -14,7 +14,6 @@ checked-in `examples/hello-world` package so the commands stay tied to the repo.
 Build the native CLI from the OSS workspace:
 
 ```bash
-cd oss
 cargo build --manifest-path crates/Cargo.toml -p runx-cli
 ```
 

docs/reference.md

@@ -12,7 +12,6 @@ The npm CLI package is `@runxhq/cli` and exposes the `runx` binary.
 Start with the checked-in hello-world skill:
 
 ```bash
-cd oss
 cargo build --manifest-path crates/Cargo.toml -p runx-cli
 export RUNX_RECEIPT_DIR="$(mktemp -d)"
 crates/target/debug/runx skill examples/hello-world \
@@ -668,17 +667,17 @@ coverage.
 ## Build And Pack
 
 ```bash
-pnpm --dir oss build
-pnpm --dir oss test tests/cli-package.test.ts
-cd oss/packages/cli
+pnpm build
+pnpm test tests/cli-package.test.ts
+cd packages/cli
 npm pack --dry-run --json
 ```
 
 The package must include `dist/index.js` and `dist/index.d.ts`, and `dist/index.js` must be executable.
 
 ## Boundary Rules
 
-- `oss/` must not import from `cloud/`.
+- `oss/` (this repository) must not import from `cloud/` (the private companion workspace, not part of this checkout).
 - State-machine and policy packages remain pure.
 - Rust owns trusted local runtime/execution, including sandbox, receipts,
   policy, authority, payment, harness, built-in adapters, and external

docs/skill-to-graph.md

@@ -104,7 +104,6 @@ The gates are intentionally narrow:
 Use the graph harness as the executable contract:
 
 ```bash
-cd oss
 cargo build --manifest-path crates/Cargo.toml -p runx-cli
 crates/target/debug/runx harness examples/hello-graph/harness.yaml --json
 ```