Merge branch 'main' into mossaka/benchmark

Signed-off-by: Jiaxiao Zhou <duibao55328@gmail.com>

Author: Mossaka

.dockerignore

@@ -0,0 +1,66 @@
+# Git files
+.git
+.gitignore
+.gitattributes
+
+# GitHub workflows and documentation
+.github
+docs/book
+docs/TODO.md
+
+# Target and build artifacts
+target/**
+!target/release/wassette
+bin
+*.wasm
+
+# Examples and tests
+examples/*/target
+tests
+
+# Documentation
+*.md
+!README.md
+LICENSE
+NOTICE
+SECURITY.md
+CODE_OF_CONDUCT.md
+CONTRIBUTING.md
+
+# Development files
+.vscode
+.idea
+*.swp
+*.swo
+*~
+
+# Rust artifacts
+**/*.rs.bk
+Cargo.lock.bak
+
+# OS files
+.DS_Store
+Thumbs.db
+
+# CI/Docker files
+Dockerfile.ci
+docker-compose.yml
+
+# Scripts
+scripts
+
+# Package manager files
+Formula
+flake.nix
+flake.lock
+winget
+
+# Other
+assets
+audit.toml
+deny.toml
+_typos.toml
+rustfmt.toml
+component-registry.json
+policy.yaml
+install.sh

.github/instructions/docs.instructions.md

@@ -6,6 +6,16 @@ applyTo: "docs/**/*.md"
 
 When working on documentation changes that affect visual presentation or layout, **always use Playwright** to display and capture visual changes. This helps reviewers understand the impact of documentation modifications.
 
+## Writing Style Guidelines
+
+**Keep documentation concise and code-focused:**
+- Prefer code examples over verbose explanations
+- Keep document files focused and concise for readability
+- Use clear, simple language that's easy to understand
+- Show working examples first, explain details second
+- Remove unnecessary words - every sentence should add value
+- Write the answer as 2–4 cohesive paragraphs. No bullet points, no numbered lists, no sub-headings, no tables, no Markdown lists.
+
 ## Running the Documentation Locally
 
 The project uses [mdbook](https://rust-lang.github.io/mdBook/) for documentation. Use the following commands:

.github/instructions/rust.instructions.md

@@ -22,6 +22,7 @@ View the design/architecture.md for a high-level overview of the architecture an
 - Use traits to define shared behavior and generics to create reusable, type-safe components. Design the API to be extensible
 - Use stdlib primitives like `Arc` and `Mutex` for thread safety and shared state.
 - Choose appropriate data types like `&str` over `String` for performance and memory efficiency.
+- ALWAYS run `cargo machete` at the end to check for unused dependencies.
 
 ## Copyright Headers