xarray-spatial 0.9.7__tar.gz → 0.9.9__tar.gz

{xarray_spatial-0.9.7 → xarray_spatial-0.9.9}/.claude/commands/bench.md

@@ -1,6 +1,6 @@
 # Bench: Local Performance Comparison
 
-Run ASV benchmarks for the current branch against master and report regressions
+Run ASV benchmarks for the current branch against main and report regressions
 and improvements. The prompt is: $ARGUMENTS
 
 ---
@@ -9,7 +9,7 @@ and improvements. The prompt is: $ARGUMENTS
 
 1. If $ARGUMENTS names specific benchmark classes or functions (e.g. `Slope`,
    `flow_accumulation`), use those directly.
-2. If $ARGUMENTS is empty or says "auto", run `git diff origin/master --name-only`
+2. If $ARGUMENTS is empty or says "auto", run `git diff origin/main --name-only`
    to find changed source files under `xrspatial/`. Map each changed file to the
    corresponding benchmark module in `benchmarks/benchmarks/`. Use the filename
    and imports to match (e.g. changes to `slope.py` map to `benchmarks/benchmarks/slope.py`).
@@ -30,7 +30,7 @@ and improvements. The prompt is: $ARGUMENTS
 Run ASV in continuous-comparison mode from the `benchmarks/` directory:
 
 ```bash
-cd benchmarks && asv continuous origin/master HEAD -b "<regex>" -e
+cd benchmarks && asv continuous origin/main HEAD -b "<regex>" -e
 ```
 
 Where `<regex>` is a pattern matching the benchmark classes identified in Step 1
@@ -64,7 +64,7 @@ Parse the output and classify each result:
 ## Step 5 -- Generate the report
 
 ```
-## Benchmark Report: <branch> vs master
+## Benchmark Report: <branch> vs main
 
 ### Changed files
 - <list of changed source files>
@@ -74,7 +74,7 @@ Parse the output and classify each result:
 
 ### Results
 
-| Benchmark                          | master    | HEAD      | Ratio | Status     |
+| Benchmark                          | main    | HEAD      | Ratio | Status     |
 |------------------------------------|-----------|-----------|-------|------------|
 | slope.Slope.time_numpy             | 3.45 ms   | 3.51 ms   | 1.02x | UNCHANGED  |
 | slope.Slope.time_dask_numpy        | 8.12 ms   | 4.23 ms   | 0.52x | IMPROVED   |
@@ -124,4 +124,4 @@ Do NOT write benchmark files automatically. Report the gap and propose, then wai
   analysis (unless the user explicitly asks for a benchmark to be written in
   response to Step 6).
 - If $ARGUMENTS says "compare <branch1> <branch2>", run
-  `asv continuous <branch1> <branch2>` instead of the default origin/master vs HEAD.
+  `asv continuous <branch1> <branch2>` instead of the default origin/main vs HEAD.

{xarray_spatial-0.9.7 → xarray_spatial-0.9.9}/.claude/commands/efficiency-audit.md

@@ -267,7 +267,7 @@ Thresholds: IMPROVED < 0.8x, REGRESSION > 1.2x, else UNCHANGED.
 - If $ARGUMENTS includes a severity filter (e.g. "high only"), only report
   findings at that severity level.
 - If $ARGUMENTS includes "diff" or "changed", restrict the audit to files
-  changed on the current branch vs origin/master.
+  changed on the current branch vs origin/main.
 - Baseline benchmark scripts are disposable. Clean up `/tmp/` scripts after
   capturing results.
 - The 512x512 array size is a default. If $ARGUMENTS includes a size like

{xarray_spatial-0.9.7 → xarray_spatial-0.9.9}/.claude/commands/release-major.md

@@ -16,7 +16,7 @@ $ARGUMENTS
 ## Step 2 -- Create a release branch
 
 ```bash
