feat: set up CI, linting, and documentation automation

.github/dependabot.yml

@@ -6,11 +6,15 @@
 
 version: 2
 updates:
-  - package-ecosystem: "devcontainers"
+  - package-ecosystem: "cargo"
     directory: "/"
     schedule:
       interval: "weekly"
-  - package-ecosystem: "cargo"
+  - package-ecosystem: "github-actions"
     directory: "/"
     schedule:
-      interval: "weekly"
+      interval: "daily"
+  - package-ecosystem: "rust-toolchain"
+    directory: "/"
+    schedule:
+      interval: "daily"

.kiro/hooks/ci-auto-fix.kiro.hook

@@ -8,15 +8,12 @@
     "patterns": [
       "src/**/*.rs",
       "Cargo.toml",
-      "Cargo.lock",
       "tests/**/*.rs",
-      "*.md",
-      "rustfmt.toml",
-      ".gitignore"
+      "rustfmt.toml"
     ]
   },
   "then": {
     "type": "askAgent",
-    "prompt": "Source files have been modified. Please run a comprehensive CI check and fix any issues found. This should include:\n\n1. **Code Formatting**: Run `cargo fmt` to fix any formatting issues\n2. **Linting**: Run `cargo clippy --all-targets --all-features -- -D warnings` and fix any clippy warnings\n3. **Compilation**: Ensure `cargo build` and `cargo build --release` both succeed\n4. **Testing**: Run `cargo test` and `cargo nextest run` (if available) and fix any test failures\n5. **Security Audit**: Run `cargo audit` and address any security vulnerabilities\n6. **License Compliance**: Check that all dependencies have compatible licenses\n7. **Documentation**: Ensure `cargo doc` builds without warnings\n8. **Coverage**: Run coverage checks if llvm-cov is available\n\nFor each issue found:\n- Identify the root cause\n- Apply the appropriate fix\n- Verify the fix resolves the issue\n- Ensure no new issues are introduced\n\nIf any issues cannot be automatically fixed, provide clear guidance on manual resolution steps needed."
+    "prompt": "Source files have been modified. Please run a comprehensive CI check and fix any issues found. This should include:\n\n1. **Code Formatting**: Run `just format` to fix any formatting issues\n2. **Linting**: Run `just lint` and fix any clippy warnings\n3. **Compilation**: Ensure `just build` and `just build-release` both succeed\n4. **Testing**: Run `just test` and `cargo nextest run` (if available) and fix any test failures\n5. **Security Audit**: Run `just audit` and address any security vulnerabilities\n6. **License Compliance**: Check that all dependencies have compatible licenses by running `just deny`\n7. **Documentation**: Ensure `just docs-build` builds without warnings (skip on Windows)\n8. **Coverage**: Run coverage checks with `just coverage-check` to ensure we are meeting our coverage thresholds\n\nFor each issue found:\n- Identify the root cause\n- Apply the appropriate fix\n- Verify the fix resolves the issue\n- Ensure no new issues are introduced\n\nIf any issues cannot be automatically fixed, provide clear guidance on manual resolution steps needed."
   }
 }