docs(issues): [#2298] add developer-tool container integration spec

[josecelano]

Summary

• Add the folder-style specification for recurring Cargo Chef and Containerfile integration failures when adding developer-only Rust tools.
• Define the desired invariant: developer-only tools remain absent from production tracker images and container test archives while their metadata stays available to Cargo Chef.

Scope

• docs/issues/open/2298-rust-dev-tool-container-integration/ISSUE.md

Validation

• linter markdown
• linter cspell
• contrib/dev-tools/git/hooks/pre-commit.sh
• pre-push checks: nightly formatting, nightly workspace check, nightly documentation build, and full test suite

Related to #2298

[Copilot]

Warning

Copilot couldn't run its full agentic review because it didn't start before the timeout. Make sure your repository has a runner available, or add a copilot-code-review.yml file specifying one with the runs-on attribute. See the docs for more details.

Copilot review overview

Review effort: Lite
Findings: 1

Open (1)

• These tables start with ||, which renders in GitHub-flavored Markdown as an extra empty first… · New

What changed in this PR

Adds an “issue spec” document for #2298 describing recurring failures when introducing developer-only Rust tools into the Cargo workspace while using Cargo Chef + Containerfile workflows, and defines invariants/acceptance criteria for a maintainable fix.

Changes:

• Introduces a detailed problem model and current manual remediation checklist for dev-tool container integration failures.
• Documents candidate solution options plus an implementation plan, verification strategy, and acceptance criteria.
• Captures progress tracking and references tied to PR #2293 and related artifacts.

File	Description
docs/​issues/​open/​2298-rust-dev-tool-container-integration/​ISSUE.md	New issue-spec documenting the dev-tool/Cargo Chef/Containerfile integration problem and outlining options + acceptance criteria.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[josecelano]

Verified the current PR diff against the Copilot suggestion. The reported leading || table syntax is not present, so no change was required.

[josecelano]

ACK 23c04f9