-git checkout master && git pull
+git checkout main && git pull
 git checkout -b release/vX.Y.Z
 ```
 
@@ -49,7 +49,7 @@ git push -u origin release/vX.Y.Z
 
 ## Step 5 -- Verify CI
 
-1. Run `gh pr create --title "Release vX.Y.Z" --body "Changelog update for vX.Y.Z major release."` to open a PR against master.
+1. Run `gh pr create --title "Release vX.Y.Z" --body "Changelog update for vX.Y.Z major release."` to open a PR against main.
 2. Wait for CI:
    ```bash
    gh pr checks <PR_NUMBER> --watch
@@ -65,7 +65,7 @@ gh pr merge <PR_NUMBER> --merge --delete-branch
 ## Step 7 -- Tag the release
 
 ```bash
-git checkout master && git pull
+git checkout main && git pull
 git tag -a vX.Y.Z -m "Version X.Y.Z"
 git push origin vX.Y.Z
 ```

{xarray_spatial-0.9.7 → xarray_spatial-0.9.9}/.claude/commands/release-minor.md

@@ -16,7 +16,7 @@ $ARGUMENTS
 ## Step 2 -- Create a release branch
 
 ```bash
-git checkout master && git pull
+git checkout main && git pull
 git checkout -b release/vX.Y.Z
 ```
 
@@ -49,7 +49,7 @@ git push -u origin release/vX.Y.Z
 
 ## Step 5 -- Verify CI
 
-1. Run `gh pr create --title "Release vX.Y.Z" --body "Changelog update for vX.Y.Z minor release."` to open a PR against master.
+1. Run `gh pr create --title "Release vX.Y.Z" --body "Changelog update for vX.Y.Z minor release."` to open a PR against main.
 2. Wait for CI:
    ```bash
    gh pr checks <PR_NUMBER> --watch
@@ -65,7 +65,7 @@ gh pr merge <PR_NUMBER> --merge --delete-branch
 ## Step 7 -- Tag the release
 
 ```bash
-git checkout master && git pull
+git checkout main && git pull
 git tag -a vX.Y.Z -m "Version X.Y.Z"
 git push origin vX.Y.Z
 ```

{xarray_spatial-0.9.7 → xarray_spatial-0.9.9}/.claude/commands/release-patch.md

@@ -16,7 +16,7 @@ $ARGUMENTS
 ## Step 2 -- Create a release branch
 
 ```bash
-git checkout master && git pull
+git checkout main && git pull
 git checkout -b release/vX.Y.Z
 ```
 
@@ -46,7 +46,7 @@ git push -u origin release/vX.Y.Z
 
 ## Step 5 -- Verify CI
 
-1. Run `gh pr create --title "Release vX.Y.Z" --body "Changelog update for vX.Y.Z patch release."` to open a PR against master.
+1. Run `gh pr create --title "Release vX.Y.Z" --body "Changelog update for vX.Y.Z patch release."` to open a PR against main.
 2. Wait for CI:
    ```bash
    gh pr checks <PR_NUMBER> --watch
@@ -62,7 +62,7 @@ gh pr merge <PR_NUMBER> --merge --delete-branch
 ## Step 7 -- Tag the release
 
 ```bash
-git checkout master && git pull
+git checkout main && git pull
 git tag -a vX.Y.Z -m "Version X.Y.Z"
 git push origin vX.Y.Z
 ```

{xarray_spatial-0.9.7 → xarray_spatial-0.9.9}/.claude/commands/sweep-accuracy.md

@@ -36,28 +36,30 @@ Store results in memory -- do NOT write intermediate files.
 
 ## Step 2 -- Load inspection state
 
-Read `.claude/sweep-accuracy-state.json`.
+Read `.claude/sweep-accuracy-state.csv`.
 
 If it does not exist, treat every module as never-inspected.
 
 If `$ARGUMENTS` contains `--reset-state`, delete the file and treat
 everything as never-inspected.
 
