chore: update CI workflows to Go 1.26 and codify AI agent branch rules

Signed-off-by: James Nesbitt <jnesbitt@mirantis.com>

Author: james-nesbitt

.github/workflows/build.yml

@@ -21,7 +21,8 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v5
         with:
-          go-version: "1.25"
+          go-version: "1.26"
+          cache: true
 
       - name: Build binaries
         run: |
@@ -55,7 +56,8 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v5
         with:
-          go-version: "1.22"
+          go-version: "1.26"
+          cache: true
 
       - name: Run unit tests
         run: go test -v ./...

.github/workflows/pr.yml

@@ -32,7 +32,8 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v5
         with:
-          go-version: "1.25"
+          go-version: "1.26"
+          cache: true
 
       - name: Run golangci-lint
         run: make lint
@@ -47,7 +48,8 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v5
         with:
-          go-version: "1.25"
+          go-version: "1.26"
+          cache: true
 
       - name: Run unit tests
         run: make unit-test
@@ -62,7 +64,8 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v5
         with:
-          go-version: "1.25"
+          go-version: "1.26"
+          cache: true
 
       - name: Run integration tests
         run: make integration-test
@@ -79,7 +82,8 @@ jobs:
       - name: Set up Go
         uses: actions/setup-go@v5
         with:
-          go-version: "1.25"
+          go-version: "1.26"
+          cache: true
 
       - name: Install govulncheck
         run: go install golang.org/x/vuln/cmd/govulncheck@latest

AI_AGENTS.md

@@ -9,6 +9,7 @@ This document defines guidelines for AI agents working on the Launchpad project.
 1. **Generalization**: Support all AI agents, not just specific providers.
 2. **Consistency**: Follow Launchpad’s architectural patterns and conventions.
 3. **Clarity**: Document decisions and reasoning for human reviewers.
+4. **Branching**: NEVER work on, push to, or merge to the `main` branch. All work MUST be done on feature branches.
 
 ---
 
@@ -29,13 +30,18 @@ Documentation is organized to minimize context overhead for agents:
 - Read `docs/guidance/project.md` to understand core architectural principles.
 - For feature requests, review the relevant PRD in `docs/requirements/`.
 - For bug fixes, review the relevant specification in `docs/specifications/`.
+- **Environment**: Ensure `GOTOOLCHAIN=auto` is used for all `go` commands to support the required toolchain.
 
 ### 2. Strategy Phase
+- **ALWAYS** create a new feature branch from `main`.
 - Propose changes that align with the **Phase Manager** architecture (`docs/specifications/architecture.md`).
 - Ensure changes are backwards compatible or include migrations (`docs/specifications/architecture.md`).
 - Document trade-offs and decisions in the PR description.
 
 ### 3. Execution Phase
+- **NEVER** push directly to `main`.
+- **NEVER** merge into `main`.
+- All work MUST be pushed to a remote feature branch for human review.
 - All commits MUST be signed.
 - Follow the testing strategy outlined in `docs/development/workflow.md`.
 - Use `make local` for rapid iteration and validation.