fix: update Go version from 1.26.1 to 1.26.2 in Dockerfile and documentation for security improvements

docs/development/go_version_upgrades.md

@@ -251,13 +251,13 @@ Go releases **two major versions per year**:
 - February (e.g., Go 1.26.0)
 - August (e.g., Go 1.27.0)
 
-Plus occasional patch releases (e.g., Go 1.26.1) for security fixes.
+Plus occasional patch releases (e.g., Go 1.26.2) for security fixes.
 
 **Bottom line:** Expect to run `./scripts/rebuild-go-tools.sh` 2-3 times per year.
 
 ### Do I need to rebuild tools for patch releases?
 
-**Usually no**, but it doesn't hurt. Patch releases (like 1.26.0 → 1.26.1) rarely break tool compatibility.
+**Usually no**, but it doesn't hurt. Patch releases (like 1.26.0 → 1.26.2) rarely break tool compatibility.
 
 **Rebuild if:**
 

docs/plans/current_spec.md

@@ -252,7 +252,7 @@ No UI/UX changes — this is a dependency-only update. Existing E2E tests valida
 
 | Task | File(s) | Action |
 |------|---------|--------|
-| 4.1 | `.github/skills/examples/gorm-scanner-ci-workflow.yml` | Bump Go version 1.26.1 → 1.26.2 |
+| 4.1 | `.github/skills/examples/gorm-scanner-ci-workflow.yml` | Bump Go version 1.26.2 → 1.26.2 |
 
 ### Phase 5: Validation
 
@@ -339,7 +339,7 @@ The `pgproto3/v2` module has **no patched release** — the fix exists only in `
 | `backend/go.mod` | Dependency version bumps (grpc, otlptracehttp) |
 | `backend/go.sum` | Auto-generated checksum updates |
 | `Dockerfile` | Add `go get` patches in caddy-builder and crowdsec-builder stages |
-| `.github/skills/examples/gorm-scanner-ci-workflow.yml` | Go version 1.26.1 → 1.26.2 |
+| `.github/skills/examples/gorm-scanner-ci-workflow.yml` | Go version 1.26.2 → 1.26.2 |
 
 **Dependencies**: None (standalone)