Fix documentation drift across README, CONTRIBUTING, and agent skills.

Corrects LSP completion docs, aligns build instructions with CI, removes hardcoded paths, and documents ion-build workflow in adding-ion-features.

Author: Cod-e-Codes

.cursor/skills/adding-ion-features/SKILL.md

@@ -30,6 +30,7 @@ Copy and track progress:
 - [ ] 5. Type checker - typing, ownership, Send in `src/tc/` (`mod.rs` plus `ownership.rs`, `builtins.rs`, `types.rs` as needed)
 - [ ] 6. IR - lowering in src/ir/mod.rs
 - [ ] 7. Codegen - C output in `src/cgen/` (`mod.rs`, `types.rs`, `builtins.rs`, `drop.rs`) (+ runtime/ if new runtime support)
+- [ ] 7b. Project build - if touching `src/build/` or ION_SPEC section 10.1: `manifest.rs`, `driver.rs`, `c_toolchain.rs`, `paths.rs`; verify `tests/build_hello/` and `tests/build_bad_main/`
 - [ ] 8. Tests - integration test in tests/ (see ion-integration-tests skill)
 - [ ] 9. LSP - update src/lsp/ if diagnostics/hover/completion affected
 - [ ] 10. cargo test && cargo build --release && tests/test_runner.sh (harness precompiles `runtime/ion_runtime.c` once per run)
@@ -91,6 +92,19 @@ Add new `TypeCheckError` variants only when existing ones can't express the fail
 - `cgen` - generated C must compile with `gcc` + `runtime/ion_runtime.c` (or precompiled `.o` via `test_runner.sh`) + `-lpthread`
 - Multi-file: test with `--mode multi` if imports or visibility involved
 
+### Project build (`src/build/`)
+
+Touch when changing `ion.toml` parsing, `ion-build` driver behavior, C toolchain flags, or import/stdlib discovery shared with LSP:
+
+| File | Role |
+|------|------|
+| `manifest.rs` | Parse `ion.toml`, `Project::discover` |
+| `driver.rs` | `build_project`: transpile, compile C, link runtime |
+| `c_toolchain.rs` | Invoke `CC`, compile and link flags |
+| `paths.rs` | Project root, stdlib paths, `discover_import_config` |
+
+Verify with `tests/build_hello/` and `tests/build_bad_main/` smoke tests. See `ion-lang/references/compiler-pipeline.md`.
+
 ### Runtime (`runtime/`)
 
 New builtins (channels, Vec, String, spawn) often need C runtime helpers. Keep headers in `ion_runtime.h` consistent with cgen calls.

.cursor/skills/ion-integration-tests/SKILL.md

@@ -40,11 +40,11 @@ cargo build --release --bin ion-compiler --bin ion-build
 cd tests && ./test_runner.sh
 ```
 
-From PowerShell:
+From PowerShell (repo root; requires Git Bash):
 
 ```powershell
 cargo build --release --bin ion-compiler --bin ion-build
-& 'C:\Program Files\Git\bin\bash.exe' -lc 'cd /c/Users/Cody/Projects/GitHub/Personal/Active/ion-lang/tests && ./test_runner.sh'
+& "${env:ProgramFiles}\Git\bin\bash.exe" -lc 'cd tests && ./test_runner.sh'
 ```
 
 The harness primarily calls `ion-compiler` for `run`/`error`/`cgen` rows. It also runs `ion-build` smoke tests (`tests/build_hello/`, `tests/build_bad_main/`) via the `ION_BUILD` env var (defaults to `../target/release/ion-build`).

.cursor/skills/ion-lang/SKILL.md

@@ -47,7 +47,7 @@ Ion identity depends on these - do not weaken them without explicit user directi
 cargo test
 cargo build --release --bin ion-compiler --bin ion-lsp --bin ion-build
 cargo clippy -- -D warnings
-& 'C:\Program Files\Git\bin\bash.exe' -lc 'cd /c/Users/Cody/Projects/GitHub/Personal/Active/ion-lang/tests && ./test_runner.sh'
+& "${env:ProgramFiles}\Git\bin\bash.exe" -lc 'cd tests && ./test_runner.sh'
 ```
 
 **Application builds:** `ion-build` reads `ion.toml` (walks up from cwd), transpiles, compiles C, links runtime. Default output under `target/`:
