rushabhcodes/fidget-counter

experiments/fresh-routing/README.md

# Fresh-routing experiment

The active1.0.28 circuit uses **tscircuit0.0.3060**, the newest npm version checked on2026-11-03. The dependency and hosted compiler are pinned. Production uses the refined new routes in the root files.

The initial trial removed every legacy manual path, prescribed router,13 positioned routing vias and saved routing input. A1.5mm ground-via stub became a global-net objective after removing its via; preflight selected a1.57mm other-pin endpoint and refused routing. The exploratory run removed that obsolete objective, then the newest default pipeline9 completed in13.3seconds from zero previous traces and a cache miss. It failed width/length/via/pad checks. The before-image initial-pcb.png and results.json record that rejected result. Failed manufacturing files and temporary logs are not shipped.

The selected revision uses19 newly generated top-layer critical paths and53 latest-pipeline traces, with four local branch repairs and three final clearance adjustments. All eight clock/load-cap branches retain10mm/zero-via constraints; the RF feed remains0.5mm/top-only. C18 retains3mm decoupling and an explicit1.5mm ground stub. No legacy path was restored. The new board has40 routing vias versus48, with unchanged28 fitted geometries and real electrical pin attributes/net membership. See the [fabrication review](../../validation/FABRICATION_REVIEW.md).

For another isolated trial, run `bun experiments/fresh-routing/prepare-experiment.mjs /absolute/outside-checkout/path experiments/fresh-routing/compiler.json`, install with Bun, repeat `bun install --frozen-lockfile`, and run that workspace's build. Omit the compiler JSON argument to query npm's current latest. The script refuses an existing destination and strips the active paths/vias without overwriting production. A raw router result requires the same electrical, mechanical and fabrication review before selection.

Production routing is reproducible from critical-routes.json, routed-paths.json and routing-contract.json. SHA256 output and physical/electrical input guards support stable-ID renumbering while rejecting real copper, connectivity, layer, location or constraint changes. The semantic routing reference and negative tests retain safeguards. Physical RF, oscillator, Hall, battery/holder, push-fit/adhesive retention and firmware qualification remain open.