ci(mint): add setup-go and setup-node to mint-cf-worker-test workflow

[guyoron1]

Summary

.github/workflows/mint-cf-worker-test.yml (from fullsend-ai#5481) runs make mint-cf-worker-test, which needs a Go toolchain (wasm-stage / GOOS=js GOARCH=wasm) and Node/npm (workersrc install + vitest). The workflow currently relies on:

• Go: GOTOOLCHAIN=auto downloading via the repo go.mod
• Node: whatever is preinstalled on ubuntu-24.04

That works today (green on fullsend-ai#5427), but the job lacks explicit actions/setup-go and actions/setup-node (and caching), unlike other CI jobs in this repo.

Why it matters

• Consistency with the rest of CI (pinned action SHAs, version from go.mod, npm cache)
• Faster / more reproducible runs as the Worker smoke suite grows
• Clearer failure modes when runners change their default tool images

Observed on

• PR feat(#5344): add CF Worker adapter and Wrangler config for mint fullsend-ai/fullsend#5427 (feat(#5344): add CF Worker adapter…) — agent review flagged this as medium; deferred because code agents cannot edit workflows and the job was already green.

Related

• ci: add mint-cf-worker-test workflow + stub Make target fullsend-ai/fullsend#5481 — added the workflow + stub Make target
• feat(#5344): add CF Worker adapter and Wrangler config for mint fullsend-ai/fullsend#5427 — populated make mint-cf-worker-test and the workersrc smoke tests

Acceptance

• mint-cf-worker-test.yml uses actions/setup-go (prefer go-version-file: go.mod) and actions/setup-node with an appropriate Node version / npm cache before make mint-cf-worker-test
• Job remains path-filtered and keeps calling the Make target by the existing contract name mint-cf-worker-test

[guyoron1]

/fs-triage

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 8:47 AM UTC · Completed 8:50 AM UTC
Commit: c887fc4 · View workflow run →

[fullsend-ai-triage]

Triage Summary

This issue requests adding actions/setup-go and actions/setup-node to the mint-cf-worker-test.yml workflow for consistency with other CI jobs in the repo.

Problem: The workflow relies on runner-preinstalled Go and Node toolchains instead of explicit setup actions with pinned SHAs, version management via go.mod, and npm caching — diverging from the repo's CI workflow conventions.

Recommended fix: Add actions/setup-go (with go-version-file: go.mod) and actions/setup-node (with npm cache) before the make mint-cf-worker-test step. Pin both to full commit SHAs per repo conventions. Preserve existing path filters, merge_group trigger, and the Make target contract name.

Proposed test verification:

1. Workflow passes on PRs touching workersrc/ or the workflow file
2. Go version matches go.mod (not runner default)
3. npm install benefits from caching on repeated runs
4. Job remains path-filtered and calls make mint-cf-worker-test
5. merge_group trigger with path-relevance guard is present

⚠ Workflow file change required. This fix involves modifying .github/workflows/mint-cf-worker-test.yml. The code agent cannot modify workflow files under current permissions — a human PR or maintainer action is needed.

---

Next steps:

• /fs-code — agent creates a PR to implement this issue
• /fs-code <your instruction> — agent implements with your specific guidance

Previous run

Triage Summary

This issue requests adding actions/setup-go and actions/setup-node to the mint-cf-worker-test.yml workflow for consistency with other CI jobs. The issue is well-defined with clear acceptance criteria.

Problem: The workflow currently relies on runner-preinstalled Go and Node toolchains instead of using explicit setup actions with pinned SHAs, version management (go.mod), and npm caching — diverging from repo CI conventions.

Recommended fix: Add actions/setup-go (with go-version-file: go.mod) and actions/setup-node (with npm cache) before the make mint-cf-worker-test step. Pin both to full SHAs per CI workflow conventions. Preserve existing path filters and the Make target contract name.

Proposed test verification:

1. Workflow still passes on PRs touching workersrc/ or the workflow file
2. Go version matches go.mod (not runner default)
3. npm install benefits from caching on repeated runs
4. Job remains path-filtered and calls make mint-cf-worker-test

⚠ Workflow file change required. This fix involves modifying .github/workflows/mint-cf-worker-test.yml. The code agent cannot modify workflow files under current permissions — a human PR or maintainer action is needed.

---

Next steps:

• /fs-code — agent creates a PR to implement this issue
• /fs-code <your instruction> — agent implements with your specific guidance

[fullsend-ai-triage]

🤖 Finished Triage · ✅ Success · Started 8:55 AM UTC · Completed 8:57 AM UTC
Commit: c887fc4 · View workflow run →

[guyoron1]

/fs-code

[fullsend-ai-coder]

🤖 Finished Code · ❌ Failure · Started 9:36 AM UTC · Completed 9:42 AM UTC
Commit: c887fc4 · View workflow run →

[fullsend-ai-coder]

⚠️ Post-code script failed — Pre-commit blocked (exit code 1)

The code agent completed, but the post-code script failed before finishing.

Workflow run: https://github.com/guyoron1/fullsend/actions/runs/30741794783

Details:
check toml...........................................(no files to check)Skipped
mixed line ending........................................................Passed
ruff (legacy alias)..................................(no files to check)Skipped
ruff format..........................................(no files to check)Skipped
ty check.............................................(no files to check)Skipped
bandit...............................................(no files to check)Skipped
Detect hardcoded secrets.................................................Passed
shellcheck...........................................(no files to check)Skipped
pinact (SHA-pin check)...................................................Failed
- hook id: pinact
- exit code: 2

�[31mERROR�[0m failed to handle a line: action can't be pinned
.github/workflows/fullsend.yaml:52
    uses: guyoron1/fullsend/.github/workflows/reusable-dispatch.yml@main
::error file=.github/workflows/fullsend.yaml,line=52,title=pinact error::action can't be pinned

Lint GitHub Actions workflow files.......................................Passed
gofmt................................................(no files to check)Skipped
go vet...............................................(no files to check)Skipped
lint mint embed sync.................................(no files to check)Skipped
lint interface doc sync..............................(no files to check)Skipped
lint ADR statuses....................................(no files to check)Skipped
lint ADR numbers.....................................(no files to check)Skipped
lint ADR frontmatter.................................(no files to check)Skipped
lint broken symlinks.....................................................Passed
lint docs link scope.................................(no files to check)Skipped
lint markdown links......................................................Passed
lint workflow file size..............................(no files to check)Skipped
lint-staged (web)....................................(no files to check)Skipped

Please check the workflow logs for full details and retry with /fs-code if appropriate.