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

{env_able-1.2.2 → env_able-1.2.4}/.gitignore

@@ -66,3 +66,11 @@ skill/venv/
 # ── Handoff artifacts ─────────────────────────────────────────────────────────
 # The .skill is rebuilt by package_skill.py and already versioned in releases/.
 handoff/*.skill
+
+# ── Model binaries in the incubator ───────────────────────────────────────────
+# Esri .dlpk study material: 1.8 GB for ~600 MB of content, because every model is present
+# three times (extracted + .dlpk + .zip). Reference only — never part of a release.
+incubator/DeepLearningModelsESRI/
+*.dlpk
+*.pth
+*.pt

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

@@ -1,5 +1,114 @@
 # Changelog
 
+## [1.2.4] - 2026-08-20
+
+Two light-mode faults on the layout page, ribbon text that was below the contrast floor in both
+themes, and the install path on a machine with no conda. The first three are library changes
+(Atlas's own UI); the last is `preflight.py` and the handoff.
+
+### Fixed
+- **The north arrow's "N" was invisible in light mode.** `.lv-north span` used
+  `color: var(--bg-1)`, but it is printed on `.lv-page`, which is `background: white` in every
+  theme. So the label tracked the app theme while its surface did not: #111 on white in dark mode,
+  #ffffff on white in light. The arrow itself was always correct — fixed dark ink, as paper needs.
+  Now the label is too.
+
+- **The scale bar lost its alternating pattern in light mode**, for exactly the same reason and
+  unreported: the odd segments were `var(--bg-3)`, which is #1a1a1a in dark and **#ffffff** in
+  light, so the bar became a blank white rectangle on white paper. Found by auditing every `.lv-*`
+  rule for theme tokens once the north arrow showed what the mistake looked like. Two more paper
+  labels (`.lv-legend-hdr`, `.lv-small-label`) were washed out the same way and are now fixed ink.
+  The ribbon controls that share the `lv-` prefix are app chrome and stay themed — the distinction
+  is whether a thing is printed on the page or sits beside it.
+
+- **Ribbon text was too faint to read, in both themes.** Every resting state — the master row, the
+  sub-tabs and the group headings — used `--tx-9`. Measured against the ribbon surface that is
+  **2.43:1 in dark and 2.57:1 in light**, where text at 9–11px needs 4.5:1, so only the active tab
+  was legible and everything else read as a ghost. The resting state is now `--tx-4` (9.43:1 /
+  8.16:1), the tool buttons are `--tx-3` (11.27:1 / 10.96:1) since they are the actual verbs, the
+  active tab steps up to `--tx-1` so the hierarchy still reads, and the group headings gained
+  `font-weight: 600` — at 9px uppercase they had none at all.
+
+- **A freshly installed conda was invisible to preflight, which then told the user to install it
+  again.** Reported from a fresh Windows machine: after installing Miniforge and re-running
+  preflight with the Miniforge Python, it still printed "There is no conda here" and repeated the
+  Miniforge instructions — the exact problem just solved.
+
+  The cause was narrower than it looked and it was self-inflicted. preflight hands the run over to
+  `<skill>/venv`, and inside a venv `sys.prefix` is the venv, which never has a `conda-meta`
+  directory. So the conda check went blind the moment the handover happened, while conda sat in
+  `sys.base_prefix` two attributes away. There is now a `_conda_prefix()` that looks at both, and
+  `_conda_exe()` finds conda beside either prefix and at the usual per-user install roots
+  (`%USERPROFILE%\miniforge3` and friends) rather than only on `PATH` — which matters because a
+  silent Miniforge install touches neither PATH nor activation.
+
+- **preflight never actually ran `conda install gdal`.** It printed the command and stopped, so a
+  fresh Miniforge — which carries conda but not GDAL — left the user to work out an undocumented
+  step. It now runs it, into the conda prefix rather than `sys.prefix`, because conda cannot
+  install into a plain venv and the venv sees the base prefix anyway.
+
+### Added
+- **`--install-conda`.** On a machine with no conda and no compiler, preflight used to diagnose
+  correctly and then leave four manual steps with nothing linking them. This flag does the lot:
+  downloads Miniforge, installs it silently for the current user (no admin), installs GDAL from
+  conda-forge, then re-runs itself from the Miniforge Python so the venv inherits GDAL. Deliberately
+  **opt-in rather than default** — it fetches an executable and runs it, which should be something
+  asked for rather than something that happens. The failure message names the flag, so asking is
+  one copy-paste.
+- **`handoff/setup.ps1`.** Unpacks the `.skill` into `~/.claude/skills/atlas/` and runs preflight
+  with `--install-conda`, in one right-click. This is the route for when Claude Code's permission
+  rules decline to unpack a skill file into their own configuration directory, which is correct
+  behaviour but leaves a user with no obvious next move if nothing else is provided.
+
+## [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.4}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: env-able
-Version: 1.2.2
+Version: 1.2.4
 Summary: AI-ready GIS toolkit for energy and subsurface workflows.
 License: MIT
 License-File: LICENSE
@@ -390,6 +390,44 @@ print(f"{rows:,} rows written")
 ## Changelog
 ### Unreleased
 
+**Fixed**
+- **Light mode fixes on the layout page.** The north arrow's "N" and the scale bar's alternating
+  segments used theme tokens, but the page is white paper in every theme — so both went
+  white-on-white in light mode. Paper is not themed; those now use fixed ink, along with two washed
+  out labels found by auditing the rest.
+- **Ribbon text is readable now.** Every resting state used the lowest-contrast token: 2.43:1 in
+  dark, 2.57:1 in light, against the 4.5:1 that 9—11px text needs. Resting states move to
+  `--tx-4`, tool buttons to `--tx-3`, and the group headings gained weight.
+- **A freshly installed conda was invisible to preflight.** Inside its own venv, `sys.prefix` has no
+  `conda-meta`, so the conda check failed while conda sat in `sys.base_prefix` — meaning a user who
+  had just installed Miniforge to fix GDAL was told to install Miniforge. preflight now checks both
+  prefixes, finds conda by path as well as on PATH, and actually runs `conda install gdal` into the
+  conda prefix instead of printing the command and stopping.
+
+**Added**
+- **`--install-conda`** — downloads and silently installs Miniforge (no admin rights), installs GDAL
+  from conda-forge, then re-runs from that Python so the venv inherits it. Opt-in, not default: it
+  fetches an executable and runs it.
+- **`handoff/setup.ps1`** — unpacks the skill and sets it up in one right-click, for when Claude
+  Code declines to install a skill file into its own configuration directory.
+
+### v1.2.3 — 2026-08-18
+
+**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.4}/README.md

@@ -364,6 +364,44 @@ print(f"{rows:,} rows written")
 ## Changelog
 ### Unreleased
 
+**Fixed**
+- **Light mode fixes on the layout page.** The north arrow's "N" and the scale bar's alternating
+  segments used theme tokens, but the page is white paper in every theme — so both went
+  white-on-white in light mode. Paper is not themed; those now use fixed ink, along with two washed
+  out labels found by auditing the rest.
+- **Ribbon text is readable now.** Every resting state used the lowest-contrast token: 2.43:1 in
+  dark, 2.57:1 in light, against the 4.5:1 that 9—11px text needs. Resting states move to
+  `--tx-4`, tool buttons to `--tx-3`, and the group headings gained weight.
+- **A freshly installed conda was invisible to preflight.** Inside its own venv, `sys.prefix` has no
+  `conda-meta`, so the conda check failed while conda sat in `sys.base_prefix` — meaning a user who
+  had just installed Miniforge to fix GDAL was told to install Miniforge. preflight now checks both
+  prefixes, finds conda by path as well as on PATH, and actually runs `conda install gdal` into the
+  conda prefix instead of printing the command and stopping.
+
+**Added**
+- **`--install-conda`** — downloads and silently installs Miniforge (no admin rights), installs GDAL
+  from conda-forge, then re-runs from that Python so the venv inherits it. Opt-in, not default: it
+  fetches an executable and runs it.
+- **`handoff/setup.ps1`** — unpacks the skill and sets it up in one right-click, for when Claude
+  Code declines to install a skill file into its own configuration directory.
+
+### v1.2.3 — 2026-08-18
+
+**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.4}/pyproject.toml

@@ -4,7 +4,7 @@ build-backend = "hatchling.build"
 
 [project]
 name = "env-able"
-version = "1.2.2"
+version = "1.2.4"
 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.4}/src/env_able/__init__.py

@@ -1,4 +1,4 @@
-__version__ = "1.2.2"
+__version__ = "1.2.4"
 
 # 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

{env_able-1.2.2 → env_able-1.2.4}/src/env_able/atlas/index.html

@@ -215,13 +215,17 @@
   }
   #ribbon-mark .mk-a { fill: currentColor; }
   #ribbon-mark .mk-w { fill: #56BC2F; }
+  /* Ribbon text: the resting state is --tx-4, not --tx-9. Measured against --bg-2, tx-9 was
+     2.43:1 in dark and 2.57:1 in light, against the 4.5:1 that text this size needs — so every
+     tab except the active one was a ghost. tx-4 is 9.43:1 / 8.16:1, and the active state moves
+     to --tx-1 so "which tab am I on" still reads at a glance. */
   .r-master {
     display: flex; align-items: center; padding: 0 18px;
     font-size: 11px; font-weight: 700; letter-spacing: 0.8px; text-transform: uppercase;
-    color: var(--tx-9); cursor: pointer; border-bottom: 2px solid transparent; transition: color 0.15s;
+    color: var(--tx-4); cursor: pointer; border-bottom: 2px solid transparent; transition: color 0.15s;
     user-select: none;
   }