-State file schema:
-
-```json
-{
-  "inspections": {
-    "slope": {
-      "last_inspected": "2026-03-28T14:00:00Z",
-      "issue": 1042,
-      "severity_max": "HIGH",
-      "categories_found": [1, 3]
-    }
-  }
-}
+State file schema (one row per module):
+
+```
+module,last_inspected,issue,severity_max,categories_found,notes
+slope,2026-03-28,1042,HIGH,1;3,"optional single-line notes"
 ```
 
+- `categories_found` is a semicolon-separated integer list (empty when null).
+- `notes` is CSV-quoted; newlines must be flattened to spaces on write so
+  every module stays exactly one line.
+
+The file is registered with `merge=union` in `.gitattributes`, so two
+parallel sweeps touching different modules auto-merge without conflict.
+A transient duplicate-row state can occur after a merge if both branches
+modified the same module; the read-update-write cycle in step 5 keys rows
+by `module` and last-write-wins, so the next write cleans up.
+
 ## Step 3 -- Score each module
 
 ```
@@ -191,19 +193,54 @@ xrspatial/tests/general_checks.py for the cross-backend comparison helpers.
 3. For each real issue found, assign a severity (CRITICAL/HIGH/MEDIUM/LOW)
    and note the exact file and line number.
 
-4. If any CRITICAL or HIGH issue is found, run /rockout to fix it end-to-end
-   (GitHub issue, worktree branch, fix, tests, and PR).
-   For MEDIUM/LOW issues, document them but do not fix.
+4. If any CRITICAL, HIGH, or MEDIUM issue is found, run /rockout to fix it
+   end-to-end (GitHub issue, worktree branch, fix, tests, and PR).
+   For LOW issues, document them but do not fix.
 
 5. After finishing (whether you found issues or not), update the inspection
-   state file .claude/sweep-accuracy-state.json by reading its current
-   contents and adding/updating the entry for "{module}" with:
-   - "last_inspected": today's ISO date
-   - "issue": the issue number from rockout (or null if clean / MEDIUM-only)
-   - "severity_max": highest severity found (or null if clean)
-   - "categories_found": list of category numbers that had findings (e.g. [1, 3])
-
-   Then `git add .claude/sweep-accuracy-state.json` and commit it to the
+   state file .claude/sweep-accuracy-state.csv. The file is row-per-module
+   CSV with header:
+
+   `module,last_inspected,issue,severity_max,categories_found,notes`
+
+   Use this Python pattern to read, update, and write it (do NOT hand-edit
+   the file -- always go through csv.DictReader / csv.DictWriter so quoting
+   stays consistent):
+
+   ```python
+   import csv
+   from pathlib import Path
+
+   path = Path(".claude/sweep-accuracy-state.csv")
+   header = ["module", "last_inspected", "issue", "severity_max",
+             "categories_found", "notes"]
+
+   rows = {}
+   if path.exists():
+       with path.open() as f:
+           for r in csv.DictReader(f):
+               rows[r["module"]] = r  # last write wins on dupes
+
+   rows["{module}"] = {
+       "module": "{module}",
+       "last_inspected": "<today's ISO date, e.g. 2026-04-27>",
+       "issue": "<issue number from rockout, or empty string>",
+       "severity_max": "<HIGH|MEDIUM|LOW, or empty>",
+       "categories_found": "<semicolon-joined ints, e.g. 1;3, or empty>",
+       "notes": "<single-line notes (replace any newlines with spaces), or empty>",
+   }
+
+   with path.open("w", newline="") as f:
+       w = csv.DictWriter(f, fieldnames=header, quoting=csv.QUOTE_MINIMAL)
+       w.writeheader()
+       for m in sorted(rows):
+           w.writerow(rows[m])
+   ```
+
+   Use empty strings (not `null`) for missing values. Set `issue` to the
+   issue number when one was filed, otherwise leave it empty.
+
+   Then `git add .claude/sweep-accuracy-state.csv` and commit it to the
    worktree branch so the state update is included in the PR.
 
 Important:
