Keep the calibration ladders in scripts/ladders, with the method
A ladder draws the candidates for a visual value side by side through MeshTerm's own renderer and live constants, so JP can choose by eye. The two that set constants are kept: hue_ladder.py (the node wheel's lightness, 0.72 on 2026-10-29) and seam_ladder.py (SEAM_BLUR, rebuilt from the 2026-09-16 tool), with contrast.py for the measurement that comes first and ladderkit.py for what they share. launch.ps1 opens a ladder in a new Windows Terminal window and waits for the ladder's marker file; -Snap also takes a screenshot through snap.ps1. It avoids the three traps that broke the launches this week: wt quoting a forwarded command line as one file name, the tab inheriting Claude Code's NO_COLOR=1, and Rich falling back to the 16-colour console API when virtual terminal processing is off. The README explains the method and the traps. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
This commit is contained in:
1 parent
598e53b488
commit
a493a6a5eb
10 files changed
+674
No files matched your search
@@ -0,0 +1,8 @@
|
||||
@echo off
|
||||
rem SPDX-License-Identifier: Apache-2.0
|
||||
rem
|
||||
rem The new Windows Terminal tab runs this file, with no arguments (refer to README.md,
|
||||
rem trap 1). launch.ps1 puts the ladder and its arguments in the environment.
|
||||
rem Claude Code runs its commands with NO_COLOR=1, and the tab gets it too (trap 2).
|
||||
set NO_COLOR=
|
||||
powershell.exe -NoExit -ExecutionPolicy Bypass -NoLogo -File "%~dp0run.ps1"
|
||||
Reference in new issue
Block a user