docs: enhance AGENTS.md and related documentation for clarity and structure

- Updated AGENTS.md to provide clearer guidance for AI coding assistants, including rules of engagement, file priority order, and critical restrictions.
- Revised project overview to emphasize Gold Digger as a production-ready Rust CLI tool for MySQL/MariaDB queries, detailing its architecture and command examples.
- Improved formatting and consistency across various documentation files, ensuring better usability and understanding for contributors.

These updates aim to enhance the documentation's clarity and provide a more structured approach to development practices within the Gold Digger project.

Author: unclesp1d3r

.cursor/rules/rust-best-practices.mdc

@@ -3,6 +3,7 @@ description:
 globs:
 alwaysApply: true
 ---
+
 # Rust Best Practices for gold_digger
 
 ## Project Structure
@@ -71,7 +72,7 @@ just security     # cargo audit (advisory)
 
 Required for all public functions using `///`:
 
-```rust
+````rust
 /// Converts MySQL rows to string vectors for output formatting.
 ///
 /// # Arguments
@@ -89,7 +90,7 @@ Required for all public functions using `///`:
 pub fn rows_to_strings(rows: Vec<mysql::Row>) -> anyhow::Result<Vec<Vec<String>>> {
     // Implementation
 }
-```
+````
 
 ## Code Style
 
@@ -108,6 +109,7 @@ pub fn rows_to_strings(rows: Vec<mysql::Row>) -> anyhow::Result<Vec<Vec<String>>
 
 - Pin dependency versions in [`Cargo.toml`](mdc:Cargo.toml) and use minimal required features for each crate
 - Use optional dependencies and features for extensibility (e.g., additional MySQL types, output formats)
+- Use context7 website or MCP tool to get current documentation for APIs and crates
 
 ## Testing Guidelines
 

.github/copilot-instructions.md

@@ -224,6 +224,7 @@ cargo test
 - [ ] Use conventional commit format
 - [ ] Suggest small, focused diffs for single-maintainer workflow
 - [ ] Use `gh` CLI for GitHub interactions
+- [ ] Use context7 website or MCP tool to get current documentation for APIs and crates
 - [ ] Link to WARP.md/AGENTS.md for comprehensive context
 
 ## References

.kiro/specs/integration-testing-enhancement/tasks.md

@@ -84,7 +84,7 @@
   - Add support for generating certificates using LibreSSL on macOS and Linux
   - _Requirements: 1.1, 1.2, 1.3, 1.5, 9.3_
 
-- [x] 1.3 Create TLS certificate management and test database schema system
+- [ ] 1.3 Create TLS certificate management and test database schema system
 
   - ✓ Basic TLS certificate handling exists in `tests/tls_integration.rs` (need to move to fixtures)
   - Create `tests/fixtures/tls/` directory with test SSL certificates for TLS-enabled containers
@@ -96,15 +96,15 @@
   - Add database-specific compatibility handling for MySQL vs MariaDB differences
   - _Requirements: 1.2, 3.1, 3.2, 3.3, 3.4, 3.5, 3.6, 3.7, 9.3_
 
-- [ ] 1.3.1 Set up TLS certificate fixtures and management
+- [x] 1.3.1 Set up TLS certificate fixtures and management
 
   - Create `tests/fixtures/tls/` directory structure
   - Move existing TLS certificate constants from `tests/tls_integration.rs` to fixture files
   - Generate self-signed CA certificate and server certificates for testing
   - Create certificate loading utilities for container configuration
   - Add certificate validation helpers for TLS connection tests
 
-- [ ] 1.3.1.1 Replace certificate generation logic with rcgen crate
+- [x] 1.3.1.1 Replace certificate generation logic with rcgen crate
 
   - Add `rcgen` crate to dev-dependencies in `Cargo.toml` for X.509 certificate generation
   - Replace existing hardcoded certificate constants with `rcgen::generate_simple_self_signed()`
@@ -116,6 +116,16 @@
   - Ensure generated certificates are compatible with MySQL/MariaDB TLS requirements
   - _Requirements: 1.2, 1.3, 9.3_
 
+- [ ] 1.3.1.2 Replace libc disk space check with sysinfo crate
+
+  - Replace unsafe `libc::statvfs()` calls in `tests/integration/containers.rs::check_disk_space()`
+    with `sysinfo` crate
+  - Remove platform-specific conditionals and manual `df` command parsing fallback
+  - Add `sysinfo = "0.36"` to `[dev-dependencies]` and remove `libc = "0.2"`
+  - Use `sysinfo::System::new_all()` with `refresh_disks()` for cross-platform disk space checking
+  - Look for `/tmp` mount point first, fallback to first available disk
+  - _Requirements: 1.2, 1.3, 9.3_
+
 - [ ] 1.3.2 Create comprehensive test database schema
 
   - Write `tests/fixtures/schema.sql` with all MySQL/MariaDB data types

.kiro/steering/project/core-concepts.md

@@ -126,6 +126,7 @@ just security     # cargo audit (advisory)
 - **Clippy warnings**: Zero tolerance (`-D warnings`)
 - **Error handling**: Use `anyhow` for applications, `thiserror` for libraries
 - **Documentation**: Doc comments (`///`) required for all public functions
+- Use context7 website or MCP tool to get current documentation for APIs and crates
 
 ### Testing Requirements
 

.mdformat.toml

