Remove incorrect nightly Rust requirements from DEVELOPMENT.md

[Copilot]

DEVELOPMENT.md incorrectly stated that nightly Rust was required for formatting and linting. The project uses stable Rust for all operations.

Changes

• Prerequisites: Removed nightly toolchain requirement, clarified stable Rust handles all operations
• Installation: Removed rustup toolchain install nightly instructions
• Formatting/Linting: Removed incorrect claims about using cargo +nightly
• CI Workflow Steps: Updated to match actual ci.yml (15 steps, stable only)
• Best Practices: Removed "Use nightly for formatting and linting" section
• Troubleshooting: Removed "Nightly Toolchain Issues" section
• rust-toolchain.toml: Removed outdated nightly-related comments

Validation

• All 14 Makefile targets confirmed to use standard cargo commands (not +nightly)
• CI workflow installs only stable Rust with rustfmt and clippy components
• No references to nightly remain in documentation

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.

[semanticdiff-com]

Review changes with  

[Copilot]

Pull request overview

Updates developer-facing documentation to accurately reflect that Jet uses the stable Rust toolchain (including rustfmt/clippy), and aligns CI documentation with the current GitHub Actions workflow.

Changes:

• Remove incorrect nightly-Rust requirements and installation steps from DEVELOPMENT.md.
• Update CI workflow documentation to reflect the current stable-only CI job (including LLVM caching and auto-format behavior).
• Remove outdated nightly-related comments from rust-toolchain.toml.

Reviewed changes

Copilot reviewed 2 out of 2 changed files in this pull request and generated 4 comments.

File	Description
rust-toolchain.toml	Removes outdated nightly-related comments; keeps stable as the configured toolchain.
DEVELOPMENT.md	Updates prerequisites, formatting/linting guidance, Makefile target descriptions, and CI step documentation to match current tooling/CI behavior.

[Copilot]

PR description claims “No references to nightly remain in documentation”, but the repo still contains “nightly” references (e.g., docs/manifesto.md). Either narrow the claim in the PR description (e.g., “in DEVELOPMENT.md / toolchain docs”) or update the remaining docs to be consistent with “stable for all operations”.

[Copilot]

The comment says the toolchain profile is “minimal” (faster to install), but the config sets profile = "default". Either change the comment to match default, or switch the profile to minimal if that’s intended.

Suggested change

	# Specify the profile - minimal is faster to install
	# Use the default profile (includes common components like rustfmt)

[Copilot]

The CI steps list says the workflow has 15 steps, but the actual .github/workflows/ci.yml also includes an actions/checkout@v4 step before caching LLVM. Consider including checkout in the numbered list (or adjust the “15 steps” wording) so the documentation matches the workflow.

Suggested change

	1. **Cache LLVM 21** - Checks for cached LLVM installation
	2. **Restore LLVM from cache** - Restores if cache hit (conditional)
	3. **Install LLVM 21** - Uses `scripts/install-llvm.sh` if not cached (conditional)
	4. **Log LLVM shared libraries** - Verification step
	5. **Set LLVM environment variables** - Configures LLVM_SYS_211_PREFIX
	6. **Cache Rust build artifacts** - Uses Swatinem/rust-cache
	7. **Install Rust stable** - With rustfmt and clippy components
	8. **Apply formatting fixes** - `cargo fmt --all`
	9. **Commit formatting fixes** - Automatically commits and pushes formatting changes (conditional)
	10. **Run clippy** - `cargo clippy --all-targets --all-features -- -D warnings`
	11. **Install cargo-nextest** - Test runner
	12. **Check all targets** - `cargo check --all-targets --all-features`
	13. **Build** - `cargo build --verbose --all-features`
	14. **Run tests with nextest** - `cargo nextest run --all-features --no-fail-fast`
	15. **Run doctests** - `cargo test --doc --all-features`
	1. **Checkout repository** - Uses `actions/checkout@v4`
	2. **Cache LLVM 21** - Checks for cached LLVM installation
	3. **Restore LLVM from cache** - Restores if cache hit (conditional)
	4. **Install LLVM 21** - Uses `scripts/install-llvm.sh` if not cached (conditional)
	5. **Log LLVM shared libraries** - Verification step
	6. **Set LLVM environment variables** - Configures LLVM_SYS_211_PREFIX
	7. **Cache Rust build artifacts** - Uses Swatinem/rust-cache
	8. **Install Rust stable** - With rustfmt and clippy components
	9. **Apply formatting fixes** - `cargo fmt --all`
	10. **Commit formatting fixes** - Automatically commits and pushes formatting changes (conditional)
	11. **Run clippy** - `cargo clippy --all-targets --all-features -- -D warnings`
	12. **Install cargo-nextest** - Test runner
	13. **Check all targets** - `cargo check --all-targets --all-features`
	14. **Build** - `cargo build --verbose --all-features`
	15. **Run tests with nextest** - `cargo nextest run --all-features --no-fail-fast`
	16. **Run doctests** - `cargo test --doc --all-features`

[Copilot]

The docs say CI “pushes [formatting fixes] back to the branch on push/PR”, but the workflow’s Commit formatting fixes step is conditional and won’t run for PRs from forks (no write permission). Suggest clarifying the condition (e.g., only on pushes and same-repo PRs) to avoid misleading contributors.

Suggested change

	- **Auto-formatting**: Automatically applies formatting fixes and pushes them back to the branch on push/PR
	- **Auto-formatting**: Automatically applies formatting fixes in CI and, when the workflow has write permission (pushes and same-repo PRs only), pushes them back to the branch