Merge origin/main with vision feature integration

- Resolved all merge conflicts
- Added vision feature with optional dependencies
- Regenerated Cargo.lock cleanly
- Ready for cloud cross-platform testing

Author: Michael-A-Kuykendall

.gitignore

@@ -1,7 +1,5 @@
 # Rust build artifacts
 **/target/
-target*/
-target-*
 /alt_target/
 /target-minimal/
 **/*.rs.bk
@@ -37,97 +35,22 @@ Thumbs.db
 
 # Internal development documents (NEVER commit)
 docs-internal/
-.internal/
-
-# Cloudflare Worker local state / secrets
-cloudflare-worker/.wrangler/
-.dev.vars
-cloudflare-worker/.dev.vars
 
-# Internal licensing notes (contains secrets)
-memory/VISION_STRIPE_KEYGEN_ARCHITECTURE.md
+# Internal workspace docs (NEVER commit)
+.internal/
 
 # Copilot instructions (internal only)
 .github/copilot-instructions.md
 
 # Local configuration
 .env
 .env.local
+.env.test
 
 # Test artifacts
 *.log
 *.db
 *.db-*
-test-screenshots/
-test_image.b64
-
-# Build outputs
-out/
-output.md
-
-# Internal development
-docs/internal/
-memory/
-secret-scan/
-
-# Vision libraries (build artifacts)
-libs/vision/
-
-# Third-party repos
-llama-cpp-minicpm/
-
-# AI instructions
-.github/instructions/
-
-# Screenshots and diagnostics
-00-diagnostic-startup.png
-*-diagnostic-*.png
-
-# Workspace files
-*.code-workspace
-
-# Python cache
-__pycache__/
-*.pyc
-
-# Chat logs and session recovery
-scripts/chat.md
-scripts/chat2.md
-
-# Internal docs
-docs/GATEWARDEN_ARCHITECTURE_PROMPT.md
-
-# Test screenshots (large binary files)
-test-screenshots/
-
-# Local vendor/build dirs (not part of shimmy repo)
-llama-cpp-minicpm/
-target-gpu/
-target-gpu-*/
-
-# Vision development output and testing artifacts
-out/
-assets/vision-samples/preprocessed-*/
-nul
-
-# Python cache
-__pycache__/
-*.pyc
-
-# Development-only binaries (not for distribution)
-src/bin/vision_preprocess_dump.rs
-scripts/vision_samples_run.sh
-
-# Windows/Git artifacts
-%s
-
-# Local logs and scratch files
-output.md
-test_image.b64
-*.b64
-00-diagnostic-startup.png
-docs/shimmy-workspace.code-workspace
-docs/internal/SHIMMY_VISION_PRICING_STRATEGY.md
 
 # Package manager artifacts
 node_modules/

CHANGELOG.md

@@ -7,18 +7,6 @@ and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0
 
 ## [Unreleased]
 
-### 🔒 **SECURITY** - Critical Security Update
-
-**🚨 STRIPE LIVE KEY EXPOSURE MITIGATED**
-- **REMOVED**: Compromised internal chat logs containing live Stripe secret key from git history
-- **ROTATED**: All Stripe API keys (test and live) have been cycled
-- **YANKED**: crates.io version 1.8.2 yanked due to potential key exposure
-- **SCANNED**: Repository scanned for additional secrets, TruffleHog security scanning implemented
-- **VERIFIED**: No sensitive data remains in public repository
-
-### 📦 **VERSION BUMP**
-- Bumped to v1.8.3 to replace compromised v1.8.2
-
 ## [1.8.1] - 2025-12-08
 
 ### 🐳 **DOCKER PUBLISHING INFRASTRUCTURE** - Container Registry Publishing Fixed

CONTRIBUTING.md

@@ -1,85 +1,121 @@
 # Contributing to Shimmy
 
-Thank you for your interest in Shimmy! ���
+Thanks for your interest in contributing to Shimmy!
 
-## Open Source, Not Open Contribution
+## 🚨 IMPORTANT: Maintainer-Only Pull Requests
 
-Shimmy is **open source** but **not open contribution**.
+**Pull requests are restricted to approved maintainers only.** Unsolicited PRs will be declined. To contribute code, you must first apply for maintainer status by emailing michaelallenkuykendall@gmail.com.
 
-- The code is freely available under the MIT license
-- You can fork, modify, use, and learn from it without restriction
-- **Pull requests are not accepted by default**
-- All architectural, roadmap, and merge decisions are made by the project maintainer
-
-This model keeps the project coherent, maintains clear ownership, and ensures consistent quality. It's the same approach used by SQLite and many infrastructure projects.
+**Non-maintainers can contribute by:**
+- Opening issues for bugs or feature requests
+- Participating in GitHub Discussions
+- Providing feedback and testing
 
 ## How to Contribute
