Address AGENTS review feedback

Author: rparolin

AGENTS.md

@@ -38,9 +38,11 @@ across the repository, in addition to any package-specific `AGENTS.md`.
 - Add targeted regression tests for behavioral fixes. Do not add elaborate
   tests that mostly prove an implementation detail or require large module
   stubbing unless that is the only practical way to cover the bug.
-- Do not weaken tests just to pass a platform or CI configuration. Avoid broad
-  platform skips such as "skip all WSL" or "skip all Windows"; query CUDA
-  driver/device capability or the specific missing library/feature instead.
+- Do not weaken tests just to pass a platform or CI configuration. Use the
+  tightest available skip criteria: broad OS skips are appropriate only when
+  upstream documentation or the support matrix says the feature is unsupported
+  on that OS; otherwise query the specific CUDA driver/device capability or
+  missing library/feature.
 - Preserve real user workflows in tests. Do not change global CUDA state, skip
   real loading paths, or disable release-note/doc checks merely to reduce CI
   load unless reviewers have agreed to that behavior change.
@@ -53,9 +55,9 @@ across the repository, in addition to any package-specific `AGENTS.md`.
 - Do not hand-edit generated binding artifacts as a shortcut. Fix the generator
   source or templates and regenerate/sync outputs so the next generation does
   not reintroduce the same review issue.
-- Lint or formatting changes that touch generated files should either be made
-  in the generator (`cython-gen`, `cybind`, templates, or sync source) or should
-  exclude generated outputs from the check.
+- Use `.pre-commit-config.yaml` as the source of truth for linting and
+  formatting. Do not perform formatting or lint fixes on files marked "This code
+  was automatically generated..." unless the repo config explicitly opts them in.
 - Keep builds working across the supported CUDA major versions. Do not cimport
   or call newly generated Cython symbols directly unless the older supported
   CUDA-major build is gated or has a wrapper/fallback path.

cuda_bindings/AGENTS.md

@@ -35,10 +35,8 @@ subpackage in the `cuda-python` monorepo.
   defined in `build_hooks.py`; update those rules when introducing new symbols.
 - **Platform split files**: keep `_linux.pyx` and `_windows.pyx` variants
   aligned when behavior should be equivalent.
-- **Lint at the source**: if formatting or lint fixes affect generated files,
-  make the fix in the generation source (`cython-gen`, `cybind`, templates, or
-  sync source) or exclude generated outputs from the check. Otherwise the next
-  regeneration will reintroduce the same issue.
+- **Don't lint generated files:** If a file has the comment "This code was
+  automatically generated...", do not perform any formatting or lint fixes.
 - **Cython copies**: prefer typed assignment for wrapper-owned C struct copies
   over raw `memcpy` when the generated Cython/C types can define the copy size.
 
@@ -76,5 +74,5 @@ subpackage in the `cuda-python` monorepo.
   through an existing Python wrapper instead of directly cimporting the new
   generated Cython symbol.
 - For external contributions touching generated `cuda_bindings` code, ask for a
-  reproducer and environment details, then route fixes through the generation
-  source rather than accepting one-off generated edits.
+  reproducer and environment details. Do not accept one-off generated edits;
+  NVIDIA maintainers should route accepted fixes through the generation source.

cuda_core/AGENTS.md

@@ -7,8 +7,11 @@ This file describes `cuda_core`, the high-level Pythonic CUDA subpackage in the
   `Program`, `Linker`, memory resources, graphs) on top of `cuda.bindings`.
 - **API intent**: keep interfaces Pythonic while preserving explicit CUDA
   behavior and error visibility.
-- **Compatibility**: changes should remain compatible with supported
-  `cuda.bindings` major versions (12.x and 13.x).
+- **API stability**: `cuda_core` is v1.0+; avoid breaking public APIs. Prefer
+  compatibility/deprecation paths and document intentional public changes in
+  docs and release notes.
+- **Compatibility**: changes should remain compatible with the supported CUDA
+  major-version matrix.
 
 ## Package architecture
 
@@ -65,14 +68,14 @@ This file describes `cuda_core`, the high-level Pythonic CUDA subpackage in the
 - If you change public behavior, update tests and docs under `docs/source/`.
 - For new public APIs or broad feature work, sketch the API and behavior in an
   issue/design discussion before opening a large implementation PR. Reviewers
-  often block major `cuda_core` features until API shape, examples, and
-  docs/release-note coverage are clear.
+  often block major `cuda_core` features until API shape, compatibility impact,
+  examples, and docs/release-note coverage are clear.
 - Feature availability checks should query CUDA driver/device capabilities
   instead of hard-coding broad platform skips. Prefer properties such as
   capability flags over assumptions like "Windows", "Linux", or "WSL".
-- Keep CUDA 12.x and 13.x build compatibility in mind. Do not directly cimport
-  newly generated binding symbols unless older supported CUDA-major builds are
-  gated or have a wrapper/fallback path.
+- Preserve compatibility with the supported CUDA major-version matrix. Do not
+  directly cimport newly generated binding symbols unless older supported
+  CUDA-major builds are gated or have a wrapper/fallback path.
 - Resource and context-manager code must preserve stream ordering, ownership,
   and exception semantics. `close()`/cleanup paths should use the stream that
   established the resource ordering, and `__exit__` should avoid masking a