@@ -58,7 +58,7 @@ cargo clippy -- -D warnings
 
 **Codegen inspection / integration harness:** `ion-compiler` still transpiles only (or `--mode multi` with in-tree link). Integration tests call `ion-compiler` directly; `test_runner.sh` also runs `ion-build` smoke tests in `tests/build_hello/`.
 
-**Stdlib imports:** `import "stdlib/io.ion" as io;` resolves via `ion.toml` `stdlib_paths`, `ION_STDLIB`, and `{project_root}/stdlib`. CLI and LSP share `build::discover_import_config`.
+**Stdlib imports:** `import "stdlib/io.ion" as io;` resolves via manifest `stdlib_paths`, `ION_STDLIB`, `{project_root}/stdlib`, then install-relative `stdlib/` next to the compiler. CLI and LSP share `build::discover_import_config`.
 
 **Windows:** Stop `ion-lsp` / `ion-compiler` before rebuilding if you get "Access is denied". After compiler or import-resolution changes, rebuild LSP and reload the editor window:
 
@@ -70,9 +70,11 @@ cargo build --release --bin ion-lsp
 
 ```powershell
 .\target\release\ion-compiler.exe examples\hello_world.ion
-gcc examples\hello_world.c runtime\ion_runtime.c -o hello_world.exe -I. -Iruntime -lpthread -lws2_32
+gcc examples\hello_world.c runtime\ion_runtime.c -o hello_world.exe -I. -Iruntime -lpthread
 ```
 
+Add `-lws2_32` on Windows when linking programs that use channels, `spawn`, or sockets.
+
 ## Specialized skills
 
 Read these when the task matches:

CONTRIBUTING.md

@@ -9,15 +9,17 @@
 ## Build
 
 ```bash
-cargo build --release --bin ion-compiler
+cargo build --release --bin ion-compiler --bin ion-build --bin ion-lsp
 ```
 
-Install the compiler into your Cargo bin directory:
+Install CLI tools into your Cargo bin directory:
 
 ```bash
-cargo install --path . --bin ion-compiler
+cargo install --path . --bin ion-compiler --bin ion-build
 ```
 
+`ion-lsp` is built with the release command above; point the editor extension at `target/release/ion-lsp` (see README IDE Support).
+
 ## Test
 
 Unit tests:

README.md

@@ -62,10 +62,10 @@ Ion has a VS Code / Cursor extension that provides:
 - Syntax highlighting
 - Real-time diagnostics (syntax and type errors)
 - Hover: variable types at use sites and `let` binding identifiers; symbol signatures and attached `//` doc prose at definitions and qualified imports
-- Completion: keywords, builtins, and file symbols
+- Completion: prefix-filtered keywords, builtins, and file symbols
 - Go to definition: variables, function calls, and user-defined methods; imported `mod::func` opens the module file
 
-Limitations: built-in methods (`Vec::push`, etc.) do not go to definition; completion has no prefix filtering. Full list in [ION_SPEC.md section 10.3](ION_SPEC.md#103-known-limitations).
+Limitations: built-in methods (`Vec::push`, etc.) do not go to definition. Full list in [ION_SPEC.md section 10.3](ION_SPEC.md#103-known-limitations).
 
 **Installation:**
 
@@ -241,6 +241,12 @@ The runner loads `tests/test_expectations.tsv` (exit codes, error patterns, code
 cargo clippy -- -D warnings
 ```
 
+### Format check
+
+```bash
+cargo fmt --check
+```
+
 ## License
 
 MIT