@@ -9,6 +9,8 @@ exclude = [
     "docs/src/SUMMARY.md",
     "docs/src/usage/output-formats.md",
     "rust_migration/index.md",
+    "target/**",
+    "megalinter-reports/**",
 ]
 validate = true
 number = true

.prettierignore

@@ -68,3 +68,4 @@ COPYING*
 # Autogenerated files
 .github/workflows/release.yml
 **/*.wxs
+**/*.mdc

AGENTS.md

@@ -1,20 +1,67 @@
 # AGENTS.md
 
-This file provides guidance for AI assistants working with the Gold Digger codebase.
+This file provides guidance for AI coding assistants working with the Gold Digger Rust codebase.
+
+## Rules of Engagement for AI Assistants
+
+### File Priority Order
+
+Always consult these files in order when working with this codebase:
+
+1. **AGENTS.md** (this file) - Primary AI assistant guidance
+2. **GEMINI.md** - Gemini-specific overrides (if present)
+3. **.cursor/rules/**/\*.mdc\*\* - Cursor-specific rules (if present)
+
+### Critical Restrictions
+
+- **NEVER** commit code, switch branches, or alter git settings without explicit maintainer
+  permission
+- **NEVER** log raw `DATABASE_URL`, connection strings, or credentials
+- **NEVER** use direct MySQL row indexing: `row[index]` or `mysql::from_value::<String>()`
+- **ALWAYS** ask clarifying questions before making risky changes
+- **ALWAYS** run `just check` and validate changes before proposing them
+
+### Change Proposals
+
+- Present changes as unified diffs, not direct file modifications
+- Include test updates when adding features
+- Run `just ci-full` locally when feasible to validate changes
+- Use context7 website or MCP tool to get current documentation for APIs and crates
+
+### Review Process
+
+- This project prefers **CodeRabbit.ai** for code review
+- Do **NOT** enable GitHub Copilot auto-review in pull requests
+- Maintainer: **UncleSp1d3r** (single-maintainer workflow)
 
 ## Project Overview
 
-Gold Digger is a Rust-based MySQL/MariaDB query tool that outputs results in CSV, JSON, or TSV
-formats. It's designed for headless operation via environment variables, making it ideal for
-database automation workflows.
+Gold Digger is a production-ready Rust CLI tool for MySQL/MariaDB database queries with structured
+output (CSV, JSON, TSV). It features comprehensive CLI interface, rustls-only TLS, and safe data
+type handling.
+
+**Current Architecture (v0.2.6):**
+
+- CLI-first with environment variable fallbacks using `clap`
+- Rustls-only TLS implementation (no OpenSSL dependencies)
+- Safe MySQL value conversion with NULL handling
+- Structured exit codes and error handling
+- Modular output format system
+
+**Command Examples:**
 
-**Key Characteristics:**
+```bash
+# CLI interface (preferred)
+gold_digger --db-url "mysql://user:pass@host:3306/db" \
+            --query "SELECT id, name FROM users" \
+            --output results.json --pretty
 
-- CLI-first (uses Clap) with environment variable overrides
-- Outputs to structured formats based on file extension
-- Fully materialized result sets (no streaming)
-- Single-maintainer project by UncleSp1d3r
-- Under active development toward v1.0
+# Environment variables (legacy support)
+DATABASE_URL="mysql://user:pass@host:3306/db" \
+DATABASE_QUERY="SELECT * FROM table" \
+OUTPUT_FILE="/tmp/data.csv" \
+cargo run --release
+```
 
 ## 🚨 Critical Safety Rules
 

Cargo.lock

@@ -48,6 +48,7 @@ url = "2.5.7"
 rustls = { version = "0.23.31", features = ["ring"] }
 rustls-native-certs = "0.8.1"
 rustls-pemfile = "2.2.0"
+regex = "1.11.1"
 
 
 [dev-dependencies]
@@ -56,10 +57,10 @@ tempfile = "3.21.0"
 assert_cmd = "2.0.17"
 insta = "1.43.1"
 temp-env = "0.3.6"
-regex = "1.11.1"
+regex = "1.11.2"
 rustls = { version = "0.23.31", features = ["ring"] }
 serde_json = "1.0.143"
-rcgen = "0.13.1"
+rcgen = "0.14.3"
 time = { version = "0.3", features = ["macros"] }
 
 [target.'cfg(unix)'.dev-dependencies]

Cargo.toml

@@ -162,10 +162,12 @@ println!("Connecting to database...");
 
 ```toml
 default = ["json", "csv", "additional_mysql_types", "verbose"]
-json = []                                  # JSON output format
-csv = []                                   # CSV output format
-additional_mysql_types = [...]             # BigDecimal, Decimal, etc.
-verbose = []                               # Conditional logging
+json = [] # JSON output format
+csv = [] # CSV output format
+additional_mysql_types = [
+  "mysql_common?/bigdecimal",
+] # BigDecimal, Decimal, etc.
+verbose = [] # Conditional logging
 ```
 
 **TLS Implementation Notes:**
@@ -224,6 +226,7 @@ cargo run --release
 3. **Target small, reviewable changes** for single-maintainer workflow
 4. **Consider streaming implications** for future compatibility
 5. **Maintain offline-first principles** - no external service calls
+6. **Use context7 website or MCP tool** to get current documentation for APIs and crates
 
 ### Testing Recommendations