fix: add rs-scripts to Docker build context

[QuantumExplorer]

Issue Being Fixed

Docker builds fail at the build-planner stage with:

Cannot extract Cargo metadata
`cargo metadata` exited with an error: error: failed to load manifest for workspace member `/platform/packages/rs-scripts`
Caused by: No such file or directory (os error 2)

Root Cause

packages/rs-scripts was added as a workspace member in Cargo.toml (PR #3391) but was not included in the Dockerfile's COPY --parents directives. The three Rust build stages (build-planner, build-drive-abci, build-rs-dapi) all copy the workspace Cargo.toml which references rs-scripts, but the package directory itself was missing from the Docker context.

What was changed

Added packages/rs-scripts \ to all three COPY --parents blocks in the Dockerfile (lines ~411, ~517, ~866).

Breaking Changes

None.

🤖 Generated with Claude Code

Summary by CodeRabbit

• Chores
  • Updated build infrastructure configuration to optimize monorepo build processes.

[thepastaclaw]

Review Gate

Commit: 690ef911

• ⏳ Debounce: 12m ago (need 30m)

• ⏳ CI checks: checks still running (1 pending)

• ✅ CodeRabbit review: comment found

• ✅ Off-peak hours: off-peak (01:18 AM PT Wednesday)

• Run review now (check to override)

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 332022d8-2665-44a3-b06c-9f8e18886da3

📥 Commits

Reviewing files that changed from the base of the PR and between 7bc901b and 690ef91.

📒 Files selected for processing (1)

• Dockerfile

---

📝 Walkthrough

Walkthrough

The Dockerfile was updated to include packages/rs-scripts in the workspace copy steps across three build stages: build-planner, build-drive-abci, and build-rs-dapi. This ensures the rs-scripts package is available during the dependency resolution and build setup phases for each stage.

Changes

Cohort / File(s)	Summary
Dockerfile workspace configuration Dockerfile	Added packages/rs-scripts to three COPY --parents blocks in the build-planner, build-drive-abci, and build-rs-dapi stages to include the package in workspace setup and build context.

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~5 minutes

Poem

🐰 A script package tucked with care,
In Dockerfiles beyond compare,
Three stages now know what to find,
With rs-scripts perfectly aligned!
Build it up, let it run—
Organization's work is done! 📦

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately describes the main change: adding rs-scripts to the Docker build context to fix a cargo metadata error during builds.
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 unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/docker-add-rs-scripts-to-build-context

---

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.}