chore: update from skeleton

.agents/references/shared/terraform-module-standards.md

@@ -37,6 +37,8 @@ These standards apply to both primitive and reference architecture modules.
 
 - Prefer `mise run <task>` when a suitable task exists.
 - Otherwise use `mise exec -- <command>` for Terraform, Go, pre-commit, and related tools.
+- When creating a module with Terratest, set the Go version in `.tool-versions` and the `go` directive in `go.mod` to the latest stable version supported by Terratest and the repository tooling. Confirm the installed version with `mise exec -- go version`.
+- From the module root, refresh the complete Go dependency graph with `mise exec -- go get -u ./...`, then run `mise exec -- go mod tidy`. Verify `mise exec -- go list -m -u all` reports no remaining available module upgrades; resolve incompatibilities in the Terratest code rather than retaining stale dependencies.
 - Run formatting and linting before broader test flows.
 - For examples, validate initialization, Terraform validation, and plan where credentials and backend constraints allow.
 - For Go tests, run `go mod tidy`, build or targeted tests, and broader Terratest only when the required cloud access is available.

.agents/skills/primitive-module/SKILL.md

@@ -24,8 +24,9 @@ Use this skill for repositories named `tf-<provider>-module_primitive-<resource>
 4. Implement one primitive resource interface with explicit variable types, descriptions, validations, resource outputs, and provider constraints.
 5. Build `examples/complete/` as the canonical secure usage example.
 6. Keep `README.md` derived from `TEMPLATED_README.md`; replace the module-specific sections and preserve skeleton development boilerplate.
-7. Add or update Terratest code so assertions verify specific expected values and security settings through provider APIs when applicable.
-8. Run focused validation, then broader checks such as formatting, linting, Terraform init/validate/plan for the example, README generation, and Go test build or Terratest where practical.
+7. Set the latest supported Go baseline and refresh the complete Go dependency graph as required by the shared Terraform module standards.
+8. Add or update Terratest code so assertions verify specific expected values and security settings through provider APIs when applicable.
+9. Run focused validation, then broader checks such as formatting, linting, Terraform init/validate/plan for the example, README generation, and Go test build or Terratest where practical.
 
 ## Completion Gate
 

.agents/skills/reference-architecture/SKILL.md

@@ -24,8 +24,9 @@ Use this skill for repositories named `tf-<provider>-module_reference-<architect
 5. Use the resource naming module for all generated names. Do not ask consumers to provide names that the architecture should own.
 6. Model optional features with explicit `create_*` flags and coherent object validation.
 7. Build `examples/complete/` as the canonical secure architecture example, including required source assets such as Lambda source directories where applicable.
-8. Add or update Terratest coverage that validates the composed resources through provider APIs, differentiates destructive and readonly flows, and checks optional features enabled by the example.
-9. Run focused validation, then broader checks such as formatting, linting, Terraform init/validate/plan for the example, README generation, and Go test build or Terratest where practical.
+8. Set the latest supported Go baseline and refresh the complete Go dependency graph as required by the shared Terraform module standards.
+9. Add or update Terratest coverage that validates the composed resources through provider APIs, differentiates destructive and readonly flows, and checks optional features enabled by the example.
+10. Run focused validation, then broader checks such as formatting, linting, Terraform init/validate/plan for the example, README generation, and Go test build or Terratest where practical.
 
 ## Completion Gate
 

.copier-answers.yml

@@ -1,5 +1,5 @@
 # NEVER EDIT MANUALLY
 # https://copier.readthedocs.io/en/stable/updating/#never-change-the-answers-file-manually
 
-_commit: 0.7.1
+_commit: 0.7.2
 _src_path: gh:launchbynttdata/launch-terraform-skeleton

AGENTS.md

@@ -32,5 +32,6 @@ This repository follows the Launch Terraform module standards. Keep this file sm
 ## Validation Expectations
 
 - Run the narrowest useful validation first, then broaden when the change affects shared behavior.
+- When creating a module with Terratest, update the Go baseline and dependency graph before considering the implementation complete; follow the shared Terraform module standards for the required commands and verification.
 - Before considering module creation complete, validate formatting, linting, Terraform initialization/validation for examples, README generation, and Terratest readiness where practical.
 - If full cloud-backed tests cannot be run, state what was validated and what remains unproven.