git-with-intent v0.9 to v0.10: Docker Upgrades, README Rewrites, and Strategic Research

Two Releases in a Week git-with-intent shipped v0.9.0 on February 17 and v0.10.0 on February 19. Two days apart. The first release was a pre-GA security hardening pass. The second was a scale and operations maturity push. Together they closed the gap between "runs on my machine" and "can handle real tenants." v0.9.0: Pre-GA Security Hardening The v0.9.0 release focused on making the platform secure enough to run multi-tenant workloads. GitHub Actions pinned to SHA digests across 17 workflow files. Every third-party action now references a specific commit hash instead of a version tag. Standard supply chain hygiene — a compromised action tag could inject malicious code into CI. Sandbox autopilot integration wired the sandbox into the file-write critical path. When an agent generates code, it executes in an isolated sandbox before any file system writes happen. The sandbox enforces deny-by-default network access, destructive operation checks, and per-agent permission profiles. onBeforeSt