@@ -236,7 +273,7 @@ State is updated by the subagents themselves (see agent prompt step 5).
 After completion, verify state with:
 
 ```
-cat .claude/sweep-accuracy-state.json
+column -t -s, .claude/sweep-accuracy-state.csv | less
 ```
 
 To reset all tracking: `/sweep-accuracy --reset-state`
@@ -248,8 +285,10 @@ To reset all tracking: `/sweep-accuracy --reset-state`
 - Do NOT modify any source files directly. Subagents handle fixes via /rockout.
 - Keep the output concise -- the table and agent dispatch are the deliverables.
 - If $ARGUMENTS is empty, use defaults: top 3, no category filter, no exclusions.
-- State file (`.claude/sweep-accuracy-state.json`) is tracked in git.
-  Subagents must `git add` and commit it so the state update lands in the PR.
+- State file (`.claude/sweep-accuracy-state.csv`) is tracked in git, with
+  `merge=union` set in `.gitattributes` so parallel sweeps touching
+  different modules auto-merge. Subagents must `git add` and commit it so
+  the state update lands in the PR.
 - For subpackage modules (geotiff, reproject, hydro), the subagent should read
   ALL `.py` files in the subpackage directory, not just `__init__.py`.
 - Only flag patterns that are ACTUALLY present in the code. Do not report

xarray_spatial-0.9.9/.claude/commands/sweep-api-consistency.md

