env-able 1.2.2__tar.gz → 1.2.3__tar.gz

{env_able-1.2.2 → env_able-1.2.3}/CHANGELOG.md

@@ -1,5 +1,54 @@
 # Changelog
 
+## [1.2.3] - 2026-08-18
+
+Skill-side only — no library code changed. The pair carries one version number, so publishing
+this stamps a library release whose content is identical to 1.2.2 except for this note.
+`dev/publish-patch.bat` will stamp a version above; fold this in and delete the heading.
+
+### Fixed
+- **GDAL on a managed Windows machine told you to do something impossible.** PyPI ships no
+  Windows wheel for GDAL, so pip compiles from source and needs a C++ compiler that a corporate
+  image usually lacks. Preflight then printed `conda install -c conda-forge gdal` — unfollowable
+  advice, on precisely the machine that reaches it, because there was no conda either.
+
+  It now inspects the machine before speaking: whether conda exists, whether some *other* Python
+  on the box can already import `osgeo`, and whether there is a compiler at all (asking `vswhere`
+  and PATH for `cl`, which is a different question from the C++ *runtime* it already checked).
+  Then it prints the one next step that applies — `conda install` where conda exists, or
+  **Miniforge** where it does not, with the no-admin silent-install flags.
+
+- **The venv could not see a GDAL installed after it was built, and nothing said so.** The venv is
+  created with `--system-site-packages`, so it inherits from whichever Python created it: build it
+  from a Python without GDAL and it stays without GDAL however much conda you install afterwards.
+  Preflight now detects that a Python with `osgeo` exists elsewhere and prints the exact rebuild
+  command, and **`--recreate-venv`** deletes and rebuilds from the interpreter you re-run with.
+  The re-exec strips the flag so a child run can never delete the venv it is executing inside.
+  This cost a real detour to discover on a colleague's first install.
+- **First run on a machine with nothing installed could not get past setup.** Reported from a
+  fresh PC: every document said "ask Claude to set it up", and Claude could not. Claude Code's
+  auto mode declined to execute `preflight.py` — a script it had just unpacked out of a skill
+  file — and then declined to write a wildcard `Bash(python *)` allow rule into `settings.json`
+  to get around itself. **Both refusals are correct**, and the second one especially: a skill
+  asking for broader execution rights looks exactly like a malicious skill doing the same, and
+  the classifier cannot tell this user's own code from a stranger's.
+
+  So the failure was ours, in the documentation. `INSTALL.md`, the handoff `README.md` and
+  `docs/atlas.md` now **lead with the command the user runs** — double-click
+  `scripts/setup_atlas.bat`, or one `preflight.py` line — and present "ask Claude" as the
+  convenience it is, with a plain warning that it may be refused and that the answer is never to
+  have Claude widen its own permissions. All three carry the `!`-prefixed form, which runs in the
+  user's own session so the output still lands in the conversation.
+
+  `SKILL.md` gained the matching instruction for Claude: if you are not permitted to run it, hand
+  the command over in one line and stop — do not edit `settings.json`, do not ask for a wildcard
+  allow rule, do not retry hoping it passes. On a fresh machine being blocked is the normal
+  outcome, and retrying spends the user's first five minutes with the product on nothing.
+
+  Also documented: a `.skill` is a zip, so unpacking it into `%USERPROFILE%\.claude\skills\atlas\`
+  installs it just as well as **Settings → Capabilities → Save Skill**. That is what Claude did
+  unprompted on the fresh machine, and it worked — worth writing down rather than rediscovering.
+
 ## [1.2.2] - 2026-08-17
 
 ### Fixed

{env_able-1.2.2 → env_able-1.2.3}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: env-able
-Version: 1.2.2
+Version: 1.2.3
 Summary: AI-ready GIS toolkit for energy and subsurface workflows.
 License: MIT
 License-File: LICENSE
@@ -390,6 +390,21 @@ print(f"{rows:,} rows written")
 ## Changelog
 ### Unreleased
 
+**Fixed**
+- **GDAL setup on managed Windows.** PyPI has no Windows GDAL wheel, so pip builds from source and
+  fails without a compiler — and preflight then suggested conda, on a machine with no conda.
+  It now checks what the machine actually has and names the one route that works, including
+  **Miniforge** (no admin needed). New **`--recreate-venv`**, because the venv only sees packages
+  from the Python that created it, so a GDAL installed afterwards needs the venv rebuilt.
+- **First-run setup on a clean machine.** Every document said "ask Claude to install it", and on a
+  fresh PC Claude cannot: auto mode declines to run a script just unpacked from a skill file, and
+  declines to grant itself permission to. Both refusals are right. The docs now lead with the
+  command the user runs — `scripts/setup_atlas.bat`, or one `preflight.py` line, with the
+  `!`-prefixed variant for the Claude prompt — and `SKILL.md` tells Claude to hand the command
+  over rather than retry or touch `settings.json`. No library code changed.
+
+### v1.2.2 — 2026-08-17
+
 **Fixed**
 - **The README documented three operations out of seven.** `Union`, `Dissolve`, `SpatialJoin`
   and `Near` had no entry at all — for several releases, on the page PyPI renders as the front

{env_able-1.2.2 → env_able-1.2.3}/README.md

@@ -364,6 +364,21 @@ print(f"{rows:,} rows written")
 ## Changelog
 ### Unreleased
 
+**Fixed**
+- **GDAL setup on managed Windows.** PyPI has no Windows GDAL wheel, so pip builds from source and
+  fails without a compiler — and preflight then suggested conda, on a machine with no conda.
+  It now checks what the machine actually has and names the one route that works, including
+  **Miniforge** (no admin needed). New **`--recreate-venv`**, because the venv only sees packages
+  from the Python that created it, so a GDAL installed afterwards needs the venv rebuilt.
+- **First-run setup on a clean machine.** Every document said "ask Claude to install it", and on a
+  fresh PC Claude cannot: auto mode declines to run a script just unpacked from a skill file, and
+  declines to grant itself permission to. Both refusals are right. The docs now lead with the
+  command the user runs — `scripts/setup_atlas.bat`, or one `preflight.py` line, with the
+  `!`-prefixed variant for the Claude prompt — and `SKILL.md` tells Claude to hand the command
+  over rather than retry or touch `settings.json`. No library code changed.
+
+### v1.2.2 — 2026-08-17
+
 **Fixed**
 - **The README documented three operations out of seven.** `Union`, `Dissolve`, `SpatialJoin`
   and `Near` had no entry at all — for several releases, on the page PyPI renders as the front

{env_able-1.2.2 → env_able-1.2.3}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "env-able"
-version = "1.2.2"
+version = "1.2.3"
 description = "AI-ready GIS toolkit for energy and subsurface workflows."
 readme = "README.md"
 requires-python = ">=3.8"

{env_able-1.2.2 → env_able-1.2.3}/src/env_able/__init__.py

@@ -1,4 +1,4 @@
-__version__ = "1.2.2"
+__version__ = "1.2.3"
 
 # Resolve GDAL_DATA / PROJ_LIB before anything imports osgeo. IDEs and bare
 # `python script.py` runs skip conda's activation scripts, which is where those