[infra] CI 優化：backend unit test 改用 native Go，移除 artifact roundtrip

[nurockplayer]

Summary

• backend job removes artifact download / docker load and runs native Go tests with actions/setup-go@v6.
• backend now runs go test ./... and go vet ./... from services/api.
• backend-build keeps Docker build cache validation but removes image artifact export/upload roundtrip.
• backend no longer depends on backend-build; backend-ci gate still depends on backend-build, backend, and backend-integration.
• Workflow regression tests assert the native Go backend path and ensure CI workflow changes are not treated as metadata-only skips.
• Backend CI wiring guard now validates the native-Go path and rejects the removed artifact roundtrip.

Source of truth：#437

Closes #437

Depends on PR：none

Backend contract already in develop：

• yes
• no

本 PR 明確不做

• Does not change Go source code or runtime behavior.
• Does not change Docker Compose runtime configuration.
• Does not change backend-integration beyond staying aligned with the services/api service root from [backend] Move backend service into services/api #435.
• Does not remove the backend Docker build job; it only removes the backend image artifact roundtrip.

Verification

• bash scripts/check-backend-ci-cache.sh
• node --test .github/workflows/ci.test.mjs — 10/10 passed
• ruby -e "require 'yaml'; YAML.safe_load(File.read('.github/workflows/ci.yml'), permitted_classes: [], aliases: false); YAML.safe_load(File.read('.github/workflows/pr-scope-police.yml'), permitted_classes: [], aliases: false); puts 'yaml ok'"
• go test ./... from services/api
• go vet ./... from services/api
• git diff --check

[github-actions]

PR Scope Police

• PASS: scope checks passed.

Snapshot

• Mode: standard PR
• Docs/template/metadata only: no
• Changed files: 3
• Diff lines (+/-): 75
• Product surfaces: none
• Dependency blocked: no
• Auto-close triggered: no
• Auto-close label: scope-violation
• Dependency block label: blocked-by-dependency
• Bypass label: scope-exception

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 5f2df75eed

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[coderabbitai]

Walkthrough

CI 工作流程移除了後端 Docker image artifact 的上傳/下載環節，改為直接在 runner 上用原生 Go 工具執行測試與檢查。同時刪除 backend 對 backend-build 的依賴，讓兩者平行執行。相應更新了 CI 測試斷言。

Changes

Cohort / File(s)	Summary
CI 工作流程簡化 .github/workflows/ci.yml	移除 backend-build 的 Docker image artifact 上傳、backend 的 artifact 下載和 docker load 步驟；改用 actions/setup-go 直接在 services/api 執行 go test 和 go vet；刪除 backend 對 backend-build 的依賴。
測試斷言更新 .github/workflows/ci.test.mjs	更新後端 job 斷言以驗證不含 docker load、actions/download-artifact、backend-image 字串，且 vet 步驟改為檢查新的 working-directory: services/api 與原生 Go 模式。

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~12 minutes

Possibly related PRs

• [chore] fix: wire backend artifact pipeline on develop #364：同樣修改後端 CI job 與相關測試，一個添加 Docker image artifact 流程，此 PR 則反向移除該流程。
• [chore] 後端測試改用 setup-go，與 image build 並行 #350：同樣移除後端 Docker image artifact 與 docker-compose 步驟，改用 actions/setup-go 執行原生 Go 測試。
• [infra] Backend integration tests — testcontainers 取代 docker-compose postgres #293：同樣將後端測試從容器化 docker-compose 改為原生 Go 執行。

Suggested labels

needs-codex-review

Suggested reviewers

• k49778749-stack
• Erick52106

Poem

🐳 Docker 映像被丟棄，
工作流輕装上陣，
原生 Go 飛速跑過，
節省百秒測試時光——
平行、迅捷、向前衝！⚡

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Title check	✅ Passed	PR title clearly describes the main change: switching backend unit tests from Docker artifact roundtrip to native Go execution.
Linked Issues check	✅ Passed	All coding requirements from issue #437 are fully implemented: native Go setup with setup-go, parallel execution via reduced dependencies, artifact steps removed from backend-build, and native go test/vet runs verified by tests.
Out of Scope Changes check	✅ Passed	Changes are strictly scoped to CI workflow files and tests as specified in issue #437; no unrelated modifications to source code, Dockerfile, or other systems detected.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

📝 Generate docstrings

• Create stacked PR
• Commit on current branch

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/backend-ci-native-go

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

[Erick52106]

Summary

先留一般 review comment，不提交 Change Request。

Blockers

1. .github/workflows/ci.yml:257 / :260 / :264

backend job 指向 services/api/go.mod 並在 services/api 執行，但 PR head 上 services/api/go.mod 目前是 404；repo 目前存在的是 backend/go.mod。一旦 scope gate 放行 backend CI，actions/setup-go 或後續 working-directory 會直接失敗。建議改回 backend/go.mod / working-directory: backend，並同步修正 .github/workflows/ci.test.mjs 斷言。

2. .github/workflows/ci.yml:351-376

這輪 checks 顯示 Backend tests、Build backend image、Backend integration tests 都是 SKIPPED，但 Backend CI (gate) 仍通過，因為 gate 接受 skipped。也就是說，PR 目前沒有實際驗證本次修改的 backend CI 路徑，也無法證明 issue #437 的「backend critical path 縮短」完成條件。建議先修 PR body / scope gate 條件讓 heavy CI 跑起來，再確認 backend jobs 真正成功。

Notes

actions/setup-go@v6 本身已發布，使用 ubuntu-latest GitHub-hosted runner 通常可接受；這點不是 blocker。

[Erick52106]

再審後確認上一輪兩個 blocker 都已解除：

• services/api/go.mod 在 PR head 已存在，backend / backend-integration 改用 services/api 的路徑可以成立。
• 最新 CI 已實際跑過並通過 Build backend image、Backend tests、Backend integration tests、Check backend CI cache wiring、Workflow regression tests。

沒有發現新的 blocker / major。建議 merge。