Add CUDA support to feature mapping and review

[danielbrodie]

Hi @steipete, proposing first-class CUDA support in clawpatch.

clawpatch's C/C++ mapper handles generic project shapes today, and CUDA is not covered: .cu/.cuh sources are not recognized, so CUDA projects map with little coverage, and the review prompt has no CUDA-specific guidance so a kernel is reviewed with the same checklist as any other file.

Proposed scope:

Mapping (src/mappers/, src/detect.ts):

• recognize .cu/.cuh across standalone main() files, CMake add_executable/add_library (including the legacy FindCUDA cuda_add_executable/cuda_add_library commands), and autotools targets
• detect repositories containing CUDA sources as cuda projects
• group source files that no build target owns into bounded, per-directory source groups
• map CMakeLists.txt, CMakePresets.json, and configure.ac as config features
• emit conservative C/C++/CUDA validation commands only from a project-declared signal (a root Makefile check/test target, or a CMakePresets.json build workflow); otherwise stay null
• tag CUDA build targets and source groups with the concurrency trust boundary

Review (src/prompt.ts):

• when a reviewed feature owns .cu/.cuh sources, add a CUDA hazard checklist to the review prompt (default mode) and the fix prompt: kernel races and synchronization, unchecked CUDA runtime calls, host/device pointer confusion, memory-access hazards, and device-memory leaks
• detection is by file extension so mixed host/device targets are covered
• findings use the existing categories; no schema change

I am opening a pull request with the implementation alongside this issue. It is based on the current main, includes focused tests for every behavior change, and the full CI sequence passes locally.

[clawsweeper]

Codex review: keeping this open for maintainer follow-up; there is still a little grit to resolve.

Latest ClawSweeper review: 2026-05-24 00:08 UTC / May 23, 2026, 8:08 PM ET.

Workflow note: Future ClawSweeper reviews update this same comment in place.

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.

Summary
Keep open: current main still lacks CUDA file recognition and CUDA-specific review guidance, and the reporter linked an open implementation PR at #108 that should be reviewed before this issue closes.

Reproducibility: not applicable. this is a feature request, not a bug reproduction. Source inspection does confirm current main does not recognize .cu or .cuh in mapper/detection paths or add CUDA-specific prompt guidance.

Ways to help us reproduce this

• Add a screenshot or short recording showing the behavior.
• Add expected vs actual behavior.
• Include redacted logs or terminal output.

Next step
Do not queue a duplicate repair lane while the reporter's linked implementation PR remains open for maintainer review.

Review details

Best possible solution:

Review and either land or explicitly close the focused CUDA implementation in #108, then close this issue after the remaining mapper and prompt scope is resolved.

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

Not applicable: this is a feature request, not a bug reproduction. Source inspection does confirm current main does not recognize .cu or .cuh in mapper/detection paths or add CUDA-specific prompt guidance.

Is this the best way to solve the issue?

Unclear until the linked PR is reviewed. The proposed direction is plausible if it extends the existing C/C++ mapper patterns, keeps validation commands conservative, and avoids changing the finding schema.

Label changes:

• add clawsweeper:no-new-fix-pr: Current issue advisory state selects this label.
• add clawsweeper:needs-product-decision: Current issue advisory state selects this label.

Label justifications:

• P2: This is a concrete mapper and review-guidance feature request with bounded implementation scope and an active companion PR.

What I checked:

• Current mapper excludes CUDA extensions: isCOrCppSource only recognizes C/C++ suffixes c|cc|cpp|cxx|h|hh|hpp|hxx, and isCOrCppCompilable only recognizes c|cc|cpp|cxx, so .cu and .cuh are not collected as C/C++ mapper candidates on current main. (src/mappers/c-cpp.ts:35, 857d854ac8d0)
• Language detection has no CUDA branch: detectLanguages adds c and cpp via containsCFile and containsCppFile; those helpers check .c, .C, .H, .cpp, .cc, .cxx, .hpp, .hh, and .hxx, but not .cu or .cuh. (src/detect.ts:1282, 857d854ac8d0)
• Review prompt has no CUDA-specific checklist: The default review prompt currently lists generic review categories and reviewModeInstructions(default) returns an empty string; the fix prompt similarly has no extension-triggered CUDA hazard block. (src/prompt.ts:194, 857d854ac8d0)
• Docs describe generic C/C++ scope only: The feature-mapping docs describe C/C++ support as standalone main(), CMake add_executable / add_library, and autotools targets, with no CUDA coverage documented. (docs/feature-mapping.md:155, 857d854ac8d0)
• Canonical linked implementation is still open: GitHub reports feat(mapper): add CUDA support #108 as open, based on current main 857d854ac8d0b802c06b0ddaa7a48329ef331fe6, with head eace83d36573ab0806df5ba2402388120077af59, and touching the expected mapper, prompt, docs, and tests. (eace83d36573)
• Canonical search found the issue and companion PR only: GitHub title/body search for CUDA mapper returned this open issue and the open companion PR, so the linked PR is the active canonical implementation path rather than a merged/superseding item.

Likely related people:

• iliaal: The generic C/C++ mapper, C/C++ language detection, docs, and focused mapper tests that CUDA support would extend were introduced in commit 5c94a30cee9f8d32b9fcc99bbeb0beeeb97ae31c. (role: introduced behavior; confidence: high; commits: 5c94a30cee9f; files: src/mappers/c-cpp.ts, src/detect.ts, docs/feature-mapping.md)
• steipete: The current release/import commit cdd58ac59213ef24c357be0749ce70f61409d95b contains the current mapper, prompt, docs, and tests at the latest release boundary. (role: recent area contributor; confidence: medium; commits: cdd58ac59213; files: src/mappers/c-cpp.ts, src/detect.ts, src/prompt.ts)
• mbelinky: Commit eabfff0ee67378ca01ae0a8cc7155aa882d965ad touched the review prompt mode path that any CUDA-specific review guidance would need to coexist with. (role: adjacent prompt contributor; confidence: medium; commits: eabfff0ee673; files: src/prompt.ts)
• danielbrodie: The reporter opened the active companion implementation PR touching the mapper, detection, prompt, docs, and test surfaces for this request. (role: companion implementation proposer; confidence: medium; commits: 955e4eb45516, 448d62b76f2c, 92ef586b8739; files: src/mappers/c-cpp.ts, src/detect.ts, src/prompt.ts)

Codex review notes: model gpt-5.5, reasoning high; reviewed against 857d854ac8d0.

[danielbrodie]

here's the link: #108

[danielbrodie]

@clawsweeper re-review

[clawsweeper]

🦞🧹
ClawSweeper re-review requested.

I asked ClawSweeper to review this item again.
Action: item re-review queued (workflow sweep.yml, event repository_dispatch).
Result: the existing ClawSweeper review comment will be edited in place when the review finishes.

Re-review progress:

• State: Complete
• Detail: The targeted re-review finished, the durable review comment was updated, and the synced verdict was routed.
• Run: https://github.com/openclaw/clawsweeper/actions/runs/26316248239
• Updated: 2026-05-22T23:11:53.481Z