-  .r-master:hover { color: var(--tx-5); }
+  .r-master:hover { color: var(--tx-1); }
   .r-master.active { color: var(--tx-1); border-bottom-color: #0078d4; }
 
   /* Sub-tab row */
@@ -234,11 +238,11 @@
   .r-tab {
     display: flex; align-items: center; padding: 0 16px;
     font-size: 10px; font-weight: 600; letter-spacing: 0.6px; text-transform: uppercase;
-    color: var(--tx-9); cursor: pointer; border-bottom: 2px solid transparent; transition: color 0.15s;
+    color: var(--tx-4); cursor: pointer; border-bottom: 2px solid transparent; transition: color 0.15s;
     user-select: none;
   }
-  .r-tab:hover { color: var(--tx-5); }
-  .r-tab.active { color: var(--tx-3); border-bottom-color: #0078d4; }
+  .r-tab:hover { color: var(--tx-1); }
+  .r-tab.active { color: var(--tx-1); border-bottom-color: #0078d4; }
 
   #ribbon-panel { display: flex; align-items: stretch; height: 78px; padding: 0 8px; }
 
@@ -248,7 +252,10 @@
   }
   .r-group:last-child { border-right: none; }
   .r-controls { display: flex; gap: 6px; align-items: center; }
-  .r-label { font-size: 9px; color: var(--tx-9); letter-spacing: 1px; text-transform: uppercase; text-align: center; }
+  .r-label {
+    font-size: 10px; font-weight: 600; color: var(--tx-4); letter-spacing: 0.8px;
+    text-transform: uppercase; text-align: center;
+  }
 
   select.r-select {
     background: var(--bg-2); color: var(--tx-3); border: 1px solid var(--bd-3); border-radius: 3px;
@@ -270,7 +277,7 @@
     display: flex; flex-direction: column; align-items: center; justify-content: center;
     gap: 3px; padding: 4px 10px; min-width: 54px; height: 52px;
     background: none; border: 1px solid transparent; border-radius: 3px;
-    cursor: pointer; color: var(--tx-5); font-family: inherit; font-size: 10px;
+    cursor: pointer; color: var(--tx-3); font-family: inherit; font-size: 10px;
     letter-spacing: 0.4px; text-transform: uppercase; user-select: none;
     transition: background 0.1s, color 0.1s;
   }
@@ -485,9 +492,12 @@
     box-sizing: border-box; padding-bottom: 2px;
   }
   .lv-north span {
-    font-size: 9px; font-weight: 700; color: var(--bg-1); line-height: 1;
+    /* Fixed ink, not theme tokens. This label sits on .lv-page, which is `background: white`
+       in every theme — so `color: var(--bg-1)` meant a white N on white paper in light mode,
+       while the arrow beside it stayed correctly dark. The page is paper; paper is not themed. */
+    font-size: 9px; font-weight: 700; color: #111; line-height: 1;
     font-family: 'Roboto', 'Segoe UI', sans-serif;
-    text-shadow: 0 0 3px var(--tx-1), 0 0 6px var(--tx-1);
+    text-shadow: 0 0 3px #fff, 0 0 6px #fff;
   }
 
   .lv-scale-bar {
@@ -496,7 +506,9 @@
   .lv-scale-bar > div {
     flex: 1; height: 100%; border: 0.4px solid rgba(0,0,0,0.28);
   }
-  .lv-scale-bar > div:nth-child(odd)  { background: var(--bg-3); }
+  /* Fixed ink: these sit on .lv-page, which is white paper in every theme. Using --bg-3 made
+     the odd segments white-on-white in light mode, so the bar lost its alternating pattern. */
+  .lv-scale-bar > div:nth-child(odd)  { background: #1a1a1a; }
   .lv-scale-bar > div:nth-child(even) { background: white; }
 
   .lv-legend {
@@ -506,13 +518,13 @@
   }
   .lv-legend-hdr {
     display: block; padding: 5px 7px 3px;
-    font-size: 8px; color: var(--tx-9); letter-spacing: 1.5px; text-transform: uppercase;
+    font-size: 8px; color: #444; letter-spacing: 1.5px; text-transform: uppercase;
     font-family: 'Roboto', 'Segoe UI', sans-serif; font-weight: 600;
     border-bottom: 0.5px solid rgba(0,0,0,0.1);
   }
 
   .lv-small-label {
-    position: absolute; color: var(--tx-8);
+    position: absolute; color: #333;
     font-family: 'Roboto', 'Segoe UI', sans-serif;
     white-space: nowrap; transform: translateY(-50%);
   }