lfx-mcp: Skill for Claude Code

Upgrade Maintenance

Perform a full upgrade maintenance pass on the lfx-mcp codebase. This covers three sequential phases: dependency upgrades, upstream contract fixes, and a query service argument review.

Phase 1 — Upgrade all dependencies

Step 1.1 — Upgrade the Go toolchain version

Compare the local toolchain version against the go directive in go.mod and update if the local toolchain is newer:

# Extract the version from the local toolchain (e.g. "go1.24.3").
LOCAL=$(go version | awk '{print $3}')        # e.g. go1.24.3
GOMOD=$(grep '^go ' go.mod | awk '{print $2}') # e.g. 1.23.0

echo "Local toolchain: $LOCAL"
echo "go.mod go directive: $GOMOD"

If the local toolchain is newer, update go.mod:

# Updates the go directive to match the local toolchain.
go mod tidy -go=${LOCAL#go}

Also update any other files that pin the Go version:

• Dockerfile — FROM golang:X.Y.Z or FROM golang:X.Y-alpine base image.
• .github/workflows/*.yml — go-version: fields in GitHub Actions steps.
• Makefile — any hardcoded GO_VERSION variable.
• AGENTS.md / README.md — version references in prerequisite tables.

After updating, verify the build still compiles with the new toolchain:

make build

If any deprecated language features or removed stdlib symbols cause errors, fix them before continuing.

Step 1.2 — Upgrade Go module dependencies

# Upgrade all direct dependencies to their latest minor/patch versions.
go get -u ./...

# Tidy the module graph (removes unused indirect deps, syncs go.sum).
go mod tidy

After running, inspect go.mod for version changes. The most impactful upgrades to watch are the github.com/linuxfoundation/lfx-v2-* packages — they regularly add, rename, or remove Goa-generated struct fields, which directly affects tool handler code in internal/tools/ and client wiring in internal/lfxv2/client.go. Phase 2 is the step that reviews these changes; if any lfx-v2-* bump lands without a same-session Phase 2 pass (e.g. it was folded into a larger commit, or maintenance was interrupted), re-run Phase 2 retroactively against that commit — see "Finding OLD and NEW" in Step 2.1.