Rust Mapper emits zero contextFiles for seeds

[Tanmay-008]

Currently, the Rust mapper does not populate contextFiles for any mapped seeds. When an AI agent processes a Rust feature, it receives zero dependency context (no Cargo.toml, no sibling modules, no entry points). This is a critical gap compared to other language mappers (Go, Node, Python, C/C++) which provide rich context out of the box, leading to potential hallucinations regarding project dependencies and architecture.

Expected Behavior

The Rust mapper should dynamically resolve and attach relevant context files to FeatureSeed outputs. Specifically:

• Manifests: Every Rust seed should include its closest Cargo.toml as a context file.
• Sibling Entries: If a crate has both src/main.rs and src/lib.rs, they should be cross-linked (since binaries often import from their own library).
• Module Tracking: Entry files (main.rs, lib.rs) should be parsed for mod foo; or pub mod foo; declarations. The mapper should resolve these to - their actual files (e.g. src/foo.rs or src/foo/mod.rs) and include them in the context to provide the AI with the crate's module tree.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve. Reviewed July 25, 2026, 12:19 PM ET / 16:19 UTC.

Summary
Keep open. The report describes a concrete gap in Rust feature context, but the supplied evidence does not establish that current main already provides the requested manifest, sibling-entry, and module resolution behavior; the scope also needs a bounded context-selection policy before implementation.

Reproducibility: unclear. The issue gives a specific expected seed payload, but the discussion contains no current-main fixture, command output, or failing mapper test that confirms the reported zero-context behavior.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.
• Share version, platform, channel/provider, and relevant config details.

Maintainer decision needed

Question	Recommendation
Should Rust seed context include only direct crate structure, or should the mapper recursively traverse declared modules subject to an explicit context budget?	Bound direct crate context: Include Cargo.toml, the paired main/lib entrypoint, and directly declared module files with a fixed deduplication and file-count limit.

Why: The requested module-tree behavior affects prompt size, traversal semantics, and support expectations across diverse Rust layouts; those limits are product and maintenance policy rather than a mechanical bug fix alone.

Next step
A maintainer should first set the supported Rust module-resolution depth and context budget; after that decision, the work should be a bounded mapper-and-test change.

Review details

Best possible solution:

Define a bounded Rust context policy, then add the nearest Cargo.toml, paired crate entrypoint, and safely resolved direct module files with deduplication and focused mapper regression coverage.

Do we have a high-confidence way to reproduce the issue?

Unclear. The issue gives a specific expected seed payload, but the discussion contains no current-main fixture, command output, or failing mapper test that confirms the reported zero-context behavior.

Is this the best way to solve the issue?

Unclear. Adding crate context is directionally appropriate, but recursive module discovery should be bounded and specified before treating the proposed traversal as the final solution.

AGENTS.md: found and applied where relevant.

Remaining risk / open question:

• Recursively attaching every declared module could create excessive or cyclic context unless the mapper defines a narrow traversal, deduplication, and file-count budget.
• Resolving only simple mod declarations may misrepresent Rust projects that use path attributes, generated modules, workspace layouts, or conditional compilation.

Codex review notes: model internal, reasoning high; reviewed against deffd4b799bd.

Label changes

Label changes:

• add P2: Missing Rust seed context can reduce agent accuracy for Rust repositories, but the report is a bounded mapper improvement without evidence of an active runtime outage.
• add impact:other: The issue affects repository-analysis context quality for downstream AI tasks rather than a more specific owned impact category.
• add issue-rating: 🦪 silver shellfish: Current issue advisory state selects this label.
• add clawsweeper:linked-pr-open: Current issue advisory state selects this label.
• add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.
• add clawsweeper:needs-maintainer-review: Current issue advisory state selects this label.
• add clawsweeper:needs-product-decision: Current issue advisory state selects this label.

Label justifications:

• P2: Missing Rust seed context can reduce agent accuracy for Rust repositories, but the report is a bounded mapper improvement without evidence of an active runtime outage.
• impact:other: The issue affects repository-analysis context quality for downstream AI tasks rather than a more specific owned impact category.

Evidence reviewed

What I checked:

• Concrete requested behavior: The issue identifies three distinct missing context sources for Rust seeds: the closest Cargo.toml, the paired src/main.rs or src/lib.rs entrypoint, and files resolved from mod declarations.
• Current-main review target: The requested behavior must be checked against current main before any implemented-on-main close; the supplied review context identifies current main as deffd4b but contains no source or test evidence proving this behavior is already implemented. (deffd4b799bd)
• Repository review policy: The repository guidance calls for focused mapper coverage and targeted validation for behavior changes, so any repair should add Rust mapper tests for the selected context relationships. (AGENTS.md:1)

Likely related people:

• unidentified: No source-history provenance for the Rust mapper was available in the supplied review evidence, so a concrete current-main owner cannot be named safely. (role: likely Rust-mapper area owner; confidence: low; files: src/mappers/rust.ts)

How this review workflow works

• ClawSweeper keeps one durable marker-backed review comment per issue or PR.
• Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
• A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
• PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
• Maintainers can also comment @clawsweeper review to request a fresh review only.
• Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
• Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
• Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

[steipete]

Fixed by #165 and landed on main through 53cdeaa8280e8d814eab3ab6308ff05e85a5565c.

The Rust mapper now attaches the nearest Cargo manifest, paired crate entrypoint, and bounded directly declared modules. Module lookup follows Rust's entrypoint-relative layout for both nested src/bin/worker/main.rs and flat src/bin/audit.rs binaries instead of assuming every module lives under crate-root src/.

Landed commits:

• 0b75e2cc7ac00ab317ce67a78abc88961936ad63 — @Tanmay-008's Rust context implementation
• f82229fc94fc89dd8bb33dff3a36a265563e4986 — @Tanmay-008's mapper assertion update
• 9492ac83fa92adb8f5fe9d436230a16b97e4cc40 — entrypoint-relative nested/flat binary repair and regressions
• 53cdeaa8280e8d814eab3ab6308ff05e85a5565c — credited changelog entry

Proof on the exact PR head:

• 894 tests passed, 1 skipped; typecheck, lint, format, build, and packaged CLI smoke passed.
• Installed-tarball behavior mapped src/bin/worker/protocol.rs and src/bin/audit/output.rs, rejected a crate-root decoy, and repeated deterministically.
• Codex autoreview reported no accepted/actionable findings.
• CI 30168989215, CodeQL 30168989313, and secret scanning 30168989236 all passed.