T-1272 (a verification, as rescoped). No directory Python imports carries a
hyphen any more. The hyphenated script trees were emptied by the per-domain
moves, not renamed. What still has a hyphen is never imported: the three Rust
crates, and the provenance under tooling/archive/, which has no __init__.py.
CLAUDE.md and DEVOPS still pointed at tooling/db/, and pyproject still
predicted the rename; all three fixed.
T-1274. E402, E702 and F841 were ignored for the whole tree from T-1066 on
(43 / 41 / 21 violations). All three are back on:
- E402: the planet modules' imports only sat below their path constants
because they used to follow a sys.path insert, gone since T-1288. Hoisted.
The Blender payloads keep a per-file exception, because they extend
sys.path under Blender's own Python.
- E702: the paired component assignments in three planet maths files are
deliberate, so they get a per-file exception scoped to those files.
- F841: 10 dead locals removed from live code, each checked for side effects
first; logo_uv keeps its call, which creates the UV layer.
- tooling/archive/ is excluded: it is provenance, and "fixing" a one-shot
falsifies the record of what actually ran.
Evidence the lint is real: violations fed through stdin fire in a domain
module, and E402 stays quiet only on a payload path. Evidence nothing moved:
globe renders are pixel-identical before and after for an oceanic, a frozen
and a gas-giant body, and the ledger edit was regenerated (stamp fresh,
generated_brands.toml unchanged).
One finding, noted in the code rather than fixed: planet_renderer computed an
oblate-spheroid ray scale and never used it, so `oblateness` shapes no globe.
Wiring it in would change every globe render; that is a decision to make
deliberately, not a lint fix.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
The 30-file tree moves under atlas as its third rung (D-243), ten verbs
fronting it. Each verb restates its module's options so `--help` describes
something; tooling/test_planet_router.py hands every declared option to the
module's own argparse and fails on drift, and now runs in make test-tooling.
The 2026-09-02 half of this move had converted the top-level imports and the
repo roots. Finishing it found what the half-move left:
- Lazy in-function imports, and all of sol_data/, still named siblings bare.
They resolved only through sys.path.insert hacks, so under reach the first
globe render in generate, batch or sol-import would have raised
ModuleNotFoundError. Qualified; the hacks are gone.
- 247 print() calls and a stdout progress writer that fired once per 8 KB
block. Report verbs (audit, quality) write through console.out, progress
through console.event, and download progress is throttled to 10% steps
so a job log is not tens of thousands of lines.
- Every error exit raises ReachError with a fix.
Two checks that could not fail:
- batch --verify-determinism printed a warning and exited 0 on a mismatch.
- import-provinces exited 0 with errors > 0.
Both now raise. The 271-body bake is only safe to re-run because the first
one holds.
sol-import --body is action="append" in the module but the router took one
value, so --body GJ0d --body GJ0e kept one. Now repeatable, and _flags repeats
list options.
test_conformance walked one level, so a nested group was reported as a verb
missing @command and its ten verbs were never checked. It recurses now;
proven by stripping @command from `planet quality` and watching it fail.
Stray PNGs from the 2026-09-03 runaway router-test run are parked in
.cache/t1288-stray-pngs/, not committed. Their reliefmaps differ from HEAD
while the heightmap regenerated byte-identical — filed as T-1291.
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
jpmschweitzerandClaude Opus 5.5