fixes go worspace setup for cost-accuracy and load-test

[akshaydeo]

Summary

The go.work file is gitignored and must be regenerated in CI environments. Without it, builds in cost-accuracy-test.sh and load-test.sh resolve core, framework, and plugins from the published versions pinned in transports/go.mod rather than the local workspace copies. This PR ensures the Go workspace is initialized before any build steps run in those scripts.

Changes

• Added a call to setup-go-workspace.sh at the start of both cost-accuracy-test.sh and load-test.sh, executed from the repo root so that the relative go work use ./core paths resolve correctly and the resulting go.work file is auto-discovered by subsequent go build invocations.

Type of change

• Bug fix
• Feature
• Refactor
• Documentation
• Chore/CI

Affected areas

• Core (Go)
• Transports (HTTP)
• Providers/Integrations
• Plugins
• UI (React)
• Docs

How to test

Trigger the cost-accuracy and load-test CI workflows and confirm that the builds resolve local module versions rather than the published ones pinned in transports/go.mod.

# Manually verify workspace setup
cd <repo-root>
source .github/workflows/scripts/setup-go-workspace.sh
go build ./transports/...

Breaking changes

• Yes
• No

Related issues

Security considerations

None.

Checklist

• I read docs/contributing/README.md and followed the guidelines
• I added/updated tests where appropriate
• I updated documentation where needed
• I verified builds succeed (Go and UI)
• I verified the CI pipeline passes locally if applicable

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro Plus

Run ID: e39ef04f-b204-45c8-b598-e500b6224b39

📥 Commits

Reviewing files that changed from the base of the PR and between f325e92 and b59d97f.

📒 Files selected for processing (2)

• .github/workflows/scripts/cost-accuracy-test.sh
• .github/workflows/scripts/load-test.sh

---

📝 Walkthrough

Summary by CodeRabbit

• Chores
  • Improved build system configuration in CI/CD workflows to ensure correct local dependency resolution during testing and cost accuracy checks.

Walkthrough

Two CI test scripts (cost-accuracy-test.sh and load-test.sh) are updated to source setup-go-workspace.sh from the repository root at startup. This regenerates the gitignored go.work file so that subsequent go build calls resolve local core/framework/plugins modules rather than the versions pinned in transports/go.mod.

Changes

Go Workspace Initialization in CI Scripts

Layer / File(s)	Summary
Source go-workspace setup in both CI test scripts .github/workflows/scripts/cost-accuracy-test.sh, .github/workflows/scripts/load-test.sh	Both scripts gain an early block that changes into the repo root and sources setup-go-workspace.sh, regenerating go.work (gitignored) before any go build step so local module replacements are used instead of pinned transports/go.mod versions.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~3 minutes

Possibly related PRs

• maximhq/bifrost#4561: Introduces the same CI harness scripts (cost-accuracy-test.sh, load-test.sh) in the release pipeline that this PR modifies to source setup-go-workspace.sh.

Suggested reviewers

• danpiths

Poem

🐇 Hop, hop into the workspace root I go,
Sourcing scripts so local modules flow,
No more pinned deps from transports afar,
go.work regenerates like a bright star,
Build steps now resolve what's truly near —
This bunny keeps the module graph clear! ✨

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Linked Issues check	⚠️ Warning	The linked issue #123 concerns Files API Support for providers like OpenAI/Anthropic, which is completely unrelated to the Go workspace setup fixes for cost-accuracy and load-test scripts in this PR.	Review and update the linked issues. The current linked issue #123 appears to be incorrectly associated with this PR. Either unlink issue #123 or link issues actually related to Go workspace setup.