@@ -0,0 +1,256 @@
+# API Consistency Sweep: Dispatch subagents to audit parameter naming and signature drift
+
+Audit xrspatial modules for API consistency issues across analogous public
+functions: parameter naming drift (`cellsize` vs `cell_size` vs `res`,
+`agg` vs `raster` vs `data`), inconsistent return-type shapes, missing or
+mismatched type hints, docstring/signature divergence. Cheap to find; makes
+the library feel polished and predictable. Subagents fix CRITICAL, HIGH,
+and MEDIUM findings via /rockout — but flag deprecation impact in the
+issue since renames are breaking changes.
+
+Optional arguments: $ARGUMENTS
+(e.g. `--top 3`, `--exclude slope,aspect`, `--only-terrain`, `--reset-state`)
+
+---
+
+## Step 1 -- Gather module metadata via git
+
+Enumerate candidate modules:
+
+**Single-file modules:** Every `.py` file directly under `xrspatial/`, excluding
+`__init__.py`, `_version.py`, `__main__.py`, `utils.py`, `accessor.py`,
+`preview.py`, `dataset_support.py`, `diagnostics.py`, `analytics.py`.
+
+**Subpackage modules:** `geotiff/`, `reproject/`, and `hydro/` directories under
+`xrspatial/`. Treat each as a single audit unit.
+
+For every module, collect:
+
+| Field | How |
+|-------|-----|
+| **last_modified** | `git log -1 --format=%aI -- <path>` |
+| **total_commits** | `git log --oneline -- <path> \| wc -l` |
+| **loc** | `wc -l < <path>` |
+| **public_funcs** | count of functions at module level (heuristic: `^def [a-z]`) |
+
+Store results in memory -- do NOT write intermediate files.
+
+## Step 2 -- Load inspection state
+
+Read `.claude/sweep-api-consistency-state.csv`.
+
+If it does not exist, treat every module as never-inspected. If
+`$ARGUMENTS` contains `--reset-state`, delete the file first.
+
+State file schema (one row per module):
+
+```
+module,last_inspected,issue,severity_max,categories_found,notes
+slope,2026-05-01,1042,HIGH,1;3,"optional single-line notes"
+```
+
+The file is registered with `merge=union` in `.gitattributes`.
+
+## Step 3 -- Score each module
+
+```
+days_since_inspected = (today - last_inspected).days   # 9999 if never
+days_since_modified  = (today - last_modified).days
+
+score = (days_since_inspected * 3)
+      + (public_funcs * 8)
+      + (total_commits * 0.3)
+      - (days_since_modified * 0.1)
+      + (loc * 0.03)
+```
+
+Rationale:
+- Public function count weighted heavily — consistency issues are
+  cross-function comparisons, so more functions = more comparison surface
+- Modules never inspected dominate
+- Recently modified slightly deprioritized
+
+## Step 4 -- Apply filters from $ARGUMENTS
+
+Same filter set as other sweeps: `--top N`, `--exclude`, `--only-terrain`,
+`--only-focal`, `--only-hydro`, `--only-io`, `--reset-state`.
+
+## Step 5 -- Print the ranked table and launch subagents
+
+### 5a. Print the ranked table
+
+Print a markdown table showing ALL scored modules sorted by score descending.
+
+### 5b. Launch subagents for the top N modules
+
+For each of the top N modules (default 3), launch an Agent in parallel using
+`isolation: "worktree"` and `mode: "auto"`. All N agents must be dispatched
+in a single message so they run concurrently.
+
+Each agent's prompt must be self-contained:
+
+```
+You are auditing the xrspatial module "{module}" for API consistency issues.
+
+This module has {commits} commits and {loc} lines of code.
+
+Read these files: {module_files}
+
+Also read xrspatial/__init__.py to see what is publicly re-exported, and
+xrspatial/utils.py for shared helpers.
+
+For comparison, read 2-3 sibling modules (analogous functions). Examples:
+- For aspect: also read slope.py and curvature.py
+- For erosion: also read morphology.py
+- For glcm: also read focal.py and convolution.py
+The point is to compare parameter naming and return shapes against
+modules with similar function families.
+
+**Your task:**
+
+1. Read all listed files thoroughly. For each public function, build a
+   small mental table of (function name, signature, return type).
+
+2. Audit for these 5 API-consistency categories. Only flag issues ACTUALLY
+   present.
+
+   **Cat 1 — Parameter naming drift**
+   - HIGH: same concept named differently across analogous public
+     functions in this module or in sibling modules. Common offenders:
+     `cellsize` vs `cell_size` vs `res` vs `resolution`
+     `agg` vs `raster` vs `data` vs `array`
+     `x` vs `xs` vs `x_coords`
+     `nodata` vs `_FillValue` vs `nodata_value`
+     `cmap` vs `color_map` vs `colormap`
+     `kernel` vs `weights` vs `mask`
+   - MEDIUM: same concept named consistently inside this module but
+     different from sibling modules
+   - MEDIUM: positional-vs-keyword convention drift (sibling functions
+     accept the same arg, one as positional, one as keyword-only)
+   Severity: HIGH if both names exist in the public API at the same time
+   (real user-facing inconsistency); MEDIUM otherwise
+
+   **Cat 2 — Return shape drift**
+   - HIGH: analogous functions return different types (one returns
+     DataArray, sibling returns Dataset for the same conceptual op)
+   - HIGH: tuple-return vs single-return drift (one function returns
+     `(slope, aspect)`, analog returns `slope` only — caller cannot
+     interchange)
+   - MEDIUM: result coord/attr conventions differ (one function emits
+     `attrs['units']`, sibling does not)
+   - MEDIUM: in-place vs returned-copy semantics drift
+   Severity: HIGH if it breaks substitutability between sibling functions
+
+   **Cat 3 — Type hints and docstrings**
+   - MEDIUM: missing type hints on a public function while sibling
+     functions in this module have them
+   - MEDIUM: type hint says `xr.DataArray` but the docstring example
+     passes a numpy array (or vice versa) — docs/types disagree
+   - MEDIUM: docstring lists a parameter that does not exist in the
+     signature (or omits one that does)
+   - MEDIUM: docstring says "Returns: DataArray" but the function returns
+     a tuple
+   - LOW: docstring style drift (numpy-style vs google-style mix)
+   Severity: MEDIUM (these are documentation bugs that mislead users)
+
+   **Cat 4 — Default value inconsistency**
+   - HIGH: same parameter has different defaults in analogous functions
+     (e.g. `kernel_size=3` in one function, `kernel_size=5` in sibling,
+     no documented reason)
+   - MEDIUM: default uses a mutable type (`def f(x=[])`) — Python anti-pattern
+   - MEDIUM: default `None` plus internal substitution where a literal
+     default would be clearer and equally correct
+   Severity: HIGH if user-surprise is likely (silent behavior change
+   when switching between sibling functions)
+
+   **Cat 5 — Public API surface drift**
+   - HIGH: function is called by tests and notebooks but is not in
+     `xrspatial/__init__.py` or in the module's `__all__` (orphan API)
+   - HIGH: function in `__all__` but undocumented in the docstring
+   - MEDIUM: deprecated alias still exported with no `DeprecationWarning`
+   - MEDIUM: private-looking name (`_foo`) but is referenced in tests as
+     if public
+   - LOW: `from .module import *` patterns that bring inconsistent
+     symbols into the public namespace
+   Severity: HIGH for orphan APIs (users find them, depend on them, then
+   break when they vanish)
+
+3. For each real issue, assign severity + file:line.
+
+4. If any CRITICAL, HIGH, or MEDIUM issue is found, run /rockout to fix it.
+   IMPORTANT: parameter renames are breaking changes — for HIGH
+   parameter-rename fixes, the rockout PR must add a deprecation
+   shim (accept both old and new names; emit DeprecationWarning on the
+   old name; update docs). Document this in the issue body. For LOW
+   issues, document but do not fix.
+
+5. Update .claude/sweep-api-consistency-state.csv using csv.DictReader/Writer:
+
+   ```python
+   import csv
+   from pathlib import Path
+
+   path = Path(".claude/sweep-api-consistency-state.csv")
+   header = ["module", "last_inspected", "issue", "severity_max",
+             "categories_found", "notes"]
+
+   rows = {}
+   if path.exists():
+       with path.open() as f:
+           for r in csv.DictReader(f):
+               rows[r["module"]] = r
+
+   rows["{module}"] = {
+       "module": "{module}",
+       "last_inspected": "<today's ISO date>",
+       "issue": "<issue number or empty>",
+       "severity_max": "<HIGH|MEDIUM|LOW or empty>",
+       "categories_found": "<semicolon-joined ints or empty>",
+       "notes": "<single-line notes or empty>",
+   }
+
+   with path.open("w", newline="") as f:
+       w = csv.DictWriter(f, fieldnames=header, quoting=csv.QUOTE_MINIMAL)
+       w.writeheader()
+       for m in sorted(rows):
+           w.writerow(rows[m])
+   ```
+
+   Then `git add` and commit.
+
+Important:
+- Only flag real consistency issues. The lib has 40+ modules — do not
+  list every minor naming difference; focus on user-facing surprise.
+- Compare against 2-3 sibling modules. Cross-cutting concerns (e.g.
+  cellsize naming convention) often span the whole library; if a rename
+  is safe in one module but breaks 20 others, surface that as a notes
+  comment, do not file a per-module issue.
+- For the hydro subpackage: pick one variant (d8) and check whether
+  dinf/mfd siblings agree.
+```
+
+### 5c. Print a status line
+
+After dispatching, print:
+
+```
+Launched {N} API consistency audit agents: {module1}, {module2}, {module3}
+```
+
+## Step 6 -- State updates
+
+To reset: `/sweep-api-consistency --reset-state`
+
+---
+
+## General Rules
+
+- Do NOT modify any source files directly. Subagents handle fixes.
+- Keep the output concise.
+- If $ARGUMENTS is empty, use defaults: top 3, no category filter, no
+  exclusions.
+- State file (`.claude/sweep-api-consistency-state.csv`) is tracked in
+  git with `merge=union`.
+- Renames are breaking. The fix path is a deprecation shim, not a
+  hard rename, unless the function has a clearly orphan/private status.
+- False positives are worse than missed issues.