task: more scanning and improvements

Author: jharlow-intel

.gitattributes

@@ -0,0 +1,3 @@
+# Keep shell scripts LF on checkout so shellcheck and conda build scripts work
+# the same on Windows and WSL checkouts with core.autocrlf enabled.
+*.sh text eol=lf

.github/ISSUE_TEMPLATE/bug_report.yml

@@ -0,0 +1,63 @@
+name: Bug report
+description: Report incorrect results, a crash, or a build failure
+labels: ["bug"]
+body:
+  - type: markdown
+    attributes:
+      value: |
+        For security vulnerabilities, do not open an issue — follow
+        [SECURITY.md](https://github.com/IntelPython/mkl_fft/blob/master/SECURITY.md).
+
+  - type: textarea
+    id: description
+    attributes:
+      label: Description
+      description: What happened, and what did you expect instead?
+    validations:
+      required: true
+
+  - type: textarea
+    id: reproducer
+    attributes:
+      label: Reproducer
+      description: A minimal, self-contained snippet. Include the input shape and dtype.
+      render: python
+    validations:
+      required: true
+
+  - type: dropdown
+    id: install-source
+    attributes:
+      label: How was `mkl_fft` installed?
+      options:
+        - Intel channel (software.repos.intel.com)
+        - conda-forge
+        - pip / PyPI
+        - Built from source
+    validations:
+      required: true
+
+  - type: textarea
+    id: versions
+    attributes:
+      label: Versions
+      description: |
+        Output of:
+        ```
+        python -c "import mkl_fft, numpy, mkl; print(mkl_fft.__version__); print(numpy.__version__); print(mkl.get_version_string())"
+        ```
+        Add your OS and Python version too.
+      render: shell
+    validations:
+      required: true
+
+  - type: textarea
+    id: notes
+    attributes:
+      label: Anything else
+      description: |
+        Optional. Whether NumPy patching was active (`mkl_fft.is_patched()`), whether
+        the result differs from `numpy.fft`/`scipy.fft`, or a non-default
+        `MKL_NUM_THREADS`.
+    validations:
+      required: false

.github/ISSUE_TEMPLATE/config.yml

@@ -0,0 +1,8 @@
+blank_issues_enabled: true
+contact_links:
+  - name: Security vulnerability
+    url: https://www.intel.com/content/www/us/en/security-center/vulnerability-handling-guidelines.html
+    about: Report security vulnerabilities through Intel's process, not a public issue.
+  - name: Question about usage
+    url: https://github.com/IntelPython/mkl_fft/blob/master/README.md
+    about: Check the README and the interfaces documentation first.

.github/ISSUE_TEMPLATE/feature_request.yml

@@ -0,0 +1,38 @@
+name: Feature request
+description: Propose a new transform, interface, or capability
+labels: ["enhancement"]
+body:
+  - type: textarea
+    id: problem
+    attributes:
+      label: What problem does this solve?
+      description: The use case, not the implementation.
+    validations:
+      required: true
+
+  - type: textarea
+    id: proposal
+    attributes:
+      label: Proposal
+      description: |
+        What you would like `mkl_fft` to do. If it mirrors a `numpy.fft` or
+        `scipy.fft` function, name it — upstream signature and semantics are the
+        contract for the interface layer.
+    validations:
+      required: true
+
+  - type: input
+    id: upstream
+    attributes:
+      label: Upstream equivalent
+      description: Link to the NumPy or SciPy docs for the equivalent API, if there is one.
+    validations:
+      required: false
+
+  - type: textarea
+    id: alternatives
+    attributes:
+      label: Alternatives considered
+      description: Optional. Workarounds you are using today.
+    validations:
+      required: false

.gitignore

@@ -5,6 +5,12 @@ mkl_fft.egg-info/
 # Byte-compiled / optimized / DLL files
 __pycache__/
 
+# Virtual environments, test caches, local env files
+.venv/
+venv/
+.pytest_cache/
+.env
+
 mkl_fft/_pydfti.c
 mkl_fft/_pydfti.cpython*.so
 mkl_fft/_pydfti.*-win_amd64.pyd

AGENTS.md

@@ -14,6 +14,7 @@ It provides accelerated FFT transforms while aiming to preserve upstream API beh
 - **Tests:** `mkl_fft/tests/`
 - **Vendored helpers:** `_vendored/`
 - **Packaging:** `conda-recipe/`, `conda-recipe-cf/`
+- **Benchmarks:** `benchmarks/`
 
 ## Build/runtime basics
 - Build system: `pyproject.toml` + `meson.build`
@@ -46,3 +47,4 @@ Use nearest local `AGENTS.md` when present:
 - `conda-recipe/AGENTS.md` — Intel-channel conda packaging
 - `conda-recipe-cf/AGENTS.md` — conda-forge recipe context
 - `_vendored/AGENTS.md` — vendored tooling boundaries
+- `benchmarks/AGENTS.md` — ASV performance suite

benchmarks/AGENTS.md

@@ -0,0 +1,20 @@
+# AGENTS.md — benchmarks/
+
+ASV performance suite for `mkl_fft`.
+
+## Scope
+- `asv.conf.json` — ASV configuration, channels, and regression thresholds
+- `benchmarks/` — benchmark modules (`bench_fft1d`, `bench_fftnd`,
+  `bench_interfaces`, `bench_memory`) plus shared bases in `_utils.py`
+- `README.md` — coverage table, threading model, and run commands
+
+## Guardrails
+- Treat `asv.conf.json` as canonical for ASV settings; treat `README.md` as
+  canonical for what each module covers.
+- Comparability across machines depends on the thread default in
+  `benchmarks/__init__.py` and the DFTI warmup in each `setup`. Changing either
+  invalidates comparison against existing results — call it out explicitly.
+- Keep inputs deterministic; benchmarks seed their own RNG.
+- Report performance numbers with reproducible context: hardware, thread count,
+  versions, and the command used.
+- Benchmark results under `.asv/` are local artifacts and are gitignored.