✅ Passed checks (4 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title is partially related to the changeset. It mentions fixing Go workspace setup but contains a typo ('worspace' instead of 'workspace'), which is a minor issue. The title accurately reflects the main changes to cost-accuracy and load-test scripts.
Description check	✅ Passed	The PR description is well-structured and follows the template. It provides a clear summary, specific changes made, correct type selection (Chore/CI), and testing instructions. While some optional sections lack detail, all critical information is present.
Out of Scope Changes check	✅ Passed	The changes are narrowly scoped and focused on fixing Go workspace setup in two CI scripts by adding workspace regeneration calls, which aligns with the PR's stated objective.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ 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 06-21-fixes_go_worspace_setup_for_cost-accuracy_and_load-test

---

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

[akshaydeo]

• fixes go worspace setup for cost-accuracy and load-test #4585 👈 (View in Graphite)
• dev

This stack of pull requests is managed by Graphite. Learn more about stacking.

[greptile-apps]

Confidence Score: 4/5

Safe to merge; the core workspace setup correctly writes go.work to the repo root so subsequent go build calls auto-discover it.

Both scripts correctly initialize the Go workspace before building binaries, which is the key fix. The only gap is that GOTOOLCHAIN=auto, exported inside the subshell, does not reach the parent shell where go build actually runs — a minor robustness concern that would only surface if the CI-installed Go version diverges from the workspace's go directive.

No files require special attention; both changed scripts are straightforward CI helpers.

Important Files Changed

Filename	Overview
.github/workflows/scripts/cost-accuracy-test.sh	Adds Go workspace bootstrap via subshell-sourced setup-go-workspace.sh before building binaries; the go.work file is correctly created at ROOT_DIR so go build auto-discovers it, but GOTOOLCHAIN=auto exported inside the subshell is not inherited by the parent shell's subsequent go build calls.
.github/workflows/scripts/load-test.sh	Same Go workspace bootstrap added; uses SCRIPT_DIR (which resolves to the same directory as setup-go-workspace.sh) and REPO_ROOT as the working directory, so module paths are correct. GOTOOLCHAIN=auto has the same scoping concern as in cost-accuracy-test.sh.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[Script starts] --> B[Resolve ROOT_DIR / REPO_ROOT]
    B --> C["Subshell: cd REPO_ROOT &&\nsource setup-go-workspace.sh"]
    C --> D{go.work\nalready exists?}
    D -- Yes --> E[Skip init, return]
    D -- No --> F["go work init\ngo work use ./core ./framework\n./plugins/* ./transports ./cli"]
    F --> G[go.work written to REPO_ROOT]
    E --> H[Subshell exits]
    G --> H
    H --> I[Parent shell continues\nwithout GOTOOLCHAIN=auto]
    I --> J["go build -o bifrost-http\n(auto-discovers go.work)"]
    J --> K[Binary uses local module sources]

Loading

%%{init: {'theme': 'base', 'themeVariables': {"darkMode": true, "background": "#0d1117", "primaryColor": "#21262d", "primaryTextColor": "#e6edf3", "primaryBorderColor": "#8b949e", "lineColor": "#8b949e", "textColor": "#e6edf3", "edgeLabelBackground": "#161b22", "actorBkg": "#21262d", "actorBorder": "#8b949e", "actorTextColor": "#e6edf3", "actorLineColor": "#8b949e", "signalColor": "#8b949e", "signalTextColor": "#e6edf3", "noteBkgColor": "#373320", "noteBorderColor": "#d4a72c", "noteTextColor": "#f0e6c0", "labelBoxBkgColor": "#21262d", "labelBoxBorderColor": "#8b949e", "labelTextColor": "#e6edf3", "loopTextColor": "#e6edf3", "activationBkgColor": "#30363d", "activationBorderColor": "#8b949e"}}}%%
flowchart TD
    A[Script starts] --> B[Resolve ROOT_DIR / REPO_ROOT]
    B --> C["Subshell: cd REPO_ROOT &&\nsource setup-go-workspace.sh"]
    C --> D{go.work\nalready exists?}
    D -- Yes --> E[Skip init, return]
    D -- No --> F["go work init\ngo work use ./core ./framework\n./plugins/* ./transports ./cli"]
    F --> G[go.work written to REPO_ROOT]
    E --> H[Subshell exits]
    G --> H
    H --> I[Parent shell continues\nwithout GOTOOLCHAIN=auto]
    I --> J["go build -o bifrost-http\n(auto-discovers go.work)"]
    J --> K[Binary uses local module sources]

Loading

_{Reviews (1): Last reviewed commit: "fixes go worspace setup for cost-accurac..." | Re-trigger Greptile}

[greptile-apps]

GOTOOLCHAIN=auto is exported inside the subshell but does not propagate to the parent shell where the go build calls in build_binaries run. If the installed Go version in CI differs from the go directive in the generated go.work file, the builds can fail with a toolchain-version mismatch. Exporting GOTOOLCHAIN=auto in the parent shell before the subshell is the minimal fix.

Suggested change

	( cd "${ROOT_DIR}" && source "${ROOT_DIR}/.github/workflows/scripts/setup-go-workspace.sh" )
	export GOTOOLCHAIN=auto
	( cd "${ROOT_DIR}" && source "${ROOT_DIR}/.github/workflows/scripts/setup-go-workspace.sh" )

[greptile-apps]

Same GOTOOLCHAIN=auto scoping issue as in cost-accuracy-test.sh — the export is confined to the subshell and is not visible to the go build call in build_bifrost_http. Exporting it in the parent shell guards against toolchain-version errors.

Suggested change

	( cd "${REPO_ROOT}" && source "${SCRIPT_DIR}/setup-go-workspace.sh" )
	export GOTOOLCHAIN=auto
	( cd "${REPO_ROOT}" && source "${SCRIPT_DIR}/setup-go-workspace.sh" )

[akshaydeo]

Merge activity

• Jun 21, 12:51 PM UTC: A user started a stack merge that includes this pull request via Graphite.
• Jun 21, 12:52 PM UTC: @akshaydeo merged this pull request with Graphite.