docs: add Development category with testing, limitations, building, and contributing guides

Add four new documentation pages under the Development category:
- Testing: test infrastructure, categories, CI/CD pipeline, how to write tests
- Known Limitations: consolidated limitations from all feature docs
- Building from Source: prerequisites, feature flags, WASM, cross-compilation
- Contributing: development rules, coding standards, PR workflow

Update CONTRIBUTING.md with accurate tooling (cargo nextest, clippy flags).
Clean up .gitignore entries.

Author: semihalev

.gitignore

@@ -33,13 +33,10 @@ cobertura.xml
 tarpaulin-report.html
 
 # Local development
-.claude/settings.local.json
-CLAUDE.md
 TODO.md
 *.disabled
 deny.toml
 
 # Documentation build artifacts
 docs/_site/
 docs/.jekyll-cache/
-git_history_backup.log

CONTRIBUTING.md

@@ -1,28 +1,62 @@
 # Contributing to Stoolap
 
-Thank you for your interest in contributing to Stoolap! This document provides guidelines and information about the contribution process.
+Thank you for your interest in contributing to Stoolap! For the full contributing guide, see our [documentation](https://stoolap.github.io/stoolap/docs/development/contributing/).
 
-## Code of Conduct
+## Quick Start
 
-By participating in this project, you agree to uphold our Code of Conduct (to be added).
+```bash
+# Fork and clone
+git clone https://github.com/YOUR-USERNAME/stoolap.git
+cd stoolap
+
+# Build
+cargo build
+
+# Run tests
+cargo nextest run
 
-## License Information
+# Lint (must pass with zero warnings)
+cargo clippy --all-targets --all-features -- -D warnings
 
-Stoolap is licensed under the [Apache License, Version 2.0](LICENSE). By contributing to Stoolap, you agree that your contributions will be licensed under the same license.
+# Format
+cargo fmt
+```
 
-### What this means for contributors
+## Development Rules
 
-1. **Contribution Licensing**: All contributions you submit will be under the Apache License 2.0. If you submit code that is not your original work, please identify its source and confirm it's compatible with the Apache License 2.0.
+- **No TODOs**: Never write `// TODO`, `unimplemented!()`, or `todo!()`
+- **Performance first**: Minimize allocations, avoid unnecessary `.clone()` and `.format()`
+- **Test everything**: `cargo nextest run` must pass before submitting
+- **Zero warnings**: `cargo clippy --all-targets --all-features -- -D warnings`
+- **Format code**: Always run `cargo fmt`
 
-2. **Contributor License Agreement (CLA)**: We currently do not require a formal CLA, but by submitting a contribution, you are agreeing that your work will be licensed under the project's Apache License 2.0.
+## Testing
 
-3. **Patent Rights**: The Apache License 2.0 includes an express grant of patent rights from contributors to users. Be aware of this when contributing patented intellectual property.
+```bash
+# Run all tests (debug mode, never use --release)
+cargo nextest run
 
-4. **Attribution Requirements**: You must retain all copyright, patent, trademark, and attribution notices from the source form of the work in any derivative works you distribute.
+# Run a specific test file (faster, compiles only that target)
+cargo nextest run --test my_feature_test
+```
+
+**Important**: Use `cargo nextest run --test <name>` instead of keyword filtering. The `--test` flag compiles only the specified test binary, which is significantly faster.
+
+## Pull Request Process
+
+1. Ensure all tests pass
+2. Ensure clippy passes with zero warnings
+3. Ensure code is formatted (`cargo fmt`)
+4. Write clear commit messages
+5. Open a pull request against `main`
+
+## License
+
+Stoolap is licensed under the [Apache License, Version 2.0](LICENSE). By contributing, you agree that your contributions will be licensed under the same license.
 
 ### License Headers
 
-All source files in the project should include a license header:
+All `.rs` source files must include the Apache 2.0 header:
 
 ```rust
 // Copyright 2025 Stoolap Contributors
@@ -39,123 +73,3 @@ All source files in the project should include a license header:
 // See the License for the specific language governing permissions and
 // limitations under the License.
 ```
-
-When creating new files, please include this header.
-
-## Development Process
-
-### Setting Up Your Development Environment
-
-1. Fork the repository on GitHub
-2. Clone your fork locally:
-   ```bash
-   git clone https://github.com/YOUR-USERNAME/stoolap.git
-   cd stoolap
-   ```
-3. Add the upstream repository as a remote:
-   ```bash
-   git remote add upstream https://github.com/stoolap/stoolap.git
-   ```
-4. Create a new branch for your feature or bugfix:
-   ```bash
-   git checkout -b feature-or-bugfix-name
-   ```
-
-### Building
-
-```bash
-# Debug build
-cargo build
-
-# Release build
-cargo build --release
-
-# Build with CLI features
-cargo build --release --features cli
-```
-
-### Testing
-
-Before submitting your changes, please run the tests:
-
-```bash
-# Run all tests
-cargo test
-
-# Run library tests only
-cargo test --lib
-
-# Run specific test
-cargo test test_name
-
-# Run tests with output
-cargo test -- --nocapture
-```
-
-### Linting
-
-Ensure your code passes clippy without warnings:
-
-```bash
-# Check library code
-cargo clippy --lib
-
-# Check all code
-cargo clippy --all-targets
-```
-
-### Formatting
-
-Format your code with rustfmt:
-
-```bash
-cargo fmt
-```
-
-### Submitting Changes
-
-1. Commit your changes using clear commit messages that explain the problem you're solving and your approach
-2. Push your branch to your fork
-3. Open a pull request against the main repository's `main` branch
-
-### Pull Request Process
-
-1. Update the README.md or documentation with details of your changes, if applicable
-2. Ensure all tests pass (`cargo test`)
-3. Ensure clippy passes (`cargo clippy --lib`)
-4. Your PR will be reviewed by maintainers, who may request changes
-5. Once approved, your PR will be merged
-
-## Coding Standards
-
-- Follow Rust standard conventions and idioms
-- Use `cargo fmt` for formatting
-- Run `cargo clippy` and fix all warnings
-- Keep functions small and focused
-- Document public APIs with doc comments (`///`)
-- Write tests for new functionality
-- Avoid `unsafe` code unless absolutely necessary (and document why)
-- Avoid `unwrap()` in library code - use proper error handling
-- No `todo!()` or `unimplemented!()` in committed code
-
-## Project Structure
-
-```
-src/
-├── api/           # Public Database API
-├── core/          # Core types (Value, Row, Schema, Error)
-├── executor/      # Query execution engine
-├── functions/     # Built-in functions (scalar, aggregate, window)
-├── optimizer/     # Cost-based query optimizer
-├── parser/        # SQL parser (lexer, AST, parser)
-├── storage/       # Storage engine and MVCC
-└── bin/           # CLI binary
-```
-
-## Additional Resources
-
-- [The Rust Book](https://doc.rust-lang.org/book/)
-- [Rust API Guidelines](https://rust-lang.github.io/api-guidelines/)
-- [Apache License 2.0 Explained](https://tldrlegal.com/license/apache-license-2.0-(apache-2.0))
-
-Thank you for contributing to Stoolap!

docs/_data/doc_categories.yml

@@ -6,3 +6,4 @@
 - name: "Functions"
 - name: "SQL Features"
 - name: "Performance"
+- name: "Development"