-
-If you believe you can contribute meaningfully to Shimmy:
-
-1. **Email the maintainer first**: [michaelallenkuykendall@gmail.com](mailto:michaelallenkuykendall@gmail.com)
-2. Describe your background and proposed contribution
-3. If there is alignment, a scoped collaboration may be discussed privately
-4. Only after discussion will PRs be considered
-
-**Unsolicited PRs will be closed without merge.** This isn't personal — it's how this project operates.
-
-## What We Welcome (via email first)
-
-- Bug reports with detailed reproduction steps (Issues are fine)
-- Security vulnerability reports (please email directly)
-- Documentation improvements (discuss first)
-- Platform-specific bug fixes (discuss first)
-
-## What We Handle Internally
-
-- New features and architectural changes
-- API design decisions
-- Dependency updates
-- Performance optimizations
-- Cross-platform compatibility work
-
-## Bug Reports
-
-Bug reports via GitHub Issues are welcome! Please include:
-- Platform (Windows/macOS/Linux) and version
-- Rust version and Shimmy version
-- Minimal reproduction case
-- Expected vs actual behavior
-- Backend details if relevant (llama.cpp version, model info)
-
-## Code Style (for reference)
-
-If a contribution is discussed and approved:
-- Rust 2021 edition with `cargo fmt` and `cargo clippy -- -D warnings`
-- Comprehensive error handling using proper Result types
-- All public APIs must have documentation with examples
-- Tests for new functionality
-
-## Shimmy Philosophy
-
-Any accepted work must align with:
+1. Fork the repo and create a branch (`git checkout -b feature/foo`)
+2. Make your changes with clear commits and tests if applicable
+3. **Sign off your commits** (required): `git commit -s -m "Your message"`
+4. Run existing tests to ensure nothing breaks (`cargo test`)
+5. Ensure code quality (`cargo fmt && cargo clippy`)
+6. Open a Pull Request against `main`
+
+### Developer Certificate of Origin (DCO)
+All contributions must be signed off with the Developer Certificate of Origin. This certifies that you have the right to contribute your code. See [DCO.md](DCO.md) for details.
+
+**Quick setup:**
+```bash
+git config format.signoff true  # Auto sign-off all commits
+```
+
+## Code Style
+- Rust 2021 edition
+- Use `cargo fmt` and `cargo clippy` before submitting
+- Keep PRs small and focused - large refactors may be rejected
+- Add tests for new functionality
+- Document public APIs with rustdoc comments
+
+## Contribution Scope
+Features should align with the **Shimmy philosophy**:
 - **Lightweight**: ~5MB binary target
 - **Zero-config**: No setup, just works
 - **OpenAI API compatibility**: Drop-in replacement
 - **Invisible infrastructure**: Minimal surface area
-- **Free forever**: Core features remain free, premium features licensed separately
 
-## Why This Model?
-
-Building reliable LLM infrastructure requires tight architectural control. This ensures:
-- Consistent API design and backwards compatibility
-- No ownership disputes or governance overhead
-- Quality control without committee delays
-- Clear direction for the project's future
-
-The code is open. The governance is centralized. This is intentional.
+## What We Welcome
+- Bug fixes with test cases
+- Performance improvements
+- API compatibility enhancements
+- Documentation improvements
+- Platform-specific fixes
+- Test coverage improvements
+
+## What We Generally Reject
+- Features that bloat binary size significantly
+- Complex configuration systems
+- UI/dashboard components (use external tools)
+- Breaking changes to established APIs
+- Features not aligned with OpenAI compatibility
+
+## Review Process
+
+**IMPORTANT: Pull Request Access is Restricted**
+- Only approved maintainers may submit pull requests
+- All contributions from non-maintainers will be declined
+- Code contributions require pre-approval via maintainer application process
+
+**For Approved Maintainers:**
+- All PRs require review and approval from the lead maintainer
+- Merge authority is reserved to maintain project direction
+- We aim to review PRs within 1-2 business days
+- Constructive feedback will be provided for rejected PRs
+
+## Development Setup
+```bash
+# Clone and setup
+git clone https://github.com/Michael-A-Kuykendall/shimmy
+cd shimmy
+cargo build
+
+# Run tests
+cargo test
+
+# Check formatting and linting
+cargo fmt --check
+cargo clippy -- -D warnings
+```
+
+## Maintainer Process
+
+### Current Maintainer Structure
+- **Lead Maintainer**: Michael A. Kuykendall (@Michael-A-Kuykendall)
+- **Additional Maintainers**: Currently none (solo-maintained project)
+
+### Becoming a Maintainer
+Currently, Shimmy is maintained by a single maintainer to ensure consistent vision and rapid iteration. **Code contributions require pre-approved maintainer status.**
+
+**To apply for maintainer status:**
+
+1. **Private Application**: Email michaelallenkuykendall@gmail.com with:
+   - Your GitHub username and relevant experience
+   - Area of expertise (e.g., performance, platform support, API design)
+   - Time commitment you can provide
+   - Why you'd like to help maintain Shimmy
+
+2. **Evaluation Process**: Applications are reviewed when additional maintainers are needed
+3. **No Unsolicited PRs**: Code contributions without prior approval will be declined
+
+### Maintainer Responsibilities
+When additional maintainers are added, they will:
+- Review and approve pull requests
+- Triage and respond to issues
+- Maintain code quality standards
+- Participate in release planning
+- Uphold the Shimmy philosophy and project direction
+
+*Note: The project may remain solo-maintained until contribution volume requires additional help.*
 
 ## Recognition
+Contributors are acknowledged in `AUTHORS.md` after a merged PR.
 
-Helpful bug reports and community members are acknowledged in release notes.
-If email collaboration leads to merged work, attribution will be given appropriately.
-
----
-
-**Maintainer**: Michael A. Kuykendall
+## Questions?
+Open a GitHub Discussion or ping @Michael-A-Kuykendall in your PR.