kerfmaster — the pipeline
The same 396 pins, on the axis the software is actually built along · updated 2026-11-20
By subjectBy pipeline stageBy evidenceOpen questions
▶ A pin says what we decided. Its contract says what the stage takes, what it makes, and what makes it fail there. Once those names line up, a gap stops being something we notice by luck: everything under Holes below was computed from the contracts, not spotted by eye.
⚠ Unknown artifact name(s): contours, def-input-formats, dxf, healing, nc-audit, nest, rate-table, shop-data, shop-dxf, start-points, vector — not in the vocabulary, so any hole they cause is a spelling mistake, not a finding.
Holes — what a stage needs that nothing upstream makes
absentdef-input-formats — nothing produces it. Needed at: ?. Produced by: nobody. No pin anywhere claims to produce this. Either a stage is missing from the list, or the name is wrong.
absenthealing — nothing produces it. Needed at: ?. Produced by: nobody. No pin anywhere claims to produce this. Either a stage is missing from the list, or the name is wrong.
absentshop-data — nothing produces it. Needed at: Intake. Produced by: nobody. No pin anywhere claims to produce this. Either a stage is missing from the list, or the name is wrong.
absentstack-up — nothing produces it. Needed at: Bridges. Produced by: nobody. No pin anywhere claims to produce this. Either a stage is missing from the list, or the name is wrong.
absentstart-points — nothing produces it. Needed at: ?. Produced by: nobody. No pin anywhere claims to produce this. Either a stage is missing from the list, or the name is wrong.
absentvector — nothing produces it. Needed at: ?, Intake. Produced by: nobody. No pin anywhere claims to produce this. Either a stage is missing from the list, or the name is wrong.
unrecordedcut-order — consumed by a record pin, produced by no record pin. Needed at: Cut order, Post. Produced by: rapid-over-slug (ruling). A pin describing what the code DOES depends on this, and nothing typed `record` makes it. Either the code does not produce it, or it does and this list never said so — both are defects of the list, and it cannot tell you which.
unrecordedtrue-size — consumed by a record pin, produced by no record pin. Needed at: Intake. Produced by: spec-checks (ruling), scale-gate (ruling). A pin describing what the code DOES depends on this, and nothing typed `record` makes it. Either the code does not produce it, or it does and this list never said so — both are defects of the list, and it cannot tell you which.
plannedbridged-part — planned both ends. Needed at: Nest. Produced by: bridges (intent), assembly-connectivity (intent), concealed-envelope (intent). No record pin on either side — a gap in the plan, not in the code. Fine now; a hole the day it ships.
plannedidentified-file — planned both ends. Needed at: Scale & units. Produced by: customer-portal (ruling), preflight-gate (ruling), delivery-rules (ruling), preflight-checks (intent), uploader (intent). No record pin on either side — a gap in the plan, not in the code. Fine now; a hole the day it ships.
plannedsheet-layout — planned both ends. Needed at: Nest, Report. Produced by: nesting (intent), tabs-nest (ruling). No record pin on either side — a gap in the plan, not in the code. Fine now; a hole the day it ships.
Intake
What arrives, whether we can read it, and whether it is allowed through the gate.
18 pins — 5 intent · 1 question · 5 record · 7 ruling
takescustomer-fileshop-data ?true-sizevector ?
makescontours ?healed-geometryidentified-filerate-table ?raw-geometry
- •Layer recordmixed — A named grouping of entities in a DXF — how we separate cut geometry from mark-up, and the original from our work.
- •Quote mode ruling — Sales' stripped surface: upload → material → auto-nest → estimates → pricing. It moves the start, not the program.
- 2PDF → G-code intentmixed
fails if A Bézier flattened into line segments; a PDF clip path read as cut geometry. - 2a.ai / SVG / PDF vector input recordmixed
fails if A Bézier flattened into line segments; a fit demanded tighter than the format itself carries; a tangent taken from the chord at a corner handle. - 2cThe vector front-end — built, measured, and where it resumes recordd10
fails if read() proceeding without a stated real-world size (it raises ScaleUnknown, deliberately); a fit-induced kink; deviation quoted without splitting out the format's own inherent error. - 7dSales surface — stripped intake/quote mode; jobs may originate in sales rulingreads as fact
fails if Building a separate quoting product; hardcoding any fee or estimate constant; letting quote nests bypass the production gates when promoted. - 7gCustomer self-serve surface — upload, educate, heal, approve, quote rulingmixedreads as fact
fails if Letting a customer approval bypass the operator, or asking the customer to approve anything sacrificial (tabs, leads, cut order) — they approve pricing and bridges, nothing else. - 7hShop-rate entry is an INTERFACE, not a spreadsheet — and the product direction behind it rulingmixed
fails if A rate value saved without who supplied it and on what authority; a 'measured' claim with no how; reads left open (this is the shop's pricing). - 8Cut vs. engrave rule questionmixed
fails if Engrave geometry cut clean through, or cut geometry engraved — with no rule held, either is currently possible. - 12Sub-kerf degenerate-speck drop intentmixed
fails if A feature above kerf width dropped as a speck; a sub-kerf speck left in to distort the fidelity score. - •DWG input support record
fails if A .dwg that converts silently wrong — conversion is a step, not a read. - 14Preflight — the intake gate rulingmixedd10deferred d14
fails if A file entering preprocessing that failed a check, or passed one we never ran. - 14aHow to deliver files to us ruling
fails if A file converted by the customer before it reached us, accepted as if native. - 14cThe check list — what is fully automated, what needs a human intentmixed
fails if A question of intent answered by automation; a check listed as automated that a human actually does. - 14dThe uploader — how the automation would work intent
fails if A report card that does not end in one clear question or a release. - 14eThe education we give customers intentmixed
fails if A rejection message that does not teach what to do differently. - 14fWhat our DXF reader actually sees — and what it silently does not rulingmixeddeferred d14
fails if An entity type dropped without a word to anyone. - •Reading an .ai by named layer — mvt_layers.py record
fails if Quoting a part size that is really the artboard clip; reading a layered .ai as one flat drawing.
Scale & units
Turning file numbers into real-world size. A guess here is wrong by a factor.
2 pins — 2 ruling
takesidentified-fileraw-geometry
makestrue-size
Heal
Facets and Béziers into true lines and arcs, faithful to the customer's actual shape.
9 pins — 4 record · 5 ruling
takesraw-geometry
makeshealed-geometry
- •Healing rules (dirty CAD → clean arcs) rulingmixedd11
fails if A fit-induced jog anywhere; deviation over the tolerance gate measured against the TRUE source; a native bulge re-fitted; a rule that only works on one file.; a sub-tolerance smoothing pass keyed to feature size rather than to deviation; a smoothing allowance carried as a separate number from the measured end-to-end deviation; a corner rounded when the feature it sits on is NOT inside the operator's tolerance.; one tolerance applied to a whole file where the features have different functions; a default gate defended on a feature whose purpose does not need it. - •Fidelity record — How closely our healed output matches the customer’s TRUE shape — the ‘did we change the part?’ number.
- •Jog / kink ruling — A non-tangent break where the true shape is smooth; a fit-induced one is an automatic FAIL.
- •Spike vs. sustained recordmixedd11 — How the healer tells a real corner (keep sharp) from a coarse arc (smooth it).
- •Bulge ruling — The DXF encoding of a native arc; we preserve these exactly, never re-fit them.
- •Polylining ruling — Exploding a real curve into hundreds of tiny straight lines — the damage we exist to undo.
- •Healing / healed recordmixed — Healing is the process; healed is the result — the clean geometry every downstream stage works from.
- •Tolerance gate vs. fit target record — The tol argument is an accept/reject gate — not a fit goal; we always best-fit tighter.
- •Repair mode must compare the two sides of a mirror split rulingmixed — Jordan 2026-08-10: repair mode must compare left and right of the split. BUILT: repair.py symmetrize() rebuilds meant-to-be-symmetric contours as left half + mirror; kern() does operator-directed letter respacing. Build 022.
QC
What the geometry IS: closed or open, inside or outside, island or hole, ours or the customer's.
7 pins — 2 intent · 1 question · 3 record · 1 ruling
takesraw-geometry
makesdeliveryhealed-geometrytopology
- •Island recordclosed d16 — Kept metal fully surrounded by cut-away area; drops out unless held by bridges.
- •Undersized ruling — Narrower than the table minimum for that material and thickness — a flag for the operator, never a silent re-cut.
- 9Auto-close threshold questionmixeddeferred d14
fails if A gap snapped shut that a human should have seen; a gap flagged that every file has. - •QC step 2 — QC_FIX correction layer intentmixed
fails if A correction applied silently rather than as a separate, labelled, deletable layer. - •QC step 3 — delivery intentmixed
fails if Fixes counted on the banner that are not visible on the board. - •QC step 1 — detection record
fails if An open contour or duplicate segment that does not reach the board gate. - 13Source-defect flag — steps that are in the customer's file recordmixed
fails if A defect that is in the customer's own file reported as ours, or silently healed away.
Bridges
Permanent holds so islands stay in the finished part.
4 pins — 3 intent · 1 ruling
takesmaterial-tablestack-uptopology
makesbridged-part
Starts & leads
Where each contour begins, where the pierce lands, and how much clear air it has.
4 pins — 2 intent · 1 record · 1 ruling
takeshealed-geometrymachine-profilematerial-tabletopology
makesboundaries-with-startsoperator-choices
- •Lead-in / lead-out rulingclosed d18 — The short ramp on/off the cut path where the pierce lives; never inside a tab span.
- 4Lead-in/out + cut-order optimization intentmixed
fails if A lead crossing geometry; a pierce whose clear air is under the standoff and is not reported; comp side inferred from geometry rather than declared. - 4bOperator pick surface — per-boundary overrides intentmixed
fails if A per-boundary choice made silently by the tool where the record says the operator picks. - 4dStart points & lead geometry recordmixedd3d5d6d7closed d18
fails if A start at a sharp point of the design; a start chosen before its lead, so the boundary ends up pierced with no lead; a corner inside the tab span, unreported.
Cut order
The time-ordering. This is a safety stage, not an optimisation.
2 pins — 1 record · 1 ruling
takesboundaries-with-startstopology
makescut-order
Nest
Parts onto a sheet, and the sacrificial tabs that hold them there.
8 pins — 1 intent · 7 ruling
takesbridged-partmaterial-table
makessheet-layout
- •Tab ruling — A deliberately breakable connection — holds parts in the sheet while cutting, snapped off afterwards.
- •Wirejoint (old CAM term) ruling — The old CAM's word for the sacrificial micro-joint — what we call a tab. Confirmed by Jordan, 2026-08-28.
- •Nesting ruling — Packing multiple parts on a stock sheet for best yield; must honour the bed envelope. Two kinds with opposite pipeline orders: true nesting and part-by-part nesting (Jordan, 2026-08-27).
- •True nesting ruling — The SAME part duplicated over and over on the sheet (Jordan, 2026-08-27). The toolpath is established FIRST on the single part; the nest then duplicates one short piece of G-code per placement.
- •Part-by-part nesting ruling — Several UNIQUE shapes nested on one sheet (Jordan's shop term for the files: Torongo files). The nest is laid out FIRST; the toolpath is established after, on the assembled sheet.
- •Bounding box ruling — The smallest upright rectangle around a part — a quick estimate only. Nest gaps are NEVER measured between bounding boxes, always between actual part geometry (Jordan, 2026-08-26).
- 3Nesting intentmixed
fails if A layout over the 80″×160″ bed; parts overlapping; yield reported without the sheet it was measured on. - 3aTabs — nest-time hold & break-off rulingmixed
fails if A tab that will not snap by hand; a lead or pierce inside a tab span; a width used that is not in the material table.
Post
Fanuc macro-B out, including the slug-retention tabs.
8 pins — 1 question · 2 record · 5 ruling
takescut-ordermaterial-tabletopology
makesgcodemachine-profilenc-audit ?
- •Output & G-code rules ruling
fails if Anything emitted that is not G1/G2/G3; a curve posted as segments; a native arc re-fitted; the G52 margin baked into coordinates instead of applied at post. - •Slug-retention tab recordmixed — A third kind of hold: material left uncut so an interior drop-out can't fall through. Width now production-validated — see item 3b.
- •Fanuc macro-B ruling — Our production G-code dialect: O-number program, #-vars, G41/42 comp, M98 pierce, true arcs.
- •Subprogram rulingclosed d13 — Jordan, 2026-08-04: one part's G-code, made from a DXF, called repeatedly across a nest.
- 3bSlug-retention tab rules — production-validated rulingmixed
fails if A slug over the drop-through size emitted with no tab; a tab narrower than the table for that material; a job carrying another machine's drop-through; a posted job with no numbered slug report. - 4aPost dialect — match the shop's G-code exactly recordclosed d13
fails if A condition var outside #102–#111/#121/#122; the G52 margin missing; a difference from the shop's dialect that is not written down. - •M-code glossary — RECEIVED, and Jordan has ruled on every code questionmixedclosed d13
fails if An M-code emitted whose meaning we inferred rather than confirmed. - 4d-3Beam compensation column + micro-segment cleanup ruling
fails if A compensated block shorter than the material's beam comp value in anything we post; a micro-segment surviving into G-code; a material row posting without a beam_comp value.
Report
What a human is given: boards, sheets, slug reports, quotes.
17 pins — 7 intent · 1 question · 6 record · 3 ruling
takesgcodehealed-geometrymachine-profilesheet-layouttopology
makesdeliverymaterial-table
Cross-cutting
Rules that hold at every stage — they are not a step in the pipeline, they are conditions on all of them.
25 pins — 1 intent · 1 question · 5 record · 18 ruling
- •Mission & the pipeline recordmixed
fails if Any stage's own gate fails, or a stage is skipped without saying so. - •Working discipline ruling
fails if A claim stated without being verified; work committed but not pushed off-box; a secret in the code; a call of Jordan's parked for Aristide to re-confirm. - •Evidence discipline — controls, and the scope of a claim rulingclosed d15
fails if A control that shares a code path with the thing it checks; a boolean that changes nothing reported as a pass; a claim stated wider than what was measured. - •Thou ruling — One thousandth of an inch (0.001″) — our working unit for tolerance and fidelity.
- •Kerf ruling — The width of material the beam removes (~7 thou); the floor for real detail.
- •Bed envelope rulingmixedd1d2closed d17 — The machine’s cuttable area: 80″ × 160″. We flag anything that exceeds it.
- •Workbench ruling — The docked ground state of the picked A+C interface — every station starts identical; ships first.
- •Graft ruling — The tear-off machinery under the Workbench — panels detach, float, cross monitors; snap back in one click.
- •Workspace ruling — A named, per-user saved panel arrangement (Adobe-style); the default workspace IS the Workbench.
- •Interrupt-and-return ruling — Pull a delivered job back in, change it, repost, and resume — losslessly, as a first-class workflow.
- •Gate vocabulary ruling — cadmaster's owned visual status language — colors, dots, glows, flags — taught once in the first-run tour.
- •Units as a skin ruling — Display/input units are a per-user skin; every field takes a unit suffix (3mm converts); inches stay the internal truth.
- 4cTable data format — agree once, use everywhere questionclosed d17closed d18
fails if A number that lives in prose instead of a table; two tables with two shapes; a value an operator cannot override; a lookup that answers with a neighbouring thickness instead of refusing. - 4gmachine.json and the material table — the numbers, and where each came from recordclosed d19
fails if A number typed into Python that belongs to a laser or a material; a lookup that answers from a neighbouring thickness; a value with no source beside it. - 4hEvery number carries how well we know it — and the register audits itself record
fails if A number in the code that the register never claimed; a register entry for a constant that no longer exists; a copy that no longer equals what it copies; an assumed number quoted to a customer as if it were measured. - 4iThe named corpus — every file we hold, run every time, with the reason beside each number recordd20d21
fails if A change to the healer, the reader or the poster landing with no corpus run beside it; an expectation promoted to `rule` with no reason written; a failing `rule` accepted with --record instead of answered. - 4jEvery open question says who answers it and what it is holding up record
fails if A question parked without naming who can answer it; a question written inside one pin while it silently blocks five; a reference to a pin, defect or number that no longer exists; an answer that arrives and is not written back. - 6aUI architecture & the pipeline model rulingmixedd11
fails if A stage that runs without an accept gate; a result with no provenance; the engine reachable only through the UI; a customer file leaving the box. - 6bThe interface is reverse-engineered FROM this list rulingclosed d19
fails if A screen designed before the stage it shows is defined; a pin's record content changed in a different commit from the code it describes. - 7Interface workflow intentmixed
fails if An operator step with no way back; a fix accepted without being shown. - 7aPaper design v1 — the document under walkthrough ruling
fails if Any interface code written before both partners sign off on the paper; any stage in the app that skips a gate the paper lists. - 7bInterface look & layout — inputs recorded, design gated on research rulingmixed
fails if Any mockup or interface code before the love/hate research is delivered and the panel-layout choice is made; treating the two panel proposals as decided. - 7eUnits — per-user display units, unit-suffix input everywhere, inches stay the internal truth ruling
fails if Letting a display-unit preference leak into stored geometry, table values or posted NC; a field that accepts only the session unit. - 7fFirst-run tour + help, manual and bug-report from anywhere (auto-capture to partners' server) rulingmixed
fails if Building the tour or bug pipeline before the auto-capture spec and server details arrive; a help/bug entry point that is only on some screens. - 11Best-practices defaults rulingmixed
fails if A default that cannot be overridden in the interface.
Unassigned
No stage declared. Deliberately visible.
233 pins — 24 intent · 13 question · 158 record · 38 ruling
- •Mission: clean, efficient nests and sane cut sequences (Jordan, 2026-11-10) intent — INTENT (Jordan 2026-11-10): two-part mission, run as a discussion with ideas, testing, trial and error. (1) Nesting: the algorithms do not produce clean, efficient, ideal nests -- fix that without breaking speed's work. (2) Sequencing: in the last 2-4 weeks nest cut sequences went chaotic; expect different sequence approaches for different scenarios, like the nesting algorithms. Owner now: this dev chat (Aristide and the speed chat moved on, Jordan 2026-11-10); every change is tested and its speed cost named. Trigger example: rec160281 round part (4.23 in) x 341 on 120x60 came out as a free scatter (winner 'free'), fewer than a plain grid (~351) or staggered (~398, unverified), chaotic travel. Proposed order: scorecard (parts/sheet, material, regularity, leftover, travel, crossings, nest time) -> sequencing regression (suspects O95 2026-11-05, O100 2026-11-07, unproven) -> nesting (one part x N first). Reference set: Jordan will supply the old CAM's nest PDFs + their G-code; we ask for the part files and material for each. FIRST FINDINGS 2026-11-10 21:25 UTC (measured, cut-order travel between part centres, same saved nests replayed on old code via scratch servers; a proxy -- crossings over cut parts not yet counted): rec160281 341 rounds (free scatter, macro form): before O95 5914 in -> O95 step 1 8648 -> now 7959; nearest-next would be ~1738; 172 hops over 15 in. Six other recent part-list jobs: O95 made travel SHORTER or equal (e.g. ll-lcb 775->531, ap-bp 441->251, t014168 792->570), but most still sit well above nearest-next (tl-1016-81 sheet 1: 5306 vs 1072). Reading: no single sequencing commit in the window explains it; the order rules (strips/columns/macro runs) assume a tidy layout, and the free-scatter nests break them -- nest and sequence are coupled. Next: check when the packer started picking 'free' scatters, and score orders by crossings over cut parts too. PLAN CHANGE 2026-11-10 21:28 UTC (Jordan, ruling): stop hunting what went wrong in the last weeks. Jordan sends good nests from the old CAM (nest PDF + the G-code it produced + his pro/con commentary); those set the new goal. Work: parse each G-code for placements and cut order, run the same parts through KerfMaster, compare side by side, then improve on them. The regression hunt (packer 'free' history) is dropped; the crossings count stays as a scorecard measure. EXAMPLE 1 (Jordan 2026-11-10, 'a really good example... nothing I'd want to improve' apart from post changes already made): 2800X 10.5 REV D, NC 3387, SUSN7 0.125, 60x36 sheet, 40 parts. Files in dev tree incoming/1794346684_* (DXF), 1794346685_* (nest PDF), 1794346687_3453629_3387.NC. Read from the G-code: two P9997 arrays (K5 rows, J6.5288 Y pitch = part 6.0288 + 0.5; Q4 cols, I13.55 X pitch), second array = part turned 180, shifted X+7.15 Y+0.12, so T-shapes interlock; array 1 cuts all 20 then array 2 all 20; per part holes first then outer last; 0.150 leads; outer G41 CW with a 0.030 end gap (part tab); holes full G3 circles, no slug tab. Next: run the same part through KerfMaster on the same sheet and compare (parts/sheet, layout, macros, order, travel, crossings). EXAMPLE 1 FIRST RUN 2026-11-10 21:46 UTC (dev :8474, list job 2800x-10-5-rev-d-ex1-1794347122, Stainless,0.125 per Jordan's yes, 60x36, qty 40): (a) UNITS: the DXF has no $INSUNITS and its header $EXTMIN/$EXTMAX span 234 while the geometry spans ~11; dxf_io trusts the header and read the part as mm (25x small). Corrected by the units door to inch; part then 11.25 x 6.0288, same as the G-code. Not fixed; raised with Jordan. (b) With the row's default rotate 360 (no turning) the pack gave 2 sheets x 20 (winner repeat). (c) With rotate 180: 40 on ONE sheet in ~3 s, winner 'oblique lattice', used X 58.56 (old CAM ~59.25), 20 at 0 and 20 at 180, interlocked, but the columns step diagonally instead of straight rows, and the cut order (screen) jumps diagonally. Post/macro count and travel not yet measured. RULING + SPEED COST 2026-11-10 21:53 UTC (Jordan: 'I want 0/180 to be the default anyway. For all jobs.'): NOT BUILT YET -- held under speed-aware-dev because the cost is over the 1 s line. Measured in-process pack with rejudge (caches as live), copies of saved list jobs with every row set to 180 vs 360, run twice, timings repeated within 0.1 s: brass-disc 0.4 -> 6.2 s (same 47, used X 14.52 -> 13.97), m1-edr 2.0 -> 12.1 s (same 72, X 107.8 -> 106.0), rec160281 6.9 -> 9.8 s (341 -> 345), t014168 4.4 -> 27.2 s (same 104, same X). The disc is a circle (a 180 turn changes nothing), so its gain comes from the lattice method becoming eligible, not the turn. Default lives in ~10 row-creation sites (app.js x8, server.py x2) plus 360 fallbacks for rows with no value; stored lists keep their saved value. Waiting on Jordan: accept the cost, or first make 180 cheap (skip parts that look the same turned, cap the extra methods). O105 WIP 2026-11-11 13:30 UTC (tag wip/O105, patch /home/cloudally/o105-tidy-lattice.patch; NOT on dev). Jordan 2026-11-11: 'Stop being so focused on the time, focus on doing it right. We can always work on the time after the fact.' Finding: the lattice method already finds the pair once and copies it; on example 1 it picked a creeping slant (Y pitch 8.170, advance 8.894/6.127) because it saves a sliver of area. Straight rows exist in its own search: pair 0/180, Y pitch 6.234, pair advance 13.426 (old CAM 6.5288 / 13.55), 40 on one sheet, 5 rows like his nest (screenshot checked). Rule built: fewest sheets, then the tidiest form (straight > half-pitch staggered > creeping) within one column advance of the least last-sheet X; a fill-the-sheet run takes most parts per full sheet, tidy only on a tie. Measured so far (scratch trees, old vs new): ex1 straight rows; hexagon qty 60 keeps staggered (23.27 X, same as old); m1-edr at 180 now 104.04 X vs 106.04; rec160281 at 180 lost 3 parts (345 -> 342) BEFORE the fill-the-sheet fix (fix not yet tested); t014168, ll-lcb, tl-1016 (saved rotation) unchanged; jobs left unmeasured: tl-1016 at 180, ap-bp, brass-disc, prd22870751. test_pl_select #18 fails (hexagon qty 12: tidy straight 8.27 vs staggered 7.38, inside one column 3.18) -- intended change or not is Jordan's call. test_nest_default fails on old code too (pre-existing). Identity gate not run. O105 ON DEV CODE 2026-11-11 ~14:20 UTC (dev commit, engine NOT restarted -- live after an OK'd restart). Jordan 2026-11-11 answers: (1) hexagon trade OK -- 'this is the purpose of having multiple nesting styles for the operator to choose from'; (2) more parts vs tidy rows 'depends on the nesting style'. Built: the lattice style prefers tidy rows (straight > staggered > dense) within one column advance of the least last-sheet X, fewest sheets first; a filler (fill-the-sheet) run takes most parts per full sheet, tidy only on a tie; NEW operator-pick style 'lattice_dense' (FORCE_ONLY, not judged) = the pre-O105 densest-area lattice, so the slanted form stays choosable. Measured old vs new (scratch trees, rejudge): ex1 lattice = straight rows (pair 0/180, Y pitch 6.234, advance 13.426), lattice_dense = old creep; rec160281 at 180 345 parts both (filler fix verified); m1-edr at 180 104.04 vs 106.04 X; brass-disc keep, ap-bp keep/180, prd22870751 keep/180, tl-1016 at 180, t014168, ll-lcb same as old; ONE loss: brass-disc at 180 judge winner was lattice 13.968 X, now free 14.517 X (tidy lattice 15.631 loses the audition) -- asked Jordan. test_pl_select #18 rewritten (dense style earns the oblique advance; lattice takes straight rows within one advance) 28 PASS; test_pl_free, pl_interlock, pkt_native, seqexact, column_join, nestdeliver_rot, nestenv, nestedit pass. Identity gate green. Timing footnote: pack times same within noise (rec160281 10.0 vs 9.9 s); F1 probe pending until after the restart. Ramifications: only the lattice candidate's form choice + one new pick key; judged roster/fingerprint unchanged; stored nests unchanged until repacked. O105 LIVE ON DEV 2026-11-11 ~15:20 UTC: kerfmaster-app restarted on Jordan's 'Yes' (both inflight 0). Jordan: the brass-disc half inch is OK -- 'think of the margin of error in terms of percentage'. Example 1 list repacked with lattice: 40 on 1 sheet, 5 straight rows of 0/180 pairs, used X 58.86 (screen checked). F1 first click (in-process probe, twice per side) 8.61s/8.68s -> 8.63s/8.62s, no change. Speed memo updated. FAIL found 2026-11-11 15:45 UTC (Jordan's screenshot, job 2800x-10-5-rev-d-1794402264-2: one row qty 1, fill the sheet on, half turns): 25 parts on 60x36 where example 1 fits 40. Causes measured in scratch: (a) lattice refuses a qty-1 row ('needs 2+ congruent copies') even when fill is on; (b) the judge ranks candidates by used X on the ASKED qty, not by parts filled, so a fill job picks the wrong style (with qty 2 it picked mixed, 25 parts); (c) with qty 2 the forced lattice fills only 35 although its own count says 42 per full sheet. Not fixed; proposed to Jordan as one fix (fill jobs judged on parts filled, lattice allowed on a fill row of qty 1, fill placement checked against the count). Ruling (Jordan 2026-11-11 ~15:50 UTC): on a fill-the-sheet job the automatic pick takes the style with the most parts, even over a tidier one -- 'but the options between styles should still exist for the operator to choose from'. Jordan asked whether the fill fix is a patch or an improvement ('we want results that cover the most scenarios possible'); answered: general rule fixes, test set named; waiting on his go. O106 (Jordan 'Go on the fix', 2026-11-11 ~22:50 UTC) BUILT IN SCRATCH, parked as tag wip/O106 (patch /tmp/o104/O106.patch), NOT on dev yet: (a) a lone fill row forms a lattice run at any qty (lattice only); (b) the lattice keeps tiling its own lattice on the last sheet for fill rows, each slot cleared by _pkt_ok against everything on the sheet, never a new sheet; (c) the judge packs WITH fill on fill jobs and ranks sheets, then most parts, then used X. Measured O105 -> O106 parts: 2800X qty1 fill 25->45 (lattice; checked: min part gap 0.204 vs bridge 0.200, all inside 60x36), 2800X qty2 25->45, round parts 341/345->376, brass fill 451->521, apbp one fill row 852->925, m1 qty110 fill over 2 sheets 110->154 (keep) / 162 (180), prd two fill rows 24->26, t014 one fill row 278 both, hexagon qty1 fill lattice refused -> 160 (free 132). Non-fill jobs unchanged by construction. Tests 9 suites pass, identity gate green, F1 8.81/8.77 -> 8.77/8.78 s. COST named to Jordan: judging fill jobs is slower (round parts 180 10->88 s, brass non-even 16->123 s, apbp 48->133 s), and deep fill hits the 120 s judge cap on two jobs (shown unfinished, Continue finishes it). Waiting: ship to dev as is, or speed it up first. O106 ON DEV 2026-11-12 ~20:48 UTC (Jordan 'Yes, let me try it before we spend too much more time on it'): same code as tag wip/O106, live with the next dev restart. Jordan asked why fill judging is slow: each style's quick trial run now does the full fill (before, it skipped fill -- why it picked the 25-part style on 2800X); the fill tries every leftover spot and checks clearance against every part on the sheet, once per style. Not profiled yet. Jordan Q3: 'I want the codeset to give us the best yield, I don't want you to manipulate the results' -> the most-parts pick stands (2800X staggered 45). F1 first 8.87/8.86 -> 8.88/8.87 s. LIVE: dev restarted 20:49 UTC 2026-11-12 on Jordan's 'restart' (both inflights 0).
- •O115: 'Clean' nest style the operator can choose -- straight grids, one array call per orientation, even sweep (proposal, not built) intent — O115 (Jordan 2026-11-12: 'Come up with a solution to clean nesting that the operator can choose, which might yield something more similar to our example... what does a clean nest and sequence look like?'). Born from 2800X: the O106 staggered lattice gives 45 parts but posts as 15 slanted array calls of 1-4 parts (P9997 steps only straight, so a skewed lattice cannot be one grid); the shop's old program 3387 gives 40 as 2 calls (upright T grid 4 x 5, upside-down T grid offset by a fixed shift), every copy the same toolpath. Inside each part both programs match (right hole, left hole, outer from mid-flat, straight lead). PROPOSAL sent to Jordan: a CLEAN style = (1) a cell of 1 part or a pair (0 + 180) with the pair offset searched on true geometry gaps; (2) the cell tiles as a straight grid, no slant, fill Y first, leftover one full-height slab at max X; (3) one array call per orientation (2 for a pair), optional one more clean grid in the slab, never scattered singles; (4) sequence = grid order from lower-left, every copy identical; second grid after the first, cut-order safety rule stays on; (5) every always-apply rule on; (6) listed beside the other styles with parts AND array calls ('40 parts, 2 runs'); automatic pick stays most parts unless Jordan sets otherwise. Open questions to Jordan: default pick, slab fill, scope (one part x N first; part lists later). Not built.
- •O120: Heat-congestion sequencing -- Nest tab Heat spread switch: spread-out passes from the bottom left, every other / every third part, Grid Y / Grid X (O121: Grid X posts P9996 arrays, LIVE 13:06 UTC); material seed (steel 1/2 up, alu + stainless 3/4 up) (dev, LIVE since the 12:54 UTC 2026-11-14 restart) record — O120 (Jordan 2026-11-13: 'heat congestion' sequencing -- 'automated nesting software does nothing to account for this. I would like us to come up with a very good solution for this. Ask me questions.'). Example job 8CONVPLTSTL0003, NC 33354, 3/4 A-36 (MSO7 .750), sheet 67.3 x 59.357, 115 parts (incoming/1794600965 dxf, 1794600966 pdf, 1794600968 NC). How the old program 3387 was tricked: ONE nest (pairs 0/180 along the slope) posted as FOUR sparse P9997 arrays, each pitch I13.3 J9.8269 (every other column, every other pair row): A54354 at .5,.5 upright 6x5; A54355 at .5,3.996 flipped 6x5; A54356 at 6.99,6.72 upright 5x5; A54357 at 7.02,.5 flipped 6x5 = 30+30+25+30. Each pass cuts no neighbours; the next pass fills between parts cut earlier, so heat has time to leave. Idea (not built, nothing promised): heat spreading is a CUT-ORDER option on the same best-yield nest, not a different nest -- N interleaved passes, per material x thickness table seed, operator override, travel-time cost shown. Touches: cut-order safety (traffic over held parts, time-ordered), P9997 macro structure (two orientations = two macros rule), part-by-part posts, cut-time estimate, speed lane (nesting/sequence). ANSWERS (Jordan 2026-11-14): (1) heat build-up gives warping, bad edges/slag, failed cuts, even melting on thick plate; (2) default on/off toggle linked to material type x thickness in the table, AND always a toggle on the Nest tab; (3) the 4-pass job is just one sample -- expect to experiment with 'never cut right next to a part just cut'; (4) inside one part too (holes near edges, close holes); (5) every job type, part lists included -- same tools on every file; (6) each pass starts bottom-left and sweeps to the far right, then the next pass returns to the cooled left side; (7) no machine pause/cool setting exists -- laser makers don't solve this, it's ours. Proposal + follow-up questions sent 2026-11-14 (table home of the default, spread knob, sweep row/column, inside-part phase, when to build given O117-O119 still in testing, nesting lane shared with speed). Not built. ROUND 2 (Jordan 2026-11-14): (1) default lives with the lead-in settings -- proposed: the per-material settings block (same place as 'lead-ins follow the sequence' O101: material default + this-job override, material key carries thickness); (2) every other / every third part = a setting to play with on Nest; (3) toggle Grid X / Grid Y for the sweep inside a pass; (4) Jordan: all nesting testing (O106 fill, O115 clean, O116, O120) continues on dev as one body -- his call over one-feature-at-a-time; (5) Aristide kept in the loop by Jordan; nesting + sequencing first, speed corrections after. Asked: go to build + which materials/thicknesses default ON. GO (Jordan 2026-11-14: seeds 'Let's do 1/2" steel and thicker. 3/4" aluminum and thicker. 3/4" stainless and thicker. Off for the rest.' + 'Yes' to build; flyover risk is a thin-sheet / high-pressure-gas concern, not thick plate). RECORD (dev): pl_post.heat_order(boxes, step, grid) -- columns by the strip_order overlap rule (new _bands helper), each part (column, rank up it); pass = (column mod step, rank mod step); passes in order, each from the bottom left, snaking columns; Grid X = rows + rank along the row. detect_macro_runs(groups=) forms arrays only inside a pass, array key (sub) unchanged. tables.heat_spread(material, job=) -- seed machine.json shop-laser heat_spread {on_from per group, step 2, grid Y} with provenance (Galv Steel read as steel), job record job.json 'heat' outranks field by field. server: _pl_heat, _pl_sheet_order(heat=) (heat on: heat order replaces the O95 strips, no orient_runs; Grid X posts part-by-part, said in the style reason); /plorder returns heat + passes; POST /api/jobs/<id>/heatspread {on,step,grid|null, clear} drops posted sheet programs when the resolved setting changes (_drop_plpost, O-numbers kept). client: Part order section of the Nest tab (both layouts) -- Heat spread On/Off, Every other / Every third part, Grid Y up the columns / Grid X along the rows, passes count, Back to the material default; part order line names it. PROOF: 33354 layout -> exactly Jordan's four arrays (origins .5,.5 / .5,3.996 / 6.99,6.72 / 7.02,.5, K6Q5 K6Q5 K5Q5 K6Q5, I13.3 J9.8269, 2 subs) -- test_heat_spread 22/22; scratch post of a copy of Jordan's 2800X list with heat on = 4 sparse P9997 calls, 2 subs, audit 0 red; browser: switch flips, numbers follow, no page errors. test_pl_macro 28, test_pl_strip_order 15, test_pl_spread 80, test_tuck_lineup 13. Identity gate green. F1 first click 8.86/8.86 -> 8.85/8.87 s (repeat 8.59/8.60 -> 8.59/8.61). RAMIFICATIONS: off = byte-identical (gate + tests). Seed-on part lists change cut order with no click: dev has 5 (m1-edr-22010 MS 1, ll-lcb-outboard MS .5 posted, 78017d04a MS .5, tl-1016-83 MS .5 posted, component131400 Al .75 posted) -- the 3 posted ones keep their old NC until re-posted (screen numbers show the new order meanwhile). On main the same would hit prod's thick lists. Grid X on interlocked pairs bands rows roughly (experimental). Not yet: inside-one-part heat (Q4), a cool-down distance rule, time-cost display, per-material default editing in the app. LIVE on dev since the 12:54 UTC restart 2026-11-14 (Jordan: 'Ok to restart'; both inflights 0; active + 200; /plorder answers heat). Jordan same day: (a) 'Grid X can use the macro P9996' -- asked for a sample; Jordan answered the format instead (2026-11-14): 'P9996 works exactly as P9997, it just simply goes in the X direction instead of the Y. We like P9997 to be the default for our shop ... We can simply change P9997 to P9996 with the exact same numbers and the nest stays the same, just goes in the X direction.' O121 BUILT: pl_post.detect_macro_runs(axis='X') -- same lattice and I/J/K/Q, exec walks ROW-major serpentine (along row 1, back along row 2; his 2026-09-06 'both serpentine'), arrays carry axis X; write_sheet_subcall posts G65P9996 for them; nc_audit.expand_p9997 expands P9996 with that walk (P9997 unchanged); server _pl_sheet_order: heat Grid X detects axis-X arrays and posts macro (the forced part-by-part branch is gone; style reason + program form name P9996); Nest tab note says Grid X posts P9996. P9997 stays the default everywhere; P9996 only on heat spread Grid X. Proof: test_heat_spread 30/30 (new: same lattice numbers as Y, row serpentine exec, hand-written P9996 vs P9997 expansion order), test_pl_macro 28, test_pl_strip_order 15, test_pl_spread 80, test_tuck_lineup 13, test_seqexact 16, test_progstyle 29; identity gate green; scratch engine post of zz-2800x-o120 Grid X = 4 G65P9996 arrays (K3Q4, K3Q4, K2Q4, K2Q4), audit 0 red, /plorder order == posted part_order; Nest tab text checked in the browser. F1 first click 8.89s/8.89s -> 8.86s/8.89s (no hot-path change to the nest). Ramifications: only jobs with heat spread ON and Grid X change (they now post P9996 macro instead of part-by-part); Grid Y, heat off, true-nest posts and every other part list are byte-identical (gate). Playback/nc_warn read P9996 through the same expander. Unknown: none of our machines' P9996 has been run from a KerfMaster file yet -- first real cut is the proof. (b) inside-one-part heat (Q4 / ramification 4) HELD -- it would change the Tooling sequencing; nesting and nest sequencing first. O121 LIVE on dev since the 13:06 UTC restart 2026-11-14 (Jordan: 'Ok to restart'; both inflights 0; active + 200; live post of zz-2800x-o120 Grid X = 4 G65P9996 calls, audit 0 red). O122 (Jordan 2026-11-16, screenshot of a 285-pc 96x48 Grid X every-other job: 'When cutting every other part, the next grid should cut up one / over one, right now it's cutting the one right next to the previous'): pl_post.heat_order now walks the passes along diagonals of the (band, rank) classes -- step 2 = (0,0) (1,1) (0,1) (1,0), step 3 = (0,0) (1,1) (2,2) (0,1) (1,2) (2,0) (0,2) (1,0) (2,1). Pass membership unchanged; only the pass order moves. Step 3: every pass starts up one AND over one from the last; step 2 has only 4 groups, so pass 3 always neighbours a cut group (passes 1->2 and 3->4 are diagonal). On his axle-cradle job pass 2 now starts at 6.985,3.125 (column 2, row 2 -- his circle) instead of 6.985,.625. Proof: test_heat_spread 43/43 (new: grid X/Y x step 2/3 diagonal starts), test_pl_macro 28, test_pl_strip_order 15, test_pl_spread 80, test_tuck_lineup 13; identity gate green; scratch post of zz-2800x Grid X = P9996, audit 0 red. F1 first click 8.95s/8.90s -> 9.02s/8.96s (heat_order is not on the nest path; noise). Ramifications: every heat-ON list changes pass order (not the nest, not membership); posted ones keep their NC until re-posted; heat off byte-identical. 33354 itself ran A,B,C,D ((0,0),(0,1),(1,1),(1,0)); now A,C,B,D. LIVE on dev since the 14:30 UTC restart 2026-11-17 (Jordan: 'Yes'; both inflights 0; active + 200; his axle-cradle /plorder pass starts 0, 20, 19, 1 = column 2 row 2 second).
- •O116: automatic nest pick decides from the parts' rough shape, quantity and mix; trial nests check it (plan, not built) intentreads as fact — O116 (Jordan 2026-11-12: 'can the codeset pick a nesting style based on the parts' rough geometry, quantity, and variations of parts?' -- answered: no, today select_pack trial-packs all 6 STRATEGIES and ranks results (sheets, parts on fill jobs, used X; ties to the regular style); then 'Yes, and I'm glad to hear it will also improve speed'). PLAN sent: (1) measure first -- every dev part-list job: what each style gives and how long, the winner, and the job's traits (distinct parts, quantities, how much of its box a part fills, interlock notches, fill rows, sheet size); derive the rules from that data, not guessed; (2) O115 Clean style built first so the rules can pick it; (3) rules give a shortlist of 2-3 styles, only those are trialled, the rest show 'not tried, click to try'; operator can force any style (recorded); (4) before live: shortlist vs full trials on every dev job, any job that loses a sheet or parts is named. Speed gain only if styles are skipped -- to be measured, not promised. RISKY: changes the default nest on every new nest; stored nests keep theirs until re-nested. Order question to Jordan: O106 is in testing on dev (one feature in testing at a time). Not built.
- •See it first, pick the part, then scale it (Jordan, 2026-11-10) ruling — RULING (Jordan 2026-11-10, after O103 went live): every upload shows its drawing at once; the operator picks what to keep (trace/pick -> Cut this), and only then states the scale on the extracted part. Never ask for a number the operator cannot see or know (a PDF's page/border width is unknowable to him). Unconfirmed scale = yellow warning, never a blocking question. Keep this workflow in mind on every build: user-friendly and comprehensive.
- •CLIENT PLATFORM REGISTRY -- one registry for every purchasing client, cloud AND local (Aristide, 2026-10-03 -- plan only, nothing executed) intent — PLAN COMMISSIONED 2026-10-03 (Aristide, reworking open item 5 the upload.kerfmaster.com tenant call: 'we need to have a way that we can track, per client that purchases, even the ones that run the software local, that we create a platform for them that this can happen. create that plan, and look at it from all angles. do not execute the plan, we are planning.'). The plan lives at docs/client-platform-plan.md -- THAT file is the execution record when a go comes (dated numbers, Sidestep log, the perf-closure-plan discipline). Shape: ONE CLIENT REGISTRY on the platform side (never in git -- the prod-runtime-clobber lesson), one record per purchasing client with status/commercial/deployment provenance; cloud mode = process-per-client instances (the proven dev/speed KM_PORT pattern; KM_DATA root env named as the one engine-adjacent pre-change, byte-identical + identity-gated, NOT commissioned); local mode = signed license + content-bounded heartbeat that NEVER carries geometry/customer data (the on-prem ITAR pitch binds it) + offline activation tier; hybrid named so the schema never precludes it; shops.json becomes a GENERATED VIEW of the registry (uploader shop_for() unchanged), which closes the upload.kerfmaster.com rider on pin prod-link-parameterization when executed -- the bare hostname's redirect-or-retire call is open question 6. Vocabulary guard sealed in the doc: CLIENT (purchasing shop) / OPERATOR (person in the shop -- own pins) / CUSTOMER (the shop's customer -- customers.json + uploader accounts) are three layers, never conflated. Nine numbered open questions await the owners (domain scheme, pricing axes, Jordan's shop as client #1, license enforcement posture, heartbeat/ITAR policy, upload hostname, provisioning operator, trial road, billing timing); phasing P0 rulings -> P1 registry+provisioning -> P2 second-tenant proof on dev -> P3 deploy fan-out -> P4 license service (blocks on the windows-installable build; supplies that pin's licensing-model decision) -> P5 billing. NOTHING BUILT -- P0 awaits the sitting. | OWNER ANSWERS 2026-10-12 (Jordan, Aristide present) to the 9 questions: (1) shop.kerfmaster.com stays OURS; every other client gets its own subdomain -- naming convention still to be decided. (2) charge-by: Jordan asked to define 'machine' vs 'box' first -- open. (3) YES, Jordan's shop is client #1, current prod box = its cloud install. (4) an expired license only stops UPDATES -- the software keeps working. (5) no internet disables the online-only features, otherwise as (4); which features count as online-only = follow-up questions to Jordan. (6) bare upload.kerfmaster.com becomes the subdomain for shop #1 (closes the shops.json rider at execution). (7) a fully automated provisioning script, run supervised until trusted. (8) demo = SELF-SERVE trial. (9) YES, billing waits until subscriptions exist. Still NOTHING BUILT; P0 waits on (2), the naming convention and the online-only list. | ANSWERS 2026-10-12 (Jordan, second round): (2) PRICING MODEL -- a BASE PACKAGE = 1 computer install + up to 3 seats + up to 2 laser machine profiles; priced add-ons per extra seat, extra computer, extra machine profile; a PC acting as a server priced differently from a real server install. Numbers not set -- guide written: docs/kerfmaster-pricing-guide.docx (16 numbered open questions inside). (5) ONLINE-ONLY = updates, self-serve trial + license check, hosted board/viewer links, sending files/bug reports to us, PLUS a PORTAL per client where THEIR customers upload files to them -- that portal is the per-client subdomain; the FULL codeset otherwise works OFFLINE. (2.1) subdomain naming AGREED: the shop's short name.kerfmaster.com, reserved words app/view/dev/speed/upload/www/shop kept for us. Nothing built.
- •Three branches only: main, dev, speed -- plus verify-before-report (Aristide, 2026-11-04) ruling — Aristide 2026-11-04: 'there should be 2 branches only, speed and yours'. main = production, dev = this chat, speed = speed chat. No feature branches, worktrees or stashes; unapproved work = tag wip/<O>, parked = tag archive/<name>. One feature in testing at a time.
- •STANDING REMINDERS -- Aristide's open questions + Lathrup testing (Jordan, 2026-10-11) intent — 2026-11-10 19:3x UTC -- the two failing tests UPDATED on Jordan's go ("1. Yes"; "2. No" to an on-screen row for healer-dropped copies: the copy case was a made-up fixture, not a troubleshot file). test_healedit: RJB-DS now asserts 173 prims, 0 open, no doubled flag, within 0.005 of the true source (measured 0.0047); B7787 asserts the healer drops its 5 doubled pieces itself -> 66 prims, 0 open, 0 flags, 0.0033 (pre-O89: 13 flags + 13 open ends); 448 M "dropped 3" -> "dropped 1" (O81 3->2, O89 2->1; old and new heal_edit identical on it), tip check unchanged and passing. 100/100 PASS. test_auto_dedup: fixture copy 1 thou -> 5.5 thou (O89's copy band is gate - budget = 5 thou), 25/25. test_qc_link 15/15. Identity gate green. Tests only, no engine change. The 2 unreadable corpus files: grill split parts part-34 and part-60 (from the 2026-10-07 split of BNM78598...GRILL_22806 with bend lines.dwg) -- each carries a zero-length segment with a bulge; heal._native_prim crashes on it (intake blocked since 10-07, both left off the 60-row list). Awaiting Jordan's call. 2026-11-10 19:18 UTC -- the two failing tests TRACED (bisected on git-archive snapshots). (1) test_healedit "RJB-DS heals to 273": since O81 (31bf8176, arc merge within the Q27 budget, on main) the file heals to 173 prims, 0 open, 0 doubled flags; measured against the true source max 0.0047 in (was 0.0035), nothing beyond 0.010 -- geometry good, the test's expected count is stale. (2) test_auto_dedup "source carries a doubled span": since O89 (3f02bb80, dev only) the cleaner drops whole exact copies itself, so the later Drop-duplicates step finds 0 -- same cause as test_upload_cancel on 2026-11-05 (fixed there by moving the fixture copies 4 thou off). Side finding: heal meta "subtol_dropped" is not read by server/app.js -- the operator gets no on-screen row for copies the cleaner drops. Tests not edited; awaiting Jordan. 2026-11-09 (Jordan: 'put it on the list, I need to understand this better'): the in/mm switch on a regular (unpinned) file re-cleans and SKIPS point-addressed hand edits (shown on a copy: delete_seg skipped, 'nothing within 0.25 in'). Pre-existing. Cut/traced parts are units_pinned and refuse the switch. Fix idea: re-address edits like Scale does (_ps_scale_edits). Explain to Jordan before building. 2026-11-09 22:40 PDF printed-size: Jordan said yes to all 3 (open at printed size with red flag; read dims from PDF; check slow Scale). Draft built, NOT on dev: patch at /home/cloudally/wip-pdf-printed-size.patch. Problem found: converting rec160281 at upload ran over 4 min on the test copy (killed), so it must run in the background, not hold the upload. Scale tool: Jordan x2 on rec160281 took about 595 s on dev (22:29:50 to 22:39:45, my test competed for CPU for part of it). 2026-11-09 OPEN (Jordan): PDF uploads are hidden until a width is typed, one by one. Asked: why hide them, and can one dimension give a default scale. Proposed (not built): show every PDF at its printed size (1 point = 1/72 in) with a red "scale not confirmed" flag, then fix with the Scale tool, by width, or by measuring one known dimension (largest best). Reading the dimension numbers out of the PDF automatically is possible only when the text is live, not built. Scale tool is slow on traced geometry, not measured yet. Waiting on his answers. STANDING REMINDERS (Jordan, 2026-10-11: 'Add a reminder for Aristide's open questions, and for testing Lathrup files'). Every session reads this pin; bring these up when the person they wait on is in the chat. Cross off by editing this pin when answered. A) WAITING ON ARISTIDE: (1) run-X-times -- build on dev now as its own candidate vs wait for Speed's packer merge, and does the speed chat own it (pin sheet-size-input); (2) cleaner chunk A in git stash -- F1 first click +0.27/+0.33s; ship with the cost or speed it up first (pins cleaned-dxf-download / cleaner-tolerance-door); (3) client platform plan -- the 9 numbered owner questions, P0 awaits the sitting (pin client-platform-registry, docs/client-platform-plan.md); (4) Windows installable -- the two strategic calls: shop-server vs per-PC state, licensing/update model (pin windows-installable); (5) security page publish -- security@/info@ addresses, keep-or-hold the two roadmap sections, his word to style it into kerfmaster-site/ (pin site-security-page); (6) nest judge TIME BUDGET -- parked for him (pins pl-strategy-selector / pl-pack-perf-many-distinct); (7) part-list display format sitting (pin partlist-display-format); (8) laser-side operator station sitting with Jordan -- how the role enters the flow + permissions (pin laser-side-station); (9) full 2D CAD suite -- tier cut and module boundaries shaped by both partners (pin full-2d-cad-suite). B) ON THE NEXT LATHRUP UPLOAD (23004-class drawing sheets): (1) browser check of the Intake/source-mode 'Hidden layers:' row -- expect 17 title-block lines on TB-HIDDEN set aside, nothing cut lost; (2) sheet extractor + blocks -- test both options against the real files: (a) a guard that refuses and names the reason vs (b) carrying block holes through extraction; Jordan picks (pin intake-reader-audit); (3) confirm the 29 shipped Lathrup flats still extract entity-identical after blocks + hidden layers (sweep says yes on dev copies; the real upload is the proof). | RECORDED 2026-10-11: pin created on Jordan's ask; record-only, zero code, zero dev O-numbers. | 2026-10-12: A2 (cleaner chunk A) ANSWERED by Aristide -- ship now at +0.24/+0.30s, Project Speed optimizes later (pin cleaner-tolerance-door). | SITTING 2026-10-12 (Jordan + Aristide): A1 ANSWERED (dev owns + builds run-X-times, Speed after); A4 Windows server question ANSWERED (one-station or shop server, wizard asks); A5 addresses created (roadmap keep-or-hold + publish word still open); A8 laser station answered (operator edits = version on top, visible at reorder, per-shop limits in the wizard); A9 CAD suite = rudimentary touch-up. Job export/import DROPPED (Jordan: non-issue). Still open: A3 client-platform 9 questions (handed to them), A6 judge time budget (details given), A7 part-list display (context given), list-opened gaps (b)/(c) clarification asked. | UPDATE 2026-10-12: REMIND JORDAN 2026-10-13 if he has not yet given the order for 'Build New Part List for Sketcher' (pin ui-tab-unification). Platform Qs 2/naming/online-only list open (pin client-platform-registry); judge 2-min cap + Continue ruled, awaiting go (pin pl-strategy-selector); run-X-times chunk 1 awaiting go. | 2026-10-12: Jordan confirmed true-gap Spread Y working (pin ui-plspread-brick36); extension to Spread X / box-fitting columns still asked. | UPDATE 2026-10-12 (second round): judge 2-min cap BUILT (dev restart pending); platform pricing guide docx delivered for Aristide + Jordan to fill (16 questions); subdomain convention agreed; online-only list answered + client portal; Spread X/box-fitting true-gap = joint test session with Jordan; run-X-times chunk 1 still awaiting go; remind Jordan 2026-10-13 about 'Build New Part List for Sketcher'. | 2026-10-13: Jordan gave the order -- 'Build New Part List for Sketcher' BUILT (pin ui-tab-unification); reminder closed. (c) 'New Job' still build-later. | 2026-10-13: (c) 'New Job' BUILT on Jordan's 'Yes, go' (pin ui-tab-unification). | 2026-10-13 REMIND ARISTIDE + JORDAN (Jordan's ask): sit down on the balance of CLEAN G-CODE vs MATERIAL USAGE -- what makes one nest better (sheets / X used / pocket / program simplicity = fewer macros); this is the held fix (b) on pin pl-frontier-tuck. Raise when both are in the chat. REMINDER FOR ARISTIDE 2026-10-15 (Jordan's ask -- he cannot work with the speed chat): look at Jordan's mixed-size sheet-list job WITH THE SPEED CHAT -- dev job 2022-1486a-210item30-2f-12ga-304s-s-46-m-1792079563 (47 rows, 118 pcs, Stainless 0.105, method runs, 9 x 120x48 stock + 7 x 96x48 drops) packed in 25m46s; suspect pack_sheet_list re-packing per sheet entry; profile on a COPY, never his job. | STASHES BACKED UP 2026-10-18 (Aristide "do 2 now"): the 4 parked stashes pushed off-box as branches, stashes kept as-is: parked/stash0-auto-close-gaps-2026-10-15 (2a109c0b), parked/stash1-dimension-scale-chunkB-2026-10-08 (f762b756), parked/stash2-linetype-wip-2026-10-06 (3160273b), parked/stash3-d31ext-baseline-corpus-2026-08-18 (d47a1e37); plus parked/drop-dup-speedup-2026-10-15 (39e3e3ee). Stash0 and stash3 carry old CLAUDE.md edits -- never take CLAUDE.md from them. | HOUSEKEEPING 2026-10-18 (Aristide 'go for 3, 4, and 5'): (3a) CORRECTION -- the 2026-10-13 plvariant/new-sketch records said verify_plvariant 'consumed dev O33466 + subs 75645-75648'; wrong: verify_plvariant never posts, and O33466 + O75645-75648 are Jordan's own CP-6005-04/-03 delivery v001 (2026-10-13 11:43:05). (3b) test_pl_consolidate unstaled to intent: later same-sheet passes (pocketdrop) record to == from; cross-sheet moves still only go LATER and same-sheet ones must carry a kind -- 13/13, now reaching the stronger 'whole trailing column moved together' branch. (3c) app/verify_seq.js: old mycloudally URL -> KM_BASE or dev.kerfmaster.com, and judges a cut plan through runCutplan when the fixture opens without one (a re-review drops cutplan.json) -- 10/10 on the isolated scratch server; verify_pldeliver/verify_plpost get the same KM_BASE override (about 30 other verify_*.js still name the old URL, which still answers 200). (4) suites re-run: test_pl_deliver 28, test_pl_post 26, test_pl_repeat_post 26, test_cl_post OK, test_post_cancel 30; browser on scratch: verify_plquote 44/44, verify_pldeliver 14/14, verify_plpost 14/14. (5) FOUND, not fixed (awaiting a go): run_nestedit and run_nestspread sample the outline from _job_prims WITHOUT the intake turn -- measured on nav209 (turned 90): they sample 1.26 x 7.803 standing up while the nest places it 7.803 x 1.26, so hand-edit judge findings and spread envelopes on turned single-part jobs use the wrong outline. _job_prims also does not replay hand edits despite its docstring (unmeasured). Fix = turn (and replay edits) like the strict test-apply site. Identity gate green, zero code change, zero dev O-numbers (all browser runs on scratch). | 2026-10-18 HOLD (Aristide 'hold on all 3 for now, i want to work on the interface'): drop-duplicates speedup (parked/drop-dup-speedup-2026-10-15), Jordan's sweep options 1/2/3 + slug ladder review, kit split door 0.020 -> heal tolerance -- all three on hold; interface work is the focus. | 2026-10-29 PARKED until Jordan answers: heal-refit-short-arc-chains (3 questions: may short bulge runs be re-fitted; re-fit tolerance, speed suggests 0.002; which runs qualify, proposal smooth moves under 0.05) and upload-split-drops-side-views (speed O58). Aristide: do nothing on either until Jordan answers. | 2026-10-29 JORDAN ANSWERED the parked items: heal re-fit GO (look of the native CAD, no new corner rounding, far larger prims), side views GO (not a bandaid), nest numbers GO. The old CAM cleanup of pins/board/code -> ASK ARISTIDE. Older questions (auto-close threshold, cut vs engrave, bend lines as etch, source-truth view, warning nagging) -> Jordan: 'elaborate on these after the other fixes are done' -- raise then. | 2026-10-30 MERGE PLAN (Aristide: 'we are drifting apart... i do not want to solve the nesting issue in 2 spots'): dev measured base c1ea6405 (2026-10-19), main +66 / speed +68 commits, same 6 shared files as speed counted; in emit/make_prints/part_list_nest main's side is mostly O63 rename text. Dev agrees with speed's plan step 1 (merge main into speed now, dev holds the 6 shared files) and the lanes, with additions: dev's nesting items move to speed; O63 S6-S8 paused until the merge lands; Touch default in speed's uncommitted machine_tables.json must be committed or decided as data; open for Aristide/Jordan: speed's screen features O54-O61 as-is vs dev review. | 2026-10-30 RULED (Aristide '1 yes 2 yes'): speed merges main into speed now (speed's step 1). DEV HOLD until speed reports the merge done: no dev commits to app/server.py, app/web/app.js, app/web/app.css, emit.py, make_prints.py, part_list_nest.py; O63 S6-S8 paused. Lanes accepted: dev = upload/sheet road + screens; speed = nesting (part_list_nest, native, nest doors); dev's nesting items move to speed. | 2026-10-30 03:03 UTC HOLD LIFTED (Aristide): speed merged main 155a2e48 into speed as d1de0fb6, no conflicts, identity 15 ok + 38 suites + browser checks green, speed engine restarted (speed only). Dev verified 155a2e48 is an ancestor of d1de0fb6 and main has not touched the 6 shared files since. Standing: speed merges main at the start of every speed session and whenever dev changes one of the 6 files; dev leaves a memo in kerf-onums when it does. Speed's merge note is O65. Next on speed: review of dev's Source-tab memo. O63 S6-S8 unpaused, awaiting a go. | 2026-10-30 JORDAN: older questions (auto-close threshold, cut vs engrave, bend lines as etch, source-truth view, warning nagging, part-list display format) -- bring back later, not urgent. | 2026-10-30 ARISTIDE: all questions from his 3 O33635 observations go to JORDAN -- (1) leftover copies cut last [pl-leftover-cut-order], (2) print follows repack [print-follows-repack], (3) flips: options A alternate column direction, B leftovers with their column, C flip-risk check/detour, D head lift + slats, E operator marks real flips; who builds (dev/speed). Plus Camp-4 open qty-prefill / rotate-mirror default / start-A questions. Nothing built until Jordan answers. | 2026-10-31 PUT TO JORDAN (Aristide: 'give Jordan all his questions now here'), 16 numbered: approval module 1 real rates, 2 operator sign-in, 3 forgot password, 4 client my-jobs page, 5 change-request reply, 6 files before/after approval, 7 metric toggle + price/bridges-only, 8 extend link, 9 client account delete; Camp-4 10 start with A, 11 qty prefill with drawn copies, 12 rotated/mirrored default per new customer; O33635 13 leftover copies with their column, 14 print after repack A/B/neither, 15 flips A-E, 16 who builds 13-15. Plus the parked older list (auto-close, cut vs engrave, bend-line etch, source-truth view, warning nagging, part-list display) offered: now or keep parked. Waiting on Jordan. | 2026-10-31 JORDAN RULED (answers 10-12 of the numbered list): 10+11 identical copies in the same drawing raise that row's quantity (qty seed = copies drawn), EXCEPT when the drawing states the quantity in text -- then the drawn count does not set it. 12 rotated = another copy of the same part; mirrored = a different part. Asked back: does a stated text qty become the row qty (with a warning when it disagrees with the drawn count); does 12 replace the 2026-10-30 'build both, customer preference' ruling; go on building A. Nothing built. | 2026-10-31 JORDAN: (1) a stated QTY in the drawing text is the row's DEFAULT qty; an operator change must NOT warn -- 'the human operator will have more context than the software'. (2) rotated/mirrored as a TOGGLE in the UI. (3) likes A but wants more details before anything is built. Details sent: grouping math exists (split_parts.congruent_parts, run_partgroups read-only, Camp-4 16 groups in 3.0 s); new = use it to build rows, tolerance from job heal tolerance (today fixed 0.005), a qty-text reader (none exists today; binds only when the note clearly belongs to one part; exploded text unreadable -> drawn count), the toggle; ramifications + proof plan; asked toggle meaning, whether to show drawn count beside a stated qty, go. Nothing built. | 2026-10-31 JORDAN: (1) toggle agreed: 'Mirrored copies count as the same part', off by default, one per job. (2) DRAWN COPIES OVERRULE A TEXT QUANTITY (text can be misread or bound to the wrong part; the operator verifies qty anyway) -- replaces his earlier 'not when a drawing states qty'. Asked back: one drawn copy + 'QTY 6' -> 6? (3) asked how A handles Camp-4. MEASURED for the answer (read-only, dev job camp-4-test-patterns-final-20260915-1793312074): 91 split parts -> 16 groups (15 x 6 + master view x 1) at BOTH 0.005 and 0.010 tolerance, 3.0 s; Camp-4 has 30 texts, none a quantity (title block, 15 labels 46.25..49.75, one 48.0 deg, START/STOP POINT). Nothing built. | 2026-10-31 JORDAN asked: what does the operator see, and in a KerfMaster-only shop at what point do they see the file the customer actually sent? and: make MERGE tolerance and HEAL tolerance two separate settings. Answered from the code (not a fresh click-through): today the original is only in Source mode (S) on a part's Geometry tab (a split part shows the customer's whole drawing, srcOrig), never on the Part list; under A the same; B (drawing beside the list, row<->copies highlight) is where the operator would see it at upload. Separate merge tolerance: yes, per-job setting beside the mirror switch; asked default (0.005 today vs 0.010) and whether B should come with A. Nothing built. | 2026-10-31 JORDAN RULED: (1) MERGE TOLERANCE default 0.001 in, its own setting separate from heal tolerance, easy for the operator to change. (2) A and B built SEPARATELY. (3) one drawn copy + text 'QTY 6' -> row starts at 6. MEASURED: Camp-4 still 16 groups (15 x 6 + 1) at 0.001 / 0.002 / 0.003, 3.0 s. Proposed A in two chunks: A1 grouping + merge tolerance + mirror switch; A2 the quantity-text reader. Awaiting go. | 2026-11-01 OPEN (question, Jordan): BNM part list flat-sh-1793535575 (1 row, qty 8, rotate 360 = locked) refuses to nest with the recorded method 'touch': touch adds its lattice try when the top qty >= TOUCH_LAT_MIN 6 (_touch_lat_ok), but the lattice needs a run and _form_runs makes none for a lone locked row, so pack raises 'no congruent-outline run to lattice' and the whole touch pack fails instead of skipping that one try. Since 88a3df10 (2026-10-20), so prod too. Scratch copy: runs 0.8s OK, free 1.4s OK, touch with the lattice try skipped 1.0s OK. Proposed fix: a lattice try that refuses is skipped and named, the other orders still pack. part_list_nest.py is speed's lane -- who builds it is Jordan's call. Not related to O78. | 2026-11-01 Jordan: wants 0/180 as the rotate default on upload (ruling; nothing built yet). Measured on a scratch copy of BNM flat-sh-1793535575 (qty 8), memo off: locked 360 -> touch 1.0s 1 sheet 100.66in, runs 0.8s 101.32, free 0.9s 100.66; 0/180 -> touch 3.7s 1 sheet 100.21 (lattice try wins), runs 2.3s 100.54, free 0.9s 100.66; 0/180 touch WITHOUT its lattice try = 2 sheets (100.46 + 50.66) -- a speed finding. 12 row-creation sites carry 360 (server 3667, 9365 + client 1395, 10812, 11019, 11054, 15976, 19412, 19466, 19542). 180 keeps the grain direction. Proposed: one default constant per side, new rows only; stored rows unchanged. Awaiting go after the cost is named. Speed message for the touch-lattice refusal drafted and given to Jordan to pass on. | 2026-11-01 OPEN (question, Jordan 'most slots get a yellow for a tight pierce ... more logical default start for slots, down the length'): BNM part-1-1793535547 has 6 yellows, all pierce_standoff: 4 end slots (25/34 0.866x0.236, 24/33 tilted 0.84 long, 0.236 wide) at 0.1178 clear, 2 small holes 22/23 (~0.235 dia) at 0.1115. Standoff = the lead length 0.125 (emit: standoff = lead_len). A slot 0.236 wide can give no pierce more than half its width, 0.118, so no start position clears it; the pierce already sits on the centreline at the end-arc centre with the lead going across to the wall. Side note: 22/23 healed as 14 wobbly arcs (r 0.107-0.1245), not a true circle. Options offered: (a) slot start rule -- pierce on the centreline, lead running along the length (cut quality, doesn't clear the yellow); (b) narrow-feature finding: when the feature's widest clear spot is under the standoff, the pierce goes to that spot and the finding says 'slot is 0.236 wide, best possible 0.118' -- yellow, or a quieter note, Jordan's call; (c) a per-row narrow-feature standoff in the Rev2 table. Nothing built. | O79 chunk a (2026-11-01, branch o79-slot-starts, not merged): slot start rule -- emit._slot_ends finds a slot by shape (aspect >= 1.5, both ends half-rounds of the slot width within 0.015, area within 8% of the obround), judged on the flattened ring so BNM's healed giant-arc sides still read as slots; a slot starts at the END of its long axis (end picked by the inner start default bearing, 4:30 when none), lead runs down the centreline; start source rule:slot-length; shop default recorded as outranked (start_default.slot). Operator start still wins. Square-ended slots and rounded-corner windows are not slots. BNM part 1: 4 end slots now start at the right end, pierce 0.125 in along the axis, clear 0.1175-0.1181 (width-bound, yellows stay until chunk b). Slot tabs (0.015) now sit on the end radius. Identity gate: tilted.nc delta = the 4 slots' starts/leads (36 lines), refs remade; green. F1 first click 7.71/7.69s -> 7.71/7.67s, repeat 7.51/7.50 -> 7.49/7.49. Tests: test_slot_start 9/9 new, test_lead_tab_comp, test_pierce_sub, test_start_anchor, test_start_defaults, test_etch_feature pass. Chunk b (light-green narrow-feature note, Jordan's call) not built: a new severity touches the NC header counts, stage flags and ~20 client sites. | 2026-11-01: dev restarted on Jordan's OK with O79 chunk a (branch o79-slot-starts). Jordan agreed chunk b as proposed: light-green narrow-feature note, not counted in the NC header, does not flag the job. Healer look (Jordan asked for a plan, nothing built): BNM part 1 source is a bulge-free DWG export -- each slot end is 4 chords (5 vertices, all on one r 0.1181 circle exactly), straight sides carry 0.0001-0.0002 vertex drift, the 0.23 holes are 14 uneven facets (0.030-0.099 long). The healer fits arc-per-facet-run: slot ends -> 4 arcs r 0.1177-0.1183, near-straight sides -> giant arcs r 59-361, holes -> 14 arcs r 0.107-0.1245. One circle r 0.1148 fits all 14 hole vertices within 0.0028, but sits up to ~0.0107 off the longest chord -- over the 0.010 tolerance when the chords are taken as truth. Plan offered: (1) near-straight runs -> line, (2) consecutive arcs on one circle -> one arc, all-arc loop on one circle -> one circle, (3) ruling needed: on coarse faceted exports, are the vertices or the chords the truth. Ramifications: every upload, stored jobs re-heal on next review, golden refs, heal speed. | O79 chunk b (2026-11-01, branch o79-slot-starts, not merged -- Jordan: no merge until both have tested): light-green pierce note. rules.pierce_rows names each tight pierce's `room` (half the width of its own round-ended slot, width solved from area -- BNM's healed sides bulge the extent to 0.250 on a 0.236 slot); check_pierce / check_pierce_nest emit severity 'note' (rule pierce_narrow, 'slot 0.236 wide, best possible clear air 0.118') when room < standoff and the pierce is within 0.002 of it; anything short stays yellow; round holes stay yellow. split_notes keeps notes out of the counted findings: check_plan(notes=) -> check_drag out['notes'] -> review.json 'notes' (only when present), nc_audit info['pierce']['notes']. NC header, stage flags and red/yellow counts never see them. Client: --note colour (dark #b8f0a8 / light #74c25e), light-green pierce dot, Checks row + note lines on Tooling. BNM part 1 copy: 6 yellow -> 2 yellow (the two uneven-healed holes) + 4 notes. Identity gate: tilted.nc header 6 WARNINGS -> 2 (one line), refs remade; green. F1 first click 7.74/7.71s -> 7.78/7.73s, repeat 7.51/7.53 -> 7.52/7.51. Tests: test_slot_start 14/14, test_rules, test_nc_warn, test_drag, test_dragcheck, test_double_cut, test_drift_cap, test_etch_feature, test_start_defaults, test_pl_subcall, test_pl_macro, test_pl_post, test_slug_ladder, test_traverse pass. Not touched: part-list pack/nest screens don't render notes yet (they simply don't count them). | 2026-11-01 Jordan on the healer (facet question): a shape not drawn as a true circle need not heal into one, but it must not come out as that many arcs -- reduce the arc count. Proposed (not built): fewest tangent-continuous arcs/lines that stay within the job tolerance of the source as drawn (facets stay the truth); near-straight runs -> lines; corpus count of features affected before building. Awaiting go + restart OK for O79 b. | 2026-11-01 dev restarted with O79 a+b (Jordan OK, inflight 0/0). Healer arc-count look, CORRECTION: BNM part 1's source is NOT bulge-free -- 1047 of 1263 segments are native arcs (each slot end = 4 bulge arcs of 45 deg, sides = near-flat bulges 4e-5..3.5e-4, holes = native uneven arcs); the arc pile is the customer's CAD export, kept on purpose by 'preserve native bulges exactly'. Earlier chat claim (no arcs, straight facets, vertices-vs-chords question) was a misread of the parse dict (bulges sit in a separate list). Scratch count /tmp/o79h/count.py (not shipped): greedy merge of consecutive prims into ONE line/arc, endpoints pinned, no merge across a >35 deg turn, kept within max(0.005, today's heal deviation on that stretch) of the source as drawn; tangency at new joints not enforced (upper bound). BNM part 1 1194 -> 514 prims (slots 13 -> 5, holes 14 -> 2). testdata: tilted grill 630->458, Inventor sheet 151->67, Camp-4 sheet 4141->3595, spline sheet 230->129, DWS logo tread 2256->603, DWS RJB 273->105, LWPOLY 34->17, spline cutout 46->18, CHECK4RAW 50->44; 7 files unchanged. Building it amends the 'preserve native bulges exactly' rule -- needs Jordan's explicit OK. | 2026-11-01 O81 (healer fewest arcs) STARTED on Jordan's go ('build it, note a rollback point, no bandaid fixes'). Branch o81-heal-merge off o79-slot-starts; rollback tag pre-o81-heal-merge = 7cf4a801. heal.merge_arc_runs + _SourceIndex: corner-free stretches re-fit into fewest lines/arcs/biarcs, knots keep old tangents (no jogs), measured both ways vs the SOURCE as drawn within max(Q27 budget, today's dev), never across corners/spikes/welds. DARK (heal(merge=False)) -- not wired on. Measured: BNM part 1 1194->602 prims, 0 jogs, dev 0.0050->0.0050; tilted 630->534; logo tread 2256->1168 (a one-way check let it skip detail 0.035 -- fixed with the reverse check, now 0.0055). OPEN before it can go on: speed (+0.5s BNM, +1.3s logo tread heal), corpus sweep incl Camp-4, identity gate --make-refs, Geometry hand-edit replay check, hover screenshots for Jordan. | 2026-11-01 O81 turn 2 (Jordan: 'I want to test everything you suggest'). Speed: per-prim source deviation now exact-zero for verbatim prims, lazy source grid, candidate judged both ways by native _biarc_dev against the old prims + their own source deviation (a bound). Heal cost: BNM +0.2s, tilted +0.43s, logo tread +0.47s, Camp-4 +1.25s. 16-file sweep with merge on: 0 jogs (0 before), contours unchanged, 0 facet runs, worst two-way source dev 0.0050 (Q27 budget; gate 0.010). Counts: BNM 1194->609, logo 448 2256->1235, RJB 273->173, tilted 630->538, Inventor 151->95, spline sheet 230->160, Camp-4 4141->3686, LWPOLY 34->24, spline cutout 46->30, CHECK4RAW 50->45, 6 unchanged. F1 bench STOP: 7.73/7.53 and 7.72/7.54 (off) -> 10.19/9.93 and 10.16/9.93 (on) = +2.4s first click, over the 1s line -- named to Jordan, pass stays DARK (merge=False). Not yet run: hand-edit replay over the 85 jobs with healedits (script /tmp/o79h/replay.py), --make-refs, screenshots. | 2026-11-01 O81 turn 3 (Jordan: 'keep going; small time increases ok, not huge'). 90% of the +2.4s was re-measuring old prims vs the source; now each fitted prim's source deviation is recorded at fit time (native _biarc_dev per span) and the rest are measured in one batch on a grid built only where needed. F1 (merge on, via /tmp/o79h/benchon.py): 7.73/7.53 -> 8.49/8.29 and 8.48/8.26 = +0.75s first click AND repeat (repeat over the 0.3s line, named; real repeat clicks hit the heal cache). Re-sweep same counts/0 jogs/<=0.005; Camp-4 heal 1.47 -> 3.19s (+1.7s, the big one). Still DARK (merge=False). Hand-edit replay over 85 jobs started (/tmp/o79h/replay.py -> replay.jsonl), not yet read. | 2026-11-01 O81 ON (Jordan: 'Yes restart and let me check it out'): heal(merge=True) on branch o81-heal-merge (not main). Identity gate refs remade: tilted.nc 1057 -> 968 lines (fewer moves, header still 2 yellow); kit_split_p1/p2/p3.dxf same shapes, closed rectangles now start at a different corner vertex (the merge starts a closed loop at a corner). Hand-edit replay: 85 jobs read, 51 with edits, 139/139 edits apply before and after, 0 lost. Dev restarted after inflight 0/0. Rollback = tag pre-o81-heal-merge or set merge=False. | 2026-11-01 Jordan: leave O81 (healer merge) ON on dev only through tomorrow (2026-11-02) so he can test with real-world files. Dev stays on branch o81-heal-merge (O79 + O81). No merge to main until Jordan AND Aristide have tested both. Speed chat to be told when it merges. | O82 (2026-11-02, branch cut-this off o81-heal-merge, rollback tag pre-o82-cut-this): right-click Select chain (drawn sheet + healed Geometry; follows ends meeting exactly one other piece, stops at forks) and Cut this on unextracted drawing sheets -- picked entities by drawn ordinal -> sheet_intake.extract_pick -> own part job + Part List row; a sheet with no list gets one (later cuts join it); no scale stated reads 1:1 with a yellow note in the toast and window record. EDS17942 temp copy: 12 pieces, 9.0000 x 0.7500, row qty 4. Identity gate green; F1 n/a (new door). Not yet: Cut this on ordinary healed jobs, the yellow note in the NC warning count, B/C/D. Not merged; dev not restarted. | O82 fix (2026-11-02, Jordan: 'had to click around and go to Tooling before it built the Part List'): the list WAS built on the press; the screen never refreshed. Cut this now redraws the tabs (Part list rides first) and the Show panel names the list with an Open Part List button. Jordan ruled: many parts per sheet onto one list; multi-sheet uploads build one list (the upload road already binds every sheet to it, so Cut this on any sheet joins it). Screen-only, identity gate green, live on dev without a restart. | O82 fix 2 (2026-11-02, Jordan: 'back on Geometry, Source Mode, the source isn't there'): a Cut-this / window part now carries lineage {root, parent = the sheet, steps = shift -origin then scale x units, entities = the pick}, the same record a split part keeps -- Source mode draws the whole original with the part bold, lined up exactly (EDS17942 temp copy: bbox 0,0-9.0,0.75 both layers), and Intake names the real original. Ramification: such parts now also count as list rows with a root for the Part List drawing beside the list (Camp-4 pick road) -- untested there. Parts made before this fix have no lineage. Identity gate green; needs a dev restart.
- standing-reminders: 2026-11-02 O84 Scale this part built on branch cut-this (pin o84-scale-this-part), waiting on a dev restart OK, then Jordan's test. Next in the EDS17942 plan: C, then D. Pre-existing: test_units_confirm checks 4 and 8 fail on the pre-O84 code too -- look into it.
- standing-reminders: 2026-11-02 dev restarted on Jordan's OK; O84 Scale this part is live on dev, waiting on Jordan's test. Jordan's overlap-to-floor request (pin o83-overlap-warn-downstream) diagnosed, plan sent, waiting on a go and his answers.
- standing-reminders: 2026-11-02 O84 yellow fix built (unconfirmed 1:1 warning on cut-out parts + Size is right), waiting on a dev restart OK. Jordan couldn't find Intake: it is the top section of the right 'Geometry -- checks' panel (Window > Reset panels to their slots if hidden). Overlap pin o83-overlap-warn-downstream still waits on his 4 answers.
- standing-reminders: 2026-11-02 dev restarted on Jordan's OK; the O84 yellow fix (ffdd1264) is live on dev. Jordan's newest part (view-1-1793650196) is scaled x2, so it shows no warning, which is correct. New intent: button-layout-readability. -- 2026-11-02 merged to main (f646311d, Aristide go): O79 slot starts, O81 fewer arcs, O82 Cut this, O84 Scale this part; O83 backed out, still on branch o83-overlap-red waiting for Jordan to test, needs a rebase onto the new main (one server.py line joins the O84 scale yellow). Rollback tag pre-merge-cut-this-2026-11-02. Speed told by memo. JORDAN, MORNING 2026-11-11 (asked 2026-11-10 21:50 UTC): remind him to try the 2800X 10.5 REV D DXF himself (no units in the file; the header claims a ~234 size, so KerfMaster read it as mm, 25x small) and to find the customer's original source file and try that too. He calls it a side issue. 2026-11-12 21:37 UTC -- SHIP TESTING (Jordan): groups 1-4 PASSED on dev ('1-4 are good'): trace tool (O92), PDF upload at printed size (O103/O104), Source-mode Cut this (O107), lances (O108-O110). Still to test: 5 change direction (O111/O113/O114), 6 fill the sheet (O106). Not shipped yet: inventory found more unshipped on dev than listed (no SHIP record on main for O85, O94, O96, O97, O98 -- to verify against main's code before any ship); O116 waits until testing finishes. INVENTORY 2026-11-13 12:5x UTC (Jordan 'check on that now'), dev vs main CODE (not records; marker functions checked both sides, cadmaster/ only, pins/jobs/viewer excluded): ALREADY ON MAIN -- O83b, O85 extra part tabs (_tab_runs), O90, O91, O93, O95 (check_flyover + snake strips), O99, O100, O101. NOT ON MAIN (dev-only code, 13 items): O89 healer drops sub-tolerance pieces (drop_sub_tol_pieces absent on main), O92 trace tool + chain_trace.py + the doubled-line/part-count speedups + updated tests, O94 Cancel for Add-to-row/New-part (_undo_rollback absent), O96 full part names in list rows, O97 mm drawing-sheet lineage (_root_units_scale absent), O98 Jobs Home 'Opening...', O103 + O104 PDF/.ai at printed size, O105 + O106 nest fill (_lat_fill_extend absent), O107 Source-mode Cut this, O108 + O109 + O110 lances (_lance_lead absent), O111 change direction (direction reverse absent), O113 panel shows comp side, O114 comp_g42_norm retired. Jordan's test groups 1-4 passed cover O92, O103/O104, O107, O108-O110; groups 5 (O111/O113/O114) and 6 (O106) still to test; O89, O94, O96, O97, O98 were never in a test group -- raised to Jordan. OPEN 2026-11-17 (Jordan): BNM78598 'with bend lines' DWG upload (jobs ...-1794925593 sheet / ...-1794925640 list) splits into 65 parts; he can't trace with Source mode on. Found: 7 colours of lines stacked ~0.008in apart (several drawn copies), 308 open ends, outline never closes, auto-close declined; Jordan was NEVER asked about colours (upload pop-up off since 38b45928, 2026-10-02, his '6'; the pick lives only as a row in the sheet job's Intake section, which the part-list landing skips) -- my 'nobody answered' was wrong, corrected to him; part 32 heal crashed (TypeError: cannot unpack non-iterable NoneType) and was left off the list. Trace pauses in Source mode by design (works on cleaned lines). Questions to Jordan out; nothing built. IDEA 2026-11-17 (Jordan): replace upload questions with an upload screen of toggles + live preview (layers/colours in or out, split or not, and similar) so the operator decides with the drawing in front of him. Proposal + questions sent; no O-number, nothing built. OPEN 2026-11-17 20:3x (Jordan, grill package bnm78846-...-1794944050): 'I am unable to select any other nesting type. The buttons are there, but they are gray and unresponsive.' Not reproduced: headless browser on the same job in Classic, New, Clear and Clear+floor layouts shows the method buttons enabled (only the current Heat spread choice 'Off' is gray by design; in New layout Spread Y/X/all render light gray but enabled). Asked him which buttons / a screenshot. UPDATE 2026-11-17 20:4x: gray nest options CONFIRMED from Jordan's screenshot (incoming/1794947702_766705_gray_nest_options.PNG): Clear layout's 'Methods tried' cards (clearNestGlance, app.js ~4293) are display-only, no click; the working 'pack with this one' buttons sit in the folded 'Nesting method' section. Fix proposed (cards clickable, client only), not built. NEST SEQUENCE review of the same job (O33701, 50x24, deep fill, posted 20:32 on the O124 engine): Auto style posts nest macros, 24 arrays with only 2 real runs, so the head goes part TYPE by type, not by position: 1 lower left -> 2 top right -> 3 top middle -> 4/5 top left ...; on the drawing the 13 -> 14 rapid appears to pass over parts 10 and 11 already cut. Audit findings 0. Questions to Jordan out.
- •JORDAN'S FIX LIST 2026-10-15 -- everything found today, for the evening fix session (Jordan: 'compile everything we saw today before I leave work') question — COMPILED 2026-10-15 (Jordan, before leaving work; fixes worked with him tonight, a separate go per item). Gaps 1-6 are the doubled-ink/red-visibility list on pin healqc-drop-duplicates: (1) red looks like yellow -- red its own status on the tabs + separate red count in the NC header; (2) cleaner leaves doubled ink (86/1006 dev jobs); (3) one-part files miss the four split-only repairs; (4) outlines not re-chained after an edit replay; (5) posting audit has no doubled-cut / split-outline check; (6) split step 0.020 vs job tolerance -- one number asked. NEW TODAY, measured on dev: (7) HOLES CAN'T BE DELETED ON A TURNED PART -- run_healedits' strict test-apply checks the click against _job_prims (the heal BEFORE the intake turn) while the operator clicks in the turned frame (_apply_healedits turns first, brick 34); every point-addressed edit lands >0.25 in off and refuses 'nothing within 0.25 in'. Reproduced on a scratch copy of 9283383-151 (turned 90 by taller-than-wider), copy trashed, his job untouched. Hits every turned or squared-up part since 2026-09-02 (92 dev jobs carry a turn); posts unaffected (the replay turns first). Fix = the save door turns the prims through the same seam before the test-apply. (8) TYPED PROGRAM NUMBER ONLY REACHES SHEET 1 -- run_plpost and run_postnest pass the operator number only when sheet == 1; later sheets keep their old number or take the next shop-sequence number, so they never follow the typed one. Proposed: typed number seeds the set, sheet k = typed + k-1, each checked like any override (warn on used/reserved), use-once vs new-sequence unchanged. (9) CUT ORDER STARTS FROM THE DRAWING'S 0,0, NOT THE PROGRAM HOME -- emit._cut_order's home defaults to (0,0) of the drawing frame and the caller never passes the real home; the program home is the part's lower-left (to_origin). A part drawn with its origin elsewhere (or moved by the intake turn) starts its sequence from that point: Jordan's 5202-0835 screenshot (prod) starts upper-right; dev 9283383-302 has 0,0 at its lower-RIGHT corner and its first hole is the far-right one. Fix = pass the part's lower-left as home; changes G-code order on such parts, so identity gate --make-refs + named delta + F1 timing. Nothing built, zero dev O-numbers. ANSWERS 2026-10-15 evening (Jordan): (7) ruling -- a band select + Delete deletes, whatever the part's rotation, end of story; the refusal is my bug (save door checks clicks against the un-turned heal), the fix makes his delete always land, nothing about rotation for him to think about. (8) 'Exactly' -- typed number starts the set, sheet k = typed + k-1. (9) he asks for the LOGICAL reason, not a Jordan rule: measured -- emit._cut_order starts the greedy from home=(0,0) in the DRAWING's frame (callers never pass home; to_origin shifts to the part lower-left only after ordering), bands harmless drop-through slugs first, then nearest-first with 24-look-ahead, safety (never rapid over a held slug) before distance, outer last; so the first feature depends on where the customer's CAD put 0,0 = the inconsistency. Proposed reason: start from where the head actually is when the part begins (program origin = part lower-left on a single part, previous part's end in a nest). Nothing built. 2026-10-15 evening (Jordan, question): the 'Nest back to Tooling feedback paradox' -- if Nest made decisions that change Tooling, his manual edits and Nest's retroactive changes cannot both stand. Answer recorded: item 9 must NOT depend on the nest; the 'previous part's end in a nest' clause is WITHDRAWN. Feature order inside a part is decided once in Tooling from the part's own lower-left and frozen (same as the 2026-09-23 frozen-leads ruling); Nest only orders whole parts and never writes back into Tooling; where a nest conflicts with tooling it flags and the operator goes back (2026-08-27 nest-tooling loop ruling). Nothing built. RED VISIBILITY BUILT 2026-10-15 (item 1, Jordan '1. go'): an unflagged RED finding now shows red -- the dot reads '‼' on red (yellow keeps '!'), the whole tab turns red, the drawer stage head and the Jobs-home card dots too (loaded findings decide, green-flagged reds stand down; unloaded falls back to the stage record's red count); the NC header splits the count: (THIS FILE HAS N WARNINGS - R RED Y YELLOW), both counts always present; warn never block, display + comment only. Identity gate: 13 refs rewritten BY INTENT, the ONLY delta is that header line (git diff: 13 lines, nothing else), green after; scoped pass-2 proof still holds on the new header; test_nc_warn 26 (new red-count control) + robust 50 + progstyle 29 + warns 20 + subnum 21 + cl_post updated; browser: mid-plate-1 Tooling tab red, 53 red home dots, verify_warnnav 10 + tabmerge 20; F1 n/a (planning untouched); zero dev O-numbers. AUTO DROP OF DOUBLED LINES AT UPLOAD 2026-10-15 (pins `jordan-fix-list-2026-10-15` + `healqc-drop-duplicates` extended, Jordan '2. Go'): a NEW job's first heal runs Drop duplicate lines by itself -- same detector, same proof gate, recorded as ONE removable Heal/QC row (source auto, labelled 'done automatically at upload'); only when every removal proves within the 6-thou band and the job tolerance is not tighter; verdict on job.json so a removed row never re-adds; older/edited/sketch jobs untouched; qc.find_duplicates early exit 3-10x faster, flags identical (35 real jobs + random control); mid-plate-1 drops its 5 by itself, RJB wedge left with its reason; upload time unchanged (3.6->3.3 / 47.7->44.1 / 11.6->12.9s); test_auto_dedup 20 + healedit 99 / qc_link 15 / tol_door 14 / drift_cap / dashed_ink 22 / healunits_cancel 30 / sheet_dimpart 23 green, identity gate green, F1 8.92/8.12 + 9.09/8.22 -> 8.78/8.24 + 8.97/8.37s no cost, zero dev O-numbers. (Item 2 BUILT; mid-plate-1's outer still plans as two features until item 4.) ITEM 3 MEASURED, NOT BUILT (2026-10-15, Jordan '3. Go'; dev restarted on his 'restart if no activity', inflight 0/0): the four split-only repairs run over the dev jobs that carry open-end flags, AFTER item 2's auto drop -- on real single parts they add almost nothing (camp-4: two 13-18 thou gaps bridged; 44558b-7: 2 of 4 open ends via the 5-thou doubled-prim drop; mid-plate/front-wall/448-fork/zeroclick kits already clean from item 2), while on unextracted drawing sheets (23004, F1 release, 78598 sheet) they bridge 19-31 title-block/dimension spans each -- moving them wholesale would invent joins on sheets. SAME MEASUREMENT FOUND A SIDE EFFECT OF ITEM 2: on BNM grill split parts (part-41/55/61) Drop duplicate lines passes its 6-thou proof but RAISES open-end flags (1->4, 2->4) -- trimming one copy of an overlapping bend line leaves loose ends mid-line; geometry stays within band, the QC/planning read gets worse. Proposed: (a) item-2 guard -- auto drop records only when qc open-end count does not rise; (b) item 3 narrowed to a gap-close at the job tolerance on real parts only (never on a detected/suspected sheet), same rise-guard, as a removable auto row. Awaiting Jordan; nothing built, zero dev O-numbers. AUTO-DEDUP NEVER INVENTS OPEN ENDS 2026-10-15 (Jordan 'Go on A', record): the upload-time automatic Drop duplicate lines now records NOTHING when the drop would leave an open end (gap or dangling) the file never had -- server._new_open_ends compares open-contour flags before vs after, skipping a there-and-back line's own true two ends (one duplicate pair as the only ink meeting there = honest, not new); a refusal lands on job.json auto_dedup in plain words naming the count and the first spot, left for the operator's own Drop click. Correction owed and given: grill part 41 was a bend line drawn there-and-back -- dropping one copy only shows its real two ends, it still drops. Measured on dev (41 jobs before the sweep was stopped): 18 drop / 23 refuse -- mid-plate-1 x3, 448-fork x3, b7787 and most grill parts still drop; grill parts 26/31/33/42/55/61 refuse (1-2 new ends each, 55 at (7.7632, 0.1339), 61 at the 14.664,0.7235 gap); 23004 unextracted sheets refuse with 5-20. TRADE stated: a refused part keeps its doubled ink and would cut twice until the operator clicks Drop duplicate lines. test_auto_dedup 20 -> 25 + healedit 99 / qc_link 15 / tol_door 14 green, identity gate green, F1 8.47/7.76 + 8.40/7.76s no cost, zero dev O-numbers. FIX B PARKED 2026-10-15 (Jordan 'Park B'): the upload-time auto gap-close (heal_edit._close_gaps + server._auto_close, test_auto_close 29/29, sweep unfinished) stays OUT of the live tree -- parked in /tmp/fixB + git stash 'fixB-wip auto-close gaps'; nothing shipped. Same turn the fix-A speedup (grill sheet auto drop >9 min -> 8.7s, same verdict, parked in /tmp/fixA_speed) was asked about, not yet given its go; Jordan asked for a summary of items 4-9. Nothing built, zero dev O-numbers. OUTLINES RE-JOIN AFTER AN EDIT REPLAY 2026-10-15 (pins `jordan-fix-list-2026-10-15` + `healqc-drop-duplicates` extended, Jordan '4. Go'): NEW heal_edit.rejoin_runs runs after every edit replay (_apply_healedits, the one road every stage reads) -- open pieces of one outline that meet end to end but sit apart in the list are put back together, reversed when needed; reorder only, nothing moved/added/dropped, 3-way nodes left alone, unsplit lists unchanged. Dev sweep 45 edited jobs: 43 identical, 2 changed -- mid-plate-1 4 -> 3 features (red wrong-side comp + needless tab gone), B7787 9 -> 5 features (his '5 features, why 7 cuts', red + 4 yellows gone); NEW test_rejoin_runs 12 + 11 neighbour suites green, identity gate green, F1 8.34/7.69 + 8.33/7.67 -> same, no cost, zero dev O-numbers | DOUBLED-CUT + SPLIT-OUTLINE AUDIT CHECK 2026-10-16 (item 5, Jordan '5. Go'): NEW rules.check_double_cut -- ONE rule, both surfaces (check_plan = Tooling review / drag judge / part-list pack; nc_audit = every posted program, macro copies folded by merge_copies). YELLOW doubled_cut: a feature lying within 1.5 thou of another feature's path (or of its OWN path further along -- B7787's outers retrace themselves) for 0.1 in or more, named with the shared length; YELLOW split_outline: an open feature whose end meets another feature's end within 2 thou (one outline cut as separate pieces). Etches ignored; warn never block; Colours label 'Doubled Cut' / 'Split Outline'. Works on the program's own lines/arcs on a 0.25 in grid, samples only pieces where two passes meet. Proven: mid-plate-1 raw = doubled 3+4 9.068 in, before item 4 = split 2+4, after = clean; B7787 raw = 5 self-retraces, before item 4 = 4 split pairs, after = clean; 604 stored dev review plans -> 17 jobs hit, every hit genuine (448 fork strokes, dirty CAD, mid-plates, front-wall open retrace); NEW test_double_cut 12 controls (kissing circles + tabbed loop silent, 0.001 flagged / 0.003 not, engine post -> audit -> header '2 YELLOW') + 20 neighbour suites + verify_warnnav 10 green; identity gate green (no golden case carries either); O33289 532 parts 0.53 s per audit pass; F1 8.35/7.67 + 8.36/7.70 -> 8.55/7.88 + 8.56/7.87s (+0.2s, under both thresholds); stated limit: a there-and-back reads up to one cell short at its turnaround; zero dev O-numbers. | HEAL EDITS LAND ON TURNED PARTS 2026-10-16 (item 7, Jordan '7. Go', record): run_healedits' strict test-apply now turns the heal through the SAME intake transform the replay uses (_rot_on/_rot_prims on job.json intake_rotate, quarter turn and square-up alike) before judging the clicks -- a band select + Delete, a hole Delete, every point-addressed edit lands on a turned part, nothing about rotation for the operator to think about. Measured on scratch copies (his jobs untouched): 9283383-151 (90 by taller-than-wider) the old door REFUSED the hole click, now lands, exactly that hole leaves; bnm78656 (90 + 13.04 square-up) the old door silently judged the click against 5 OTHER prims lying there in the un-turned frame, now the right hole; band delete_seg on top lands, pipeline replay applies both rows. Saved edit lists on old turned jobs unchanged (the replay always turned first) = nothing to re-run; posts unchanged. NEW test_turned_edits 17 (old-road control both ways + unturned control) + healedit 99 / healunits_cancel 30 / auto_dedup 25 / tol_door 14 / rejoin_runs 12 / square_up 23 / setsize 27 / weld 24 green; identity gate green; F1 n/a (save door only); zero dev O-numbers. | CUT ORDER STARTS FROM THE PART'S LOWER-LEFT 2026-10-16 (item 9, Jordan '3. Go on Item 9', record): emit.write_gcode_macrob's cut-order search (_cut_order home, the outer-first approach head, the operator-sequence recount) now starts from the part's OWN lower-left (order_home = bbox min incl. arc extremes = the program's X0Y0), never the drawing's 0,0 -- same point with or without to_origin, so the plan Tooling freezes and every later post (single, true-nest sub, part-list sub, common-line) agree; nest never writes back. Same part drawn anywhere now posts the SAME program. 9283383-302 (drawing 0,0 at its lower-RIGHT): was right-side holes first, now the left holes nearest the lower-left, then right, outer last. Dev sweep 596 reviewed jobs old vs new: 584 identical, 12 reordered (7497, 7498, 78017d02a detail, 9283383-151/-206/-302/-711, b7787, c01c, ex2-dirty, two side-plates) -- no pierce moved, findings identical on every job (no new crossings/reds); 5202-0835 is prod-only, not on dev. NEW test_order_home 4 (fails 2 on the old code) + small_first 15 / drag 23 / tooling_doc / start_defaults / slug_seq / pl_sync 25 / pl_macro 28 / pl_origin 13 / traverse 10 / double_cut / slug_chop / approach / robust 50 green; identity gate green with NO ref change (every golden fixture is drawn at its own lower-left -- stated); F1 8.43/7.79 + 8.46/7.77 -> 8.42/7.77 + 8.47/7.78s no cost; zero dev O-numbers. SAME MESSAGE, recorded: (1) Jordan asked whether kits and single parts are still treated differently -- honest answer YES in one place: items 2+4 run on every file, but the split door's 0.020 fragment merge + gap bridging still run on kits only (fix B parked), so item 6 and fix B are the same question; (2) item 8 gains Jordan's ask: override the STARTING sub-program number too (subs numbered from it, each checked like any override) -- intent, not built; (4) fix-A speedup 'same result' proven on the grill only so far -- the all-jobs sweep runs before it ships; (5) dev restarted on his 'restart if no activity' (inflight 0/0), items 4/5/7 live on dev. | ITEM 8 BUILT 2026-10-16 (Jordan 'Go on Item 8' + his 'also override a starting subprogram number'): a typed program number now numbers EVERY sheet program on both sheet posts -- sheet k = typed + k - 1 (part list + true nest; was sheet 1 only, later sheets kept their own); NEW 'first sub-program number' field on both Post drawers -- subs number from it in posting order (true nest: sheet 1's orientations, then sheet 2's ...); every number still judged like any typed override (reserved / already used = yellow in the file, never a block); the ONE refusal: a series handing one number to a sheet program AND a sub of the same post, refused plainly BEFORE anything is recorded (auto sheet numbers skip the typed sub series); blank fields byte-identical (auto / kept); single-part post refuses a sub start (no subs). NEW test_series_numbers 18 + post_cancel 30 / pl_macro 28 / pl_repeat_post 26 / pl_origin 13 green, identity gate green, F1 n/a (numbering only), zero dev O-numbers (scratch progseq). Browser suites not re-run (client change = one field + wording, syntax-checked). | ITEM 6 / FIX B BUILT 2026-10-16 (Jordan '1. I think it should be the Heal Tolerance ... build this then go back if it ends up not being the right solution'): every NEW single-file job's first heal now closes small gaps by itself, right after the automatic duplicate drop -- loose ends within the job's cleaner (heal) tolerance join ONLY where the joins close a contour (two open lines are never spliced into a longer open line), never on a chain with a branch, never on an unextracted drawing sheet, never when the operator already has edits; the result must invent no open end and no branch; recorded as ONE removable Heal/QC row 'Close small gaps up to X (done automatically at upload)', verdict on job.json so a removed row never re-adds; older jobs untouched. Join corners are exempt from the jog check (the source has a gap there). Dev check, 695 non-sketch jobs as if new: fires on 1 (cp-6005-04, 1.5 thou), 76 unextracted sheets left alone, 3 grill sheets refused by the guard, slowest 0.1s, 0 errors. STILL DIFFERENT, stated: the split door's own kit repair merges/bridges at a fixed 0.020 in, singles now close at the heal tolerance (default 0.010) -- moving the kit door to the heal tolerance is a separate decision (it changes kit outputs, needs its own sweep). ROLLBACK: tag pre-autoclose-gaps (revert the commit; jobs already carrying the row keep it until the row is removed). test_auto_close 29 + auto_dedup 25 / healedit 99 / rejoin_runs 12 / turned_edits 17 / tol_door 14 / healunits_cancel 30 / sheet_dimpart 23 / qc_link 15 green, identity gate green, F1 8.47/7.86 + 8.45/7.77 -> 8.46/7.84 + 8.46/7.78s no cost, zero dev O-numbers. | FRESH-UPLOAD RE-JOIN FIX 2026-10-16 (Jordan re-uploaded mid_plate_1+2 on dev: 'Still having the same issues'): record -- the upload's automatic Drop duplicate lines (and auto Close gaps) primed the edit-replay cache with the bare edit result, BEFORE the item-4 re-join, so every stage after a fresh upload read the outer as two open runs (review 4 features, red wrong-side comp, split_outline yellow); my ordering defect -- item 4 was wired into the replay only. Both cache primes now store heal_edit.rejoin_runs(out) = exactly what a cold replay gives. Proven fresh upload of both files: mid_plate_1 4 -> 3 features, mid_plate_2 5 -> 4, red + tab_needless + split_outline gone on both (pierce_standoff yellows in the narrow slots remain, honest). test_rejoin_runs 12 -> 13 (13 = fresh upload, cached replay == cold replay; old code FAILS it) + auto_dedup 25 / auto_close 29 / double_cut / weld 24 / healedit 99 green; identity gate green; F1 n/a (upload-only path, the probe re-plans existing jobs); zero dev O-numbers. His two jobs already on dev keep their stale plan until re-planned (Apply toolpaths) after the restart.
- •Everything gets a pin — every artifact, draft, open item and decision lands on the pin list, same turn it is born ruling — Aristide, 2026-09-13 — ruling: 'make it a rule that all items like these are always tracked in the pin site.' Born from the security-page draft, which existed in docs/ for a day with no pin — a future session would never have found it. Nothing lives only in chat, memory, or a stray file again. | CLAUDE.MD TRIM 2026-10-18 (ruling, Aristide 'go' on the CLAUDE.md audit): CLAUDE.md was 356 KB (~89k tokens) and loaded whole every session -- 346 per-build summary lines were 241 KB of it. Ruling tightened: a build record goes on its pin + docs/brick-history.md only, NO per-build line in CLAUDE.md; CLAUDE.md keeps standing rules, how-to and current state; new standing rulings get one short line. Old sections condensed; stale definition-phase 'don't build the interface' wording replaced by the 2026-09-01 UI-phase ruling. Pre-trim file moved verbatim to docs/claude-md-archive-2026-10-18.md (every line checked present). New size ~29 KB.
- •Nesting rules — Jordan's rulings (2026-08-10/12) ruling — Spacing floor .200 (ruled for TL-1016); 96" runs in X and long parts lie in X (slat-bridging bias, not a rule); flip-180 profile nesting; open profiles close at 0.020 by trim/dedupe, never gap-bridging; no common-line; material > tipping > time. Y-first columns now implemented (remnant = one full-height strip at far X); lead-ins planned in-nest, 0.300" between lead-hosting hypotenuses (0.150 lead + 0.150 pierce standoff); Aristide 2026-08-13: separate orders, nested per ORDER — efficiency within an order, never across. X-extent is the cost function (Jordan 2026-08-18): fill internal voids before extending the X frontier; remnant = full-height strip beyond max X.
- •Production quantities in the nest — qty replication after heal, before packing record — split_parts.main(qty=N) replicates every grouped part N times AFTER heal/group/lead-planning and BEFORE the packer — the expensive per-part work runs once per unique part, copies are packed as first-class parts (ids p00XcNN). Built for the ISV-H grille job (Jordan 2026-08-21: 15 each on 48x96); first use = build 035 (105 parts, 5 sheets, min gap 0.2019, all gates pass). Composer for multi-file jobs: nest_isvh.py pattern — one copy of each healed part on a virtual canvas, qty at the nest call. Build 124 (2026-08-24) supersedes 035: Jordan confirmed MSO7,0.080 with 0.030 part tabs (his number equals the table value measured from his own 33199.NC) and sent a MANUAL flat for BNM78880 (build 123, PASS 0.62 thou) -- 8 parts, 120 placed, 5 sheets, min gap 0.2019, all nest gates pass.
- •Manual nest adjustments — the operator's move is applied, then audited recordfixed d36 — Jordan 2026-08-18 (-86/-93 screenshots): 'I moved the parts that are blue... Make these changes on your end.' split_parts.main(moves=) reads part -> outline-bbox target JSON, applies AFTER the packer, BEFORE the clearance audit -- a hand placement is measured like any other (first two targets failed at 0.1815/0.1967 and were corrected from the audit, not by eye). Recorded in stats.manual_moves. Same change: nest margin is a parameter; -86 nests at 0 because the baked 0.5 double-counted the G52X.2Y.2 the post applies (margin is per-job, applied at post, never baked into the DXF). Physical edge = the shop's own 0.2.
- •Program numbers & mixed-sheet traceability — deferred to 2.x ruling — Operator assigns the program number from the shop's list at nest time; auto-numbering and part-to-order sorting are version 2.x.
- •Bridge emission — bridges cut into the geometry (Jordan's go, 2026-08-10) record — place() is SYMMETRY-FIRST (mirrored pairs about a detected axis); widths 125/80 by Jordan's ruling; straddled limbs OWN their segments (window fill barred, round 4); every contour stays closed; the old CAM shop DXF carries the bridges.
- •The slot-break rule — showing "on top" in a one-piece cut ruling — Buried edge drawn as a narrow gap broken by ligaments; break at interior ends, never at emergence points.
- •STEP (.stp) input — step_io.py reader: bent parts unfold, flat parts deliver direct (builds 139/140/151) record — record: step_io.py (pure-Python AP214 B-rep reader, 2026-08-26) + unfold.py give STEP two paths: a BENT part develops to a flat blank (neutral-axis unroll, BA = theta*(R + K*t), K=0.33 stated assumption -- builds 139/140, BNM78651), and an ALREADY-FLAT solid skips the unfold: the top Z-normal planar face's outer + hole loops convert EXACTLY (STEP carries true curves -- no healing). First flat delivery: build 151, 8VACUSEPRNG0001_FLAT (Jordan 2026-08-28), DXF-vs-source audit 0.00005 in; material answered 2026-08-28: 16 ga 304 stainless (.060 in), Rev2 row exists.
- •Nest shop ergonomics — uniform arrays, axis preference, remnant as objective (Jordan 2026-08-24) rulingmixed — ruling: three packer rules from Jordan's mark-up of the ISV-H sheet-1 image. (1) Identical parts nest in a REGULAR orientation pattern -- refined same day by Jordan ('Push back on the P9997 hard rule: items like this can be 180 rotated in pairs', with an image of hook-shaped parts interlocked head-to-tail): one shared orientation OR a consistent 180-degree pairing that interlocks; the ban is on stray one-off rotations within a part type ('one part on the bottom right is randomly rotated 180 degrees from the rest. Human operators would not prefer this, but also using nesting macros like P9997 would not work well with anomalies like this'). (2) Odd tilts are suspect: min-area rotation stood two bracket types at 172.5/352.5 (7.5 deg off axis) and 'doesn't seem efficient' -- axis-aligned unless tilt buys real packing. (3) Remnant shape is an OBJECTIVE: 'why didn't you put these elements on top of the large grills on the left side, and leave the rest of the sheet for a cut off?' -- consolidate parts to one end, fill grille-sheet spare bands before sprawling, leave one clean rectangular cutoff.
- •Production nests: as few NC programs as possible — identical sheets = one nest + 'Run (X) copies' (Jordan 2026-08-25) rulingmixed — ruling: for large sheet-quantity jobs, identical sheet layouts collapse into ONE nest/program carrying a run-copies note — 'For nesting large sheet quantities like this, it's better to use as few nc programs as possible. Seems like some of these nests are similar, if not the same, and should be one nest/program with a note: Run (X) copies.'
- •Engineering-drawing PDFs read end-to-end — part extracted from dims/border/views clutter (2026-08-25, Jordan's 8ARCHBASSTL0006 test) recordmixed — record: vec_io now unpacks PDF 1.5+ object streams (CAD exporters pack the page tree there; the file read as zero paths before), and drawing_extract.py selects PART geometry out of a dimensioned drawing: fills+arrowhead twins dropped, stitched chains must CLOSE (dim/leader lines dangle by construction), page frame and loops outside the main view dropped, line-side junction snapping heals the drawing's own micro-gaps. 8ARCHBASSTL0006: all 16 printed dims within the drawing's +/-.005 block; our fit adds 0.27 thou, 0 kinks. Build 134: part snapped to printed callouts by Jordan's ruling (as-drawn scatter re-measured by Jordan in CAD). NX dialect (12729704): gapped/overshooting outlines bridged by angular pairing + trim + seam-spur cleanup (drop_seam_spurs); the two 'unresolved holes' were ONE 10.50x12.50 obround slot (datum C); scale proved by least-squares over all 14 printed spans (0.4703725 mm/pt); build 135 delivered in MM, 23/23 callouts exact from the delivered DXF. Build 156 (EXM275FG-0625): third dialect (Exotic, 0 beziers), 4.50 callout disambiguated from its own arrowhead positions, nominal-from-callouts nested 81-up on 36x48 .125 copper — first copper job and first production nest sourced from a drawing PDF. Fourth dialect (Navistar 3683209C2, build 160): doubled-run fragments deduped+restitched, true beziers via bezfit; part geometry now BUILT FROM CALLOUTS per the pdf-dims-govern ruling (holes 3/4 at stack ys 123/151, R6 lobes concentric, R16.4 waists re-solved by tangency) with the healed trace as the verification layer — max delta 0.333mm, all inside +-0.8. Supersedes build 159's drawn-position call.
- •Called-out dimensions are AUTHORITATIVE at their stated precision (Jordan, 2026-08-25) ruling — ruling: any dimension called out on a print must be exact in the DXF we deliver. The ONE legitimate mismatch is print-side rounding: a .375 feature commonly prints as .38 when the tol key gives +/-.005 for 3 decimals and +/-.010 for 2 — the decimal count SELECTS the tolerance, and a 2-place callout is a rounded view of the true value, not a command to build .380.
- •Machine condition tables — Jordan's Rev2 workbook is the MASTER (Jordan 2026-08-24) rulingmixed — ruling: 'Use these as our master but each of our clients may want to change these for themselves.' One sheet per machine (clients build one per THEIR machines too, 'organized in form-type so that our clients can modify these easily'). Rev2 supersedes prior measured/ruled values going forward ('You can refer to this table going forward'), including 1/8-and-under mild offsets (.004 vs the earlier .007) and the per-class D registers -- 'The new D values will be our improvement versus the old CAM's old ways of doing things' (Profile D3/#108, Inside D1/#107, Small D2/#106 -- corpus single-D7 is the old CAM's old way). Time columns (feedrate, pierce time, extra lead-in, corner dwell -- both in seconds, from the laser's own condition-table parameters) are ESTIMATE-ONLY: 'they don't have any effect on how GCode is posted'; pierce time 0 on thin aluminum 'is real'. Slug tabs: one width between Small and Large limits; 'The large limit for slug tab will replace that [0.75in drop-through] rule'. Small Threshold = SMALLEST dimension, inside contours only (a .100x.500 slot in .040 steel takes the small parameters). Bed sizes are PER MACHINE: GX 10K and EX 4.5K are 60x120; '80x160 is another machine which we have not added yet'. Stock (sheet sizes, cost) is 'a separate sheet and a separate table. Has nothing to do with the machine.' ZHL = focus type at the machine, irrelevant to posting. Etch: condition + feedrate columns still to be added (Jordan: 'remind me to do that'); etch runs as its own step right after cleanup in the interface, G-code adjusted accordingly. CONFIRMED 2026-08-31 (Jordan, on the post-wiring plan): 'What we want is the newest format, where D1/#107, etc. are defined by the tables' — registers and conditions are READ FROM the table rows, never hardcoded; a client's own machine sheet defines their registers. WIRED 2026-08-31: registers ingested from the offset headers (profile D3 / inside D1 / small D2, per machine); tables.rev2_tooling raises on blanks; write_gcode_macrob(tooling=...) classifies profile/inside/small per boundary and posts each class's #501 condition + D register (legacy path untouched); nc_audit(tooling=...) independently re-derives class from posted geometry and flags mismatches (legacy control: 3/3 caught); bed 60x120 in machine.json; MSO7,0.375 row added (.016 decided from Rev2). ETCH VARIABLE HOME 2026-09-01 (Aristide: don't wait for the numbers, 'you already know it is going to be a variable, just work around that'): tables.etch(material, machine) exists now -- reads etch_condition/etch_feedrate off the Rev2 row when typed in, raises MaterialIncomplete while absent (TBD never a silent default, no etch literal in Python); Jordan's columns become a row edit, not a build. Open: etch column VALUES (Jordan owes), per-machine profiles, rotated-slot min-width.
- •Interface requirement — right-click per-contour override of any table value (Jordan 2026-08-24) rulingreads as fact — ruling on future interface, NOT build authorization: 'In the final interface, the software should give us the option to right click and override whatever value came from this table for that particular contour. When they right click, it should display the \"current\" value.' The old CAM's tooling dialogs (EDIT_TOOLING_0-3) are the reference feature set -- 'it's ugly but functional. We will look for these features to be added to our interface.' Sharpens the standing best-practices rule (every default overridable) into a mechanism: per-CONTOUR override, seeded with the value the machine table resolved for that contour so the operator sees what they are overriding. Scope per the old CAM's dialogs: condition number, direction, comp on/off (No Beam-offset), constant power, approach (length/radius/angle/pierce/dwell/condition), escape (same + gap width, after-cut). Extended same day (Jordan): lead-in LENGTH and PIERCE TYPE are also per-contour overridable, and the alternative pierces he will add to the table 'will be available to override easily for the operator.'
- •Scanned/raster input — the 3A76 lessons (ratified by Aristide 2026-08-27) ruling — A scan trace is a reviewable DRAFT, never production geometry. Ask for the customer's native CAD first. And an audit must be independent of the pipeline it audits — comparing a trace to its own re-run confirmed defects as 'matches'.
- •Input triage prompt — ask the right questions when a file predicts a poor result (Aristide 2026-08-27) intent — Intent, phase rule applies: when load-time analysis sees the input cannot give a good result (raster scan, no scale, fused leaders, unreadable callouts), the interface prompts the operator with the RIGHT QUESTIONS instead of proceeding silently. Aristide: 'ask the right questions, if you see that the file is not going to give a good result, a pop up prompt?'
- •Toolpath view — visualize the posted path on screen recordmixed — intent (Jordan, 2026-08-28): the interface shows the path the laser will follow — cut direction, pierce points, lead-ins, and dashed rapids feature to feature. The old CAM's tooled view is the reference example. RAPIDS LAYER BUILT 2026-09-17 (Jordan: 'a good feature for visual reference for the operator ... make it hideable like the other features on the left column'): rapids between features are a toggleable display LAYER (toolbar button + key R, default on, rides the Colours & legend --dim role). Three scenes: (1) the Part review scene draws the chain straight from review.json's plan array -- the FLOWN approach (Traverse Routing waypoints) when the row carries one, straight line otherwise, arrowhead at each landing pierce; no cut-plan judgment needed, a Manual Sort re-plan re-orders it by itself; (2) the Cut plan scene's existing rapids now obey the same toggle; (3) the part-list Nest canvas chains the whole sheet in the CURRENT emission order (the numbered boxes' own numbering, plOrderForSheet), features within a part in plan order, straight between parts (what the part-by-part main program does); _pl_build plan rows now ship the within-part flown rapid (base frame, rotated like pierce/segs) so a NEW pack draws routed approaches -- packs made before this build fall back to the straight line, honest, a re-pack refreshes. Chain restarts per sheet (each sheet its own program). Honest limit: the single-part TRUE-nest canvas (Nest tab on a single job) still draws leads only, no sheet chain. Display only -- no engine or judgment change. STITCHED 2026-09-18 (Jordan's Rapid_Path screenshot -- 'Rapid path does not represent reality of the nest?'; Aristide 'Go'): the part-list chain drew each part as its own ISLAND -- the pack ships each part's lone-plan approach whose first point is the part's OWN origin, and the canvas trusted it at the seam, so every entry leg rose from the part's lower-left corner and no leg connected part to part. Now each placement's entry leg is stitched to where the head really is: the previous part's last cut end (routed waypoints kept), the sheet's first part from the G92X0Y0 program start. Within-part rapids unchanged; client-only (app.js). Verified on the dev CAMP nest -- one continuous chain in emission order. RAPID DIRECTION ARROWS 2026-09-18 (Jordan's Rapids_9-18-1 BRONX screenshot -- 'One of the things that would really help the operator is to clearly see what direction the rapids are heading. What I'm expecting is a repeated arrow along the rapids' -- plus his old CAM reference shot, whose lone tiny end-arrow is the thing to beat): every rapid leg on all three drawing surfaces (review-scene plan chain, cut-plan scene, part-list Nest canvas) now carries REPEATED arrowheads oriented along the direction of travel -- one shared helper rapidArrows(), arrows every ~64 SCREEN px (zoom-independent: wherever the operator looks at a rapid there is an arrow nearby; a short leg keeps just its landing arrowhead, which stays on every leg). Same --dim colour and layer as the dashes, so the R toggle hides arrows with the chain. Client-only (app.js). Verified live on dev (B7787 review chain + cut plan screenshots -- direction reads at a glance across crossing legs) + verify_traverse 10/10; traverse check 10 made self-sufficient in the same pass (a verify_draghandle run re-plans nav209 and drops cutplan.json -- suite-order coupling, the check now posts its own cutplan door first; suite fix, zero app change).
- •Static toolpath plot — every posted program ships one record — record: toolpath_plot.py draws the laser's path from the posted NC — green cut path with direction arrows, orange lead-ins, numbered red pierces, dashed rapids in cut order. Wired into post_nest; approved by Jordan 2026-08-28.
- •Per-contour tooling document — the override slots get their data-model home record — record: tooling_doc.py + emit stats["contours"] — every posted boundary's decisions (sequence, condition/register, comp, direction, start, pierce, lead, tab) recorded as ran-value + source, with an override slot per ruled field. CONSUMABLE = start + lead_length; post_nest ships the document beside every NC and takes overrides= back in. The seam the right-click UI will sit on.
- •Drag-handle validator: click-time findings for a forced start/lead (built 2026-09-01) record — 3d, built on Aristide's 'Build what is buildable now' (2026-09-01). rules.check_drag(prims, overrides, material, tooling=..., **post_kwargs): hand it the part and a proposed per-feature override (the drag -- write_gcode_macrob's overrides= shape, or tooling_doc.overrides_from of an edited doc) and it answers 'if the handle drops HERE, these findings fire' -- before any NC exists. No drift by construction: the plan comes from the ENGINE's own planning (a plan-only post to os.devnull with the new emit plan_samples=True seam -- lead aim, scrap-side, tab span and snap are exactly what a real post would do; the plan poly is the AS-CUT contour so the tab gap is visible to rules.annotate) and the judgment is the same shared rule functions the NC audit calls (rules.check_plan) at the audit's own parameter sourcing (tables drop-through / material standoff). Returns findings red-first plus 'dragged' (the bnd ids the override features bound to -- read back from the engine's own per-contour record, never re-derived) and 'dragged_findings' (the subset touching them) so the UI can show the operator what THEIR drag caused vs what was already flagged. Warn never block; the posted-NC re-read stays the final gate. Proven: test_drag.py 10 controls incl. the parity control -- the same overrides posted for real and audited report the identical (rule, bnds) findings. plan_samples is off by default: normal posts and tooling docs byte-unchanged (control 1).
- •The old CAM Add-Toolpath walkthrough — the operator-override reference set ruling — ruling/reference (Jordan, 2026-08-28): full screenshot walkthrough of how the shop tools a part in the old CAM — auto-tool seed, then detailed overrides: per-feature dialog (2A), drag lead-in/pierce + typed values (2B), manual sequencing (2C), all-identical vs single-feature propagation (2D). All open questions answered 2026-08-28: Alt/Shift keys = the old CAM's failed resequence shortcuts (our click-in-order model is the envisioned UI); the old CAM warns on risky re-sequence, dismissible (→ gcode-warning-callouts); wirejoint rides the approach drag. BUILD CONFIRMED 2026-08-31 (Jordan): the drag-handle engine ('this will definitely have to be built') and identical-feature propagation ALL-mode ('Good, build it') are ordered — engine pieces first (validator + fan-out), canvas later per phase. FIRST ENGINE SLOT BUILT 2026-08-31: emit.write_gcode_macrob(start_at={'outer': (x, y)}) forces a boundary's start/pierce to the contour point nearest the given one — tab span, snap and into-scrap lead rules all still apply. Born on O33286: the lone-part chooser aimed the outer lead -Y into the next nest row; the nest layout owns the pierce-channel knowledge, so it passes the point. The full per-contour override surface stays intent.
- •Warning severity + warnings carried into the posted G-code intent — intent (Jordan, 2026-08-28 — decided): risky operator choices (e.g. manual re-sequence) raise a warning with severity — yellow or red — the operator can dismiss; if G-code is generated with a live warning, the NC carries a (warning) comment at the spot AND a top-of-file callout: (Contains X # of warnings). DECIDED 2026-08-31 (Jordan): compute the warnings LIVE as well — one-time refactor so the live click-time check and the final NC audit call the SAME rule functions; the posted-NC re-read stays as the final independent gate (it judges what the machine will see). No downside beyond the refactor; single source of rules so the two views cannot drift. REFACTOR DONE 2026-09-01: rule functions shared — see pin click-time-rule-checks; NC CALLOUTS BUILT 2026-09-01 — see pin nc-warning-comments; severity colours still the proposed table awaiting Jordan.
- •Shared rule checks — rules.py, one set of functions for the audit and the click-time warning record — record: the decided one-time refactor (Jordan 2026-08-31) is DONE 2026-09-01 — the rule DECISIONS (comp side, tabs/traffic, cut order, pierce standoff) live in rules.py; nc_audit calls exactly these functions on the posted NC (final gate unchanged — reference audits byte-identical) and rules.check_plan() runs them on a PLANNED sequence with no NC file: the click-time entry point. Findings carry a PROPOSED yellow/red severity, awaiting Jordan's ratification.
- •Warnings ride IN the posted G-code — nc_warn.py writes Jordan's (warning) callouts record — record: built 2026-09-01 (Aristide 'let's do it') — every post_nest program that posts with yellow/red findings now carries Jordan's ruled callouts: (CONTAINS N WARNINGS) right under the O-number plus the numbered full messages, and a (WARNING k: SEV RULE) spot marker after each affected (BND:n). On a P9997 macro program the expanded-boundary findings map back to the subprogram's local bnd — one marker covers every arrayed instance. Comments only, proven transparent: the annotated file is re-audited and must report identical anomalies or the post raises. Warn, never block. EVERY POSTING SURFACE 2026-09-01 (Aristide 'Build what is buildable now'): the audit->inject->recheck sequence moved into nc_warn.audit_and_inject() -- the one call a posting surface makes after writing a program. post_nest refactored onto it (behaviour identical, test_nc_warn 12 controls pass); the board surfaces wired: build_board.py (_prod125.nc) and build_vec_board.py (_prod.nc) now audit every board-built production post and write the callouts in-file (they previously posted UNAUDITED -- closing that too). Proven on discarded smokes: ex2 prod post carries 6 warnings (2 red incl. wrong-side comp), EAGLES prod post 5 (red wrong-side comp bnds 17-19 + red untabbed-slug traffic) -- real findings on old fixtures, now travelling with the program. Bespoke deliver scripts call the same helper going forward. Still open: severity ratification (Jordan).
- •Job versioning — every customer job is a chain of openable versions intent — intent (Jordan, 2026-08-28 — decided): all files carry versioning; 'Envision GitHub as a model.' Every posted delivery automatically creates an immutable version; internal chain = what we produced (commits), customer print rev = label on a version (tag). Deprecation RULED same day: versions immutable forever; metadata marks — superseded (automatic on replacement) vs deprecated/do-not-cut (explicit human call with reason; re-posting = RED warning). Default open = latest delivered. | NEW QUESTION 2026-10-10 (Jordan '1. Yes, let's design it ... discuss before anything gets built'): drop a customer's NEW REVISION DXF onto an existing cleaned job -- carry the recorded cleanup/tooling rows across by nearest-feature matching, list any row that cannot re-attach, old revision kept as an openable version. Today a re-upload makes a new job (no such door). Jordan has jobs in mind it would help; design discussion first, nothing built. | JORDAN ANSWERS 2026-10-10 (question, nothing built): (1) the case is Detroit Wrecker -- they change a hole size or a piece of outer profile and bury "V2-10-10-2026-b" somewhere in the part number; seeing WHICH part changed and the overlay is the value. (2) update-nested-and-posted vs part-only = CASE BY CASE, operator options (aid-the-operator), never one fixed behaviour. (3) his ask: how do we tell which listed part is being revised when names run from "Rev B" to convoluted strings? PROPOSED: pair by SHAPE first (outline size, hole count/sizes, outline overlay score), name similarity only a second hint, never a name parser; pairing table operator confirms/re-pairs, each pair offers revise / new part / skip. Prior Detroit Wrecker work = display-only shared-prefix tail labels (ui-partlist-brick21, 2026-09-17), nothing on revisions. Unsaved-rows guard: Jordan asks if a Save button suits -- Save list exists; proposal = Save and leave / Leave without saving / Stay on the leave prompt. | JORDAN 2026-10-10 (question): shape-first pairing YES, "as long as it is user-friendly"; asks what the operator workflow looks like and whether there is a "New Rev" button. PROPOSED: a New revision button on the Part list tab (and a file dropped onto an open list asks new parts vs new revision) -> pairing table -> overlay per pair -> revise/new/skip per pair -> for nested/posted parts, the operator picks part-only or refresh the nest too. Nothing built.
- •Common-line cutting — wanted, gated by a shop preference set at onboarding intent — intent (Jordan, 2026-08-28): common-line cutting functionality wanted; the modal's common-line block defaults COLLAPSED under a chevron for a precision shop and OPEN for a speed shop — default disclosure seeded by the onboarding archetype, never fully hidden. Reference: the common-line block of the old CAM's Layout Array dialog.
- •ONE SOURCE OF TRUTH, THREE LENSES — every UI feature exists on Web, Mac and PC (Aristide 2026-09-01) ruling — ruling (Aristide 2026-09-01, 'one big last rule for the UI'): "We need to have one source of truth, always. When we ask for a feature or button, it needs to be developed for all versions: Web or Mac or PC. So it needs to be looked at through all 3 lenses, always. Do not develop a feature for the web version that later can't be also created for the PC and vice versa. Same for Mac vs web." Two binding halves: (1) ONE SOURCE OF TRUTH -- a feature's logic, data and defaults live once, in the shared engine, never re-implemented per platform (the standing build rule 'data in JSON, generator separate from presentation' is this rule's foundation: engine decides, every shell renders); (2) the THREE-LENS GATE -- before any feature or button is accepted for one platform, it must be checked as buildable on all three (Web, Mac, PC); a design that only one platform can carry is rejected at design time, not discovered later. Applies from the FIRST UI work onward -- the phase rule still holds (record intent, build engine seams), and this ruling is why the engine-slot discipline (per-contour overrides, layout-modal one-clicks, drag validator) keeps every UI feature representable as data + engine calls that any of the three shells can drive.
- •Onboarding wizard — shop-level preferences asked once, up front intent — intent (Jordan, 2026-08-28, first mention): shop-level preference questions asked once at setup. Underlying axis (same day): two kinds of shops — precision-first (his) vs speed/efficiency-first — 'We need to be able to accommodate both'; the archetype seeds defaults (common-line the first case), never locks features. | 2026-10-30: wizard asks for the shop's logo (see cut-playback-animation); saves through its own door POST /api/shop/logo, kept across wizard saves.
- •Uneven +/- tolerance — default to the CENTER of the band (Jordan 2026-08-27) ruling — ruling: 'When a tolerance has an uneven + versus - let's make it a rule to go to the center of the tolerance. If the operator disagrees they will be able to manually change the hole size, but center of tolerance should be the default.' Where we generate or size geometry from a print callout, the default cut size is the mid-band value; a symmetric +/- keeps nominal (same number). Operator override rides the per-contour right-click slot. First applied: build 145 (LS1156258 holes o3.8 +0.08/-0.03 -> o.1506).
- •Nests fill Y FIRST — full sheet height, remnant one vertical slab (Jordan 2026-08-27) ruling — ruling: 'I see once again that you did not maximize the Y first. Why does this keep recurring? I thought it was a rule already.' Every nest stacks the sheet's full height before consuming X; leftover is one clean full-height vertical slab at max X. Max-Y is judged against the SHEET EDGE, not an assumed margin — his NC 28585 runs 32 rows to 47.845 of a 48in sheet; our 0.5 margin (assumed since build 137, never ruled) + the Rev2 0.25 aluminum gap is what cost the 32nd row. Numbers answered same day: margin DERIVES from the Rev2 min_gap column (see nest-margin-from-min-gap); builds 148/149 re-issued, rule wired into nest_rules.py.
- •Pocket backfill — a spill sheet empties into the true-outline gaps of earlier sheets (Jordan 2026-08-31) record — record: born on build 153 — Jordan: 'I know the 2 rows on sheet 4 could fit in the gaps on the other 3.' The row packer's monotone right-profile can never revisit the concave pockets between meshed long parts once a row closes, so spill opened a 4th sheet while inches-deep pockets sat empty. split_parts.pocket_backfill now runs after packing: last-sheet parts are placed into REAL free space on earlier sheets — occupancy-bitmap prefilter, then exact placed-outline clearance at the ruled gap and pierce standoff; audit_clearance stays the gate. All-or-nothing per sheet (a last sheet that cannot fully empty is restored as packed — partial moves buy no material and scramble a reviewed layout). Candidates are capped at each sheet's used X extent, so the clean remnant slab is never spent automatically (that spend stays the operator's click, per the spread-X ruling). Locked rotations honored. First applied: build 154 (ISV-H recall prototype, 4 sheets -> 3, util 50.6 -> 67.5, audited gap 0.2502). stats.pocket_backfilled counts the moves. Nest-in-hole ruled an operator option same day (Jordan): the engine may use big interior cutouts only as an operator toggle — intent recorded, UI not built.
- •Sheet-edge margin DERIVES from the Rev2 min_gap column — and the operator may shrink both (Jordan 2026-08-27) ruling — ruling: 'The 0.5 margin is not a rule, this should be derived from the "minimum gap" column of the tables we provided. In this case it should be set to 0.25 (.125" aluminum, cell 51 U).' Gap and edge margin are ONE table value; the operator may shrink them case by case (easy in the interface). His worked example on LS1156258: 0.23 instead of 0.25 — 0.020 tighter — fits 32 rows/col instead of 31, 12 columns instead of 13, saving over 5in of X. Both options delivered (builds 148/149) so the operator picks; applied to stainless same day — build 150 re-tiles the 3A76 lattice at margin 0.2 (was assumed 0.5): 300 pcs vs 288. In code: tables.nest_gap / tables.sheet_margin / nest_rules.resolve_spacing.
- •Free-rotation double-lattice nest search — the between-column meshing the shelf packer lacks (trial_lattice.py) record — record: angle sweep + 180-pair unit cell + slide-to-contact on TRUE outlines, tiled on lattice vectors; the pairwise fine-outline audit is the gate, never the constructor. Three production deliveries: build 147 (3A76, 36x60), build 157 (untooled) and build 158 (EXM275FG-0625 TOOLED FIRST per the true-nesting order — Jordan 2026-08-31 'add the real toolpath THEN nest': outer lead 0.15 arrayed with the part, common start point searched so every copy's pierce lands in a meshing void, verified exhaustively at 0.2745 clear-air vs the 0.15 standoff; still 99 on 36x48 .125 copper at the ruled 0.2 gap vs the shop's 94 at their measured 0.303 = lead+standoff across a straight channel — their NC 66261 layout, 0/180 half-offset rows, is the search's theta=0 case and it reproduces exactly 94 there). Benchmark 12729704: 114 vs their 108 (not delivered). Still a per-job script, not wired into split_parts — the standard path still advances columns by full bbox; recorded gap.
- •Two-orientation true nest = STRICT alternation, two P9997 macros (Jordan 2026-08-31 — ruling) ruling — ruling, on build 159's free-packed 125/65 mix: 'There are two orientations, which makes sense, but then they are not nested evenly, I would make every other part 180 degrees, and end up with two true nests, and therefore the main program would have two P9997 macros to make editing very easy. That would fall in line with what we've discussed before regarding nesting biases.' When a true nest runs two orientations, they alternate REGULARLY (every other part 180) so each orientation forms its own sublattice — two true nests, one P9997 Y-array macro each, trivially editable. An irregular orientation mix from the free packer is a defect on a same-part nest. Engine: nest_rules.fill_y_first(alt_every=True) — rows alternate 0/180 within every column, columns identical. First applied: build 160 (196 pcs, 0-deg lattice 4/col + 180 lattice 3/col x 28 cols; pierce channels 0.75 = lead+standoff shared row-wise between adjacent columns). REFINED same day (Jordan, marked screenshot of 159's print — the correct 'mini-nest' circled, an irregular same-orientation adjacency crossed off): 'approach it like math, you need to find the common denominator, and the smallest pair of parts that together consume the least amount of material. Once you have defined that, you copy that in Y and then X.' The PAIR is the unit: measure its least-material form on true outlines (meshing/phase-shift tried, not assumed), then tile the pair Y-first, then X. Build 161 applies it: long-axis-X orientation (the pierce channel amortizes over the 7.8in column length, not the 1.26in width — 160's 90-deg turn was the wrong economics, superseded), X phase sweep measured <=0.0002in of scallop meshing (irregular lobe spacing — flat-stacked aligned pair IS the minimum, as his screenshot shows), 5 cols x 19 pairs = 190 exactly, gap 0.3000, pierce clear 0.3791, remnant slab 76.9in (was 63.4). COLUMN-FLIP VARIANT + the WHY (Jordan, same day, his old CAM Edit Array screenshot — 'we talked about this example before': the flip-every-other-column trick, now with its construction order): 'I take the part and maximize Y... the only way I can maximize material is if I share the space of the lead-ins between the parts. So what I do, I flip one part, place it in the correct spot so that the leadin space is shared, and then I copy the whole left column and give it the space that I need for that one flipped part and duplicate that in X. Next, I will take that one flipped part and duplicate that in Y. Lastly, I take that full column and duplicate that in X.' The unit cell is the COLUMN PAIR seeded by ONE flipped part placed for shared lead space — the X-axis form of the mini-nest common denominator. Three standing objectives named: minimize material lost; consistency for the human breaking out the parts; the shortest GCode, editable by one value ('I can change one value and the whole program runs no problem' — the array parameter). Engine: fill_y_first(alt_flip=True) is the slot; the shared-lead tuck offset (the 'correct spot' for that one flipped part, found on true outlines + lead envelope) is NOT computed yet — recorded gap. BUILD ORDERED 2026-08-31 (Jordan: 'Build it'): the alt_flip shared-lead tuck offset — solve the flipped column's position from true outlines + lead envelope instead of measuring it off shop layouts. BUILT 2026-09-01: nest_rules.tuck_alt_flip + fill_y_first(alt_flip=True, tuck=...) — see pin alt-flip-tuck-solver. POSTED 2026-08-31: O33286 (build 163) IS this program — main + two G172/G65P9997 arrays (I=column pitch 8.5526, J=pair pitch 3.1198, K19 Q5; K=Y-rows/Q=X-cols decoded from 33215.NC's own array origins: its third array starts at Y38.433 = .5 + 5x7.5866), subprograms O75286 (0-deg) / O75287 (the IDENTICAL toolpath rotated 180 about the part centre), 212 lines for 190 parts — edit one value, the whole nest follows. nc_audit now transparently EXPANDS P9997 programs and judges the 1140-boundary part-by-part form the machine executes: 0 Rev2 tooling mismatches, geom dev 0.0005, comp all G41; only findings = 950 sanctioned hole centre-pierces (o10/o9 mm < 0.375 standoff), reported never hidden. TUCK-PAIR FORM POSTED 2026-09-01: O33289 (build 164) — the column-flip construction as a delivered program: pair_pitch 16.592 vs 17.105 per two O33286-form columns, 14 columns = 532 pcs on the full 60x120 vs 494; same two-macro shape, sub O75290 = the toolpath rotated 180 and tucked (dx 8.5366, dy 0.4238). See pin alt-flip-tuck-solver.
- •Shared-lead tuck offset SOLVED on true outlines (built 2026-09-01; posted as O33289, build 164) record — The ordered alt_flip engine (Jordan 2026-08-31 'Build it'): nest_rules.tuck_alt_flip(opts, lead, pitch_y, gap, standoff) computes where the one flipped part goes so the lead-in space is shared — slide-to-contact from outside on the TRUE outline + lead/pierce envelope, never bounding boxes. Pair unit: [0-deg col] –shared lead channel– [180 col] –bare gap– next pair; the channel is paid once per PAIR. Constraints per interacting row: ruled outline gap, pierce clear-air BOTH directions, lead-cut clearance (default = gap — a lead is a cut). dy swept and refined; every candidate rides beside the winner with its numbers (nest-objective-function rule); winner re-audited on the fine outline at the ruled values — construction pads 0.010, audit separate (the 3A76 lesson). fill_y_first(alt_flip=True, tuck=...) consumes it: pair columns advance by pair_pitch, odd columns at (dx, dy) rot 180, headroom guard raises with a dy_max re-solve hint; excludes spreads/alt_every/gap_x. Proven: test_tuck.py 22 controls (flat-face closed form recovered at dy=0; tab-nosed part tucks 0.6 under the flat pair; minimality — 0.06 tighter breaks a ruled clearance, measured by an independent shapely check). Smoke on 3683209C2 (Rev2 MS 3/8: lead .375 standoff .375 gap .3): dx 8.5366, dy 0.4238 (capped by column headroom), pair_pitch 16.592 — 14 columns on 60x120 where the O33286 every-channel-0.75 form fits 13: 532 vs 494 parts, X for 5 columns 40.99 vs 42.76 (1.78in saved). Interesting find, proven in controls: even a plain rectangle beats the flat closed form — at interleaved dy the pierce nestles corner-wise into the row gap. DELIVERED 2026-09-01: build 164 / O33289 (deliver_post164_nav209_tuck.py) posts the full-sheet tuck-pair form — 14 cols x 38 = 532 pcs, two P9997 macros (O75289 0-deg 7x38, O75290 180 tucked 7x38 at +8.5366,+0.4238), 212-line program; expanded 3192-boundary audit clean (0 tooling mismatches, geom dev 0.0007, min true-outline gap exactly the ruled 0.3, only findings = 2660 sanctioned hole centre-pierces). Job asked 190 — recorded beside the 532 filled (capacity comparator, Jordan picks which form cuts). Program number 33289 skips reserved 33287/33288 (parked Navistar).
- •The standing nest objective function (Jordan 2026-08-31 — ruling, confirmed 'yes') ruling — ruling. Asked 'what didn't I tell you to make this never go wrong again', Jordan confirmed this articulation: MINIMIZE THE MATERIAL CONSUMED PER PART BY THE FULL REPEATING CYCLE — part, gap, AND lead/pierce envelope together — with every always-apply rule on, tiled so regularly that each orientation is one array, one macro, one editable value, one pattern for the person breaking parts out. Every individual correction (159's irregular mix, 160's wrong orientation economics, the mini-nest pair, the column flip, EXM275FG's dropped leads) is this one function applied to a case. Three consequences, all confirmed: (1) the TOOLPATH IS INSIDE THE UNIT from the first move — lead-in space is material, the common denominator is part+lead+pierce envelope, never bare geometry; (2) a correction on one job is a WINDOW into the rule, never the rule — derive the invariant, don't transplant the example's surface onto the next job; (3) every nest DELIVERY carries the candidate units that were rejected, with their numbers, beside the winner — a wrong pick must show on our sheet, not in Jordan's marked-up screenshot. Self-test ('approach it like math'): if we can't DERIVE Jordan's layout from the stated objectives, we don't understand yet — measure until we can, don't wait for markup.
- •One-click FINISH EVEN COLUMNS — round qty up to fill the last column (Jordan 2026-08-31) intentmixed — intent + engine record: 'we should include a one-click option to finish even columns in Y, meaning we asked for 190 pcs, but we can fit a few more to finish that last column (and also end up with cleaner GCode - one set of P9997 macros) so the total might end up being 194 with clean, even columns.' The nesting tab offers a one-click 'finish columns': qty rounds UP to n_cols x per_col so no column runs partial and the Y-array macro pattern stays uniform. Operator's click, never a default (it cuts more parts than were asked for); the asked qty is recorded beside the filled qty. Engine slot IS built: nest_rules.fill_y_first(finish_columns=True); first applied build 160 (asked 190, filled 196 = 28x7).
- •Interface intent — nest spacing prompt: table default, operator shrink OR spread-out, both layouts shown (Jordan 2026-08-27) intent — intent: at the nesting step the spacing (gap + derived margin) defaults from the Rev2 min_gap; the operator can shrink it per job — 'this should be easy to do in the interface.' And the interface should SHOW the trade: Jordan's worked example (0.23 vs 0.25 on LS1156258 = one whole column, over 5in of X) is the template — 'You should give the operator both options and they can pick.' So the nesting tab presents the ruled layout beside tightened alternative(s) with the material saved, and the operator picks. Same day he added the opposite command: SPREAD IT OUT — with large parts, small gaps and plenty of scrap at the top of the columns, one command evens out all the gaps, which spreads the heat load and reduces thermal-expansion error during cutting. Engine: nest_rules.fill_y_first(spread_y=True). And X: the auto spread never touches the clean remnant slab, but the OPERATOR gets manual X-spacing increments (his old CAM Layout Array demo: X spacing 0.23 -> 1.03 walks the columns across the sheet) — engine slot fill_y_first(gap_x=...). The resolved value is a STARTING POINT, not a floor — the operator may override below it ('just your starting point'). And it's ONE MODAL: shrink to max Y + max remnant, spread out, or FLIP EVERY OTHER COLUMN — 'one trick that us humans do that no nesting software does, and we want you to do it': 180 the odd columns so pierce points align in Y, X spacing unchanged, squeezing in a whole extra column on a tight sheet. Engine: fill_y_first(alt_flip=True). Sibling intents: free-rotation toggle, nest-tooling feedback loop, per-contour override. Phase rule: record here, do NOT build the UI. ANSWERED 2026-08-27: the tight-nest demo's 180-pair element was teaching only (production 28585 runs one orientation); shortening lead-ins / moving pierce points in tight nests is MANUAL operator work, never an automatic default; and the modal's array face belongs to TRUE NESTING (same part duplicated, toolpath before nest) — see pin def-true-vs-part-by-part-nesting. ONE-CLICK CONFIRMED + REFINED (Jordan 2026-08-28, live-nest screenshot, 3 cols x 18 rows, X 0.2/Y 0.32): he manually evened the Y gap — top, bottom, AND between parts — for thermal-expansion control, and asked for one-click 'spread Y', 'spread X', and 'back to table values'. The spread evening now includes the edge gaps (supersedes edge-margins-stay-put); spread X spends the clean remnant slab so it is only ever the operator's click; reset reseeds from the Rev2 min_gap. Engine updated same commit: fill_y_first(spread_y=True / spread_x=True), defaults = the reset.
- •THE PHILOSOPHY — aid the operator, never decide for the operator (Jordan 2026-08-27) ruling — ruling: 'We are here to aid the operator, not to decide things for the operator. That is the whole philosophy of our software, we need to wrap ourselves around the workflow of the customer instead of forcing the customer to adhere to our limitations.' Said while overruling our lower-right pierce bias with the flip-every-other-column trick. Table values seed, never bind; biases guide, never block; every automatic decision stays operator-overridable and the override is recorded, not resisted.
- •A beat only counts with every always-apply rule in force (Jordan 2026-08-31 — ruling) ruling — ruling, on EXM275FG-0625: 'once I challenged you, you tried to beat me without applying the rules. That is pleasing behavior, and not acceptable in our environment. So, in this case you dropped the lead-ins like I pointed out, and that is one of the rules that always have to be applied. Look, I expect you to beat me, but not by cutting corners.' Build 157 delivered a 99-vs-94 nest count with UNTOOLED geometry — no leads in the envelope — against his measured layout that carries lead+standoff room; build 158 (tooled, still 99) is the honest form. The rule: a comparison against the shop only counts when every always-apply rule (lead-ins at ruled length, pierce clear-air, gaps, cut-order safety) is applied to OUR side; a count achieved by dropping one is not a result, it is pleasing behavior. When a rule must be relaxed to match a shop layout, say so explicitly — never silently omit it.
- •Print DIMENSIONS govern over drawn geometry (Jordan 2026-08-31 — ruling) ruling — ruling: 'The goal for us will be to have a program that can read pdf prints and generate a dxf from the called out dimensions. If the customer can only provide a pdf print with dimensions then it is ethical of us to assume the stated dimensions are correct, even if the pdf is drawn slightly off.' Where a callout and the drawn geometry disagree, the callout wins; undimensioned features follow the design intent the drawing shows (concentric, tangent, flush), re-solved around the dimensioned ones. The trace becomes the VERIFICATION layer — deltas measured and reported against the print's tolerance. First applied: nav209_part.py build 160 (supersedes 159's internally-consistent-drawn call on holes 3/4: callout ys 123/151, lobes+waists re-solved, trace verifies at 0.333mm max inside +-0.8).
- •True nesting vs part-by-part nesting — two kinds, two pipeline orders (Jordan 2026-08-27) ruling — ruling: same part duplicated over and over = TRUE NESTING — the toolpath is established FIRST on the single part, then the nest duplicates one short piece of G-code per placement. Several unique shapes on one sheet (Jordan's term: Torongo files) = PART-BY-PART NESTING — nest first, toolpath after. The lead/cut-order and nest stages swap depending on which kind the job is.
- •Part-list nesting — Qty / Rotate / Bridge / Filler columns (Jordan 2026-08-31) rulingmixed — ruling+intent: part-by-part nesting is driven by a PART LIST — per part: Qty (0 = listed but excluded), Rotate step (360 = locked, 180 = 0/180, 90 = quarter steps; the grain-direction click writes this), Bridge = per-part gap seeded from the Rev2 min_gap — OUR semantics: the TOTAL gap around that part (the old CAM's half-sum .15+.15=.3 rejected as confusing), operator-overridable per part, larger value governs each pair (confirmed) with the small-bridge hunt as the recovery lever; Filler flag = this part may be duplicated beyond ordered qty to fill the sheet — default UNCLICKED: never fill, maximize Y, keep the X remnant. bridge also governs the part's SHEET-EDGE clearance (per-part margin); filler extras ship asked-qty beside filled-qty and obey bridge/rotate like ordered parts; Priority column: ignored, ruled out. Benchmark: the old CAM put the LH-2.5 340-part 3/8 job on 5 sheets 60x120 — we need not beat 5, but 7 is a fail (job-specific target, education only — no deliverable; a real test job follows). HOME ruling 2026-08-31 (Jordan): the packer engine is still to be built ('we will spend the next few days on that'), but the part-list columns already get their HOME in the nesting tab — the per-part grid (qty/rotate/bridge/filler) is part of the nest stage's data model now, so the packer plugs into existing fields when it lands. ENGINE BUILT 2026-09-01: part_list_nest.pack() -- see pin part-list-packer; every column semantic above is enforced in code and proven in test_part_list.py (24 controls).
- •Part-list packer ENGINE — part_list_nest.pack() (built 2026-09-01) record — record: the part-by-part packer driven by the ruled part-list columns (pin part-list-nest-columns) is BUILT: part_list_nest.pack(items, sheet_w, sheet_h, table_gap, standoff) -- pure geometry engine, no UI (phase rule). Per part: qty (0 = listed-but-excluded, quantities split across sheets), rotate step (360/0 = locked, 180, 90, any divisor of 360; non-divisor raises), bridge = the FULL clearance around the part (None = table_gap seed recorded source 'table', explicit = 'operator', either direction), filler flag (default off: never fill, max Y, X remnant kept; on: extras fill OPENED sheets only, never a new sheet, obey bridge/rotate exactly, asked-qty reported beside filled-qty). Pairwise gap = max of the two bridges, enforced by a per-bin Pareto frontier (right-x, owner bridge) in the sliding profile so each pair is charged its own requirement; the bridge also sets that part's sheet-edge clearance (per-part margin). Fill-Y-first via the nest_y_first transposed frame (a row = a real full-height column; remnant = one clean X slab, used_x reported per sheet); placement score = projected real-X use, so a rotation variant only turns the part when it buys X back. Leads: caller passes pre-planned lead/pierce samples (split_parts lineage); lead-to-neighbour clearance = max(standoff, pair gap). The engine AUDITS its own result from the placed points at the ruled values (construction slides on padded bins -- separate arithmetic, the 3A76 lesson) and RAISES on any miss; report carries adjacencies (required / governed_by / measured), bridges with sources, excluded list, and 'hunt' = every column advance that paid a neighbouring column's larger max-bridge (Jordan's regrouping lever; equal-size parts already group by bridge in the sort). Terminology guard: this 'bridge' is the old CAM's part-GAP column, never bridges.py's island bridge. Proven: test_part_list.py, 24 controls on synthetic fixtures -- no delivery yet; Jordan's real test job is the first fixture when it lands (LH-2.5 was education only).
- •The old CAM Basic tab — the CAD editor's reference feature set (Aristide + Jordan, 2026-08-31) record — reference: Aristide read the old CAM sidebar's Basic tab out block by block (Jordan supplied the screenshot, incoming/1788211410_645725_file.jpg). Three tabs exist — Basic / Advanced / Dimension; this covers Basic only. Its edit/QC block (Fit Arc, Join, Remove Small Segments, Mark Open Polylines, Highlight Duplicate Segments, Mark Small Segments, Mark Non-Tangent Corners, Mark Large Radius) is our healing pipeline as MANUAL buttons — same defect taxonomy, opposite philosophy (operator finds+fixes each; we detect+heal+report). Corner-treatment block (Chamfer, Fillet, Inside Fillet, Corner Step, Edge Recess, Edge U-Cut, Edge V-Cut) not yet in our catalog. RULING added same day: automated or not, 'all buttons like these need a home' — automation sets the default, the manual button stays as the operator's override. General (Windows-standard) top toolbar also recorded in detail.
- •The old CAM Advanced tab — notches, booleans, splines, sheet-metal 3D (Aristide + Jordan, 2026-08-31) record — reference: Aristide dictated the Advanced tab (Jordan's screenshot incoming/1788211783_645725_Advanced_Tab.JPG confirms the block structure). Notch suite = manual identical-feature propagation; booleans (union/intersection/subtraction) = our filled-art union lessons as buttons; spline tools rebuild what the old CAM's own DXF import drops; the sheet-metal 3D block (flange/plane joining, follow to 3D model, plane extract, Edit bend information) is their face of our step_io/unfold territory — Edit bend information is where the open K-factor question lives; Mark text vs TrueType text = the etch-vs-cut split on text. Dimension tab still to come.
- •The old CAM Dimension tab — the dimensioning toolbar Jordan uses daily (Aristide + Jordan, 2026-08-31) record — reference: Aristide dictated the Dimension tab (Jordan's screenshot incoming/1788212237_645725_Dimension_Tab.JPG confirms the blocks) — 'Jordan says he uses these a lot,' so dimensioning is a daily operator activity, not a drafting afterthought. Linear block = a 4x3 matrix (horizontal/vertical/aligned/perpendicular x baseline/continue/ordinate) + smart dimension; radial/angular block (radius center, radius diameter, center diameter, angular, 3-point angular, callout, segment, multi dimension); properties/auto-dimension/text/edit-text/view-legends; view block. Completes the three-tab set (Basic/Advanced/Dimension). Ties to make_prints dimensioned pages and pdf-dims-govern — the shop lives in callouts.
- •UI BUILD PHASE OPENED (Aristide, 2026-09-01 — ruling) ruling — Aristide, 2026-09-01: 'go ahead. let's go. you have all the information. start building the UI.' The owner's call opens the interface as a BUILDABLE thing — this supersedes the 2026-08-02 phase rule's 'do not build the interface' for the UI itself; every definition-phase ruling, gate and table stands unchanged, and the UI is built strictly on the recorded design corpus (paper-design signed off 2026-08-17; sitting answers 2026-08-19 incl. the A+C pick; ui-one-source-three-lenses; aid-the-operator-philosophy). Build order: turn-sized bricks, engine-first, honest placeholders for unwired stages.
- •kerfmaster app — brick 1: shared-engine server + canvas shell + Jobs home (2026-09-01) record — BUILT (app/): the one-source-three-lenses architecture in code. app/server.py — stdlib-only HTTP door over the SAME engine modules the boards run (dxf_io.parse → to_inches → heal.heal → find_jogs → qc.analyze, fidelity vs true source with the board's own measure); the job is a JSON document (app/jobs/<id>/job.json + geometry.json) — the one source of truth every shell renders; Web/Mac/PC = the identical renderer (app/web/, plain HTTP+JSON+canvas, nothing platform-only), native shells will wrap it, never reimplement. Shell per the rulings: canvas owns the screen; eight top tabs (Intake…Deliver) wearing status colours PLUS glyphs (✓/!/✕ — the colour-blind-safe half of agenda item 4, done cheap-now); Jobs home front door with per-job mini tab-strips + drop/browse intake; left toolbar (contents to grow per tab), right checks drawer (A+C dock ground state; tear-off/workspaces = later brick); original DXF as toggleable gray base layer under healed overlay (house style); zoom %% readout + presets AND self-proving scale bar in user units (zoom ruling); light/dark one-click; per-user units pref, inputs accept unit suffixes (3mm/0.125in); one-letter tool keys (V/F/O/H/J). Blocked intake = red tab + engine's own message, warn-never-block elsewhere. Unwired tabs say so honestly in the drawer. Persistent: systemd kerfmaster-app (unit in repo, setup_app.sh idempotent) + mca-host sub kerfmaster-app → https://kerfmaster-app.aristide.mycloudally.com — verified live over the public URL (ex2_dirty job: mm detect, heal PASS 1.08 thou, 19 QC flags, auto-lands on the flagged tab). NOT YET (brick list): nest/cutplan/post/deliver screens, sketcher, tear-off panels, sales surface, first-run tour. SHORTCUTS FIT THE SCENE 2026-09-17 (Jordan: 'Shortcut keys should also be global. Right now I'm in the Nest tab, and F isn't working'): the F key and the palette Fit button were hardwired to fit('fitpart') -- dead on every sheet view, and silently a no-op on part-list jobs, which carry no part extents at all. fitScene() now makes the same sheet-vs-part pick the tab click and deep link make; fit() itself falls through to the sheet extents when the job has no geometry of its own; and typing in a focused SELECT/TEXTAREA no longer leaks into the shortcut keys (only INPUT was guarded). Verified via Playwright on the CAMP part-list Nest tab.
- •Part review screen (UI brick 2) — the per-contour override ruling on glass record — BUILT (app/, brick 2 of the 2026-09-01 build-them-all go): the Part review tab is the 2026-08-24 right-click ruling running live. Operator assigns material × machine from the Rev2 tables (only rows with a recorded shop post code are offered — Mild Steel ↔ MSO7, the deliver-script pairing; no invented mappings) and the server plans the toolpath through rules.check_drag — the SAME click-time entry point the drag validator uses (new want_stats flag returns the plan it judged: one plan, one judgment, no drift). Canvas draws the AS-CUT paths over the gray base layer: sequence numbers, pierce rings, dashed lead-ins, finding contours tinted red/yellow. Click or right-click a contour → checks drawer shows EVERY ruled field as ran-value + source (class, condition #, comp register D, comp side, direction, sequence, start/pierce, clear air, lead, tab — tooling_doc's record verbatim) plus override slots: start/pierce = pick-on-canvas (the drag-handle model's click form), lead length = unit-suffix input; both re-plan through the engine's overrides= seam and the ran value flips to source:operator — seed never bind, warn never block, recorded never silent. Non-consumable slots say honestly their engine inputs aren't built. Findings list red-first with the shared rule messages; stage dot done/flagged/blocked (engine refusal = blocked + its own words, e.g. beam_comp TBD rows). tooling.json + review.json persist in the job dir; deep link #job=<id>&tab=review. Verified live (ex2_dirty: 7 contours tooled, 2 red / 4 yellow honest findings, override round trip lead 0.15→0.08 source:operator, test_drag 10 + test_tooling_doc 15 controls pass). NOT YET: drag as one continuous handle (click-pick form only), remaining brick-list screens.
- •Nest screen (UI brick 3) — the layout-array modal rulings on glass record — BUILT (app/, brick 3 of the 2026-09-01 build-them-all go): the Nest tab is the layout-array modal rulings running live, on the ruled engines only. Server POST/GET /api/jobs/<id>/nest: TRUE-nests the REVIEWED part (material x machine come from the Part review stage -- toolpath before nest for a duplicated part, ruling def-true-vs-part-by-part-nesting) through nest_rules.resolve_spacing (gap AND edge margin seed from the Rev2 min_gap; operator overrides run in either direction -- starting point, never a floor -- and every value records ran + source: table:min_gap / derived:gap / operator, never silent) and nest_rules.fill_y_first (fill Y first, remnant one clean full-height slab; spread_y / spread_x / gap_x / alt_flip / alt_every / finish_columns are the operator's ruled one-clicks). Multi-sheet by per-sheet capacity, remainder on the last; sheet = the machine bed via tables.bed() (120x60 X-major); engine refusal = blocked stage with the engine's own words; nest.json persists per job. Drawer = the layout-array modal: qty, gap/margin/X-spacing unit-suffix inputs whose placeholders show the ruled current value (min_gap now rides on /api/materials options), orientation select (all one way / flip every other column / every other part 180), finish-even-columns checkbox with asked -> filled recorded beside each other, one-click spread Y / spread X / back-to-table-values (spread X labelled as spending the remnant slab -- operator's click only). Canvas draws the sheet + dashed margin, every placement stroked from the REAL healed geometry (one cached true-arc Path2D placed by canvas transform, 180s rotated about the part centre), remnant slab tinted, per-sheet caption. Defect caught + fixed in the build: the view extents pad arcs by their full circle -- nesting on them inflated the 209 part 1.26 -> 3.456 in wide; the job document now carries part_bbox (true sampled bbox) and the nest grid + renderer run on it. Verified live over the public URL on the real 209 part (MS 3/8, Rev2 min_gap 0.3): 190 asked -> 196 filled = 28 cols x 7/col, the recorded build-160 finish-even-columns numbers reproduced exactly; alt_flip renders the odd columns 180; gap 0.23 operator override records source:operator; remnant slab 76.3 in. HONEST LIMITS stated on-screen: grid nest on the part bounding box; leads/pierce envelope not in the nest unit yet -- the nest<->tooling loop, tuck pairs, part-list packing and free rotation have engines but not this screen (later bricks).
- •Cut plan screen (UI brick 4) — the toolpath view judged by the shared rules record — BUILT (app/, brick 4 of the 2026-09-01 build-them-all go): the Cut plan tab is the toolpath view (Jordan 2026-08-28, pin toolpath-view-intent) as a live screen -- the path the laser will follow, judged at click time by the SAME shared rule functions the NC audit runs. Server POST/GET /api/jobs/<id>/cutplan: the sequence IS review.json's plan array (the engine's own safety order -- outer profile last, safety before distance; requires Part review first, refusal in the engine's own words), judged by rules.check_plan with the audit's own parameter sourcing (tables.drop_through / tables.standoff(material)) -- one plan, one judgment, no drift with the final posted-NC gate. Document per step: seq, bnd id, outer/interior, comp word, cut length, straight-line rapid in (from previous contour end to this pierce) with its length; totals cut travel + rapid travel; findings red-first; cutplan.json persists; stage done/flagged/blocked. A re-plan in Part review DELETES the persisted cut plan and resets the stage to pending -- a stale judgment never keeps serving (one source of truth). Renderer: as-cut paths tinted by finding severity, TWO direction arrowheads per contour along the cut, pierce dots, dashed rapids with an arrowhead at the landing pierce (drawn under the cuts), sequence number at each contour; drawer = ordered cut-order list (circled seq badges tinted by severity, click to select, selection syncs with canvas + right-click), findings rows, totals. Honest limits on-screen: Manual Sort (click-in-order) is recorded intent -- the operator sequence is not a consumable engine input yet, so the screen shows the engine's order and where it would warn; rapids are straight lines (rapid routing around held slugs = the recorded unbuilt Traverse Routing lever), crossings counted never hidden. Verified live over the public URL: 209 part 6 contours outer-last 0 red / 6 yellow; ex2_dirty 7 contours 2 red (wrong-side comp, cut-after-severed-outer) / 4 yellow; suites test_drag 10 + test_tooling_doc 15 + test_rules 11 pass. Deep link #job=<id>&tab=cutplan. [2026-09-01, brick 6: Manual Sort is BUILT and consumable -- the click-in-order UI lives on this screen; see ui-manual-sort-brick6.]
- •Post screen (UI brick 5) — the posted program, audited, with the warning callouts in the file record — BUILT (app/, brick 5 of the 2026-09-01 build-them-all go): the Post tab turns the reviewed toolpath into a real Fanuc macro-B program with the audit and warning callouts riding IN the file. POST/GET /api/jobs/<id>/post + GET post.nc|post_tooling.json|post_slugs.csv. The server posts the SAME engine inputs Part review planned with -- material x machine tooling row (tables.rev2_tooling) + the operator's recorded overrides read back through tooling_doc.overrides_from(tooling.json) -- through emit.write_gcode_macrob in the master dialect, so the file IS the reviewed plan, posted; then the one shared sequence every posting surface runs: nc_warn.audit_and_inject -- audit vs source (Jordan 2026-08-12), (CONTAINS N WARNINGS) + per-boundary (WARNING k: SEV RULE) callouts written into the G-code (Jordan 2026-08-28), re-audit must judge identical. Warn never block: findings/anomalies flag the stage; only an engine refusal (MaterialIncomplete etc.) blocks it, in its own words. Program number per nest-name-prog-number: auto-assign next = last used + 1 (app/progseq.json seeded 33289 = this box's last posted; 9000-series macro space and parked 33287/33288 skipped), operator-overridable (recorded source:operator; since fix block 3 the override is USED ONCE by default -- the sequence does not move -- or restarts the sequence when the operator says so, reserved/used numbers a yellow warning, see app-onum-modes-block3), and a job KEEPS its number across re-posts. A re-plan in Part review deletes the posted files and resets the stage keeping the assigned number -- a stale program never keeps serving. Every post writes the tooling doc beside the NC (tooling-doc-model) and the numbered slug report when slugs exist. Drawer: program/material/machine/dialect/moves/extent as ran+source, download links, findings red-first (click = select contour), the audit's anomalies verbatim, first-24-line program preview; canvas = the cut-plan (or review) scene the program was posted from. Verified live over the public URL: 209 part O33291 0 red/6 yellow, (CONTAINS 6 WARNINGS) + 10 spot markers in-file, 134 lines; ex2_dirty O33290 2 red/4 yellow incl. wrong-side comp DO NOT RUN; operator onum round-trips to source:operator. Honest limits on-screen: posts the single reviewed part (the nested sheet program -- post_nest, P9997 macros -- is a later brick); operator sequence still not a consumable engine input; program-number scope (shop-wide vs per machine) open with Jordan. [2026-09-01, brick 6: operator sequence IS a consumable engine input now -- it rides into the post through overrides_from like every override; see ui-manual-sort-brick6.]
- •Manual Sort (UI brick 6) — the operator sequence as a CONSUMABLE engine input, click-in-order record — BUILT (brick 6 of the 2026-09-01 build-them-all go): Jordan's click-in-order model (2026-08-28, old-cam-add-toolpath-walkthrough -- 'exactly what we envisioned for the user interface'; never the old CAM's broken modifier keys) is now a consumable override end to end. ENGINE: 'sequence' joined tooling_doc.CONSUMABLE (same commit as the input, per the model rule); emit.write_gcode_macrob overrides= takes {'near','sequence':k} per feature, nearest-centroid binding like start/lead_length -- sequenced features cut FIRST in click order, unclicked keep the engine's safety order after them; the operator's order gets its rapids over held slugs RECOUNTED with the same _seg_hits_poly test (counted and reported, never silent); an outer clicked first takes its approach from home; sequence recorded per contour as ran+source (operator vs rule:safe-order) and the click index beside it in overrides.sequence; overrides_from round-trips it, unconsumed() no longer lists it; overrides=None stays byte-identical. Moves the ORDER, never a gate: a risky order fires the same shared rules (check_plan/check_drag == nc_audit -- outer_not_last red proven both surfaces, test_drag control 7) and rides into the posted NC via the existing nc_warn callouts. APP: run_review consumes sequence through the same override channel; run_cutplan judges the operator's order (sequence_source names it + operator_sequenced count); run_post consumes it via overrides_from like every override -- honest-limit notes updated. UI (Cut plan tab): Manual Sort section -- Click in order... mode (canvas clicks add/unpick, accent pick badges), Apply re-plans + re-judges, Back to engine order clears; the P9996/P9997 cost notice (Jordan 2026-08-28 ruling: a custom sequence drops the nest macros, program posts part-by-part) shows at the first departing click -- informational, never a block; review drawer's sequence slot is live (clear per contour). Defect fixed on the way: runReview read material/machine from the review drawer's selects only -- a re-plan from another tab silently no-opped; now falls back to the assigned review row. Verified live over the public URL (app/verify_seq.js, Playwright): 209 part -- all 6 contours clicked outer-first ran as clicked (source:operator on all 6), outer_not_last RED fired and rode into O33291's G-code, number kept across re-posts, Back to engine order restored 0-red clean. Suites: test_drag 13 + test_tooling_doc 21 + test_rules 11 + test_nc_warn 12 pass. Honest limits: nest-LEVEL part sequence (nest-part-sequence, serpentine default + numbered boxes) is a later brick; rapid routing still unbuilt (crossings counted, shown).
- •Deliver screen (UI brick 7) — the delivery set: versioned, census-checked, boarded record — BUILT (brick 7 of the 2026-09-01 build-them-all go): the Deliver screen -- the posted program becomes the DELIVERY SET, versioned and boarded. Server: POST/GET /api/jobs/<id>/deliver (+ GET /deliver/v<k>/<file>) requires the Post stage (refusal in honest words); writes an IMMUTABLE VERSION dir (jobs/<id>/deliver/vNNN) holding: the audited O<num>.nc (warnings riding in the file), the CAM-safe DXF written by emit.write_dxf_shop (the ruled writer for anything a human downloads) and CENSUS-CHECKED on the written file (only POLYLINE/VERTEX/SEQEND/CIRCLE; a census FAIL refuses the delivery), the numbered slug report, the tooling document, the FLOOR PACKET (Aristide 2026-08-19 ruling, PINLIST 7c: floor operators are file recipients, not app users -- program number big, material, machine, extent, slug count by number, part preview SVG, time estimate honestly PENDING, usage honestly n/a for a single part) rendered from packet.json (data in JSON, generator separate from presentation), and a full-set zip (design 3.8's folder/USB handoff). Job-versioning ruling (Jordan 2026-08-28) applied: append-only chain, delivery is the trigger, versions immutable forever -- a re-delivery appends v(n+1) and marks older versions superseded (metadata only, files never touched); a re-plan in Part review deletes the posted program but NOT deliveries -- it marks the deliver stage 'replanned' so the screen says v<n> predates the re-plan. Every delivery is also a NUMBERED BUILD on the comparison board (boards.py, kind 'app' -- one build sequence across DXF/vector/app so it can be said out loud), board page rendered from the same version dataset: downloads, warnings banner, findings + audit anomalies verbatim, census result, part SVG. Warn never block: ex2's 2-red program delivers flagged with the reds on every page and in the file. UI (Deliver tab, placeholder retired): Deliver button, DELIVERED v<n> banner, census/slug/program rows, board + packet + per-file download links, version chain list with superseded badges, honest 'by whom awaits operator accounts'. Verified live over the public URL (app/verify_deliver.js, Playwright, 12 checks): nav209 chain v1..v3 (builds 165-167) superseded correctly, number O33291 kept on every version, board build serves publicly, packet + NC (CONTAINS N WARNINGS) + zip download, DXF census independently re-checked on the served bytes; ex2_dirty v1 (build 168) flagged 2 red. Suites: test_drag 13 + test_tooling_doc 21 + test_rules 11 + test_nc_warn 12 pass. Honest limits on-screen: single reviewed part (nested-sheet delivery = later brick); the packet is SHOP-facing -- the customer sheet of the ruled customer/shop split is a later brick; time estimate PENDING (no estimator); 'delivered by whom' waits on operator accounts. Verify-script lesson re-learned: a hash-only goto does not reload the SPA -- the first run's ex2 section delivered nav209 v3 instead (build 167, immutable, stands as the honest record); fresh page per job.
- •Nested-sheet post (UI brick 8) — the P9997 macro program from the app, part-by-part when Manual Sort rules the macros out record — BUILT (brick 8 of the 2026-09-01 build-them-all go): the nested-sheet program posts from the app. Server: POST/GET /api/jobs/<id>/postnest (+ GET postnest.nc / postnest_tooling.json / postnest_slugs.csv) arrays the REVIEWED toolpath (same engine inputs run_post posts: Rev2 tooling row + overrides via tooling_doc.overrides_from) over the Nest tab's persisted layout. Exactly TWO shapes per Jordan's 2026-08-28 ruling (Mitsubishi controls won't mix nest macros and part-by-part sequences): MACRO mode (default) = the 33215.NC true-nest form via emit.write_gcode_macrob(nest=...) -- main O<n> with G172 origins + G65P9997 calls, one sub per orientation (two orientations = two P9997 macros, 2026-08-31 ruling), subs main+42000 (corpus convention, ranges question open); the app decomposes the persisted placements into regular sublattice array blocks with span-derived pitches (successive rounded deltas fragmented a perfect lattice on the first run -- fixed; a partial last column becomes its own block; a genuinely irregular layout refuses with its own words). PART-BY-PART mode: any Manual Sort sequence override drops the macros -- the program posts fully expanded, every placement's features in the operator's per-part order (replicated per copy with transformed near/start points), parts in placement order. Audit: nc_warn.audit_and_inject on the file, source = the placed geometry; the audit EXPANDS the macro program to the part-by-part form the machine executes (nav209: 6 program bnds -> 1176 executed) and the callouts ride in-file with spot markers mapped back into the subs. nc_warn._san now truncates a comment line past 160 chars honestly ([TRUNCATED - FULL TEXT IN THE AUDIT DOCUMENT]) -- a 196-part expanded finding named 940 boundaries in one 4KB comment line, a control-format hazard in the arc-center-ceiling spirit. Stale-program rule extended: a re-plan in Part review OR a re-nest deletes the posted nest program, keeping its assigned number (job keeps its number across re-posts, proven both modes). UI: 'Nested sheet program' section on the Post tab (sibling of the single-part post -- renders even when no single-part program exists), form + why + arrays + parts + warnings + downloads; Manual Sort cost notice repeated at the post itself. Verified live over the public URL (app/verify_postnest.js, Playwright, 12 checks, fresh page per job): nav209 macro O33292 two 14x7 arrays, scratch job part-by-part O33293 with outer_not_last RED riding in the file. Suites test_drag 13 + test_tooling_doc 21 + test_rules 11 + test_nc_warn 12 pass. Honest limits on-screen: posts sheet 1 (multi-sheet = one program per sheet, later brick); nest-level part sequence BUILT as brick 15 (ui-nestseq-brick15) -- serpentine default consumable, part-by-part order clicked-first-then-serpentine; nested-sheet DELIVERY later brick; slug tabs ride the same legacy defaults as the single-part post (needless-tab yellows are the audit's honest output).
- •Nested-sheet delivery (UI brick 9) — the posted nest program as its own versioned delivery set, with real sheet usage and the placement→part map record — BUILT (brick 9 of the 2026-09-01 build-them-all go): the posted NESTED-SHEET program ships as its own DELIVERY SET. Server: POST/GET /api/jobs/<id>/delivernest (+ GET /delivernest/v<k>/<file>) requires the posted nest program (refusal in honest words) and writes an IMMUTABLE version dir per delivery on its OWN append-only chain -- a SIBLING of the single-part chain, same job-versioning ruling (append-only, re-delivery appends v(n+1) and supersedes older versions -- metadata only, files never touched). The set: the audited O<num>.nc (callouts riding in the file), the CAM-safe DXF of the WHOLE PLACED SHEET (every placement's healed geometry transformed to its nest position, emit.write_dxf_shop, CENSUS-CHECKED on the written file -- census FAIL refuses the delivery; nav209: 196 POLYLINE outlines + 980 CIRCLEs, nothing else), the numbered slug report + tooling doc, the PLACEMENT->PART-NUMBER MAP as a CSV (Jordan 2026-08-31 nest-summary ruling: 'part 001 is BNM78655' -- single-part true nest, every placement numbered anyway), the NEST FLOOR PACKET with REAL SHEET USAGE (net part area x parts / sheet area, shoelace on densely sampled TRUE outlines -- the benchmark's own measure, never bounding boxes; nav209: 196 x 8.2572 in2 on 7200 = 22.5%), program form (macro subs+arrays or part-by-part), qty asked beside filled, time estimate honestly PENDING, and a full-set zip. Every delivery = a NUMBERED BUILD on the comparison board (kind app, one sequence). Stale rule: a re-plan OR a re-nest marks the nest delivery 'replanned' (screen says v<n> predates it) while its files stand immutable; the postnest program is dropped, number kept. Warn never block: the part-by-part fixture delivers flagged 1 RED, the RED riding in the delivered NC. UI: 'Nested sheet delivery' section on the Deliver tab, sibling of the single-part set (renders without one); banner / usage / part map / census / downloads / version chain. DEFECT CAUGHT IN THE BUILD: a client disconnect during the HTTP reply (broken pipe on a piped curl) was recorded as a BLOCKED stage though the delivery had succeeded -- ALL POST routes now write the response OUTSIDE the blocked-marking try, so a transport failure can never falsify a stage record; nav209's false record repaired to the truth. Verified live over the public URL (app/verify_delivernest.js, Playwright, 13 checks, fresh page per job): nav209 macro chain v1-v2 supersedes with O33292 kept, packet/board/map/zip serve publicly, served sheet DXF re-censused INDEPENDENTLY on the bytes, re-nest->replanned->re-post->number-kept loop proven, brick8-seq fixture O33294 part-by-part 1 RED in-file. Suites test_drag 13 + test_tooling_doc 21 + test_rules 11 + test_nc_warn 12 pass. Honest limits on-screen: sheet 1's program only (multi-sheet = one program per sheet, later brick); packet SHOP-facing (customer sheet of the ruled split later); 'by whom' awaits operator accounts. ROTATION FIX 2026-09-06 (Jordan's catch on 44558B_10 v2 -- 'nest floor packet doesn't appear to represent the nests/layout accurately'): run_delivernest rebuilt the placed sheet with a 0/180-only shortcut predating the any-angle hand editor, so a hand layout's 90-degree placements shipped drawn as 180s in the sheet DXF and BOTH packet previews (the posted program was correct -- the newer per-orientation path). Fix = ONE shared placement function, server._place_prims (rotate about the part centre, 180 keeping the exact closed form), consumed by run_postnest's place() AND the delivery rebuild -- post and shipped drawing can never rotate differently again. v2 stands as delivered per the versioning rule; v3 is the corrected set. Proven: test_nestdeliver_rot.py 14 NEW controls (90 corners + off-centre hole at the rotated spot in the written DXF bytes, 180 byte-equal, automatic-nest regression) + 7 neighbour suites green.
- •The sketcher (UI brick 10) — dimensioned primitives typed as numbers, compiled into a real source.dxf, born clean into the normal pipeline record — BUILT (brick 10 of the 2026-09-01 build-them-all go) -- the ruled v1 scope of sitting answer 8 (Aristide 2026-08-19: 'a real sketcher' -- lines, arcs, circles, all assignable numerical values; the dimensioned-primitive sketcher, NOT a constraint-solver CAD; born-clean geometry rides the normal pipeline from QC on). ENGINE: sketch.py compile(doc) turns the typed document (inches; angles in degrees; circle by DIAMETER, the shop's word) into the pipeline's own prim form, stitching typed segments into contours by endpoint agreement -- lines are the flexible member (a line endpoint within 5e-4 snaps TO an arc's computed endpoint; arcs are rigid, moving their ends would corrupt the radius), arc-to-arc joins must already agree to the 1e-4 contour gate with a near-miss reported in honest words, circles compile as two semicircle bulge arcs (dxf_io's own CIRCLE diet) and come back out of the CAM-safe writer as true CIRCLEs. A bad sketch refuses with its own words (SketchInvalid: empty sketch / zero-length line / non-positive diameter or radius / zero-sweep arc = 'use the circle primitive' / non-number); an OPEN chain is NOT a refusal -- QC's open-contour flag is the ruled surface (warn never block). SERVER: POST /api/jobs?sketch=1&name= starts a job from a BLANK SKETCH (no file); GET/POST /api/jobs/<id>/sketch saves the document on every edit (typed work never lost -- saved BEFORE compile, proven on the refusal path) and with apply=true compiles -> writes a REAL source.dxf via emit.write_dxf_shop (the ruled writer) -> runs the SAME run_pipeline every customer file rides; nothing downstream knows the sketch exists. Aristide's own ruled example (the 2" OD / 0.5" ID customer) round-trips at heal fidelity EXACTLY 0 with QC clean -- born clean, measured, not asserted. RE-COMPILE = the geometry changed under every downstream stage: run_pipeline (now merge-aware) drops review/nest/cutplan/post/postnest documents (a stale judgment never keeps serving), KEEPS the job's assigned O-numbers on the pending stage records, and marks delivered versions replanned -- immutable files untouched, per the job-versioning ruling. An edit WITHOUT apply marks the sketch stage stale so the screen says the compiled geometry predates the typed values. UI: 'New sketch' on the Jobs home; a Sketch tab AHEAD of the standard eight on sketch-born jobs only; primitive rows as unit-suffix inputs (mm accepted anywhere), add/delete, live canvas preview of the typed geometry over the gray base layer, Apply, refusals and compile notes in the engine's words, the scope note on-screen ('dimensioned primitives, not a constraint solver; drawing by mouse is a later brick'). Verified live over the public URL (app/verify_sketch.js, Playwright, 13 checks, fresh page per phase): washer typed -> applied -> reviewed -> POSTED as O33296 (a sketch becomes a numbered program), ID edited 0.5->0.75 -> stale marker -> re-apply drops the program and KEEPS O33296, zero-diameter refusal in the engine's words with the document surviving, open two-line chain applies with QC dangling flags. Suites: test_sketch 21 controls + test_drag 13 + test_tooling_doc 21 + test_rules 11 + test_nc_warn 12 all pass. Honest limits: typed numbers only (mouse drawing, snapping, trim/fillet later); no constraint solver by ruling; a sketch job nests/posts exactly like any other job (nothing special-cased). [2026-09-01, fix block 4: sketch UNITS PINNED to inches in the pipeline -- the R12 source.dxf carries no $INSUNITS and a >200-inch sketch was silently re-read as mm by the magnitude heuristic; pinned, never inferred, the intake note says so.] LABELED CONTROLS + EXCEL ENTRY 2026-09-06 (Jordan testing the sketcher: 'nothing is labeled. Can we improve this so that a human operator has intuitive controls?' and 'When I click a dimension box, I want the number I'm typing to automatically replace the text... Kinda like Excel'): every sketch field now carries a visible label above the input (line: from X/from Y/to X/to Y; circle: center X/center Y/Ø dia; arc: center X/center Y/radius/start°/end°/dir) -- a hover tooltip alone is not a label; and clicking ANY unit input app-wide selects its whole value so typing replaces it (focusin select + one-shot mouseup suppression so the browser keeps the selection; a second click in the focused field places the cursor normally). Client-only (app.js/app.css), serves from disk, no restart; proven by 6 live real-mouse Playwright checks on Jordan's own sketch job. DRAW GESTURES ARRIVED 2026-09-19 (Jordan's "Yes" -- pin add-feature-draw-flow carries the full record): the 'mouse drawing, snapping later' honest limit closed -- click-to-draw line chains, the draw parameter bar and magnet snaps run on the sketch preview, committing typed rows; typed forms stay the record and the fallback; arc/circle rows arm a one-click center pick. verify_sketchdraw.js 17/17 + verify_sketch 13/13 (suite-fixed for the tab merge + dev-links BASE). BAND SELECT JOINS THE SKETCH SCREEN 2026-09-22 (pin global-controls carries the full record): shift-drag bands typed rows by their ink, Delete removes them in one recorded save, Escape clears; verify_sketchband.js 10/10.
- •Tear-off panels & workspaces (UI brick 11) — the A+C ruling live: dock ground state, tear-off floats, one-click snap-back, named per-station layouts, a panel never lost record — BUILT (brick 11 of the 2026-09-01 build-them-all go) — the A+C ruling (Aristide 2026-08-19: docked Workbench is the ground state on every workstation; C's machinery underneath — tear-off panels, named per-user Adobe-style workspaces — snap-back always one click) as it stands in app/web. The two panels that exist today (Tools, Checks) each carry a GRIP: dragging it IS the tear-off (proposal A's gesture) — the panel becomes a floating window over the canvas, draggable by its grip, resizable by its corner, and the dock reflows so the canvas takes the freed space; the SAME live drawer renders inside the float (one renderer, no parallel panel). Drop a dragged panel on a screen edge to dock it there (panels drag between slots — Tools can dock right, Checks left; an edge hint bar shows the target); the float button is the ruled ONE-CLICK snap-back to the panel's last slot. Collapse ('–') folds a docked panel to a 26px strip with a vertical title, one click expands (proposal A's icon strip). NEVER LOST, enforced two ways: any float clamps into the viewport on load and on window resize (a stored x=9000 comes back on-screen — verified), and Reset re-docks everything. Workspaces menu (⧉ chip): save the current layout under a name, apply, delete, Reset — layout state is per-STATION presentation state (localStorage, exactly like the ruled theme/units chips) with the honest note on-screen: per-station until operator accounts arrive. THREE-LENS CHECK APPLIED: floats live INSIDE the app window on all three lenses alike (plain DOM + pointer events); true separate-OS-window / second-monitor placement is platform-divergent on the web lens, so it is recorded as arriving with the Mac/PC shells — stated on-screen, not silently web-only. Defect caught in the build: a click inside the workspace menu that re-renders the menu detached its own click target before the close-on-outside-click handler ran, so the menu closed itself after Save — the handler now tests the event's composedPath, captured at dispatch. No server or engine change; panel INVENTORY unchanged (more panels join the dock as they are built — the old CAM panel document is still the awaited inventory source). Verified live over the public URL (app/verify_panels.js, Playwright, 14 checks): tear-off by real mouse drag, canvas reflow, layout surviving a full reload, one-click snap-back, edge-docking, collapse/expand, save/reset/apply/delete of a named workspace, off-screen clamp, and the torn-off Checks serving the real nav209 Part review drawer. Suites: test_sketch 21 + test_drag 13 + test_tooling_doc 21 + test_rules 11 + test_nc_warn 12 pass.
- •Streamline the panels -- menu bar, stage-aware layout, Properties vs Checks, Dimension as a tool (Aristide 2026-10-18) recordmixed — STATUS 2026-10-19 (cold-review M9): steps 1-7 of the plan BUILT; the follow-on UI OPPORTUNITY LIST #1-#10 (asked 'what other opportunities do you see for the UI?', 136e7962), all BUILT: #1 Clear for every screen (a8181434 closed it); #2 Clear folds -- Cut plan etc. fold to one summary line (f02fc2b7); #3 warnings chip on the menu row (16be0cf1); #4 Search box + jobs/parts/warnings in Ctrl+K (2f3f61c9, f1da5f43); #5 Nest at a glance -- sheet per piece in big type (87b7ace3); #6 editing basics -- select/delete a dimension, Close gap + Add feature rail tools (13e563ba, 8908af11); #7 jobs home queue cards 'Where jobs stand' (6b006d3b); #8 shop-floor mode: big type (ff4a17d0), Ready-to-cut home (767c0c2b), floor lock (682ef05b); #9 Clear welcome tour (0eaed793); #10 one product name, KerfMaster (092075f6, a315b4d8, dcf8ab0c). Cold review 1ed590e7, fixes 8fa8d692, ec0fe97d, 855b56f6. STILL OPEN (intent/question): options bars for the remaining rail tools; rejected-nest thumbnails (engine); retire one layout; make Clear the default (question, Aristide + Jordan); M10 move queues / Ready to cut / warnings tally / floor lock into the engine with unlocking recorded (three lenses); M11 test housekeeping. | intent (Aristide 2026-10-18: 'what is a little messy right now, we seem to have 2 windows: 1 for dimensions and one for the rest, depending on which tab you select, the contents changes ... come up with a plan to streamline that. it may require a menu that is not built yet. take a deep dive in how Adobe takes care of these things, and give me a solution that surpasses that.'). FOUND on dev (nav209): Heal/QC panel shows on every tab incl. Tooling/Nest/Post; Checks drawer mixes settings, results and help paragraphs; Dimension panel is a separate collapsed strip; no menu bar. PLAN (docs/ui-streamline-plan.md, nothing built, one step per go): (1) JSON command list of every button -- id/label/stage/shortcut/menu home; (2) menu bar File/Edit/View/Select/Part/Job/Window/Help + Ctrl+K command search from that list (Mac shell renders native menu -- three lenses); (3) the stage IS the workspace -- tools/panels per tab automatically; (4) Dimension becomes a rail tool with an options bar, panel retired; (5) right side = Properties (what you change, follows selection, stage settings when none) + Checks (what the engine found, clickable findings, green flags); help paragraphs -> (i) tips; (6) context bar beside the selection. Open questions to Aristide: menu names, Properties/Checks stacked vs tabbed, keep Dimension panel as a Window-menu option? | ROLLBACK (Aristide 2026-10-18: 'I need to be able to roll all this back if I do not like it'): tag rollback-point-ui-2026-10-18 at b14b7cb4, pushed; new layout ships as a per-station Classic/New switch, Classic stays default (prod unchanged) until an owner says make New the default; one commit per step; Classic removed only on a separate 'keep it' go. | ANSWERS (Aristide 2026-10-18): (1) menu names OK -- File/Edit/View/Select/Part/Job/Window/Help; (3) 'stays' -- the Dimension panel stays (Window menu opens it) alongside the new Dimension tool + options bar; (2) 'not sure, help here' -- recommended stacked (Properties above Checks, draggable divider, each collapsible) so a changed value and its result are seen together; awaiting his pick. | 2026-10-18 UI STREAMLINE STEP 1 -- COMMAND LIST (pin ui-streamline-panels, Aristide 'go'; stacked Properties-over-Checks accepted with the same go): NEW cadmaster/app/web/commands.json -- 125 commands catalogued from a live scrape of every panel on 17 screens (single part, part list, list member, no-scale sheet; scratch server with copied jobs, zero dev O-numbers) plus the keyboard map and right-click menus. Each: id, label, menu (File/Edit/View/Select/Part/Job/Window/Help), stages, kind, shortcut, today (where it lives now), home in the New layout (menu 51, properties 31, context 21, rail 9, optionsbar 7, checks 5, canvas 1) and a hook string that must exist in app.js/index.html. NEW test_commands_json.py 699 checks (ids, menus, homes, stages, single-key collisions per stage, hooks, every panel in Window menu); a missing hook fails it (seen: 6 fails before the hooks were fixed). Nothing reads the file yet -- no visible change. Noted for step 4: D is taken by the as-drawn layer, so the Dimension tool needs another key. Identity gate green, F1 n/a. | 2026-10-18 UI STREAMLINE STEP 2 -- MENU BAR + CTRL+K (pin ui-streamline-panels, Aristide 'go'): NEW app/web/menubar.js (own file, one <script> line + one hook line in renderWSMenu + a CSS block) -- File/Edit/View/Select/Part/Job/Window/Help built from commands.json; usable items first, the rest dimmed with where they work (tab / part list / single part / right-click), shortcut shown; hover-switch between open menus; Esc closes. Ctrl+K search over the same list (every word must hit; usable first). One road: a menu item presses today's button, calls the same KM function or sends the same key, switching tab first where needed. commands.json gains run (105 commands) and jobs (part/list, 42) -- the browser test caught dims offered on part-list tabs and list buttons offered on a single part, fixed by jobs. ROLLBACK SWITCH: per-station Classic/New (localStorage km.layout, ?layout=new), Classic default; Classic's only visible change is a 'Try the New layout' line in the Workspaces menu; Window > Classic layout switches back. NEW verify_menubar.js 19/19 on scratch (Classic default, switch, 8 menus, View>Healed toggles, dimmed reasons, Ctrl+K finds + runs, 107 single-part + 78 part-list menu targets present on their tabs, persists across reload both ways, zero page errors). test_commands_json 964. Classic regressions on scratch old vs new identical: verify_display 12/12 both, verify_ctxmenu 26/26, verify_panels 13 ok + check 14 fails IDENTICALLY on old code (pre-existing: expects the retired Review tab title; the suite also still points at the old mycloudally URL). Known: Part menu offers the sheet-only items (Extract flat pattern / Pick views / Run full checks) on any part -- they answer 'not available' when pressed. Identity gate green, F1 n/a (front end only; +44 KB commands.json fetched once at load). | STEP 3 2026-10-18 (Aristide '3'): stage-aware left side, NEW layout only. commands.json gains stage_layout -- panels: Heal / QC shows on Geometry only; rail: each tab shows only the layer buttons it draws (Geometry: source/healed/jogs/annot/as-drawn; Tooling/Post/Deliver: those + offset/nominal/rapids; Nest/Quote: offset; part-list Nest/Post/Deliver/Quote: rapids; Part list tab: none). V/F everywhere; a hidden button keeps its key. Drawing-sheet Part-menu items now dim on ordinary parts (when: sheet / sheet_pick) instead of answering 'not available'; Pick views from the menu opens Source mode first. Window > Heal / QC dims off Geometry with 'on the Geometry tab'. Gate keyed to the page's own state (body.layout-new), not the saved setting, so a second browser tab can't half-switch this one (caught by the new test). Floating panels keep their size while hidden (ResizeObserver guard). Classic: app.js changes are 3 guarded lines, no-ops unless New is on. NEW verify_stage_layout.js 23/23 on scratch (incl. Classic reference per tab and switch-back restoring rail/panel/width exactly; drawing gains 236 px on Tooling in New). verify_menubar 19/19, test_commands_json 1126, Classic verify_display 12/12, verify_ctxmenu 26/26, verify_panels 13 ok + check 14 pre-existing fail as before. Identity gate green, F1 n/a (front end only). | MENU ROW 2026-10-18 (Aristide screenshot: 'put that in a separate row, keep the tabs where they were'): New layout's menu bar moved out of the header into its own 28px row above it; job name + tabs back exactly where Classic has them; workbench, dock hints and float clamp take the 28px only when New is on. verify_menubar 20/20 (+ row check), verify_stage_layout 23/23, ctxmenu 26/26, test_commands_json 1126. Identity gate green, F1 n/a. | STEP 4 2026-10-18 (Aristide 'go', key M): Dimension becomes a tool, New layout only. Rail tool (ruler, M) on a part's Geometry/Tooling/Post/Deliver (not Nest/Quote sheet, not Source mode, not part lists -- same test as the canvas pick, dimToolOK()); turning it on arms the last kind (Horizontal first) and shows the options bar top-centre over the drawing: the six kinds as one switch, pick count, Auto, N placed, Clear all, List... (opens the panel), Done; Esc/Done/M turn it off. Source mode keeps M = two-point measure. The Dimension panel STAYS (Aristide): in New it is on-demand -- Window > Dimension panel opens/closes it, remembered per station (stage_layout.on_demand). Bar and panel share one handler (dmAct, refactored from the panel listener -- Classic panel behaviour unchanged, tested). Menu/Ctrl+K dimension kinds now call KM.dimMode (works with the panel folded or hidden); NEW command dim.tool (126 commands). NEW verify_dim_tool.js 23/23 on scratch (Classic: no ruler, M inert, panel arms as before; New: M, bar kinds, Auto 5 dims + Clear all via the engine, Esc/Done, last kind remembered, Tooling yes / Nest no, Source-mode measure kept, Window panel open/close survives reload, Ctrl+K 'dimension radius'). verify_menubar 20/20, verify_stage_layout 23/23, test_commands_json 1147, Classic verify_display 12/12, verify_ctxmenu 26/26, verify_panels 13 ok + pre-existing check 14. Identity gate green, F1 n/a (front end only). Options bars for the other tools (Add feature, Close gap...) not built -- later chunk if wanted. | STEP 5 2026-10-18 (Aristide 'step 5'): the right drawer becomes Properties stacked ABOVE Checks, New layout only. renderDrawer is untouched; a post-pass (menubar.js kmDrawerSplit, one guarded hook line at the end of renderDrawer) SORTS the drawer's own rows into two halves inside #drawerbody, moving each element whole (ids, handlers, values unchanged -- one road). Properties = rows with fields/buttons; Checks = read-outs (kv, banners, findings, versions); a help note follows its row; a result that follows a card's settings files under the STAGE heading (Tooling: NO FINDINGS under Part review, not Material record). Draggable divider (15-85%, remembered per station), each half folds by its heading (remembered), an empty half shrinks to its heading, scroll kept through re-renders. Help paragraphs over 90 chars fold to one-line (i) tips, click to read -- a note that warns/blocks/is stale is never folded (softening is a defect). The part-list table already lived in this 300px drawer, so Properties is no narrower than today -- Aristide's width worry resolves with no change. NEW verify_props_checks.js 16/16 on scratch: every drawer row present in New exactly as in Classic on 8 screens (part Geometry/Tooling/Nest/Quote/Post/Deliver, list Part list/Nest), Nest has 19 fields in Properties and 0 in Checks, controls still act, fold/drag remembered, scroll kept, tips fold and open, switch-back restores the Classic drawer exactly. verify_menubar 20/20, verify_dim_tool 23/23, verify_stage_layout 23/23, Classic display 12/12, ctxmenu 26/26, panels 13 + pre-existing 14. Identity gate green, F1 n/a (front end only). | STEP 6 DONE 2026-10-18 (Aristide 'step 6'): context bar beside the selection, New layout only -- a small floating bar just above the selected item (below when no room), following pan/zoom, hidden while a mouse button is down on the drawing and while any tool is armed. Its buttons are the selection's own right-click items (one list in app.js: ctxReviewItems / ctxNestEditItems / ctxGeomMenu, items marked `bar` with a short label; ctxSelBar gives the items + world box, pure); More... opens the full right-click list. Tooling feature: Start... / Lead... / Tab... / Chop|Tab it; Post: Edit tooling; Geometry band: Delete N / Weld; Nest hand edit: +90 / 180 / Copy / Delete (band: Group / Split / Delete). Part-list hand edit keeps its own top bar. Classic unchanged (one guarded hook in draw(); right-click menus give the same items). NEW verify_ctxbar.js 18/18; menubar 20/20, stage_layout 23/23, dim_tool 23/23, props_checks 16/16, ctxmenu 26/26, Classic display 12/12, panels 13 + pre-existing 14, test_commands_json 1147. Identity gate green, F1 n/a. | CONTEXT BAR ON/OFF 2026-10-18 (Aristide 'can you turn this on and off?' / 'yes'): View menu > Context bar beside the selection (also Ctrl+K), shows on/off beside it; per station (localStorage km.ctxbar), default on; off = right-click keeps every action. New command view.ctxbar (127); test_commands_json now also reads menubar.js (1156). verify_ctxbar.js 22/22, menubar 20/20. Identity gate green, F1 n/a. | LOAD FLICKER FIX 2026-10-18 (Aristide 'now when I load the page it shows different views in succession'): measured on a slowed load of dev -- New layout painted Classic panels first, then the opening job's Geometry drawer + Heal/QC over the Jobs page for ~1.5s (commands.json landing mid-openJob re-rendered the drawer). Fix: the layout class is set by a tiny inline script before anything paints, stage panels wait (km-wait) for the list, and the New layout treats a job as on screen only once the Jobs page is put away. Now: Jobs page, then the part, same as Classic. menubar 20/20, stage_layout 23/23, dim_tool 23/23, props_checks 16/16, ctxbar 22/22, ctxmenu 26/26, Classic display 12/12, test_commands_json 1156. Identity gate green, F1 n/a. | WINDOW/VIEW CHECKMARKS 2026-10-18 (Aristide screenshot of Illustrator's Window menu + 'go'): New layout only -- on/off menu items carry a checkmark from commands.json `check` (layer / src / panel / ctxbar). Window menu: Dimension, Tools, Heal/QC, Checks panels + Context bar (moved from View, id window.ctxbar) listed first under a line, each a show/hide toggle per station (localStorage km.hide.<panel>; Dimension keeps km.open.dims); a tab's own panel stays tied to its tab. View layers + Source mode show checkmarks that follow the keys. Reset panels = every panel back, Dimension closed, context bar on. Ctrl+K rows show the same checkmarks. NEW verify_window_checks.js 24/24; ctxbar 22/22, menubar 20/20, stage_layout 23/23, dim_tool 23/23, props_checks 16/16, ctxmenu 26/26, Classic display 12/12, test_commands_json 1178. Identity gate green, F1 n/a. | UI CLARITY MOCKUP 2026-10-18 (Aristide 'i need a better UI... mock up the one that gives the best insight, before and after, in pdf'): picture-only before/after of the Tooling tab, NO app change. Before = real dev screen (nav209-part, New layout); after = docs/mockups/ui-clarity/after.html (shop words on screen + explanations on hover/Help; selection first then checks then part; every value tagged table / set by you + Back to table values; colour only for status; numbered steps + one main Next button; labelled tools, Layers button). PDF docs/mockups/ui-clarity/kerfmaster-tooling-before-after.pdf (build.js), hosted dev.kerfmaster.com/viewer/builds/ui-clarity/. OPEN (intent): roll out tab by tab in New layout only on a go; Jordan's operator read wanted. | UI STREAMLINE CLEAR LAYOUT, CHUNK 1 2026-10-18 (Aristide 'go' on a third UI beside Classic and New): rollback tag rollback-point-ui-2026-10-18b (4b0f29ae, pushed) = Classic + New as of the mockup. km.layout now classic | new | clear (?layout=clear); Clear = body.layout-new + layout-clear, so New renders exactly as before. Window menu ends with Layout: Classic / New / Clear (preview), current one checked; Workspaces row offers the other two. Clear pieces so far (mockup docs/mockups/ui-clarity): tabs as numbered steps with ›, one main button Next: <next tab> (presses that tab only), every rail tool labelled (LAYSHORT), explanations (drawernote) cut to one line with hover for all, all-clear banner a quiet green line. NEXT (chunk 2, on a go): Tooling panel order Selected -> Checks -> Part, values tagged table / set by you, plain headings, findings as short rows. NEW verify_clear_layout.js 20/20; window_checks 24/24, menubar 20/20, ctxbar 22/22, test_commands_json 1178. Identity gate green, F1 n/a. | UI STREAMLINE CLEAR HEADER 2026-10-19 (Aristide 'the menu is SUPER FULL': K in the corner, KerfMaster left of File, number IN the circle, the > makes no sense, height when the window is narrow): Clear only -- #mbbrand 'KerfMaster' before File; #brand shows a K badge; tab number inside its status dot (green/yellow/red, grey ring when pending; tabs without a dot get a ring), › removed; topbar stays one row: Workspaces/units/theme/help chips step aside in Clear (Window/View/Help menus carry them), undo/redo stay, job name + group chip ellipsize, under 1360px the other tabs show just their numbered circle. verify_clear_layout.js 27/27 (one row at 1100 and 1280px); menubar 20/20, window_checks 24/24, test_commands_json 1178. New and Classic unchanged. Identity gate green, F1 n/a. | UI STREAMLINE CLEAR CHIPS UP 2026-10-19 (Aristide 'all these can be one menu higher too'): Clear only -- the six corner chips (undo, redo, workspaces, in/mm, light/dark, ?) move as the same nodes to the menu row's right end, small (22px); back to the header in New/Classic before the menu row can go. Next button now sits right after the tabs in every layout (hidden outside Clear). verify_clear_layout.js 28/28; menubar 20/20, window_checks 24/24, test_commands_json 1178. Identity gate green, F1 n/a. | UI STREAMLINE CLEAR NAME LINK 2026-10-19 (Aristide 'make the KerfMaster also a hyperlink, like the K'): Clear only -- KerfMaster in the menu row presses the same brand control (Jobs home), pointer + underline on hover. Aristide on the Clear header: 'that cleaned it all up, way better.' verify_clear_layout.js 29/29, test_commands_json 1178. Identity gate green, F1 n/a. | UI STREAMLINE CLEAR CHUNK 2 -- TOOLING PANEL 2026-10-19 (Aristide 'go for Chunck 2'): Clear only -- reviewDrawer keeps its pieces (top / part / job card / checks / contour) and New+Classic join them in the old order; Clear's clearTooling() orders them Selected -> Checks -> Part (.kmclear, no Properties/Checks split, title = tab name). Selected: '<Hole|Small hole|Outside> N · cut n of m', Start (clock from centre) / Lead-in / Pierce clear air / Cut side / tab, each tagged table | rule | auto | set by you (ctag from the record's source + S.ov); Start... (pickStart) Lead... Tab... (open the full contour panel folded below and focus the field); Back to table values clears that feature's overrides (one ovApply + runReview). Checks: Ready to nest | N red · M yellow line, N changes by you, starts moved / no safe spot, unconsumed changes, findrows as before, Lead-in defaults link. Part: machine/material/Re-plan as before, job card folded ('Job card -- heat/lot ...'). Nothing removed: the old contour panel and job card fold open in place. verify_clear_layout.js 41/41; props_checks 16/16, ctxmenu 26/26, test_commands_json 1178. Identity gate green, F1 n/a. | UI STREAMLINE CLEAR FOLDS 2026-10-19 (Aristide 'go fro 2'): Clear only -- Tooling's Cut plan folds to one summary line under Part (stage dot + 'not built yet' / 'N cuts in order' / 'blocked'; opens by itself while Manual Sort picks or when blocked); the drawer's Layers list folds to 'Layers (same as the left rail)' on every tab, still switching layers. New/Classic unchanged. verify_clear_layout.js 48/48, props_checks 16/16, stage_layout 23/23, ctxmenu 26/26, test_commands_json 1178. Identity gate green, F1 n/a. | UI STREAMLINE CLEAR CUT PLAN DOT 2026-10-19 (Aristide 'alignment issue on the grey circle'): Clear only -- the Cut plan fold's status dot sat high (empty inline-flex on the baseline); now 11px, centred on the text. verify_clear_layout.js 49/49 (new centring check). Identity gate green, F1 n/a. | UI STREAMLINE CLEAR NEST 2026-10-19 (Aristide 'next one you suggested' = Clear for the next tab): Clear only -- the packed part-list Nest drawer reads Nest (N pieces on M sheets, material, Spread/Jam/Pack again, sheets folded) / Checks (one status line: Ready to post or N red · M yellow; spacing audit line; hand-edit, variant, update rows; grouped warnings in view; per-part counts folded) / Part order / Sheet and method (sheet rows; sheet size + list, nesting method, parts asked vs filled, how-this-works folded). Built by cutting plNestDrawer's own html at marks -- New/Classic concatenate exactly as before; the test proves every field and button of the New panel is in Clear. Not yet: the single-part (true-nest) Nest drawer and the unpacked/blocked states keep the old look. verify_clear_layout.js 56/56, plseq 15/15, test_commands_json 1178. Identity gate green, F1 n/a. | UI STREAMLINE CLEAR QUOTE 2026-10-19 (Aristide 'go' = Quote next): Clear only -- the part-list Quote reads Quote (the price, or 'No price yet'; parts, sheets, usage; Quote again + Record customer approval) / Checks (Firm price | Indicative | N price rows missing with the Set fields in view; approval status; changes by you; program warnings) / Per part (the math table) / Details folds (Adjust this quote, How the total is built, Measured run, Material notes and job card, Customer approval, How this works). Cut from quoteDrawer's own html at marks; New/Classic unchanged; test proves every field and button is in Clear. Also: Clear check rows keep bold text inline (Tooling, Nest, Quote). Nest + Quote checks split into NEW verify_clear_tabs.js 14/14 (2-minute cap); verify_clear_layout.js 49/49; plquote 44/44 (its test rates restored from git); test_commands_json 1178. Not yet: single-part quote. Identity gate green, F1 n/a. | UI STREAMLINE CLEAR GEOMETRY 2026-10-19 (Aristide 'continue' = Geometry next): Clear only -- one part's Geometry tab (what a part-list row opens) reads Part (size in big type; file, outlines, segments) / Checks (Healed within N thou | Heal flagged N jogs; QC clean | QC N flags with the counts; units read from the file or confirmed; drawing-sheet, ink-colour, split-parts and units questions as rows) / Details folds (File units and setup = the whole Intake section, opening by itself while intake asks; Heal; QC). Blocked or awaiting-size intake and sketch jobs keep the old stacked panel. New/Classic unchanged; test proves every field and button is in Clear. verify_clear_tabs.js 21/21, verify_clear_layout.js 49/49, stage_layout 23/23, test_commands_json 1178. Identity gate green, F1 n/a. | UI STREAMLINE CLEAR POST 2026-10-19 (Aristide 'next' = Post): Clear only -- the part-list Post tab reads Post (N programs posted or Not posted yet; material, machine, sheets, O-numbers; Post/Re-post sheet programs up top) / Checks (Ready to deliver | N red · M yellow; warning lines riding in the file; repeated-sheet run count; feature overrides carried; the grouped audit warnings in view) / Programs (one stacked line per program with .nc, tooling and slug downloads; program form, arrays and subs folded) / Details folds (Program numbers and style; How this works). Cut from plPostSection's own html at marks; blocked or unpacked states keep the old note. New/Classic unchanged; NEW verify_clear_post.js 11/11 proves every field, button and link of the New panel is in Clear. verify_clear_tabs 21/21, verify_clear_layout 49/49, stage_layout 23/23, plpost 14/14, test_commands_json 1178. Not yet: single-part / true-nest Post. Identity gate green, F1 n/a. | UI STREAMLINE CLEAR DELIVER 2026-10-19 (Aristide 'next' = Deliver): Clear only -- the part-list Deliver tab reads Deliver (vN delivered or Not delivered yet; parts, sheets, O-numbers, date; Deliver / Deliver again up top; the current version's files as quiet outline chips: board, operator PDF, floor packet, customer sheet, part map, zip, .nc, DXF, tooling, slugs) / Checks (the delivered verdict as one row: N red · M yellow in the delivered file | Delivered clean | Ready to deliver | Nothing posted yet; re-posted after delivery; predates a re-pack; blocked) / Earlier versions (folded, superseded, files kept) / Details folds (What vN contains; Reference prints; How this works). Cut from plDeliverSection's own html at marks; the no-pack state keeps the old note. New/Classic unchanged; NEW verify_clear_deliver.js 12/12 (delivers v1 on scratch, proves every field, button and link of the New panel is in Clear before and after); a v2 run checked the Earlier versions fold, same inventory as New. verify_clear_post 11/11, verify_clear_tabs 21/21, verify_clear_layout 49/49, stage_layout 23/23, pldeliver 14/14, test_commands_json 1178. Scratch board builds 256-261 removed, viewer index restored. Not yet: single-part / true-nest Deliver. Identity gate green, F1 n/a. | UI STREAMLINE WARNINGS CHIP 2026-10-19 (Aristide 'Go' on opportunity #3): Clear only -- a chip on the menu row counts the OPEN findings (green-flagged ones are signed off and leave the count), e.g. '1 red · 417 yellow on Post', red when any tab holds an open red, else yellow; it names the furthest tab along the road that has any, hidden when nothing is open. Click = a list of every tab with its own count (unloaded stage documents fall back to the stage record's numbers, 'open the tab to see'; a stage flagged for another reason, e.g. a stale quote, is left to its tab dot). A row opens that tab on its first open finding, red first: the contour selected and framed where the finding names one, the row opened out of its folds, scrolled into view and outlined, with its own detail and green-flag. Reads the same stageFindings the tab dots read; green-flag refreshes the chip at once. Display only, warn never block. New/Classic: no chip. NEW verify_warn_chip.js 12/12 (part list chip + list + jump to Nest; part P0 jump selects contour 8 its red names; green-flag drops the red, unflag restores; no-warning part shows no chip). verify_clear_layout.js 49/49 after a test fix: the Cut plan dot check now measures the line the dot sits on (a narrow panel wraps the summary; failed with the chip disabled too, so not this change). menubar 20/20, ctxbar 22/22, clear_tabs 21/21, clear_post 11/11, clear_deliver 12/12, stage_layout 23/23, test_commands_json 1178. Scratch board 256 removed, viewer index restored. Identity gate green, F1 n/a. | UI GREEN-FLAG DOTS 2026-10-19 (Aristide 'Fix 2first'): every layout -- a green-flag (or unflag) now redraws the tab strip at once, so the tab dot steps red -> yellow -> done the moment the sign-off is recorded (before: gfToggle redrew only the drawer and the dot waited for the next tab redraw); Clear's warnings chip rides the same redraw. verify_warn_chip.js 14/14 (NEW check: New layout, green-flag P0's only red, Tooling dot red -> yellow at once, unflag back; fails 13/14 on the old code). stage_layout 23/23, menubar 20/20, warnnav 10/10 (that suite has the dev URL hard-coded -- it re-posted the ex2 fixture on dev; fixture files restored from git, no program-number change). Identity gate green, F1 n/a. | UI SEARCH BOX + JOBS IN CTRL+K 2026-10-19 (Aristide 'A+B' on opportunity #4 -- Ctrl+K command search already existed since 00a15244, so #4 became its upgrade): New + Clear -- (a) a Search box on the menu row (magnifier, 'Search', Ctrl+K / Cmd+K key hint; Clear: between the menus and the corner chips) opens the same search, findable without knowing the key; (b) the search finds jobs too, on the jobs-home search fields (name, id, order ref, customer, every O-number on the job; an exact O-number ranks first), up to 6 under a Jobs heading with customer / ref / date; Enter or click opens the job like its card. Commands and Jobs headings show when both match; the section with the better match comes first. Classic unchanged (no box, no Ctrl+K). NEW verify_palsearch.js 17/17 on scratch (Classic none; New box opens search; 'post' command first; 'nav209' job first + Enter opens it; O-number finds its job + click opens; no match; Esc; Clear placement + row). menubar 20/20, ctxbar 22/22, stage_layout 23/23, test_commands_json 1178. Identity gate green, F1 n/a. | UI CTRL+K PARTS + WARNINGS 2026-10-19 (Aristide '4c'): New + Clear -- inside a job the search box / Ctrl+K also finds (1) a part list's parts (name or id; a part outranks the warnings that merely name it), Enter opens the part; (2) the open warnings (green-flagged ones excluded): one row per tab with its count (warnTally, same as the chip; an unloaded tab says open the tab to see) and one row per finding in memory (warnList: the same stageFindings the dots read; part-list nest findings carry their part name the way the Nest drawer writes it), with a red/yellow dot, long feature lists clipped. Enter on a finding = warnFind: opens its tab, finds that finding's own drawer row, selects + frames its contour where it names one, unfolds, scrolls, outlines (falls back to the tab's first open finding, as the chip does); Enter on a tab row = warnGo. Sections Commands / Warnings / Parts / Jobs, the better match first. Jobs home unchanged (no parts/warnings). Classic unchanged. Display only, warn never block. verify_palsearch.js 28/28 (+11: part first + opens; Warnings on Nest row; a warning names its part + Enter outlines its own row; P0 'red comp' selects contour 8 + outlines; from Geometry the tab row opens Tooling on its warnings; home shows neither). menubar 20/20, warn_chip 14/14, ctxbar 22/22, stage_layout 23/23, test_commands_json 1178. Identity gate green, F1 n/a. | UI NEST AT A GLANCE 2026-10-19 (Aristide '5'): Clear only, part-list Nest -- the Nest section now carries the objective in big type: sheet per piece (every sheet's height x its used length, gaps and lead room inside, / pieces; 'per part' when the list is one part, 'per piece, average' otherwise; in² or cm² by the station's units) and the share of the sheets used; then 'Methods tried -- the winner first': one row per method the judge measured or estimated, each with a small sheet-use picture (its used length shaded per sheet, up to 4 drawn, the rest counted), sheets, used length, clean pocket, measured/estimated; the winner marked chosen, and when the layout changed after judging (spread, sheet list) its row says 'N sheets when judged -- now M'. Methods not tried (skipped / refused / still judging) fold into one line per reason. The judge keeps numbers, not layouts, for the methods it did not ship -- the picture is sheet use, never a layout; true layout thumbnails would need the engine to keep each candidate's placements (named, not built). Display only; the pack-with-this-one buttons stay in the Nesting method fold. New/Classic unchanged. NEW verify_nest_glance.js 10/10 (New none; numbers recomputed from the stored pack; one row per tried method, winner first; pictures; no buttons; cm² on an mm station). clear_tabs 21/21 (New-vs-Clear inventory unchanged), clear_layout 49/49, test_commands_json 1178. Dev serves app/web live: a syntax slip (duplicate const) broke app.js on dev for about a minute mid-build, fixed before commit. Identity gate green, F1 n/a. | UI EDITING BASICS (a) -- SELECT + DELETE A DIMENSION, CONTEXT BAR x 2026-10-19 (Aristide '6', first half): New + Clear -- a click on a dimension's value label (no drag) selects it: an accent ring round the label; the context bar shows 'Dimension <value>' with Remove; Delete/Backspace removes it; Escape or a left press anywhere else lets it go; a drag still only places the label. One remove road (dimRemove) for the Delete key, the bar, the right-click 'Remove this dimension' and the panel x. The context bar gets a x on every selection: hides the bar for THIS selection only (pans/redraws keep it hidden), the next selection brings it back; Window > Context bar still turns it off for good. Classic exactly as before (a label click selects nothing; the bar is New/Clear only). NEW verify_edit_basics.js 13/13 on scratch (select, bar Remove + x, x hides and stays hidden, click-away deselects, next selection brings the bar back, Delete 5->4, bar Remove, Escape, drag no select, Classic unchanged). verify_ctxbar 22/22 (its Post check now expects 'Edit tooling,x'), verify_dim_tool 23/23, test_commands_json 1178. Still to come in #6: Add feature and Close gap as rail tools with options bars. Identity gate green, F1 n/a. | UI EDITING BASICS (b) -- CLOSE GAP + ADD FEATURE AS RAIL TOOLS 2026-10-19 (Aristide 'continue' = #6 second half): New + Clear, Geometry tab of a part -- two rail tools under Measure: Gap (Close gap) and Add (Add feature). Each arms the Heal/QC panel's OWN mode (join / addpick / draw -- one road; the panel buttons stay and pick the same tool up) and shows an options bar above the drawing (#hqbar, the Dimension bar's look). Close gap bar: click near a gap, Show open ends (the open-ends lens), edits recorded, Done. Add feature bar: Circle / Line / Arc as one switch; circle X/Y/Ø, arc X/Y/R/from/to/CCW-CW, a canvas click fills X/Y (magnet as before), Add records the same add_circle/add_arc edit; Line arms the existing Draw flow (its bottom parameter bar unchanged), 'Draw again' after a chain ends. The tool is sticky (CAD habit): after a committed edit or a pick the same mode re-arms; Esc, Done, the rail button, right-click Cancel, or the Dimension tool put it down. Not on other tabs, part lists or sketches. Classic exactly as before (no rail tools, no bar; the panel buttons work as today). commands.json notes updated (runs unchanged). NEW verify_rail_tools.js 20/20 on scratch (rail New+Clear, Gap arms join + bar, lens, Esc; Add kinds/fields, click fills X/Y, Add records add_circle 0.25 and stays up, Arc fields, Line arms Draw, Done; panel button shows the bar; M drops it; Tooling none; Classic none + panel unchanged). edit_basics 13/13, dim_tool 23/23, ctxbar 22/22, menubar 20/20, stage_layout 23/23, healadd 12/12, drawline 32/32, healqc 14/14, test_commands_json 1178. Identity gate green, F1 n/a. | UI JOBS HOME QUEUE CARDS 2026-10-19 (Aristide '7'; the "workflow queues derived from stage status" half of pin jobs-home-filing): New + Clear jobs home -- a row of queue cards above the search box, 'Where jobs stand': Geometry / Tooling / Nest / Quote / Post / Deliver / Delivered / Blocked / Red. Each job sits in ONE queue: the step after the furthest stage it has finished (done or flagged), so a skipped Quote never strands a posted job; Blocked when that next step is blocked; Delivered when nothing is left. Red is a separate card (any stage with a RED). Group members ride their list (not counted loose), as the folders already do. Each card: count in big type + the 3 newest job names. A click narrows the customer folders to that queue (card lit, folders open, 'N matching'); it combines with the search box ('No jobs match ... in this queue'); a second click shows all. Derived from the same stage records the card dots read -- display only, nothing stored, no engine change. Sales door and Classic unchanged (no cards). The menu-row Search keeps finding jobs; the home keeps its one filter box. NEW verify_jobqueues.js 10/10 on scratch (Classic none; every count equals an INDEPENDENT derivation from /api/jobs with the stage order written out in the test; each loose job in exactly one queue; click lists only that queue's jobs + lit; queue+search no-match; click again = all; Clear same cards). palsearch 28/28, menubar 20/20, stage_layout 23/23, test_commands_json 1178. Identity gate green, F1 n/a. | UI NEST FINDING LIGHTS ITS SPOT 2026-10-19 (Aristide, screenshot of the part-list Nest drawer's Tight Pierce rows: "when I click one of these warnings, can the spot on the fixture light up on the screen to the left?"): a part list's per-part finding row in the Nest drawer (the rows that name their part and feature) is now clickable (the nav cursor + target mark like a single part's rows). A click lights every feature the row names on EVERY placed copy of that part: the feature's as-cut path stroked thick in the finding's colour (yellow/red) and a double ring round its pierce -- the plan row whose id is the finding's feature number, placed by the same placement transform the toolpath draws with (rotated copies use their own orientation's plan). The row is outlined; a toast says 'Feature N lit on M copies -- Esc clears'; if the first copy is off screen the view pans to it (zoom kept). Click the row again or Escape: off. Ctrl+K's jump to such a finding now lights it too (it clicks the row). Display only. All three layouts (the drawer is shared; single-part finding rows already navigated in Classic). Sheet-wide judge rows (no part/feature) unchanged. NEW verify_plfind.js 12/12 on scratch (New + Classic: 76 clickable rows; a Tight Pierce lights its feature on both placed copies, on screen, row outlined; again clears; a 6-feature row lights 6 x 2 = 12; Escape clears; zoomed far off -> pans to the first copy). palsearch 28/28, warn_chip 14/14, test_commands_json 1178. Identity gate green, F1 n/a. | UI NEST FINDING OPTION+CLICK ZOOMS 2026-10-19 (Aristide: "could you do OPTION + click to zoom in and click to just do what it does now?"): a part list's clickable Nest-drawer finding row -- plain click unchanged (lights the feature on every copy, pans only if off screen, click again clears). Option+click (Alt on PC) lights the same AND zooms to frame the lit feature(s) of the first copy with 0.75" of air, capped at 800% (the goFinding framing); Option+click on an already-lit row re-frames, never clears. Each hit now carries its world box (feature segs + pierce, arcs boxed by centre +- r) and its placement key. Row tooltip names the modifier; toast adds ', zoomed to the first'. Display only, all three layouts. verify_plfind.js 17/17 on scratch (+5: alt zooms 9.7 -> 504 k under the cap, lit feature centred, alt on lit row keeps it, plain click still clears with zoom kept, tooltip). palsearch 28/28, warn_chip 14/14. Identity gate green, F1 n/a. | UI STREAMLINE CLEAR NEST, NOT PACKED + BLOCKED 2026-10-19 (Aristide 'next' = #1 Clear for the remaining screens; picked the part-list Nest's not-packed/blocked states first because every new job lands there, while single-part true-nest screens are reached only by older one-off jobs): Clear only -- the part-list Nest drawer with no layout reads Nest (big status: Not packed yet / Pack cancelled -- nothing saved / Not packed -- blocked; material on machine; Pack sheets or Pack again (+ Overwrite toolpaths and pack on a DIFFERENT-material block) in the first section; the cancelled / needs-a-method / packs-by-itself / delivered-predates notes as one-line rows; a block keeps its BLOCKED banner and engine reason) / Nesting method (the same picker, buttons as outlined rows instead of a blue wall; not on a block, as before) / Sheet (size + sheet list folded, opening by itself when the block is about the sheets). clearPlNestBare(pn); same blocks and button ids, only placed. New and Classic unchanged. NEW verify_clear_nestbare.js 25/25 on scratch (four states set in page: New + Classic keep the old panel and wording; Clear has every field id and button label of the New panel in each state; sections, Pack sheets wired, cancelled time, blocked reason, sheet fold auto-opens on a sheet block, Overwrite on a material block). clear_layout 49/49, props_checks 16/16, plseq 15/15, test_commands_json 1178. Identity gate green, F1 n/a. Still to come in #1: single-part true-nest Nest/Quote/Post/Deliver, sketch, part-list Geometry cards. | UI STREAMLINE CLEAR PART LIST PANEL 2026-10-19 (Aristide 'go' = next piece of #1, Clear for the remaining screens): Clear only -- the part list's own panel, which the Part list tab and the list's Geometry and Tooling tabs all carry, reads Job (machine, material, Apply toolpaths + its result banner; the material and Apply explanations fold into 'How material works') / Parts (N parts · M pieces in big type, counted from the list's rows with qty > 0; on Geometry/Tooling one line says a list has none of its own and a card opens that part's Geometry or Tooling screen -- replacing the old paragraph there; no-healed-jobs note, blocked cards, upload notes, add-all-from-split, shared-prefix note, the cards, Add part / Add from existing / New sketch part / Save list, fill even rows, a pack-blocked banner) / Settings for every part (folds: Slug tabs and chop; Part frames and nest rotation) / How this works (bridge and part-by-part notes). clearPlList cuts plListDrawer's own html at marks -- same ids, data-pl controls and wiring; New and Classic concatenate exactly as before. NEW verify_clear_plist.js 27/27 on scratch (New + Classic keep the old panel and the Geometry note on all three tabs; Clear has every field id, 48 card controls and every button label of New on each tab; sections; count matches the stored list independently; where-a-card-opens line; folds; a card qty edit + Save list is recorded and put back; 'open' on a Geometry-tab card lands on that part's Geometry). clear_layout 49/49, clear_tabs 21/21, stage_layout 23/23, props_checks 16/16, test_commands_json 1178. Identity gate green, F1 n/a. Still to come in #1: single-part true-nest Nest/Quote/Post/Deliver (older one-off jobs only), sketch. | UI STREAMLINE CLEAR SKETCH 2026-10-19 (Aristide 'next' = next piece of #1): Clear only -- a sketch part's Geometry tab reads Sketch first (stage dot; N shapes in big type; one status row: Applied -- N contours (closed/open) | Edited since Apply -- Apply again | Not applied | the REFUSED banner + engine reason; the typed shape rows, line/arc/circle, Apply sketch -- highlighted when there is something to apply; the long how-to folds into 'How sketching works'), then, once applied, the same Part / Checks / Details as any part (clearGeometry now takes the sketch section in front). Before the first Apply the Intake/Heal/QC sections fold under 'Intake, heal and QC -- after Apply'. A sketch's units row reads as typed (no longer 'read from the file'). sketchDrawer marks its pieces only when Clear asks (New/Classic output unchanged). NEW verify_clear_sketch.js 11/11 on scratch (KM_EXTRA=verify-washer-1790047223: New + Classic old panel; Clear has every field id, typed field and button of New; sections; shape count matches the stored sketch; units wording; an edited diameter -> Edited since Apply + Apply highlighted; put back + Apply from the section -> Applied; not-applied state folds the stages). verify_sketchdraw 17/17 (Classic, bandsel scratch), clear_tabs 21/21, clear_layout 49/49, test_commands_json 1178. Identity gate green, F1 n/a. /tmp/km_cmdscan/scratch.py now takes KM_EXTRA=<job ids> (outside the repo). Still to come in #1: single-part true-nest Nest/Quote/Post/Deliver (older one-off jobs only). | UI STREAMLINE CLEAR SINGLE-PART NEST 2026-10-19 (Aristide 'finish 1 first then on to 8'): Clear only -- a single part's own true-nest (one part x N) Nest drawer reads Nest (stage dot; N parts on M sheets in big type; material on machine, asked count when it differs; block banner; 'Layout edited by hand' row; quantity + Nest/Re-nest -- primary before the first nest -- + spread Y / spread X / back to table values up top; the PLACED banner and result numbers fold into 'Result -- gap, sheet') / Spacing and orientation (gap, edge margin, X spacing, orientation, finish even columns + the seed note, folded) / Manual layout (Edit layout by hand / the editor controls in view; the editor's long how-to folds into 'How hand editing works'; restore + hand-edit findings in view) / Part order (the pattern knobs, per-nest pattern, Click parts in order; its long note folds into 'How the order works') / Sheet (size folded) / Common-line cutting (its own details, unchanged) / How this works. No toolpath yet: Not nested yet + the old note. nestDrawer(st, cut) marks its pieces only when Clear asks (New/Classic output unchanged); clearNest(st). NEW verify_clear_nest.js 13/13 on scratch (nav209: New + Classic old panel; Clear has every field id, control and button of New; sections; count matches the stored nest; folds; hand editor + click-in-order modes; quantity 20 + Re-nest from the section then put back to 196; no-toolpath state set in page). clear_layout 49/49, ctxbar 22/22, test_commands_json 1178. Identity gate green, F1 n/a. Still to come in #1: single-part Quote, Post, Deliver. | UI STREAMLINE CLEAR SINGLE-PART QUOTE 2026-10-19 (Aristide 'finish 1 first then on to 8'): Clear only -- a single part's own Quote reads Quote (stage dot; the price in big type -- '— indicative' when not firm, 'No price yet' when rows are missing, 'Not estimated yet' before the first run; N of M parts on S sheets, sheet usage, material on machine; quantity, Re-estimate / Auto-nest + estimate -- highlighted before the first run -- and Record customer approval up top; the stale / two-week banners and the sales-door note stay in front as before) / Checks (missing price rows, firm or indicative, approval, the fast estimate as one line, program warnings; on missing rows the NO TOTAL list with its typeable rate fields stays in view) / Details folds (how the total is built or cost lines so far, measured run, fast estimate, material + sheet + notes, customer approval, how this works). quoteDrawer marks the single-part pieces too (New/Classic output unchanged); clearQuote(Q, h, cut); the part-list quote still goes to clearPlQuote. NEW verify_clear_quote.js 13/13 on scratch (nav209: New + Classic old panel; Clear has every field id, control and button of New; sections; big line and missing-row count match the stored quote; rate fields and quantity out of folds; quantity 20 + Re-estimate then put back to 196; not-estimated state set in page). verify_plquote 44/44 (rates.json restored). Identity gate green, F1 n/a. Still to come in #1: single-part Post, Deliver. | UI STREAMLINE CLEAR SINGLE-PART POST 2026-10-19 (Aristide 'finish 1 first then on to 8'): Clear only -- a single part's own Post reads Sheet program first (the nested sheet leads, Jordan 2026-09-07: stage dot; its program number(s) in big type or 'Not posted yet' / 'No sheet layout yet'; N programs · nest macro or part-by-part · N sheets; refusal/block and the audit banner; a 'Posts part-by-part' row when Manual Sort or a clicked part order drops the macros; Post / Re-post nested sheet -- highlighted before the first post; per program the downloads and findings in view, the numbers folded into 'Program details' (per sheet when several); program number, style and sub numbers folded; the notes fold into 'How this works') then Single part program the same way (number, lines + arcs, banner, Post / Re-post, downloads and findings in view; 'Program details', 'Program text', 'Program number' and 'How this works' folded). postNestSection(st, cut) and postDrawer(st, cut) mark their pieces only when Clear asks (New/Classic output unchanged); clearPost(st); new helper kmPieces(h, cut). NEW verify_clear_postsolo.js 13/13 on scratch (nav209: New + Classic old panel before and after posting; Clear has every field id, control, download link and button of New, before and after; sections; unposted state; Post nested sheet and Post G-code from the Clear sections -> big numbers match the stored stage onums; both downloads in view; details + program text fold; both banners in view). verify_clear_post 11/11 (part-list Post unchanged). Identity gate green, F1 n/a. Still to come in #1: single-part Deliver. | UI STREAMLINE CLEAR SINGLE-PART DELIVER 2026-10-19 (Aristide 'finish 1 first then on to 8'; closes #1 -- every screen now has its Clear form): Clear only -- a single part's own Deliver reads Sheet delivery first (the nested sheet leads, as on Post), then Single part delivery, each: stage dot; 'vN delivered' / 'Not delivered yet' / 'Post first' in big type; O-number(s) · build # · date; block banner, the re-planned / post-again notes and the delivered banner in view; Deliver / Deliver again -- highlighted when posted and nothing delivered or the job was re-planned; board, floor packet and customer sheet links in view; the file downloads fold into 'Files -- N', the numbers into 'Delivery details', the chain into 'Versions -- N', the note into 'How this works'. deliverNestSection(st, cut) and deliverDrawer(st, cut) mark their pieces only when Clear asks (New/Classic output unchanged); clearDeliver(st). NEW verify_clear_deliversolo.js 13/13 on scratch (nav209: New + Classic old panel before and after delivering; Clear has every field id, control, link and button of New; sections; big lines match the stored stage versions; links in view, files/details/versions folded; post both by API, Deliver both from the Clear sections -> new versions match; nothing-posted state set in page). verify_clear_deliver 12/12 (part-list Deliver unchanged). Test boards removed from the real viewer, builds.json/index.html restored. Identity gate green, F1 n/a. #1 done; next #8 shop-floor mode. | UI STREAMLINE FLOOR MODE (a) 2026-10-19 (Aristide 'a' = #8 shop-floor mode, piece a): Clear in big type with tap-sized controls for a shop-floor tablet. View > 'Floor mode — big type, touch' (a checkmark item, offered only in Clear), per station like the layout (localStorage km.floor), ?floor=1 / ?floor=0; index.html sets body.km-floor before paint. Every rule is gated on body.layout-clear.km-floor, so Classic, New and plain Clear render exactly as before. What changes: menu row 38px and 16px menus with tall items; header 56px, 17px tabs with 26px numbered circles (below 1700px only the open tab keeps its name, as plain Clear does below 1360px); the right panel docks at 400px and its contents, the Heal/QC and Dimension panels, the tool rail and the zoom bar scale x1.3 with CSS zoom (text reflows to the panel, nothing overflows); drawer buttons, links, inputs, selects, checkboxes and fold headers get tap-sized minimums (buttons 44px on screen); jobs home x1.25. The canvas is never zoomed, so picking and dragging on it stay true. Nothing new is built and nothing is hidden. menubar.js floorOn/setFloor (kmMenu exposes both). NEW verify_floor.js 16/16 on scratch at iPad landscape 1180x820 (Classic and New ignore the flag; Clear unchanged without it; View item turns it on, checkmark, remembered after reload; every visible drawer button >= 40px on screen (smallest 44); big line 21px; no page scroll, canvas 708px; header fits without overlap on a part and on a 7-tab part list; canvas not zoomed; ?floor=0/1). verify_menubar 20/20, clear_layout 49/49, test_commands_json 1178. Identity gate green, F1 n/a. Next in #8: (b) floor home -- big cards for jobs ready to cut; (c) hide editing tools in Floor mode. | UI STREAMLINE FLOOR HOME (b) 2026-10-19 (Aristide 'B' = #8 shop-floor mode, piece b): in Floor mode the jobs home leads with 'Ready to cut' -- one big card per job with a delivered program, newest first, latest 8 with 'Show all N'. Each card: the program number(s) in big type; job name, customer, order reference; which delivery (part-list sheets, nested sheet, single part -- the sheet delivery leads, a single-part delivery rides as a second packet link), its version and red/yellow counts; the sheet picture is the first drawing of that delivery's own floor packet (loaded as the card scrolls into view); a tap on the card opens the floor packet; Floor packet and Open job buttons. A delivery re-planned since it shipped stays on the band, amber, with 'Re-planned after this delivery -- check the job before cutting' (warn, never block). The search box narrows the band too; the queues and customer folders stay below, nothing hidden. Display only, read from the stage records already in /api/jobs; no server change, no restart. Classic, New and plain Clear never show it; View > Floor mode on/off re-renders the home at once (menubar.js setFloor). app.js renderFloorReady/floorDeliveries/floorPic, index.html #floorready, app.css #floorready block. NEW verify_floor_home.js 18/18 on scratch and 18/18 read-only on dev data (39 delivered jobs, 8 cards): absent in Classic/New/plain Clear; card count, packet paths, program numbers, re-plan warnings and link counts match the job records; picture loads from the packet; packet url 200; tap opens the packet; search by program number finds the card, no-match empties the band; Open job opens it; turning Floor off hides it. verify_floor 16/16, verify_menubar 20/20, clear_layout 49/49, test_commands_json 1178. Identity gate green, F1 n/a. Known: a multi-sheet delivery shows sheet 1's picture; search wants the digits (O33292 without the O finds nothing -- existing home search). Next in #8: (c) hide editing tools in Floor mode. | UI STREAMLINE FLOOR LOCK (c) 2026-10-19 (Aristide 'C go' = #8 shop-floor mode, piece c): in Floor mode a station is LOCKED by default -- it can look but not change a job; one tap on the header chip ('🔒 Locked', amber, beside the job name) switches to '✎ Editing', another tap locks again; per station (localStorage km.floorlock), also View > 'Floor lock — look, don't change' (checkmark, offered only in Floor mode). While locked: the Gap/Add rail tools, the Heal/QC edit modes (join, drag end, fit arc, delete, add), the add-feature kinds, undo/redo and the home upload drop zone hide; Edit/Part/Job/Select menu items dim with 'locked — tap Locked to edit' except the read-only ones (view, window, help, file, lenses, the measure tool and its kinds, downloads, Escape, check details); and every request that would write is refused in the app's fetch wrapper with a toast ('Locked — nothing was changed') and a plain 423 answer the existing error paths show (e.g. the Post tab's own 'NEST POST REFUSED ... nothing was posted' banner) -- the read-only doors still pass (dragcheck, nestspread, healmarks, textdetect, isogroups, partgroups, cancel, plcancel, uploadcancel, bugreport). Viewing, measuring, Next, the floor home, floor packets and downloads all stay. Floor mode off = no chip, no lock, whatever the flag says; Classic, New and plain Clear never see it. index.html sets body.km-floorlock before paint. menubar.js floorLocked/setFloorLock/lockChip/LOCK_OK (kmMenu exposes both); app.js FLOOR_LOCK_OK + floorLockRefuses in the fetch wrapper; app.css lock block. No server change, no restart. NEW verify_floor_lock.js 22/22 on scratch (no lock in Classic/New/plain Clear; locked by default; tools/modes/undo hidden, Select stays; Job menu edit items dimmed, View items usable, View lock item checked; a Post request refused 423 in plain words + toast; dragcheck passes; clicking Post in the drawer leaves the job record byte-identical; tap unlocks, tools back, remembered after reload, writes pass, menu usable; tap locks again; home locked hides the drop zone, unlocked shows it; Floor off ignores the flag). verify_floor 16/16 (header still fits with the chip on a 7-tab part list), verify_floor_home 18/18, verify_menubar 20/20, clear_layout 49/49, test_commands_json 1178. Identity gate green, F1 n/a. #8 (a)(b)(c) done. | UI STREAMLINE CLEAR TOUR 2026-10-19 (Aristide '9' = #9 update the welcome tour for Clear): the Clear layout walks its own first-run tour; Classic and New keep the original 10 steps unchanged. Clear steps: Welcome (Clear keeps each screen to what matters now, nothing removed, only moved or folded) / One menu row (Adobe-style menus, dimmed items say where they work, Ctrl+K finds any command) / Ready to cut (Floor mode, home) or Jobs home (drop zone, part list, Sales door; not on a floor station) / Where jobs stand (queues, home only) / The steps, numbered (circles, the open one named, the dot legend) / Next / The drawing / Tools, labelled (V F M, options on the bar above the drawing) / The right panel -- big line first (answer in big type, main button highlighted, details under fold arrows, right-click to override, warnings never block) / Panels tear off (Window > Reset panels) / Locked -- look, don't change (Floor mode only) / Layout and Floor mode (anchored on the View menu) / Help, from anywhere. A step may anchor on a CSS selector (sel) and show only when its 'when' holds; the counter counts the filtered steps; Help > Guided tour replays the layout's own tour. In Floor mode the tour card reads larger (15px body, 18px title, 40px buttons; width kept so placement holds). app.js TOUR_CLEAR/tourSteps/floorTour, tourPlace sel support; app.css floor tour block. NEW verify_clear_tour.js 15/15 on scratch at 1366x860 (Classic and New: the original 10-step tour, Done marks the station; Clear first run starts the Clear tour; home: no floor steps, menu row/drop zone/queues/View menu/help light live elements, card on screen every step, counter counts filtered steps; in a job: tabs, Next, drawing, rail, right panel and grip light live elements, queue step left out; Floor: Ready to cut replaces the drop-zone step and lights the band, the lock step lights the Locked chip; Help replay opens the Clear tour). verify_floor 16/16, verify_menubar 20/20, clear_layout 49/49, test_commands_json 1178. verify_tour.js (old, hard-wired to the public URL) passes its tour steps; its Help-menu checks 9-10 assert an older Help list (now carries Colors & legend and Shop setup) -- stale, untouched here. Identity gate green, F1 n/a. | COLD REVIEW 2026-10-19 (Aristide: 'look at all the UI work, and tell me what we missed -- have a cold agent run through it'; fresh agent, scratch :8479, screenshots /tmp/coldreview/, read-only). OPEN, nothing fixed yet. HIGH: H1 Floor on iPad portrait 820x1180 does not fit -- sideways scroll, Search cut, corner chips off screen, zoom bar over the panel; home portrait: empty 400px Checks panel covers half the Ready-to-cut card (verify_floor only landscape). H2 Floor on Geometry scrolls the whole page even in landscape (1017px in 820; Heal/QC body under zoom 1.3 overflows) -- confirmed. H3 Floor lock hides only some editing tools; Re-plan, Nest/Re-nest, Spread/Jam, Post, Deliver again, Apply, quantity fields, Drop tiny/duplicates stay visible and are refused only after the tap; partial hiding leaves empty boxes and CENTER X/Y labels without inputs -- confirmed (Deliver again visible). H4 Clear clamps some notes to one line with hover-to-read, including warnings (re-planned/post again, nest program superseded, drawing sheet 'why it can't nest'); a tablet cannot hover (app.css ~1163). MEDIUM: M5 Heal/QC panel never got the Clear treatment (button wall + long italic help). M6 Jobs home / Sales door: empty Checks panel, Select/Fit rail doing nothing, unstyled drop-zone buttons, Sales hint text describes the wrong door after switching. M7 Next: is a bare next-tab button -- sits beside the highlighted Post as a second main button, offers Quote on a sheet that can't nest. M8 Name: three spellings live; CLAUDE.md line still says KERFMASTER (ruling 092075f6 says Kerfmaster). M9 Open plan items: options bars for the remaining tools; rejected-nest thumbnails (engine); retire one layout; Clear is not the default (prod users never see it); the #1-#10 opportunity list lives on no pin/doc; plan header still says 'nothing built', pin typed intent. M10 Queues, Ready-to-cut, warnings tally and floor lock are web-only JS (three-lenses rule); lock is per browser, server unaware, unlock not recorded. M11 Tests: Clear suites mostly check presence not click-through; 96/155 verify suites ignore KM_BASE (hard-wired to dev/public); lock suite tests one refusal; no portrait/geometry-floor/hover-note tests; verify_tour 9-10 stale. LOW: L12 Floor tap targets: corner chips 26x22, panel -/expand 13x19, Search 22px; Clear corner chips are bare glyphs. L13 Single-part Deliver: board/packet links filled like action buttons (part-list uses outline chips); delivered banner repeats the big line. L14 nav209 scratch: Post 'Not posted yet' + Tooling grey while Deliver shows v2/v10 -- unexplained, maybe a scratch-copy artefact. Not covered: sketch/washer, Ctrl+K and warnings chip in Floor, tour portrait, context bar/right-click while locked, light theme, Sales quote view in a job, part-list member tabs. | UI COLD REVIEW FIXES -- HIGH 1-4 + M6 home panels + L12 tap sizes, 2026-10-19 (Aristide 'Fix all new agent findings'; chunk 1 of the fix list). H1 Floor upright (iPad 820x1180): under 1000px wide the menus tighten, Search becomes its icon, the warnings chip keeps dot + count, the menu-row brand steps aside (the K stays), the Locked chip shows its padlock only, Next steps aside, the job name caps at 150px, the right panel is 360px, the zoom bar is 1x and stays inside the drawing, Ready-to-cut cards go one per row -- no sideways scroll on any screen. H2 Floor Geometry: the 1.3x Heal/QC and Dimension panel bodies scroll inside their panel, so the page never scrolls (was 1017px in 820). H3 Floor lock completed: every panel button that writes hides (the in/mm display switch stays), every panel field stays visible with its value but read-only (disabled, marked data-flock), the Heal/QC edit panel and the context bar step aside, the panel opens with '🔒 View only — tap Locked to edit'; unlocking re-renders it with everything back (the fetch guard stays as the net). H4 notes: a note that warns (re-planned, superseded, post/deliver again, refused, blocked, can't, before cutting, RED, the drawing sheet's why-it-can't-nest) is marked kwarn and never clips, in warn colour; any clipped note opens/closes on a tap (capture listener, a tablet can't hover); Floor mode never clips notes. M6 (part): the jobs home in Clear drops the empty Checks panel, the tool rail and the Heal/QC/Dims panels (body.km-home set by loadHome, cleared by openJob). L12: Floor header chips 40x34, Search 34px tall, panel minimise/float buttons 40x36. app.js NOTE_WARN/markWarnNotes (MutationObserver on drawer, Heal/QC body, home) + tap toggle + km-home; menubar.js lock chip icon/text spans and re-render on lock change; app.css blocks. NEW verify_floor_fit.js 9/9 (upright locked, landscape locked, upright unlocked: home, geometry, nest, post, deliver, part list, part-list nest, drawing-sheet nest all fit with no page scroll either way, no header overlap, zoom bar inside the drawing; floor home upright has no empty panels and the card in view; deliver re-plan/superseded warnings marked and shown in full; drawing-sheet why-it-can't-nest shown in full; a tap opens a clipped note; Floor clips no note). verify_floor_lock now 27/27 (panel buttons hidden, View only line, Heal/QC gone, part-list fields shown read-only, nothing changed; unlocked: buttons and Heal/QC back). verify_floor 16/16 (sizes now checked unlocked), floor_home 18/18, clear_layout 49/49, clear_tour 15/15, menubar 20/20, test_commands_json 1178. Identity gate green, F1 n/a. Still to fix from the review: M5 Heal/QC panel in Clear, M6 rest (Sales door wording, drop-zone buttons), M7 Next, M9 plan/pin housekeeping, M10 three-lenses, M11 test housekeeping, L13 Deliver link styling, L14 nav209 post/deliver mismatch check. | UI COLD REVIEW FIXES -- chunk 2: M5 Heal/QC + M6 rest + M7 Next + L13 Deliver, 2026-10-19 (Aristide 'Next chunk'). M5 Heal/QC panel in Clear: the tool buttons are quiet outlined rows (the active tool stays lit), the Add / pick buttons outline chips, the select themed; the long italic help folds under 'How these edits work' (all of it kept, normal type, open state remembered). M6 rest: the Sales door hint names the door the button opens (on the Sales door: 'back to every step -- the same jobs, full tooling'; the old text described the wrong door after switching -- a wording fix that shows in every layout); in Clear the drop zone's New part list and Sales door buttons are outline chips beside Browse. M7 Next: an outline button, no longer a second filled main button; offered only once the open step has run (done, or done with warnings/red -- warn, never block); Tooling always passes (its plan is automatic, its dot stays grey); a step that has not run (nav209 Post not posted, the drawing sheet's Nest that can't nest) and a blocked next step offer nothing; on a part list Next steps over the member Geometry/Tooling tabs (they open a part) to Nest; tooltip says the tabs still work. Tabs now carry data-tab (invisible). Clear tour Next step text updated. L13 single-part Deliver in Clear: the banner that repeated the big line is gone; its verdict rides as one row ('0 red · 10 yellow in the delivered file' / 'Delivered clean'); board / floor packet / customer sheet links are outline chips like the part list's. Classic and New unchanged apart from the Sales hint wording. NEW verify_clear_review2.js 18/18. verify_clear_layout 49/49 (first run caught my Heal/QC fold reusing the drawer's fold class -- fixed with its own details), clear_tour 15/15, clear_deliversolo 13/13 (its two new viewer builds removed, builds.json/index.html restored), floor 16/16, floor_home 18/18, floor_lock 27/27, floor_fit 9/9 (on fresh scratch copies; one run right after deliversolo failed only because that suite had just re-delivered nav209), menubar 20/20, test_commands_json 1178. Identity gate green, F1 n/a. Still open from the review: L14 nav209 post/deliver check, M9 plan/pin housekeeping, M10 three-lenses proposal, M11 test housekeeping; decision: Clear as default. | NAME SPELLING CORRECTED to KerfMaster, 2026-10-19 (Aristide: 'I had a typo on the name change. Is supposed to be KerfMaster. Change it and then go for restart'). Pin product-name-spelling re-ruled (KerfMaster; the same day's 'Kerfmaster' was a typo, its text kept on the pin); CLAUDE.md name line updated. Every 'Kerfmaster' from the a315b4d8 sweep now reads 'KerfMaster': 76 spots in 19 files -- screens (page title, header brand, jobs home heading, Clear menu-row brand, both tour welcomes, split-out note), paperwork (floor packets, delivery pages, customer sheet, approval pages, production post, boards, reference print, slug report, material worksheet, shop-tables page, open-questions page) and NC header comments (part, nest, part-list, common-line, quote-count, geometry post, emit default part name) plus the test expectations. Intended G-code delta: golden refs re-made (--make-refs); exactly 17 lines in 17 references changed, each the header comment 'Kerfmaster' -> 'KerfMaster', nothing else (checked). Identity gate green after. Pin history text and already-delivered files keep the old spelling (immutable versions). verify_clear_tour 15/15, verify_clear_layout 49/49. F1 n/a. | UI COLD REVIEW FIX L14 -- nav209 Post 'not posted' beside delivered v2/v10, 2026-10-19 (Aristide 'Go on next'). Investigated on the dev disk: NOT a scratch artefact and not a data fault. nav209 was re-planned on 2026-09-19 after both deliveries; by design a re-plan deletes the stale programs (post.nc / postnest.nc, O33291/O33292 kept on the stage records) and marks the immutable deliveries replanned (deliver v10, delivernest v2, files untouched). The Deliver tab already said so; the Clear Post tab only said 'Not posted yet'. Fix (Clear only, Classic unchanged): when a program is not posted and its delivery is marked replanned, Post shows one yellow row -- 'Delivered v2 predates a re-plan or re-nest -- post again, then deliver again to supersede it' (sheet) / 'Delivered v10 predates a re-plan -- ...' (single part). Warn, never block. verify_clear_review2 19/19 (new L14 check), clear_layout 49/49, floor_fit 9/9 (upright Post still fits). Identity gate green, F1 n/a. | UI COLD REVIEW FIX M11 -- test housekeeping, 2026-10-19 (Aristide 'Go'). The 96 browser suites that ignored KM_BASE now honour it: each one's single address line (BASE / URL / APP / B / URL0, hard-wired to dev.kerfmaster.com, the old kerfmaster-app mycloudally URL, localhost:8474 or a fixed scratch port) reads process.env.KM_BASE first and keeps its old address as the fallback, with its trailing-slash style kept (so a run without KM_BASE behaves exactly as before). All 157 verify_*.js suites now take KM_BASE; all 96 pass node --check. Stale checks fixed: verify_tour 9/10/17 picked Help menu items by position (the menu grew to 5: Colors & legend, Shop setup) -- now found by name; 20/20 on scratch (its test bug report removed after). verify_panels 14 expected the retired 'Part review' title on tab=review -- now Tooling; 14/14 on scratch. Spot run verify_display 12/12 on scratch. Not changed: the viewer/board URLs inside verify_deliver, verify_customer and verify_delivernest (board, not app). Test files only; identity gate green, F1 n/a.
- •Move the web-only UI state into the engine -- queues, Ready to cut, warnings tally, floor lock (cold review M10, 2026-10-19) recordmixed — ANSWERS 2026-10-19 (Aristide): Q1 unlock = one recorded tap, no name/PIN (PIN a later option) -- AGREED; Q2 station names set once per tablet by whoever sets it up -- AGREED; Q3 asked back 'what do you suggest?' -- suggested: the full lock/unlock log on the Shop setup page (shop-level, where stations are named); on the floor the header chip itself says the state and since when ('Editing since 14:02 -- Laser 1 tablet'); nothing on the jobs home. Awaiting OK. | intent (Aristide 'Yes' 2026-10-19 to writing the M10 proposal; proposal only, nothing built, each chunk needs a go). Proposal: docs/m10-engine-side-ui-state.md. Four features are worked out only in the web page's JS (job queues jobQueue/jobRed, Ready to cut floorDeliveries, warnings tally warnTally, floor lock km.floorlock + fetch guard floorLockRefuses) -- against the three-lenses rule (ui-one-source-three-lenses); the lock is per browser, the engine never sees it, unlocking is not recorded. Chunks: A engine owns the tab-to-stage map + /api/jobs gives each job queue + red (old-vs-new match over every job on dev); B /api/jobs gives each job its ready list; C GET /api/jobs/<id>/warnings (per-tab red/yellow minus green flags, from the findings on disk); D station id + name, lock state per station in a shop file, the engine refuses writes from a locked station (same allowed doors), every lock/unlock recorded in a station log, page guard stays as a net. Each chunk: engine change = coordinated dev restart, jobs-home load timed before/after, identity gate green, speed told. QUESTIONS before D: (1) unlock = recorded tap (suggested) or name/PIN first; (2) station names set once per tablet; (3) station log shown on jobs home, Shop setup, or both. | ENGINE-SIDE UI STATE chunk A -- jobs-home queues worked out in the engine, 2026-10-19 (Aristide 'Yes agreed go on the rest. Build it'; Q3 answered: the full lock/unlock log on Shop setup, the floor header chip shows state + since when, nothing on the jobs home). NEW cadmaster/jobstate.py: the tab strip, which stages each tab covers (tabs_for / stages_for / doors_converged / quote_converged), job_queue and job_red -- a straight port of the web's tabsFor / stagesFor / jobQueue / jobRed as the jobs home uses them, JS truthiness kept for job.group. GET /api/jobs now gives every job home: {queue, red}, worked out at read time, never stored. app.js jobQueue / jobRed read it; their old lines stay only as cover until dev's engine is restarted onto it, then come out. Checked old-vs-new: the web's own functions (lifted from app.js) and the engine over every job on dev -- 1315 jobs, 0 differ (tooling 1080, post 70, quote 34, done 31, deliver 30, geometry 27, blocked 22, nest 21). NEW test_jobstate.py 12/12 (each branch). verify_jobqueues 10/10, verify_floor_home 18/18 on scratch. Cost: 14 ms for 1315 jobs on a /api/jobs that takes ~80 ms on dev. Noted, unchanged: a job whose last finished step is Deliver reads Delivered even when Post was dropped by a re-plan (nav209) -- as the web always read it. Engine change: live on dev after a coordinated restart; prod picks it up with its deploy. Identity gate green, F1 n/a (jobs list, not the first-click path). | ENGINE-SIDE UI STATE chunk B -- Ready to cut from the engine, 2026-10-19 (Aristide 'go on the rest. Build it'). jobstate.ready(job): every delivered program a floor station can cut from -- part-list sheets, then nested sheet, then single part; version, O-numbers, red/yellow, re-planned mark, floor packet link -- a port of the web's floorDeliveries. GET /api/jobs gives it as home.ready. app.js floorDeliveries reads it (old lines kept only as cover until dev's engine is restarted onto it). Checked old-vs-new over every job on dev: 1315 jobs, 40 deliveries, 0 differ. test_jobstate 16/16 (4 new). verify_floor_home 18/18, verify_jobqueues 10/10 on scratch. Identity gate green, F1 n/a. | ENGINE-SIDE UI STATE chunk C -- warnings tally from the engine, 2026-10-19 (Aristide 'go on the rest. Build it'). jobstate.stage_findings + jobstate.tally: per tab, the open red / yellow findings with green-flagged ones left out (nc_warn's own _fkey/_ckey, the keys the post already honours); a stage with no document falls back to its record's counts, marked known=False -- a port of the web's stageFindings/warnTally. NEW GET /api/jobs/<id>/warnings[?material=&machine=] (server.warnings_state) reads the stage documents the job screen loads (review plan incl. a list-opened part's material, cutplan, post, postnest, the part-list pack + its programs). app.js warnTally asks the engine whenever the job's stages, versions or green flags change and shows its answer; the old count stays only as cover until dev's engine is restarted onto it. Gain: the engine always reads the documents, so a tab no longer shows a stage-record guess ('open the tab to see') before it is opened. Checked old-vs-new over every job on dev with the documents loaded: 1306 openable jobs (9 '--help' ids the engine refuses), 337 tabs with warnings, 0 differ. NEW verify_engine_ui_state.js 5/5 on scratch (every job carries home; queue cards, Ready to cut and the chip each show an engine answer the page could not have counted itself). verify_warn_chip 14/14. Correction to chunk B's record: test_jobstate read 15/16 at that commit (my home() shape check had not been updated for the new ready field), not 16/16 as written; fixed here, 16/16. Identity gate green, F1 n/a. | DEV RESTART + NOTE FOR SPEED, M10 2026-10-19 (Aristide 'restart', then 'formulate detailed instructions for Speed in an MD'). Dev kerfmaster-app restarted onto chunks A-C after both engines read inflight 0 (8475 untouched); live check: 1315/1315 jobs carry home, /api/jobs/<id>/warnings answers (mid-plate-2: Tooling 1 red 4 yellow); /api/jobs 98-128 ms wall, /warnings 1.6-14 ms. NEW docs/for-speed-m10-engine-ui-state.md: what moved into the engine, files, API shapes, cost, merge notes, heads-up on cover removal and chunk D (423 from a locked station; header-less requests not refused -- to confirm in D), three questions back. Docs only; identity gate n/a, F1 n/a. | ANSWERS FROM SPEED, M10 2026-10-19 (relayed by Aristide): Speed takes server.py/app.js from main untouched (last merge 830a4655, 424 behind; will take all at once); no objection to the cover removal; Speed's writes go to :8475 with no station header. Chunk D design rules fixed by this: header-less requests are never refused by the lock (tested in D); lock state per tree in APP_DIR beside shop.json, gitignored runtime data (shop.json itself is tracked, so its pattern is not copied), so a dev tablet can't block :8475 and no merge or deploy carries lock state. docs/for-speed-m10-engine-ui-state.md updated. Docs only; identity gate green, F1 n/a. | ENGINE-SIDE UI STATE cover removal, 2026-10-19 (Aristide 'go'; dev engine restarted onto A-C earlier today). app.js: jobQueue / jobRed / floorDeliveries now only read job.home from GET /api/jobs; warnTally only reads GET /api/jobs/<id>/warnings and, until the answer lands, keeps the engine's last answer for the same job (else nothing). The page's own copies of the queue, red, ready and warnings logic are gone (-65 lines), plus the now-unused QTAB / FLOOR_DLV. tabsFor / stagesFor / stageFindings stay (tab strip and tab dots). Speed agreed (page and engine come from one tree). On scratch: verify_jobqueues 10/10, verify_floor_home 18/18, verify_warn_chip 14/14, verify_engine_ui_state 5/5, verify_clear_review2 19/19, verify_panels 14/14. Live dev: Ready to cut band shows 39 cards (39 jobs, 40 deliveries), the same as the old page. Web only, live at once, no restart. Identity gate green, F1 n/a. | ENGINE-SIDE UI STATE chunk D1 -- floor stations + the lock in the engine, 2026-10-19 (Aristide 'go'). NEW cadmaster/stations.py: per-station name, locked, since; every naming / lock / unlock is one log line (station, name, time, did, who = 'typed in the app'); no change = no line. NEW GET /api/stations (stations + last 500 log lines) and POST /api/stations/<id> {name?, locked?, why?}. Every POST first asks stations.refuses(): a station whose X-KM-Station header names a LOCKED station gets 423 with the page's own words; the allow-list is app.js FLOOR_LOCK_OK, and /api/stations/* always passes so a tablet can always unlock. NO station header = never refused (Speed's tools, curl, bench_f1_probe; confirmed to Speed), and an unknown station is not refused either. The file is cadmaster/app/stations.json beside this tree's shop.json, runtime data, gitignored (shop.json is tracked, so its pattern is not copied): dev and :8475 never share lock state, and no merge or deploy carries it. No page sends the header yet, so nothing changes for anyone until D2 (page: station id + name, chip 'Editing since HH:MM -- <station>', log on Shop setup). NEW test_stations.py 19/19 (real handler, tempdir). test_jobstate 16/16, test_commands_json 1178 OK. Engine change: live on dev after a coordinated restart. Identity gate green, F1 n/a. | ENGINE-SIDE UI STATE chunk D2 -- the page side of the floor lock, 2026-10-19 (Aristide 'restart' after the D1 report, which said D2 follows the restart; dev restarted onto D1 first, both engines inflight 0, :8475 untouched). app.js: kmStationId() makes the station id once (km.station; it lives in app.js because the page's first requests go out before menubar.js loads). kmStationOpts adds X-KM-Station to every engine request in Floor mode (read from the head script's km-floor class until menubar.js is up). The page's own guard lets /api/stations through, so locking and unlocking always reach the engine; a 423 from the engine makes the page re-read it. menubar.js: on entering Floor mode the engine's word wins (a stale local flag is overruled; a tablet the engine never saw reports once as 'first seen'); each tap posts the lock to the engine. The header chip reads 'Editing since HH:MM -- <name>' (date added when not today), and its title says 'Name this tablet under ? > Shop setup' while unnamed. Shop setup gains Floor stations: name this tablet (saves at once), every tablet's state and since when, and the lock log newest first (15, then show all) with who. The page guard stays as the second net. Outside Floor mode there is no header and nothing is refused. NEW verify_station_lock.js 21/21 on scratch (its stations file now in scratch's tempdir, so dev's real log stays empty). Regression on scratch: verify_floor_lock 27/27, verify_floor 16/16, verify_floor_home 18/18, verify_floor_fit 9/9, verify_jobqueues 10/10, verify_warn_chip 14/14, verify_panels 14/14. Not checked live in Floor mode on dev, so as not to log a test tablet in dev's real station log. M10 complete (A, B, C, cover removal, D1, D2): pin retyped intent -> record (flag mixed kept). Web only, live at once. Identity gate green, F1 n/a.
- •Product name is spelled KerfMaster (capital K, capital M) rulingmixedreads as fact — RULING Aristide 2026-10-19 (correction, 'I had a typo on the name change. Is supposed to be KerfMaster'): the product name is written KerfMaster. Supersedes the same day's 'Kerfmaster' (a typo). Same reach as before: screens, paperwork, NC header comments; domains, service names, schema ids stay lower-case; delivered versions keep their spelling. Earlier ruling text, kept: RULING Aristide 2026-10-19 ('Kerfmaster', answering #10 of the UI streamline list: KerfMaster / kerfmaster / KERFMASTER): the product name is written Kerfmaster. Supersedes the 2026-08-19 'KERFMASTER' spelling for the name as shown; that ruling's reach (every page title, packet header, NC comment and report) stands. Internal identifiers keep 'cadmaster', and domains/URLs/service names keep lower-case kerfmaster. Open: the sweep itself awaits a go -- (a) screens, (b) delivered documents, (c) NC comments (changes every posted program's text; golden refs move); Jordan to hear it. Today the code mixes all three: on screen mostly 'kerfmaster', the Clear menu-bar brand 'KerfMaster', the reference print header 'KERFMASTER', NC comments '(kerfmaster ...)'. | BUILT 2026-10-19 (Aristide 'On the name, go on all 3'): the name now shows as Kerfmaster, 75 lines in 19 files. (a) Screens: page title, header brand, jobs home heading, Clear menu-bar brand (was KerfMaster), both tour welcomes, the split-out note; shop-tables editor page and open-questions page. (b) Paperwork: floor packets (part, nested sheet, part-list), delivery pages, customer sheet 'Prepared with Kerfmaster', approval pages (customer + shop), production-post page, comparison/vector/bridged/split boards, reference print header (was KERFMASTER), slug report header, material worksheet title. (c) NC: the program header comment (job label) on part, nest, part-list, common-line and quote-count posts, and the geometry-post comment; emit default part name. Lower-case letters were already in these comments, so no new character class reaches the control. Intended G-code delta: golden refs re-made (--make-refs); exactly 17 lines in 17 reference programs changed, each the header comment 'kerfmaster' -> 'Kerfmaster', nothing else (checked line by line). Identity gate green after. Not changed: domains/URLs, service and server names, schema id kerfmaster-tooling-doc/1, file names, code comments/docstrings, console logs, the marketing site (kerfmaster-site / kerfmaster-v2), old static approval pages under viewer/approval, already-delivered files (immutable versions keep the old spelling). Server-side text needs the engine restart to show on dev (prod restarts itself on deploy). Tests: verify_clear_tour 15/15, verify_clear_layout 49/49 (name checks updated), verify_tour title checks updated, test_commands_json 1178, packets rendered from stored nav209 data read 'Kerfmaster floor packet'. CLAUDE.md name line updated. | MARKETING SITE NAME SWEEP to KerfMaster, 2026-10-19 (Aristide: 'Marketing site changes too, and then restart'). kerfmaster-site (kerfmaster.com) and kerfmaster-v2, the same changes in both: 33 spots each in index.html, prep.html, logo.svg, app.js and the asset sources. Page titles, meta/og/twitter tags, the header and footer wordmark (was KERFMASTER), the logo lockup, the copyright lines, the body copy, the early-access mail subject, and the demo G-code comments (KerfMaster DEMO - RING/PLATE/LINK/GUSSET) all read KerfMaster. The wordmark's wide caps letter-spacing is tightened for mixed case (.22em -> .05em, mobile .16em -> .04em, logo 7 -> 2, share image .22em -> .05em, shop-sheet title .2em -> .05em). Regenerated with the site's own generators: og.png share image, the shop-sheet specimen (PDF + page images + thumbnail) and the floor-packet specimen (header was 'kerfmaster floor packet'); favicons re-rendered unchanged in design; copies went to v2. Kept as they were: domains and email addresses (kerfmaster.com, hello@), all-caps mono labels as a type style ('WHAT KERFMASTER POSTS', the 'KERFMASTER · KERFMASTER.COM' sheet footer, 'BACK TO KERFMASTER.COM'), code comments, BRIEF.md and designs/ drafts. Static files: live on dev at once through Caddy, no restart needed; kerfmaster.com on prod follows through the mirror deploy. Checked by screenshot of the v2 page (title 'KerfMaster — Reads what customers actually send.'), the share image and the shop-sheet thumbnail. No cadmaster/ change, identity gate n/a, F1 n/a. | MARKETING SITE CAPS, 2026-10-23 (Aristide 'change All Caps on Marketing site', answering the question left open by the 2026-10-19 sweep 98974242). The three all-caps labels were typed in capitals in the page source (no CSS text-transform), so the text itself changed; the mono letter-spaced label style is unchanged. index.html pane tag 'WHAT KERFMASTER POSTS' -> 'What KerfMaster posts'. prep.html '<- BACK TO KERFMASTER.COM' -> '<- Back to kerfmaster.com' (domain lower-case per the name ruling). The shop-sheet specimen footer on both pages 'KERFMASTER · KERFMASTER.COM' -> 'KerfMaster · kerfmaster.com'; the PDF, p1/p2 PNGs and thumbnail were regenerated with genshopsheet.js from a source unchanged since 98974242, and the pixel diff on page 1 is the footer text only. Left as is: the design drafts in kerfmaster-site/designs/a|b|c and code comments. The marketing site reaches prod through the mirror (~4 min). No cadmaster/ change; identity gate n/a.
- •Sales surface (UI brick 12) -- the stripped quote door wired to the existing two-tier quote stack record — UI brick 12 BUILT 2026-09-01: the SALES SURFACE -- the ruled stripped flow (Aristide 2026-08-19, sitting answer 2: upload, assign material, auto-nest -> material-use + time estimates -> pricing) live in the app, WIRED to the EXISTING quote stack (2026-08-21: quote.py FIRM tier, fast_estimate.py FAST tier, rollup.py Q29 per-shop policy, rates.json) -- nothing re-implemented. Sales door on the Jobs home = a stripped VIEW of the same tool (intake/heal/qc/quote tabs only; role locks await operator accounts -- stated on-screen, never silent); a sales upload marks the job origin:sales -- the SAME job object the operator opens ('it moves the start, it doesn't move the program'). POST /api/jobs/<id>/quote: AUTO runs a defaults Part review on an untooled part and a table-values nest at qty (an existing reviewed/nested state is priced AS IS -- operator overrides survive, nothing clobbered); writes quote.nc from the reviewed plan (O1 counting artifact, audited per the 2026-08-12 rule, NO program number consumed) -> quote.count() measured per part x qty_filled -> quote.price() -> rollup.compose(). A missing shop rate = a BLOCKED line naming its exact rates.json row, fillable in the drawer (POST /api/rates writes value + provenance decided/dated -- 'This is today's rate'); seed rows keep the composed figure honestly INDICATIVE with assumed_rows named; markup/margin stay per-shop policy knobs, never auto-picked. FAST tier beside the firm one, biased at-or-above (15d). Customer approval = the ruled explicit gate between sales intake and production finishing, recorded by typed name until the portal binds identity. Staleness: re-plan, re-nest or sketch re-compile marks the quote stale on-screen; the document STANDS (a quote is a record). TWO DEFECTS CAUGHT IN THE BUILD: (1) the client split the dotted rate row on '.' -- a material key carries a dot (MSO7,0.125), so a typed rate landed in a junk row; material-keyed sections now rejoin the key; (2) fast_estimate.measure() built its bbox from vertex points only -- a pure-circle part (two semicircle bulges) measured bbox height ZERO, zeroed the sheet estimate and the fast tier read BELOW the firm tier, the exact 15d failure: arc axis-extremes now ride into the bbox and sheets_high floors at 1 (verified fast $258.66 >= firm $257). Verified live over the public URL: app/verify_quote.js, Playwright, 14 checks (sales door, origin:sales, stripped tabs, blocked-rows worksheet, typed rate re-prices with provenance, INDICATIVE total, fast>=firm, approval record, stale mark, full station same job); rates.json restored after the verify -- throwaway figures never linger as decided shop values. Suites: test_sketch 21 + test_drag 13 + test_tooling_doc 21 + test_rules 11 + test_nc_warn 12 pass.
- •First-run tour, help from anywhere, bug report (UI brick 13) -- sitting answer 9 live record — UI brick 13 BUILT 2026-09-01: FIRST-RUN TOUR + HELP FROM ANYWHERE + BUG REPORT -- the ruled scope of sitting answer 9 (Aristide 2026-08-19) live, nothing more. (1) GUIDED TOUR: a detectable first run (per STATION via localStorage, like theme/units -- per-user first-LOGIN detection arrives with operator accounts, stated on the first card) auto-starts a 10-step tour of the whole gamut -- where things live (Jobs home / dropzone / sales door), how tools open (one-letter keys), how a panel tears off (the step spotlights the real grip: 'try it now, or Next' -- the overlay passes pointer events, only the card takes them, so try-it works LIVE under the tour). Skippable per step (Next never forces an action) or Skip all; Escape ends it; replays any time from the ? Help menu. Ruling 6 rides in it: the dot/colour vocabulary (colour AND glyph -- done/flagged/blocked/pending, warn-never-block, refusals in the engine's own words) is TAUGHT in the tour, once, with a live legend. Steps anchor real on-screen elements through a spotlight hole; an anchor that needs an open job (tabs, canvas, zoom) falls back to a centered card at the Jobs home rather than pointing at nothing. (2) HELP FROM ANYWHERE: a ? chip in the always-present topbar -- guided-tour replay, Manual (HONEST: not written yet; the tour and tooltips are today's teaching surface), Report a bug. (3) BUG REPORT FROM ANYWHERE, capturing what is on screen: canvas as PNG + app state (job, tab, stage statuses, units, viewport, UA) -> POST /api/bugreport -> one immutable directory per report under app/bugreports/. Routing to the partners' existing bug server AWAITS the details Aristide supplies, and the fuller auto-capture list is specified together later -- both ruled-pending, both stated on the form itself. DEFECT CAUGHT IN THE BUILD: the bug modal's display:flex outranked the UA's [hidden]{display:none} -- the INVISIBLE modal covered the screen and ate every click; [hidden] override added, named in the verify. Verified live over the public URL (app/verify_tour.js, Playwright, 20 checks, fresh context = fresh station): auto-start, per-station wording, non-blocking overlay, anchored spotlights (dropzone/tabs/grip), taught vocabulary, Skip all persistence across reload, honest Manual, replay+Escape, bug report verified ON DISK (report.json words+state, screen.png beside it). Suites: test_sketch 21 + test_drag 13 + test_tooling_doc 21 + test_rules 11 + test_nc_warn 12 pass. Tour != onboarding wizard: the wizard (shop-archetype profiling, common-line question) is its OWN pinned intent, untouched by this brick.
- •Multi-sheet programs -- one program per sheet (UI brick 14) record — UI brick 14 BUILT 2026-09-01: MULTI-SHEET PROGRAMS -- ONE PROGRAM PER SHEET, the recorded honest limit of bricks 8/9 closed. SERVER run_postnest loops EVERY sheet of the persisted nest layout: each sheet posts its own complete program (macro or part-by-part -- the two-shapes ruling unchanged, Manual Sort drops the macros on every sheet alike) with its OWN O-number from the one shop sequence (nest-name-prog-number: sheet 1 takes the operator's typed number; EVERY sheet keeps its number across re-posts AND re-nests -- the stage record carries onums[], _drop_postnest deletes every per-sheet artifact keeping all numbers). Each sheet's program is audited by nc_warn.audit_and_inject against ITS OWN placed geometry, callouts riding in its own file. Files: postnest.nc (sheet 1, the bricks-8/9 name -- old readers keep working) + postnest_s<k>.nc, each with its per-sheet tooling doc and slug report; postnest.json keeps sheet 1's program at top level and adds programs[] for all sheets. DELIVERY run_delivernest ships EVERY sheet: per-sheet O<num>.nc + census-checked CAM-safe sheet DXF (a FAIL on any sheet refuses the whole delivery) + tooling doc/slugs, ONE placement->part map for the whole job whose sheet+program columns name which program cuts each placement (the 2026-08-31 map ruling extended), packet with per-sheet program lines and usage measured over ALL sheets, per-sheet SVG previews, all in one zip/version/board build. UI: the Post tab renders every sheet's program (number/form/arrays/boundaries/warnings/downloads per sheet + the one-program-per-sheet note at the form); the Deliver tab lists every program in the version row and the chain. Verified live over the public URL (app/verify_multisheet.js, Playwright, 15 checks): a 30x40 sketch part at qty 5 spills 3+2 over two sheets -> two programs with distinct auto-sequence numbers, per-sheet audits (6 vs 4 executed boundaries), numbers kept across re-post AND re-nest->re-post, delivery with both NCs + both DXF censuses PASS + the sheet-aware part map + packet lines, and the single-sheet nav209 document still rendering (regression). Suites: test_sketch 21 + test_drag 13 + test_tooling_doc 21 + test_rules 11 + test_nc_warn 12 pass. Honest limit: customer sheet later brick (nest-level part sequence BUILT as brick 15, ui-nestseq-brick15).
- •Nest-level part sequence (UI brick 15) — serpentine default CONSUMABLE, numbered boxes, click-in-order at part scale record — BUILT (brick 15 of the 2026-09-01 build-them-all go): the ruled scope of pin nest-part-sequence (Jordan 2026-08-28 walkthrough step 3) live and CONSUMABLE. ENGINE nest_rules.serpentine_order(placements): the ruled default order -- bottom-left start, up column 1, down column 2 (Jordan's live 3x18 nest) -- columns grouped by X within tol; test_nestseq.py proves the worst consecutive hop is one column pitch where the all-up emission order pays the full column height (the rule's whole point). SERVER: GET/POST /api/jobs/<id>/nestseq -- the numbered-boxes state: engine serpentine per sheet + the operator's clicked order, ONE source (the UI never recomputes the serpentine). Saving a clicked order validates every [sheet, placement] entry (bad sheet / double click refused in the server's own words -- a plain request error, never a blocked stage) and drops the posted nest program per the stale-program rule, every sheet keeping its O-number; clearing restores the serpentine + macro eligibility the same way; a re-nest clears the sequence naturally (it lives ON the nest document -- new placements, new numbers). run_postnest consumes it: EITHER override (per-feature Manual Sort or nest-level clicks) drops the P9996/P9997 macros per the two-shapes ruling -- a part-by-part program runs its parts clicked-first-then-serpentine (default pure serpentine, source rule:serpentine); each program records part_order + part_order_source, macro mode honestly naming the control's own G65P9997 array loop as its order. The operator's order rides the same audit as every post (nc_warn.audit_and_inject vs placed geometry -- same shared rules, warnings ride into the NC; moves the ORDER, never a gate). UI Nest tab: numbered boxes on every placed part (numbers restart per sheet -- each sheet is its own program), 'Click parts in order...' mode with add/unpick canvas clicks and live renumbering, the macro cost notice at the FIRST DEPARTING CLICK (a serpentine-prefix order keeps the macros), Apply / Cancel / Back to serpentine; Post tab names the part order per program. DEFECT CAUGHT IN THE BUILD: a #tab=nest deep link part-fit the view and left the sheet off-canvas (openJob always fit the part) -- deep links onto sheet tabs now fitsheet exactly like clicking the tab. Verified live over the public URL (app/verify_nestseq.js, Playwright, 17 checks, fresh page per phase): serpentine on a 5+5+2 layout, macro default unchanged, departing click -> notice, clicked order persisted, macro -> part-by-part -> macro with O33307 kept throughout, part_order [5,0,1,2,3,4,9,8,7,6,10,11] exact, refusals verbatim, nav209 196-permutation + ms-verify multi-sheet regressions. Suites: test_sketch 21 + test_drag 13 + test_tooling_doc 21 + test_rules 11 + test_nc_warn 12 + test_nestseq 12 (new) pass. Open with Jordan (unchanged from the intent pin): 'Process in part-by-part mode' checkbox semantics, 'Process only one part of each type'.
- •User strings are TEXT on every rendered surface (systems-test fix block 1) record — Every user-typed string (part name first) is HTML-escaped at the render boundary on every generated page and every app innerHTML site; the census exemption is scoped to the marked name spans; the part-map CSV quotes a name that needs it.
- •App robustness: honest 404s, request validation at the door, atomic writes + locks (systems-test fix block 2) record — A malformed request is a plain 400 in honest words and touches no job document; a missing job is an honest 404; every JSON document writes atomically; a per-job lock and a progseq lock kill the measured races (duplicate O-numbers, deliver version-dir collision, torn reads); same-second job ids and ghost job dirs fixed.
- •Program-number override modes: use once (default) vs start new sequence; reserved/used = yellow, never block (systems-test fix block 3) record — Ruling B (Aristide, 2026-09-01) built: an operator program number is USED ONCE by default -- the shop sequence does not move, so a one-off O99999999999 can never poison it -- or restarts the sequence at that number when the operator picks NEW SEQUENCE. A reserved or apparently-used number posts anyway with a YELLOW warning that rides in the record, the stage counts and the NC file itself as a top-of-file callout; the auto-increment never silently re-issues a use-once number ahead of the sequence.
- •Stage-level yellow warns: machine envelope, sub-beam-comp features, units inferred + sketch units pinned to inches (systems-test fix block 4) record — Fix block 4 (2026-09-01, Jordan's 'Go'): three yellow warns the systems test found missing, all warn-never-block, riding the block-3 stage-warning path. (1) MACHINE ENVELOPE (Jordan 2026-08-24 'flag anything, part or nest, that exceeds the job's machine'): a part over the bed in either orientation warns at Part review and the callout rides in every posted NC. (2) SUB-BEAM-COMP FEATURES: a contour whose smallest dimension is at or under TWICE the row's beam compensation warns at review and in the file -- severity PROPOSED yellow, on Jordan's ratification list. (3) UNITS INFERRED: a headerless upload flags intake with 'units were INFERRED, not stated' in honest words; a file stating $INSUNITS stays clean. Plus SKETCH UNITS PINNED: sketch-born geometry is typed in inches by definition -- the pipeline pins it and a >200-inch sketch is no longer silently re-read as mm.
- •Brick 17: warning rows NAVIGATE — click a finding, land on its geometry, pulsed; wordmark/job-name return to Jobs home record — Built 2026-09-01 on Aristide's 'go' after his review of the Part-review yellows ('Quite frankly, I do not see them'): the click existed but gave invisible feedback — selectContour only highlighted the contour in place and swapped the drawer; the view never moved, rows didn't look clickable. Now every finding row that KNOWS its geometry (bnds -> contour, an '(X.. Y..)' in the shared message string -> the exact point) renders as navigable — pointer cursor, accent hover ring, a go-glyph suffix — and the click selects the contour AND frames the spot (zoom capped at 800% so a tiny hole never becomes a wall of pixels) with a ~1s expanding pulse ring at the exact point, so the operator's eye lands where the warning fired. One renderer (findrow()) across Part review findings+warnings, Cut plan findings, Post single-part findings + stage warnings, and the nested-sheet section's stage warnings. Stage-level warnings with no geometry (units-INFERRED, envelope) render flat — honestly not navigable; the nested program's expanded-boundary findings stay flat too (renumbered bnds don't map to part contours). Home navigation made visible: the kerfmaster wordmark and the job name both return to the Jobs screen (shared goHome(); underline on hover) — the path existed on the job name but nothing looked clickable. Warn-never-block untouched: navigation reads findings, changes nothing. Verified live over the public URL (app/verify_warnnav.js, Playwright, 10 checks, fresh page per phase): review click zoomed 103.3%->509.7% onto the clear-air hole and opened its contour record, cut plan + post navigate, units-INFERRED stays flat, wordmark + job-name land on Jobs home. UI-only change — no server/engine edits, python suites unaffected. This is brick A of the 2026-09-01 execution plan; next: B drag-handle UI, C consumable tab size, D propagation ALL/SINGLE, E part-list nest UI, F Heal/QC manual edit buttons.
- •Brick 18: the drag-handle — grab the pierce ring, drag along the contour, the engine judges every candidate LIVE, the drop applies the override record — Built 2026-09-01 on Aristide's 'B' (brick B of the ruled execution plan) — the UI gesture over the finished engine seam (pin drag-handle-validator): Jordan's Add-Toolpath ruling live, pierce + lead + start move as ONE handle. SERVER: POST /api/jobs/<id>/dragcheck — rules.check_drag against the assigned Part review's material x machine (refusal in honest words before a review exists), read-only by construction: no job lock, no stage record, nothing persisted; the override shaping is ONE function (_feats_from) shared with run_review so the live judge and the recorded judgment can never read an override differently, and an empty drag returns byte-identically the review's own findings (no drift, proven live). UI (Part review canvas): the pierce ring is grabbable (grab cursor on hover, 10px hit) — mousedown grabs (selects the contour), the handle rides the cursor SNAPPED to its contour's as-cut path, throttled (~7/s) dragcheck calls colour the handle red/yellow/green by what WOULD fire there with the counts written beside it ('2 yellow would fire here' / 'clear here'); mouseup applies start via the SAME override channel as pick-on-canvas (S.ov near+start -> review overrides= -> source:operator) and re-plans — one plan, one judgment; Escape cancels with nothing recorded; empty-canvas drag still pans. Warn never block throughout; the posted-NC re-read stays the final gate. Concentric-contour lesson recorded in the suite: two contours sharing a centroid tie under nearest-centroid binding — inherent to the binding, fixtures must offset. Proven: test_dragcheck.py NEW (15 controls: refusal, no-drift, outer-first candidate fires the shared red live before any NC, read-only byte-stability, malformed 400s) + app/verify_draghandle.js live over the public URL (Playwright real-mouse, 13 checks: grab cursor, live judgment mid-drag, drop -> operator override recorded -> cleared/restored, Escape cancels, endpoint persists nothing, pan regression) + test_robust 50 / test_warns 17 / test_sketch 21 / test_drag 13 / test_tooling_doc 21 / test_rules 11 all green after the _feats_from refactor. Honest limits: the handle forces the START point — lead length rides the existing typed slot (the drag does not stretch the lead); wirejoint-rides-the-drag is engine behavior at the new start, not a separately grabbable tab handle yet. Next per the plan: C consumable tab size, D propagation ALL/SINGLE, E part-list nest UI, F Heal/QC manual buttons. EXTENDED 2026-09-17 (Jordan's 'the click and drag ... would magnet to midpoints' catch, his 'Go'): the handle now magnets to corners / edge midpoints / quarter points (quadrants+45s on circles), Alt slides free -- full record on pin start-anchor-constraint. FIXED same day (Jordan on prod: 'still free-moving with no magnet'): the pull was measured from the RAW CURSOR, but the handle rides the contour by projection -- a hand drifting >10px off the edge (the natural sliding motion) never triggered a magnet; measured 0/16 landmarks caught at a 20px perpendicular offset. The pull now measures from the PROJECTED handle point (cursor kept as a secondary catch): 16/16 at the same offset. Landmark dots raised 2px->3px at 0.8 alpha so the operator can see them. Client-only. MAGNET DERIVATION REBUILT ON TRUE PRIMITIVES 2026-09-18 (Jordan's Magnets_9-18-1 screenshot -- red dots at the mid/quarter points, rad endpoints and rad 45s he expected, none of them magnets; Aristide 'go for fix'): the built derivation detected corners by a 25-degree turn test on the sampled as-cut poly, so a TANGENT corner rad -- which never turns sharply anywhere -- yielded no corners at all and the whole loop degraded to the 8-point smooth-circle fallback (the compass extremes near the rads were what read as 'endpoint' magnets; the pull at the lead-in was just the handle's own contour projection). The defined rule (corners/midpoints/quarters, quadrants+45s on circles) stood; the implementation missed it on tangent parts. NEW dragMagsSegs derives landmarks from the plan row's TRUE as-cut segs: units first -- collinear line fragments merge into one edge, contiguous pieces of the same arc merge into one sweep (across the cut-start wrap too, so a start point mid-edge invents no corner) -- then every unit endpoint is a corner landmark (TANGENT seams included: both ends of every rad magnet even at zero turn; tab-gap ends too), straight edges >= 0.08 get midpoint + quarters of the WHOLE merged edge, arcs get their 45-degree bearing marks inside the sweep plus the arc midpoint (a 90-degree rad's midpoint IS its 45; a rotated rad that misses every 45 bearing keeps its natural mark), full circles = quadrants + 45s unchanged. Reviews that predate plan segs keep the old poly turn test as fallback. The start-anchor corner pick rides the same function, so 'the bottom right corner' now also means a tangent seam. Client-only (app.js). Proven: 12-control node unit test on the derivation (rounded rect with a dirty-CAD split edge, full circle, off-45 rotated rad, cut-start-mid-edge wrap) + LIVE on dev 44558B_10's outer: 10 corners = all 8 true tangent-rad seams + the 2 tab-gap ends with the one artificial same-arc split correctly erased, 19 pts = mid/quarters per edge + a mark on every rad -- exactly Jordan's red-dot set; verify_snapdrag 10/10 + verify_draghandle 13/13 + verify_gc56 25/25 green.
- •Brick 19: tab size as a per-contour CONSUMABLE — typed width per feature, 0 = no tab (suppress-wirejoint), width moves, gates don't record — Built 2026-09-01 on Aristide's 'c' (brick C of the ruled execution plan): tab_width joined tooling_doc.CONSUMABLE in the same commit as the engine input, per the model rule — the walkthrough's typed tab size live end to end.
- •Brick 20: identical-feature propagation — mode ALL vs SINGLE FEATURE, the engine's own congruence record, one override channel record — Built 2026-09-01 on Aristide's 'd' (brick D of the ruled execution plan): Jordan's walkthrough ruling live — manipulate ONE feature and 'the rest all followed suit', vs SINGLE FEATURE; groups come from the engine's record, never re-derived by a lens.
- •Brick 21: the part-list nest UI — Qty / Rotate / Bridge / Filler live over the proven pack engine; 2026-09-20 preview cards -- thumbnail + full name + X x Y per row, selected part large on canvas, sheet moved to the Nest tab record — O97 (Jordan 2026-11-06 "Ok to fix"; built on dev, engine part needs a dev restart, NOT shipped): server._root_units_scale -- a root with no job.units (drawing sheet, heavy checks skipped) maps its original through the same to_inches reading _job_prims makes, not 1.0. Re-linked all 479 stored TL-1016 children (9 roots) with /tmp/o97/relink.py (backups /tmp/o97/bak): 479/479 now carry entities; Part list drawing on tl-1016-81-3-more-1793969452 = 60/60 rows linked, clicking a part line finds its row. Only the 9 TL roots on dev had the bug. Touches lineage for new splits (split door, Add to row / New part from selection parent frame, Source-mode original on a part); parts/heal/nest/G-code untouched. Identity gate green; test_lineage_mm_units 5/5 (new); original_lineage 26, split_door 17, split_side_views 15, split_loose_owner, split_bridge_rollback, sheet_window 30, sheet_draw 22, sheet_intake 98, pl_sheet_door all green. F1 not timed: the path only changes when a root has no units record. | 2026-11-06 JORDAN (fresh TL-1016 81/82/86/87 upload, list tl-1016-81-3-more-1793969452): (a) hovering the grey drawing lights a feature far from the cursor -- NOT reproduced headless (4/4 hovers hit the aimed line, also after collapsing a panel); suspect the stale-canvas glitch (pin nest-blue-band-glitch), asked Jordan which tab + whether resizing the window clears it. (b) selected row not lit on the drawing -- confirmed: all 479 fresh children have empty lineage.entities (same mm-sheet lineage-scale bug); fix awaits his go. | O96 BUILT + LIVE on dev 2026-11-05 ~23:10 UTC (Jordan 'Ok to build step 1'; client-only app.js/app.css, served from disk, no restart; NOT shipped): a listed row shows its part's FULL name as plain text that wraps (no part picker, no clipped tail); only a row just made by 'Add part' keeps a picker (S.plPickRows, a WeakSet -- never saved); the shared-prefix drawernote and the grey full-name line show only beside picker rows. MEASURED on Jordan's 238-row list (headless 1600x900, dev): drawer HTML 42 MB -> 0.42 MB; 11 drawer renders 38.6 s -> 0.69 s; page settled 27.7 s -> 1.6 s; 0 page errors. Tests: verify_pltabs 24/24, verify_plpick 17/17, verify_plreturn 10/10, verify_fork 24/24, verify_partlist 18/19 (check 3 'Nest landing asks for a method' fails -- Nest method prompt, not the row cards; not proven pre-existing), verify_plsel not run (needs a scratch engine on :8479). Identity gate green. F1 n/a (screen only). Ramifications: Part list + Geometry-tab row cards only; a saved row can no longer be swapped to another part from its card (Jordan: 'makes no sense'; '+ Add part' redesign is step 2). Rollback: /tmp/o96/app.js.pre + app.css.pre. FOUND 2026-11-05 (no row lights on the drawing, Jordan's point 2): a separate SERVER bug -- lineage. The four TL-1016 roots are mm drawing sheets with no stated scale whose heavy checks were skipped, so job.json carries no 'units'; _root_steps then states scale 1.0 while run_split cut the parts in inches (x0.03937), so _attribute_entities matched 0 of 1,089 entities and every child's lineage.entities is []. Proven on part 5: scale 1.0 -> 0 entities, scale 0.03937 -> 11. Not fixed (needs a go): stored lists stay unlinked until re-attributed. JORDAN 2026-11-05 ~22:30 UTC on the row select: 'I don't understand why we would have a dropdown with every part the shop has ever done in every part list ... makes no sense' -- direction: no per-row part dropdown; instead '+ Add part' at the bottom of the list (file-open style) to add parts that were not part of the upload. Build go not yet given (proposal sent). ALSO (Jordan, standing ask): the row display cuts off the long part numbers the shop uses and slows his workflow regularly -- work on it together when there is a chance. FOUND 2026-11-05 ~22:20 UTC (Jordan, TL-1016-81 + 3 more list on dev, 238 rows: opening it showed nothing for a long time, hover was slow, the stale-strip glitch appeared, no row lit on the drawing). MEASURED headless on dev (1600x900): the drawer HTML is 42 MB -- every row's name select carries one option per healed job on the WHOLE BOX (S.plJobs, 1,976 on dev), so 238 rows x 1,976 = ~470k options; each renderDrawer ~5.8 s and it runs ~10 times while the list opens (38.6 s total; page frozen in 3 stalls of 6-13 s, settled at ~28 s). Server side fine (pldrawing 0.07 s, 0.7 MB). Grows with rows x jobs on the box, so prod has it too at its own job count (not measured). Fix idea, NOT built (no go): a row's select holds only its own part until it is opened (fill the choices on focus), and/or offer only this list's parts. Client-only. Profile scripts /tmp/o96/pw/. Built 2026-09-01 on Aristide's 'E' (brick E of the ruled execution plan): the part-list part-by-part surface — rows reference healed jobs, the four ruled columns, pack through part_list_nest.pack. Synthetic fixtures; Jordan's real test job is the first real fixture and drops straight in. BACK-TO-PART-LIST CHIP 2026-09-14 (Jordan stuck mid-list: a row's 'open' button swapped the screen to the part's own job with no way back, and DRAFT rows -- client-side until 'Save list + pack sheets' -- died on the trip): KM.openPart now stashes the list job + draft rows + machine/material picks; a '← back to <list>' chip rides the topbar on the opened part, one click returns AND restores the unsaved draft; chip clears on return or going home. Client-only app.js, live immediately; verify_plreturn.js 11 live real-mouse checks (draft row survives the round trip, zero page errors) on the Lathrup list, read-only. ROW LABELS SHOW THE TAIL 2026-09-17 (Jordan's Detroit Wrecker catch -- six uploads sharing the 22-char filename head 'DWS-LH-2.5-LOGO-TREAD-' all clipped to the identical prefix in the 150px row select, so 'where are the files I uploaded?' -- they were all six rows, indistinguishable): the part-list rows now apply the operator-PDF _short_names rule client-side -- when listed rows share a substantial (>=8 char) filename prefix with every tail non-empty, option labels carrying that prefix display the tail, a drawernote states the stripped prefix, and the full name rides each row's tooltip; a row's job change re-renders so prefix and tooltip stay honest. Display only -- rows/pack/record unchanged. EXTENDED 2026-09-20 (Jordan's Part-List screenshot -- 'It is difficult for me as the operator, just now seeing these parts for the first time, to know which part is which'; his 'Go' on the numbered proposal): the Part list tab is a LIST, not a sheet -- every row is a preview CARD: an outline thumbnail of the actual part, the full name (shared-prefix tail rule kept, full name on the card when shortened), a read-only overall X x Y bounding size (as drawn; the tooltip states a quarter rotation lets the pack stand it up), and the same recorded inputs the packer consumes (qty, rotate step, bridge, filler). Clicking a card shows that part LARGE on the canvas, named and dimensioned -- the packed sheet stops drawing on this tab and lives on the Nest/Post/Deliver tabs where the programs post from. ONE geometry builder (plPathFromGeo) feeds the nest canvas, the thumbnails and the preview; the pack's own geometry fetch seeds the row cache so a packed list previews instantly. Presentation and navigation only: rows keep their data-pl hooks, the saved list and packed nests are untouched. EXTENDED 2026-09-22 (band select -- pin global-controls chunk 2): the card list joins the global shift-drag gesture -- band selects cards via a document-level overlay, small shift-drag toggles one card, Delete trims the banded rows from the DRAFT (Save list + pack sheets stays the record), Escape clears, plain click collapses; controls inside cards keep their own clicks. Full record on pin global-controls; app/verify_cardband.js 13/13. ROW NAMES NEVER LIE 2026-09-30 (Jordan's File_Name_Mixup catch -- his 32-file ROUSH upload healed and listed correctly server-side, yet every row's name select read 'BNM7865...' from the PREVIOUS large upload; sizes/thumbnails were right, only the names lied): cause was client-side, twofold -- (1) S.plJobs (the healed-jobs cache feeding the row selects and the add-all-parts family picker) was fetched once per browser session and never refreshed on a job switch, so a list opened after a fresh upload rendered against a cache that predated its own parts; (2) an HTML select whose value matches no option silently displays the FIRST option, so every row wore the alphabetical stranger's name instead of failing honestly. Fix, both halves: openJob nulls S.plJobs + S.plUAll (the drawer refetches, a fresh job never renders against a stale list), and the row select prepends the row's OWN recorded name (server writes name into every saved row) whenever its job is missing from the options -- covering the stale cache AND the legitimate case of a listed part whose heal is not done/flagged; the canvas preview label and the sibling-strip stash take the same r.name fallback. Proven: defect REPRODUCED on pre-fix code (3/3 rows wore an injected ghost name), fix shows 0/3 with names preserved; verify_pltabs 24/24 + verify_plpick 17/17; client-only, no restart; zero dev O-numbers. | ANSWER 2026-10-12 (Jordan): the 9-20 preview cards are functionally good as is; right reserved to revisit and clean it up later. Closed for now.
- •Brick 22: Heal/QC manual edit buttons — the old CAM Basic-tab block as the operator's per-case override record — Built 2026-09-01 on Aristide's 'F' (brick F of the ruled execution plan): the Basic-tab edit/QC block live — five read-only mark lenses + Join / Fit Arc / Remove Small Segments as recorded, replayed operator edits in a third dockable panel. Jordan's ruling applied: automation heals first, every button has a home. NO-OP GUARD 2026-09-06 (the 44558B_10 layout drop): a healedits save that leaves the list UNCHANGED -- Clear all with nothing recorded, or an identical re-save -- is now RECORD-ONLY (noop:true, honest note, nothing re-runs, no stage drops; the units-confirm precedent: never drop stages over a no-op). A changed list still re-heals and the standing stale rule still fires. The real incident: an empty Clear all re-ran the pipeline and dropped Jordan's hand-edited 66-placement nest minutes after delivery; restored byte-exact from the auto-versioned record (review/nest/cutplan/postnest + job stages merged, v3 delivery kept). Proven: test_healedit_noop.py 8 NEW server controls; healedit 29 / nestdeliver_rot 14 / nestedit 38 / units_confirm 27 / sketch 21 green. EXTENDED 2026-09-10 (Jordan's go): DRAG-TO-SNAP -- engine op snap_end drags the loose end nearest the grab along its OWN carrier (a line extends/trims on its own direction, an arc end slides on its own circle -- center+radius rigid, the sketcher's rule); the drop lands ON the carrier, off-curve misses reported in the note; reach-gated by point like delete (replay skips in the same words when the end left). UI: 'Drag end to point' armed mode -- loose ends ring as grabbable, the handle rides its carrier under the cursor, the aim SNAPS to corners/points of the gray original base layer (accent ring), Escape cancels, the drop records through the standing /healedits door. Proven: test_healedit 60->70 + verify_snapdrag.js 10 live real-mouse checks (snap to (0,0) exact, QC closes, persistence, refusals verbatim, Escape). EXTENDED 2026-09-15 (Jordan's standing go, Aristide 'go ahead and start': BAND SELECT ON THE GEOMETRY TAB -- the committed next build built): Illustrator-style rubber band over the healed layer. ENGINE op delete_seg = the per-segment delete (takes the ONE segment nearest the point, never the chain -- delete stays the chain op, the two distinct on purpose); same reach gate/replay-skip words as delete, removed ink rides the report row (fidelity exemption), last-geometry refuses ('nothing would be left to cut'). UI: 'Band select' armed mode in the Heal/QC panel -- drag a box, segments select by sampled on-curve points + anchor points (endpoints) inside the rect (selection colored --sel, anchors as squares: filled = banded point, hollow = selected segment's ends); Shift-band ADDS; a tiny drag = click clears; Escape clears first, disarms second; Delete/Backspace removes every selected segment in ONE save -- one delete_seg row per segment (near = a point ON its own segment), per-row removable in the recorded list, one re-heal, standing stale rule; a GRABBED LOOSE END rides the SAME drag-to-snap with no mode switch (the marked rings are shared). Selection is a picking aid only -- the engine re-finds every segment by point behind its own reach gate. Scene-guarded like armed clicks (never over a nest scene). TDZ lesson re-hit and fixed (top-level KM.x= before KM initializes -- plain function now, the plhRenderBar precedent). Proven: test_healedit 70->78 + verify_bandselgeo.js 13 NEW live real-mouse checks (band 2+4 anchors, shift-add, escape ladder, grab-rides-snap, one-gesture delete, delete-everything refusal verbatim, fresh-page replay, per-row restore); healadd 13 / healedit_noop 8 / sketch 21 / isoedit 18 / isoserver 17 / split_door 13 / dragcheck 15 green; verify_snapdrag 10 re-run green.
- •Brick 23: the onboarding wizard + shop profile (GET/POST /api/shop) record — Built 2026-09-01 on Aristide's 'go for next build': the ruled first half of the common-line item — the shop-setup wizard live, SHOP-level shop.json shared by every station, the two ruled questions (archetype, common-line yes/no), seed-never-bind, 11 live checks. TABLE REFUSALS POINT HOME 2026-09-10 (Jordan's ruling on the table-less flow -- 'I would just like to see a simple message saying "for this to work we need more information from you" and then a link back to the wizard'): every stage BLOCKED by a TABLE gap (tables.TableError incl. MaterialUnknown/MaterialIncomplete/RateMissing, plus the Rev2 no-row/blank-cell KeyErrors -- marked needs_setup on the stage record by the one server catch) now leads with exactly that plain sentence + an 'Open Shop setup...' link, on every surface through ONE renderer (blockBanner -- 12 call sites folded); the engine's exact words stay beneath, never hidden -- they name the row and column to fill. The wizard gained an honest Machines & materials section: defining them in-app is a coming build, today tables load from the shop workbook and quote rates fill on the Quote drawer; geometry work (heal/edits/clean-DXF delivery) needs no tables at all. Proven live: app/verify_setupask.js 8 Playwright checks (scratch sketch -> Stainless row without materials.json backing -> blocked + needs_setup + banner wording verbatim + link opens the wizard + honest note; fixtures removed). HUMAN SPEAK 2026-09-10 (Jordan: 'use human speak, not computer speak... "Material Not Defined" "Material Thickness Not Entered"'): a needs_setup refusal now LEADS with plain-words heads -- Material Not Defined / Material Value Not Entered / Machine Settings Not Entered / Shop Rate Not Entered -- with the missing thing named in a human sentence (client humanTableWords over the engine strings, presentation only); the exact table words stay one click away in a collapsed 'exact table words' row, never leading. verify_setupask.js 8->10 checks. TOAST JOINS THE TREATMENT 2026-09-16 (Jordan's CAMP 0.040 pack refusal toast showed the raw MaterialUnknown words -- the part-list pack-refused toast bypassed humanTableWords while the blocked-tab banner translated): the toast now leads with the same human head/sentence and points at the Nest tab banner for the exact table words. Client-only, live on refresh.
- •Brick 24: common-line cutting — the shared-edge web design, engine + Nest-tab disclosure block record — Built 2026-09-01 on Aristide's 'go': common-line cutting's first working form — common_line.py answers the shared-edge safety design the pin left open (perimeter-last, monotone band sweep, no-comp shared edges), plans the welded-band layout + ordered cut plan with the trade in numbers, and the ruled default-disclosure block is live on the Nest tab reading the shop profile. Posting the shared-edge program is the next brick.
- •Brick 25: posting the shared-edge web — the common-line program, one per sheet record — Built 2026-09-02 on Aristide's 'go': the recorded brick-24 limit closed — the common-line plan posts as real Fanuc macro-B programs, one per sheet. cl_post.py: every closed cut (holes, band perimeters) posted by write_gcode_macrob itself, one welded band per call (outer-last IS perimeter-last — zero drift on leads/comp/slug tabs/chording); shared edges written as open NO-COMP cuts, pierce and lead in the inter-band channel, overcut past the far perimeter; its own re-read audit judges the stitched file sheet-wide, callouts ride in the NC.
- •Brick 26: Traverse Routing — rapids detour around held slugs record — Built 2026-09-02 on Aristide's 'go': the recorded unbuilt rapid-routing lever (the old CAM's Traverse Routing) — approach rapids detour around pieces already cut and still at bed level; a crossing no detour can clear stays straight and counted, never silent.
- •Brick 27: the Dimension surface — engine-measured dimensions on the canvas record — Built 2026-09-02 on Aristide's '1st one': the old-cam-dimension-tab-menu intent's first working form — a fourth dockable Dimension panel; H/V/aligned/radius/diameter/angular picks snapped and MEASURED by the engine (a readout, never an input), Auto dimension, live re-measure on every geometry edit, stale in the engine's words. DRAG-TO-PLACE 2026-09-09 (Jordan 'do this'): grab the value label, drop it where you want it -- presentation only, the value keeps re-measuring. ARMED-GRAB FIX 2026-09-11 (Aristide: after two armed picks placed the dim, 'shouldn't it automatically flip so I can now move the dimension?' -- Escape was needed first): the kind stays armed on purpose (place several dims in a row without re-clicking the button), but the label grab now WINS over the pick whenever no pick is mid-flight -- drag right after the dim lands, no Escape; a pick sequence in progress keeps every click a pick, and the armed crosshair no longer clears on mouse move. Client-only, live immediately; verify_dimarm.js 12 live real-mouse checks. AIM FEEDBACK 2026-09-11 (Aristide: hovering should 'magnetically attach' and leave a 'trail'; 'pick 1 of 2' in the button 'took me a few days to discover'): with a kind armed the canvas shows the live aim -- a magnet marker at the point the pick will snap to (client mirror of the engine's dims.snap: vertex / arc center within the 0.25 reach, else edge foot -- a picking aid only, the raw click still posts and the engine stays the authority), a hint chip riding the cursor ('pick k of n -- corner / circle center / on edge'; honest no-geometry-in-reach words in warn color when the click would refuse), markers on picks already taken and a dashed rubber-band trail from them to the aim; suppressed over a grabbable label, cleared on pan / Escape / disarm / leaving the canvas. Client-only, live immediately; verify_dimaim.js 12 live real-mouse checks + dimarm 12 / dimdrag 10 re-run green.
- •Brick 28: toolpath-after-nest for part lists — lead/pierce envelopes reserved in the pack record — Built 2026-09-02 on Aristide's 'go with what you have': the brick-21 honest limit closed — part-by-part tools AFTER the nest, and the pack reserves the room.
- •Brick 29: posting the part-list sheet program — one program per sheet, part-by-part by construction record — Built 2026-09-02 on Aristide's 'Go': the remaining brick-21 honest limit closed — the packed part list posts as real Fanuc macro-B programs, one per sheet, part-by-part by construction (several unique shapes, no macros); per-part overrides join part-list plans; plans_match is the stale gate. (Form superseded 2026-09-17: main + M98 sub callouts -- pin pl-post-subcall.)
- •Part-list programs post as MAIN + SUB-PROGRAM CALLOUTS (G52 + M98P, one sub per distinct part x orientation) -- and MACRO RUNS where the layout earns them (P9997 arrays, style auto/partbypart) record — Built 2026-09-17 on Jordan's GO (his O33342 catch: 'Where is the main program as we've discussed?'): the 2026-09-06 G52 sub-call ruling lands on the part-list surface -- edit one sub and every copy follows. EXTENDED 2026-09-19 (Jordan 'Go' on the standing macro-run offer): where the placed layout forms uniform runs, style auto posts the true-nest macro form -- one G172 + G65P9997 per run, a lone placement as K1Q1, never a mixed main. EXTENDED 2026-09-20 (Jordan's 26342 catch: 'we should put these values as what they would have been if there were repeated parts in X or Y, rather than leaving them at 0 ... they can easily call that up in the gcode without having to do math on the fly'; his refinement: an overridden clearance must show in the words; his 'Go if this makes sense'): SPARE PITCH WORDS on single-count axes -- every K1/Q1 axis posts the pitch a repeated run WOULD use, so a make-up part in the scrap is one K or Q edit at the control.
- •Part-list subs post from their toolpath's lower-left -- every X/Y position positive (Jordan 2026-10-01, ruling + record) record — BUILT (Jordan 2026-10-01, his O33458 catch on the electrical-cabinet kit, screenshot gcode_10-1-1: 'Why do we have negative values for X and Y in both the main and sub programs? This will not work at the laser'; his answer 4: the TOOLPATH corner -- 'we want all of the values to be positive'; 'Arc centers don't matter here. Go.'). CAUSE (mine): each part-list sub posted in the part's DRAWING frame and a rotated copy turned about the drawing's 0,0 (the frozen-lead form), so a part drawn away from 0,0 or turned 270 posted negative sub positions (to Y-24.17) and negative G52 shifts (X-8.7288, X-10.9689); executed positions were right, the numbers unusable at the control. FIX in pl_post.write_sheet_subcall: every sub body is TRANSLATED so the lower-left of everything the head touches -- rapid targets, pierces, leads and each G2/G3's TRUE extremes (pl_post.body_extent reads them off the posted text, cardinal points inside the sweep, full circle all four) -- sits at X0Y0 (floored to whole 0.0001in counts so nothing goes below 0); the main's G52 (sub-call form) or G172 (macro form) carries that corner's sheet position, integer-count arithmetic both sides so executed positions are IDENTICAL; I/J stay signed (arc-centre offsets, never positions). GUARD: pl_post.negative_positions over the whole program -- any negative X/Y position on a move, G52 or G172 refuses the post in honest words ('a part's toolpath reaches past the sheet's 0,0 edge'), nothing written. Sections + the plpost record carry origin (= the shift the program posts) beside placed (the pack's placement); the macro drawer row names the G172 the file carries. SCOPE: part-list sheet programs only. Single-part posts and true-nest programs still pierce outer leads below the part (e.g. Y-0.15 under G52X.2Y.2 -- on the sheet at +0.05) -- measured on dev, ANSWERED NO (Jordan 2026-10-01, his answer 6): 'No, that is consistent with the other Fanuc style programs that we regularly work with. As long as it's familiar to the laser operators, we are good.' -- single-part and true-nest posts keep their part-frame lead positions; the all-positive rule is a part-list sub-program rule, born where the sub frame was the drawing's arbitrary 0,0. Familiar-to-the-operator is the governing test. PROVEN: NEW test_pl_origin.py 13 (arc-extreme reads, count shift, off-origin part at 0 and 270 -> zero negatives, each sub min at X0Y0 within one count, expanded program cuts on the placed parts, off-sheet refuses, G172 form, subs byte-identical across forms); old-vs-new in-process re-posts on copies of 6 real dev part-list jobs (his O33458 kit 196 negative lines -> 0; CAMP#4 macro 995 -> 0; 44556B macro 101 -> 0; three verify kits) -- EXPANDED executed moves identical move-for-move and audits identical on every one; test_pl_subcall 18 + test_pl_macro 28 (two expectation updates: G52 values / rotated sub now origin-shifted) + pl_post 26, pl_seq 27, pl_sync 25, pl_deliver 28 green. Old delivered programs stand (immutable); a re-post picks up the new form. Zero dev O-numbers (proofs ran on temp copies).
- •Brick 30: the part-list delivery — versioned set, floor packet, placement→part map, customer sheet record — Built 2026-09-02 on Aristide's 'next natural brick': the posted part-list sheet programs become a versioned immutable delivery set — per-sheet audited NC + census-checked CAM-safe sheet DXF, one placement→part-number map naming each placement's OWN part, floor packet with asked-beside-filled per row, customer sheet under every brick-16 split rule (multi-name exemption), zip + numbered board build; append-only chain, supersede as metadata, replanned marker on list edit/re-pack. EXTENDED 2026-09-17 (Jordan's 'I changed the program number to 33385... and it reverted to 33342' -- his re-post DID take (plpost.nc = O33385, operator source recorded) but he downloaded from delivered v1, which immutably carries the OLD O33342 program; nothing on the Deliver tab said a newer post existed): the part-list Deliver tab now shows a warning note whenever the posted program is NEWER than the latest delivered version (stage plpost.date vs the version's own date; both O-number sets named) -- 'the vN downloads below are the OLD post, click Deliver again to ship the new program'. Client-only (app.js + one .drawernote.stale css rule); delivered versions stay immutable, the notice is presentation. || DELIVERED VERDICT IN PLAIN WORDS 2026-09-22 (Jordan: the Deliver tab's yellow mark had no readable reason -- '"pldeliver: flagged" -- I don't understand what that means and I don't expect the customers to either'; his Go): the part-list Deliver drawer now LEADS with the same DELIVERED banner the single-part and nested-sheet surfaces carry (vN -- N RED / M YELLOW IN THE FILE, CLEAN when clean) plus the plain reason under it: the warnings ride in the delivered file for the laser operator, the findings are listed on the Tooling and Post tabs where each can be green-flagged, a re-post + new delivery ships a clean count. The flagged status itself is honest and unchanged -- it is baked at delivery time from the shipped file's own warning counts, never from later edits (those show as the predates note + the stale re-post notice). Client-only; verify_pldeliver 14/14.
- •Brick 31: nest-level click-in-order for part lists — the numbered boxes on the part-by-part kind record — Built 2026-09-02 on Aristide's 'Go': the brick-15 numbered-boxes/click-in-order model lands on the part-list Nest canvas — clicked placements cut first, the pack's fill order continues after; part-by-part by construction, so the order changes the order, never the program form.
- •Jobs home filing: customer = the master file, workflow = derived queues ruling — 2026-11-06 JORDAN: O98 "Much better"; asked for a Cancel on opening, then chose to leave it alone for now (faster on a local PC) -- not built, parked. | O98 (Jordan 2026-11-06 "Ok to build"; LIVE on dev, client-only, NOT shipped): homeOpen() -- a Jobs Home click (job card or floor card Open job) marks the card "Opening..." + wait cursor at once; other Jobs Home clicks ignored until the open finishes; a failed open puts the card back + toast. Other openJob callers untouched. Checked headless on dev: tag shows within 60 ms, a second card click during the open is ignored (the clicked job opens), bad id resets card/cursor, 0 page errors. Identity gate green; F1 n/a (screen only). Rollback /tmp/o97/app.js.pre98 + app.css.pre98. | 2026-11-06 JORDAN: "still nothing indicating that a job is loading from Jobs Home" (also 11-05: clicked a job, saw nothing, started the next upload). Found: openJob runs ~15 fetches one after another with no sign on screen; Jobs Home stays up until done. Measured headless on dev: TL 238-row list 1.4 s, a single part 0.1 s (local, warm; slower over the internet and while an upload runs). Proposed (no go yet): the clicked card shows "Opening..." + wait cursor at once, a second click is ignored while it opens. Jordan 2026-11-06: canvas fix (O83b) looks good. | Jordan + Aristide 2026-09-02: the program number severs the customer link at archive time — so the CUSTOMER is the master folder, workflow queues populate themselves, and the order reference is free text (a PO or 'Jim said run.').
- •Brick 32: customer registry + folders + search — filing brick A record — Built 2026-09-02 on Jordan's go: customers.json registry, POST /api/jobs/<id>/file (customer + free-text order ref), Jobs home grouped into collapsible customer folders with search over names, customers, order refs and every program number.
- •Brick 33: drawing-sheet intake -- extract the 1:1 flat pattern in the app record — Built 2026-09-02 on Jordan's go ('Go ahead for that brick 1:4'): a customer DXF that is a scaled DRAWING SHEET (title block, dims, views at 1:4/1:5/...) is detected at intake and the operator extracts the 1:1 flat by stating the print's flat size + scale -- the Lathrup preprocessing, generalized into the app. INTERIOR ABSORPTION 2026-10-06 (Jordan's 79602 catch -- his 17x17 plate's four 1.000 holes vanished from the extraction; his 'Go on 1'): a detached entity cluster WHOLLY INSIDE the matched view's bbox is ABSORBED into the flat before the annotation split -- the proximity clustering (CLUSTER_GAP) only sees touching ink, so a bare hole circle drawn clear of the outline formed its own cluster and was silently dropped. Strict containment, never padded (a cluster poking past the view is another view, not a feature); absorbed ink rides the SAME annotation split (79602's center-mark crosses drop recorded); every absorption lands in report.absorbed_views (census + scaled size) and the Intake note states it in plain words; a sheet with no contained clusters is byte-identical by construction. PROVEN: the real 79602 (NEW committed Inventor-class fixture testdata/79602-INVENTOR-SHEET.dxf, per the one-fixture-per-CAD-export-class prevention rule) extracts 17.0000 x 17.0000 with all four 1.000 holes on the print's 14.000 centers, heals fidelity 0.0 / 0 jogs / QC clean through the live doors; 29/29 Lathrup sheets byte-identical old-vs-new; corpus sweep 901 sources / 65 detected sheets all identical, absorption fired on no existing extraction; test_sheet_intake 54 -> 66; verify_dwgtray 20/20; identity gate green; F1 8.35/7.64s = baseline, no cost. 79602's zero-click stand-down unchanged (no stated scale -- the dimension-derived scale lever is its own build). FLAGGED, unbuilt: split_annotations reads linetype 'Continuous' as non-solid (the 'SOLID'-substring test) -- right result on 79602's center marks by luck, the SLD-Solid lesson shape; the honest fix is the LTYPE dash-declaration rule, its own chunk awaiting a go. LINETYPE CHUNK HELD (Jordan, 2026-10-06): 'don't do anything with this yet ... we need to test this' -- concern: an LTYPE-declaration rule may rely on GOOD CAD; garbage customer files with no/odd linetype names and tables must be handled. The 'SOLID'-substring test stands unchanged; WIP parked in git stash 'linetype-chunk WIP'. Proposed next (awaiting go): a measurement-only garbage-file test of today's rule vs the proposal. Nothing built.
- •Zero-click sheet intake -- ruled, chunk 1 (auto-extract at upload) BUILT rulingmixed — RULED 2026-10-05 (Jordan '1.-5. Yes'; Aristide: expectations not aligned with delivery, he is NOT wrong) + CHUNK 1 BUILT same day (Aristide 'Go, but if this wasn't it, be ready to roll back to this point' -- rollback tag pre-zeroclick-intake at bfbbe578): a multi-view drawing sheet is handled with ZERO operator clicks -- views dropped, scale corrected from the sheet's OWN stated scale note, flat ready to toolpath, operator asked only when the print states nothing, best read + red flag never a silent stop. Supersedes brick 33's confirm-first default and the Sep-19 one-road unextracted-sheet carve-out. Chunk 1 = auto-extract at the upload seam, live on dev: sheet_intake.auto_plan/auto_extract (scale from exactly one distinct stated note, else honest stand-down; flat view by DIMENSION PROOF -- each DIMENSION's defpoints voting for the smallest containing cluster, most votes >=2 strictly ahead = proven; best-read fallback stated and flagged), riding the SAME extract() road; server upload seam auto-extracts detected sheets (extracted.auto=true, refusal recorded never a failed upload), intake words state the zero-click handling in plain words, best-read lands a warning. Client needed ZERO change -- gates key on status 'detected', so an auto-extracted sheet rides the one road to a part-list row by construction. PROVEN: 29/29 real Lathrup/F1 sheets auto-extract ENTITY-IDENTICAL to the shipped flats (all dimension-proven, 4 stated scales 1:4/1:5/1:6/1:8); 389-source corpus sweep -- auto fires ONLY on this class, 97 detected sheets stand down honestly, zero best-reads, zero crashes (NEW honest refusal where annotation split leaves no geometry -- was a min() crash on real CP-8005 files); test_sheet_intake 34 -> 54; verify_dwgtray 20/20; identity gate green; F1 8.21/7.54 -> 8.24/7.55s no cost; browser end-to-end raw 2.6MB sheet -> part-list landing at 1:1. HONEST LIMIT: 79602 itself (Inventor IDW class) carries its scale only as an unrendered field expression -- no scale text in the DXF, so it stands down and stays ask-the-operator until its own lever. Chunks 2-3 stay intent. DIMENSION-DERIVED SCALE 2026-10-06 (Jordan 'Go' + Aristide 'Go', Jordan's answer 1 -- 'I thought we could calculate this from dimensions also?'): the honest limit above CLOSED. Measured finding: both CAD classes declare the drawing scale on their dimensions as DIMLFAC (group 144) -- SolidWorks/Lathrup in the DIMSTYLE table (4.0 on 1:4 sheets), Inventor/79602 as a per-dimension ACAD DSTYLE xdata override (0.25, measurement 17 on a 68 drawn span); displayed = drawn span x DIMLFAC, so DIMLFAC IS the scale. sheet_intake.dim_scale reads it per linear dimension (override > style > none; angular/ordinate, typed text overrides, undeclared or non-positive factors and a stored measurement matching neither reading give NO evidence -- never assumed 1); auto_plan picks the view first then _decide_scale: one note + agreeing or silent dims = the note governs ('confirmed by k of K dimensions'); note vs dims disagree = refuse naming both; several notes = dims pick one; no note + 2+ flat-view dims all declaring one factor = DERIVED ('4:1 (drawn at 4x full size) derived from 3 of 3 dimensions on the flat view'); anything else = honest refusal; the scale is never a guess. report.auto carries scale_how + dim_scale; the Intake note states it. PROVEN: 79602 now ZERO-CLICK at 0.25 -> 17x17 with all four holes, identical to the manual extract; 29/29 Lathrup sheets every dimension agrees with its stated note, zero conflicts, same scales; corpus sweep 2548 DXFs / 131 detected sheets -- 55 identical, 74 refusal-wording only, exactly 2 changed (79602 intended; the 3A76 customer DWG, drawn full size, now derives 1:1 and extracts 2.7179 x 3.8753, consistent with the 3A76 DWG precedent); zero crashes; test_sheet_intake 66 -> 81; verify_dwgtray 20/20 (check 9 updated to the intended 3A76 auto-extract; one check-15 miss on a reused scratch instance, green on re-run); identity gate GREEN (2.4s, byte-identical); F1 8.35/7.64 -> 8.32/7.62 + 8.31/7.61s, no cost. Ordinate dims excluded (conservative). Zero dev O-numbers; progseq untouched.: 79602-class sheets (no scale note) now derive their scale from their own dimensions and extract zero-click. | OPEN 2026-10-08 (question, HELD -- Jordan 'don't build yet, keep separate'): CHECK#4RAW REV D (Ecker, sha 777c6228) stood down 'no scale stated' though all 8 linear dims STORE a measurement (group 42) equal to the drawn span with no DIMLFAC declared -- a real 1:1 witness that dim_scale today counts as 'no declared factor' (the 10-06 build read declared factors only; Jordan recalled the agreed rule as 'check the real dimensions against the stated ones'). Proposed: stored measurement == drawn span on 2+ flat-view dims, none disagreeing = 1:1 derived, said so; still never a guess. | CHUNK B BUILT, MEASURED, HELD 2026-10-08 (question; Jordan '2. no ... confirm the dimensions ... go on B' -- the title block's 'FULL' word is NOT trusted as a scale, confirmed dimensions are): NEW sheet_intake.dim_measured + _decide_scale last witness -- where nothing is stated or declared, 2+ flat-view linear dims whose stored value (group 42) equals their drawn span and none off = 1:1, any off = ask. Sweep of 132 distinct sheets on the box: ONLY CHECK#4RAW changes (refused -> 1:1, 5 of 6 dims). But the extraction it unlocks is WRONG: 18 of the file's arcs/circles carry a mirrored extrusion (230=-1) and sheet_intake (clusters/_epts/_ent_geom) ignores OCS, so the part body reads at negated x and the zero-click flat is only the 2.912 x 2.499 arm (QC 2 dangling). Pre-existing extractor defect, NOT B's: a manually typed 1:1 extract takes the same road and gets the same arm; dxf_io and sheet_draw already honour OCS. One other sheet on the box carries mirrored geometry (1448 entities, refuses today). B's code parked in git stash ('chunk B ... HELD'), F1 baseline 8.09/8.13s measured, nothing committed. Proposed order: OCS fix in the sheet extractor first (its own chunk, own sweep), then B. | 2026-10-08 OCS FIX CHANGES B's CASE: with sheet_intake reading mirrored arcs right (pin dxf-ocs-mirrored-entities), CHECK#4RAW is not a drawing sheet at all -- it uploads as its whole 1:1 part with zero clicks, no scale question. Chunk B (stash@{0}) changed ONLY that file in its sweep, so on today's box B would change nothing; whether it still ships is Jordan's call (question). | OLD-STYLE POLYLINE OUTLINES SEEN BY THE SHEET DETECTOR 2026-10-11 (record; Jordan's 78017D04A, his 'Go'): an AutoCAD Mechanical 1:1 plate (19.25 x 3.1875, 8 holes, 4 dims) wrote its outline as an old-style POLYLINE+VERTEX+SEQEND; sheet_intake read only LINE/ARC/CIRCLE/LWPOLYLINE, so detect() saw 8 hole 'views' + dims and called it a drawing sheet -> no scale -> left off the list. FIX at the one load seam: NEW _fold_heavy_polylines folds each 2D POLYLINE into an LWPOLYLINE-shaped entity (layer/colour/linetype/closed/extrusion/bulges kept, spline-frame vertices flag 16 skipped, 3D/mesh flags 8/16/64 left as read) -- detect, clusters, extract and sheet_ink all see it. Measured first: 418 unique dev sources, 224 use old-style polylines (179 our own split children), only 78017D04A also carries dimensions; 155 modern-CAD files, it is the only old-style one. SWEEP 427 files old-vs-new: ONE sheet flip (78017D04A True -> False), all 31 successful auto-extractions byte-identical, zero extraction outcome changes; detail-only diffs = cluster lists now include old-style outlines, refusal wording on non-sheets (never called there), source-mode sheet ink now draws them. test_sheet_intake 89 -> 98 (rule-as-control HP 1-9, old code fails), NEW fixture testdata/78017D04A-ACADMECH-HEAVYPOLY.dxf (AutoCAD Mechanical class). Honest limit: SPLINE/ELLIPSE outlines are still invisible to the detector (18 dev files carry them, none with dims) -- offered, unbuilt. FIX B BUILT 2026-10-12 (record, Jordan 'Go on B' after his CP-6005-03/-04 catch -- each sheet's flat view carries SPLINEs, zero-click extraction honestly stood down, then the one-road split cut the SHEET into parts and the border landed as 'part 1' at 30.90 x 23.40): a drawing sheet whose flat view was NOT extracted never splits and never becomes a row. SERVER: NEW _sheet_split_block(jdir, prims) at the top of run_split refuses in plain words ('drawing sheet, flat view NOT extracted: <the extractor's own reason> -- ... nothing from it is listed, nested or posted; open it to see the drawing in source mode, or state the flat size and scale on its Intake row to extract'), nothing saved; it blocks only where the file is PROVEN a sheet -- auto_view (sheet_intake.auto_extract now tags a content refusal with the plan that SUCCEEDED: scale + flat view proven; the upload records sidoc.auto_view) OR the largest split group spans >= 95% of the drawing both axes (a border frame owning the views; covers old jobs with no auto_view). A kit the detector merely suspects (CAMP#4, 91 real test patterns, no scale, no frame) splits exactly as before. uploadnotes door keeps a literal blocked:true. CLIENT: roadGroup routes the split door's refusal to a BLOCKED note (never a row; the post-split detected-sheet note is blocked too); Part list drawer renders each blocked note as a RED 'BLOCKED --' card with 'open it', above the yellow notes. PROVEN: NEW test_sheet_blocked 17 (rule-as-control: old code fails 8 of 13 with the exact 30.9 x 23.4 border part) + committed fixtures testdata/CP-6005-03-SPLINE-SHEET.dxf + CAMP4-KIT-SUSPECTED-SHEET.dxf; NEW app/verify_sheetblock.js 9/9 (two CP-6005 copies dropped as a group: zero rows, zero children, two red cards, open-it lands on Geometry); dev sweep of 36 unextracted sheets: 33 block (29 old Lathrup/F1 border splits + CP-6005 x2 + 2 stale), 3 split as before (CAMP#4 + two pre-dim-scale 79602 jobs, which now auto-extract on upload anyway); sheet_intake 98, reader_types 23, srcsheet 6, split_door 17, split_bridge_rollback, original_lineage 26, upnotes_open 10, dwgtray 20, oneroad 17, multiupload 13 green; identity gate green; F1 8.34/8.36s vs 8.33/8.37 no cost; zero dev O-numbers. Existing bogus CP-6005 children on dev are left as they are (not deleted). Fix A (extractor carries SPLINE/ELLIPSE) = the next chunk, awaiting go. FIX-B FALSE BLOCK + EXTRACTED SHEET NEVER JOINS ITS LIST 2026-10-15 (pin `zero-click-sheet-intake` extended, question; Jordan's 2026-1486B-210-18 upload, 6 of 8 blocked, extracted parts never return to the Part List): measured on dev, two defects, both mine. (1) The six files are NOT drawing sheets -- each is one plain flat part (89.9 / 51.8 x 8.46 strip, 3-9 slots 1.002 x 0.312) carrying its own 6-12 dimension entities, no text, no border; the detector reads 'dims + separated clusters' (the slots) as a sheet, and Fix B's border-frame test then calls it PROVEN because a part's own outline always spans the whole file -- so any single dimensioned part the detector suspects is hard-blocked. (2) After a manual extract, sheetExtract calls oneRoadWrap, which refuses any job already inside a group -- a blocked member is grouped at upload but given no row, so the extracted part never lands on its list (1a extracted + reviewed on dev, list still 2 rows). Proposed fix (awaiting go): frame test counts only a group that contains other cut groups AND is not itself a closed part outline holding them as cutouts (or: no title/text + scale 1 measured = plain part), and an extracted member of a group gets added as a row on its own list. Nothing built, zero dev O-numbers. FIX-B SCOPE WIDENED + REMOVED ROWS STAY OFF 2026-10-15 (pin `zero-click-sheet-intake` extended, question; Jordan): measured on dev -- all 38 blocked sheet jobs block on the frame test alone (Jordan's 6 + 32 real sheets: 20 Lathrup, 9 F1, 2 CP-6005, 78017 detail, a DWG test), so the border rule ships only if all 38 separate cleanly; a part blocked then cleaned by hand in Heal/QC has NO road back to its list (heal-edit save never checks it), vector convert has the same group bug -- proposal widened to ONE server rule: a list member with no row joins its list (qty 1) when it first passes heal, whatever the road; RULING Jordan: a row the operator removed stays off ('there would be a reason the operator deleted it'); Jordan re-uploads to test, no dev repair. Nothing built, zero dev O-numbers. BLOCKED PARTS VISIBLE ON THE LIST QUESTION 2026-10-15 (pin `zero-click-sheet-intake` extended, question; Jordan: 8 files uploaded, cards for 2, the other 6 'flying blind' with only 'open it' and words, no picture of the defect -- 'tell me what is still wrong VISUALLY'): proposal -- every uploaded file keeps a card on its list (blocked ones in a red 'needs attention' group at the top, never packed), thumbnail of what we read with the Geometry lenses' own marks drawn on it in the Colours & legend colours (open ends, duplicates, jogs, a suspected sheet border/views dashed, scale unknown badge), one plain line + the fix button on the card where one click fixes it ('Not a drawing sheet -- treat as a part' as a recorded operator override, extract at scale, join/drop duplicates), 'open it' lands on Geometry with the matching lens already on; a passed card becomes a normal row by the widened rule. Nothing built, zero dev O-numbers.
DIMENSIONED PARTS + ONE LIST-JOIN RULE BUILT 2026-10-15 (record; Jordan 'If the fix chunk is clear to you now, go ahead and build it'; cards keep today's order): (a) Fix-B border rule narrowed -- a group spanning the file is a BORDER only if it holds shapes that hold shapes (depth >= 2) or frames >= 20 text entities; NEW _dimensioned_part: a suspected sheet with no proven view, 2+ linear dims ALL storing a measurement equal to the drawn span (1:1, no factor), and ONE part of depth <= 1 is a dimensioned PART -- intake sheet status 'part' (not flagged), split answers single part, extract fields stay as the override. (b) NEW _list_join at the end of every pipeline run: a list member with no row joins its list qty 1 once healed (done/flagged) and not an unextracted sheet -- extract, vector convert, units, tolerance, Heal/QC cleanup alike; never twice; partlist.json 'removed' keeps operator-removed rows off; 'joined' + body known_joined keep a row joined while a draft was open from being read as a removal (plBack merges it into the draft); join drops pack + programs like any list edit, rides the door's undo step; list busy > 3s = left, recorded as waiting, joins on the part's next save (honest limit); _job_lock now re-entrant per thread. (c) Jordan's strip committed as testdata/2026-1486B-1B-DIMENSIONED-STRIP.dxf, NEW test_sheet_dimpart 23 (old code fails 2+3). (d) 44-sheet dev sweep: 31 real sheets still block (20 Lathrup, 9 F1, 2 CP-6005), 3 kits split, 7 freed = Jordan's 5 unextracted strips + 78017d04a detail + dwg-door-test (both single parts I had wrongly counted as real sheets, owned). (e) identity gate green; test_sheet_blocked 22 / sheet_intake 98 / reader_types 30 green; F1 8.40/7.74 -> 8.43/7.80s no cost; zero dev O-numbers. Visual blocked-card chunk stays proposed. | MANUAL ROAD FOR ANY SHEET QUESTION 2026-10-16 (question; Jordan after the 22-min black-box sheet, dev restarted on his OK at inflight 0/0 -- upload cancel live): 'a small shop that only has this software needs to be able to at least open and view any dxf/dwg/pdf/ai ... and DO something with it, even if it's not automated' -- today an unextracted sheet with no stated scale has NO manual road: sheetextract takes scale+flat size and auto-matches ONE view, the operator cannot pick a view, cannot take several views as several parts, cannot set scale from a known length. Proposal: in source mode, window a view (band), set scale by clicking two points + typing the true distance (or type the ratio), name it + qty -> a part job bound to the list through the existing split/one-road machinery, repeat per view; recorded per view, removable; the view-pick also feeds the automatic road when it can't decide. Questions out to Jordan. Nothing built, zero dev O-numbers. | MANUAL SHEET ROAD ANSWERS 2026-10-17 (question; Jordan): (1) the 6-step road approved as the workflow (window a view in source mode, scale, name+qty -> Part List row, repeat per view, recorded+removable, unwindowed views never cut); (2) two clicked points + typed true length is user-friendly (typed ratio kept as the second way); (3) one window = one part = one file -- if a window holds more than one separate outline we say so and offer the split, warn never block; (4) an unextracted sheet with no scale should skip the heavy automatic checks at upload and land straight in source mode asking to pick views (ends the 22-minute Black Box wait; also answers the earlier skip-heavy-checks question). Chunk plan offered: (a) server door making a part from a window + scale via the extract writer and the one-road row join, (b) source-mode window + two-point scale UI, (c) unextracted sheet skips heavy checks and lands in source mode. Awaiting go. Nothing built, zero dev O-numbers. | MANUAL SHEET ROAD CHUNK (a): PART FROM A WINDOWED VIEW 2026-10-17 (pin `zero-click-sheet-intake` extended, Jordan 'Go'): NEW POST /api/jobs/<id>/sheetwindow -- window one view on a drawing sheet (sheet coordinates, window selection: only what lies wholly inside, edge-crossers counted) + scale by typed ratio OR two points + true length in inches (mm sheets x 25.4) -> its own part job (one window = one part = one file), healed, a row on the sheet's Part List with the typed name + qty via the one list-join rule (now takes qty, default 1 unchanged); a window holding 2+ separate parts is said with the Split offer, never blocked; {remove} takes the row off + marks it removed (stays off, part job left); windows recorded on sheetintake.json; same annotation rules + R12 writer as extract(), polylines carried as exact lines/arcs (black-box sheet is all polylines: its tab windowed -> 1 part, heal PASS, 1.5s); server door only, UI = chunk (b); NEW test_sheet_window 27 + sheet_intake 98 / dimpart 23 / blocked 22 / reader_types 30 / srcsheet 6 green, identity gate green, F1 n/a (new door), zero dev O-numbers | MANUAL SHEET ROAD CHUNKS (b)+(c) 2026-10-18 (Aristide 'build b and c'): (c) a drawing sheet the zero-click road refuses for NO SCALE (sheet_intake marks that refusal no_scale -> sheetintake auto_no_scale) skips heal/QC at upload: _sheet_pick_land writes stages.intake sheet_pick + the usual detected-sheet record + an empty sheet_pick geometry doc; other refusals (several scales, ambiguous views) keep the old road. Black-box sheet lands in 0.5-0.6s (was ~22 min). NEW POST sheetfullcheck = the skipped heal/QC on the operator's click only (cancel restores job.json + geometry byte-exact; a job that ran them refuses). (b) the job opens straight in source mode on Geometry; Show panel 'Pick views to cut' card: Window a view (armed plain drag, Esc drops), scale by the 📏 measured two points + typed true length OR ratio 1:n, name + qty, Make part -> POST sheetwindow frame:'view' (new _view_to_sheet maps screen frame -> sheet: undo intake turn, then units scale; window = box round the mapped corners; measure points mapped too); made windows drawn dashed with name x qty (record keeps view_window), listed with open + remove; flips hidden on a skipped sheet (a flip re-runs the full checks). NEW test_sheet_road_bc 19 (frame inverse on plain/mm/quarter/square-up/turn+mm, same view sheet-frame vs turned view-frame = same part), verify_sheetroad.js 12/12 on scratch; sheet_intake 98 (check 21 updated to intent), sheet_window 27, upload_cancel 15 green. Identity gate green. F1 n/a (non-sheet uploads unchanged). Live on dev after the next restart.
- •INTAKE READER AUDIT -- every reader sees every entity the cutter cuts (Jordan, 2026-10-11 -- 'make sure we're not overlooking any other fundamental issues like these') questionmixed — QUESTION 2026-10-11. | MEASURED 2026-10-11 (Jordan: 'I thought the spline issue was settled a long time ago? ... a deep dive'). Splines ARE settled for CUTTING -- dxf_io.parse reads SPLINE/ELLIPSE and heal fits them since 2026-08-06 (short-spline thinning 2026-10-07). ROOT CAUSE of the 78017D04A class: kerfmaster has FOUR DXF readers each with its own entity list -- dxf_io (cuts: LINE/ARC/CIRCLE/LWPOLYLINE/POLYLINE/SPLINE/ELLIPSE), sheet_intake (detector + extractor: GEOM_TYPES LINE/ARC/CIRCLE/LWPOLYLINE, POLYLINE folded since e63e1a1a), annot (dims/text display), sheet_draw (source view). Findings on 423 unique dev sources: (1) sheet_intake is blind to SPLINE/ELLIPSE -- 17 files carry splines, 3 ellipses, none with dims so no misread today; WORSE half by code reading (not yet proven on a file): a spline/ellipse cutout INSIDE an extracted flat view is never in a cluster, so extraction drops it SILENTLY (the extractor refuses honestly only on types it sees). (2) geometry inside BLOCKS (INSERT) is never cut -- proven on a synthetic file: block-only part -> parse empty -> refusal blaming linetypes (wrong reason); outline as lines + holes as a block -> holes missing SILENTLY by construction. Dev: 38 files with INSERTs, all title blocks/tables/logos/centre marks, none part geometry. (3) ink on layers the customer turned OFF is cut like any other: 20 dev files, all Lathrup title-block TB-HIDDEN on extracted sheets, no harm today. (4) a no-scale multi-view sheet the split door CAN split lands its views as rows (pre-existing; zero-click chunks 2-3). (5) SOLID/HATCH/POINT/OLE never cut -- none seen as cut ink on dev. PROPOSED order: one shared entity reader for every stage + a rule-as-control test that fails if any reader skips a type the cutter cuts + extraction refuses on any entity it cannot carry; then blocks (exploded with scale/rotate/array, the default awaiting Jordan); then off-layer flag (warn, operator decides); then chunks 2-3. Each: committed fixture, rule-as-control, full corpus sweep, F1, identity gate. Nothing built. | CHUNK A BUILT 2026-10-11 (record; Jordan '1. Go'): ONE ENTITY TABLE -- NEW dxf_io.CUT_TYPES names exactly the kinds parse() cuts (LINE/ARC/CIRCLE/LWPOLYLINE/POLYLINE/SPLINE/ELLIPSE); sheet_intake.GEOM_TYPES now DERIVES from it (POLYLINE arrives folded) so the sheet detector/extractor sees splines and ellipses (on-curve points through dxf_io's own eval_spline/eval_ellipse; an unreadable spline falls back to its control+fit hull, never empty); NEW sheet_intake.EXTRACT_TYPES = LINE/ARC/CIRCLE -- any other cut kind inside the matched flat view (absorbed clusters included) REFUSES BY NAME on both the manual extract and zero-click doors ('carries 1 ELLIPSE, 1 SPLINE -- ... refuses rather than drop them'), never a silent drop; the sheet stays as sent for the operator. Finding 1 PROVEN on the committed fixture testdata/SPLINE-CUTOUT-SHEET.dxf: the old code zero-click extracted a 6x4 plate and silently lost its spline and ellipse cutouts. HONEST LIMIT: carrying splines/ellipses through the extraction (scale+translate is affine-safe for both) is the next step, not built -- such a sheet is refused, not extracted. NEW test_reader_types.py 23 (rule-as-control: parse() branches == CUT_TYPES, every cut kind seen by sheet_intake AND drawn by sheet_draw, fixture refuses on both doors, curves-removed control extracts 6x4; old code fails). 427-file sweep old-vs-new: zero sheet flips, all 31 auto-extractions byte-identical (79602's report dim_votes reorder only -- its ellipses now form their own side-view clusters), 19 detect reports gain spline/ellipse clusters. test_sheet_intake 98 / srcsheet 6 / sheet_draw 22 / dashed_ink 22 / original_lineage 26 / color_sets 25 / feat_report 17 green; identity gate green; F1 first click 8.13/8.08 -> 8.09/8.10s, repeat 7.39/7.36 -> 7.39/7.39s (in-process, caches off) -- no cost; zero dev O-numbers. Same message, Jordan's other answers: (3) RULING -- ink on layers the customer turned off is NOT cut by default ('there's probably a reason the customer hid them'), and it can be switched on in source mode as an honest review of the data (supersedes the warn-only proposal C; not built). (2) blocks -- he asked for an explanation before deciding; question stands. (4) RULING -- no more deep dives for now ('finding new random issues slows our progress'; be proactive instead). (5) dev restart OK'd if idle -- done, both inflight 0, e63e1a1a's detector fix now live on dev. | BLOCKS CUT (finding 2) BUILT 2026-10-11 (record; Jordan '1. Go' on cut-by-default, title blocks never, note on upload): dxf_io.parse now places every INSERT's block geometry -- insert point, rotation, uniform scale, block base point, row x column arrays, nested blocks, OCS-mirrored inserts; placed circles stay true circles (centre + diameter), arcs true arcs; layer-0 / BYBLOCK ink inherits the INSERT's layer/colour/linetype and rides the SAME routing (dashed, colour pick, flips). A copy is SET ASIDE, counted by reason in parse()['blocks'], never silent: carries text/attributes/dimensions (title blocks, notes, balloons), sits on a layer with no directly-drawn part lines or with dimensions/notes (MEASURED need: SolidWorks SW_CENTERMARKSYMBOL on DIMS and the Lathrup logo on TB-BLOCKS are solid lines inside the sheet -- extents alone would have cut them on 20 files), lies outside the drawn part, frames a whole-part-as-block, paper space, missing/xref, or stretched unevenly with curves (never seen in 428 dev files; set aside pending Jordan's call). dxf_io.CONTAINER_TYPES declares INSERT; test_reader_types control refined (containers must be declared). Server: geometry.json carries the blocks summary; Intake 'Blocks:' row + source-mode line name what was cut and what was set aside and why; the zero-cut refusal no longer blames the linetype table. Corpus: 428 files, ZERO cut-geometry changes (38 INSERT files: all furniture -- title blocks, borders, notes, logos, centre marks); no real block-placed part feature exists in the corpus, so the committed fixtures are synthetic: testdata/BLOCK-HOLES-PART.dxf + BLOCK-WHOLE-PART.dxf. NEW test_block_inserts 19 (old code passes 1/18). HONEST LIMITS: the sheet detector/extractor still does not read blocks (a drawing sheet whose flat view holds block-placed holes would extract without them -- guard is the next step); a set-aside copy cannot yet be flipped to cut from source mode. | HIDDEN LAYERS NOT CUT 2026-10-11 (record; Jordan's ruling 'hidden-layer ink not cut by default, switchable in source mode' + his 'You choose' on the next chunk): dxf_io.parse reads each LAYER's flags (code 70) beside its colour; a layer turned OFF (negative colour) or FROZEN (flag bit 1) routes its ink to colorink (display-only, drawn faded in source mode), counted per layer with state in parse()['hidden'] -> geometry.json 'hidden' -> Intake 'Hidden layers:' row (+ source-mode panel); a block copy placed on a hidden layer is set aside whole (blocks.set_aside 'hidden'); routes reason 'hidden' names it in source mode; the SWITCH is source mode's existing layer flip -- a recorded 'cut' flip on that layer cuts it again (drawn ink and block copies). Hidden ink is kept out of the colour census. Zero-cut refusal counts hidden entities. Sweep 430 files: exactly 20 changed, all unextracted Lathrup drawing sheets, 17 title-block lines each on TB-HIDDEN (off) now set aside; nothing else moved. Committed fixture testdata/HIDDEN-LAYERS-PART.dxf; NEW test_hidden_layers 13 (old code 4/13) + block_inserts 19 / reader_types 23 / dashed_ink 22 / color_sets 25 / srcflip / original_lineage 26 / sheet_intake 98 / srcsheet 6 / sheet_draw 22 / feat_report 17 / cleaned_dxf 11 / spline_thin 12 green; identity gate green; F1 first click 8.05/8.07 -> 8.09/8.07s, repeat 7.36 -> 7.40/7.37s -- no cost; zero dev O-numbers. Honest limits: sheet extractor reads layers its own way (unchanged); browser proof waits for the dev restart. SAME DAY, Jordan's answers: (a) stretched block copies -- keep set aside and named until a real one is seen (ovals rare, usually slots); (b) sheet-extractor blind to blocks -- PARKED until the next Lathrup upload, then test both theories (guard that refuses by name vs carrying block holes through extraction) against those real files. FIX A BUILT 2026-10-12 (record, Jordan 'Continue' after Fix B -- the cure for CP-6005-03/-04): the sheet extractor CARRIES SPLINE and ELLIPSE out of the flat view EXACTLY -- EXTRACT_TYPES grows both; spline control points and the ellipse centre move with the flat's scale + shift, the ellipse axis vector scales, knots/weights/degree/flags/ratio/parameters stay (uniform scale + shift leaves both curve kinds invariant; nothing faceted); split_annotations judges curves as chains (endpoints from the curve itself, dedupe key on sampled points); a kind it still cannot carry (LWPOLYLINE) refuses BY NAME, never drops. TWO PRE-EXISTING DEFECTS this exposed, both fixed in the same chunk and both necessary: (1) split_annotations' linetype test read any name without 'SOLID' as drafting ink, so CP-6005's whole 'Continuous' outline was dropped -- now CONTINUOUS counts solid (narrow on purpose; the LTYPE dash-declaration rule stays HELD per Jordan 2026-10-06); (2) the extractor ALWAYS wrote $INSUNITS=1, so an undeclared mm sheet came out 25.4x too big (CP-6005-03 read as a 95.5 x 69.1 INCH part) -- NEW sheet_intake.sheet_units applies dxf_io.to_inches' own rule to the WHOLE SHEET ($INSUNITS 1/4 wins, else the sheet's extent over 200 cannot be inches) and the flat is written in those units, report.units records it. RESULT: CP-6005-03 extracts with zero clicks to the true flat, 95.5352 x 69.1235 mm = 3.7612 x 2.7214 in, 18 splines kept, both slots absorbed, never the border; CP-6005-04 6.4917 x 3.6182 in. HONEST LIMITS: (a) the pick is a BEST READ (one dimension on the sheet) so intake stays flagged with the standing best-read warning; (b) -03 heal flags real defects in the customer's drawing (a stray 0.96 mm line overdrawn on the bottom edge = 37.7 thou gap, a near-zero-length line in one slot = jog/branch); (c) -04 heal reads 49 thou FAIL but that is a MEASURING ARTIFACT -- dxf_io.eval_spline samples uniformly in the spline parameter, so a long straight knot span gets one sample per 0.175 in and the fidelity check measures healed ink against sample points; against a dense source the heal is 5.4 thou (inside the 10 thou gate). The sampler fix (arc-length-aware sampling) touches every spline file and the Speed chat's native sampler -- OFFERED as its own chunk, not built. PROVEN: corpus sweep 436 unique DXFs old vs new -- 31 previously extracted sheets BYTE-IDENTICAL (Lathrup/F1 included), only 3 changed, all intended (CP-6005-03, CP-6005-04, SPLINE-CUTOUT fixture); test_reader_types 23 -> 30 (section 3 rewritten: carries + exact scaled control point/ellipse, LWPOLYLINE refuses by name; NEW fixture testdata/LWPOLY-CUTOUT-SHEET.dxf); test_sheet_blocked 17 -> 22 (Fix B's refusal case moves to the LWPOLYLINE sheet, NEW CP-6005 Fix A checks 9a-9f, frame signal proven on a simulated old job); rule-as-control: pre-Fix-A code fails 2 + 6 of them; app/verify_sheetblock.js 9 -> 11 (CP-6005-03 lands as ONE part row 3.7612 x 2.7214 in mm); sheet_intake 98, srcsheet 6, hidden_layers 13, block_inserts 19, sheet_draw 22, split_door 17, original_lineage 26, dwgtray 20, upnotes_open 10, srcunext 11 green; identity gate green; F1 8.41/8.40s vs 8.34/8.36 (noise, extractor not on the plan path); zero dev O-numbers. SPLINE CHECKER STEP 1 BUILT 2026-10-12 (Jordan 'Yes. Go on step 1'): the heal fidelity reference no longer has holes -- spline/ellipse samples are uniform in PARAMETER, so a long straight spline span could leave 0.175in between reference points and the check read the hole as deviation (CP-6005-04 false FAIL 49.31 thou). NEW dxf_io._fill_param_gaps bisects every over-long interval on the true curve until each chord <= step, keeping the sample's own points; sample_true_source(fill=True) used ONLY by the fidelity measurement (server pipeline, heal __main__, check_corpus) -- cleaner input, every other caller and the G-code untouched. CP-6005-04 49.31 -> 3.72 thou PASS; -03 3.06 unchanged; 21-file spline/ellipse sweep: 10 identical, 10 lower, cbb-1-flat 0.79 -> 0.82 (a real deviation the old holes hid, inside gate); 44558b-7 not judged (measurement timed out, heavy file). NEW test_fill_gaps 10 rule-as-control (the plain sample fails every-gap-<=-step on the control) + 7 neighbour suites green; identity gate green byte-identical; F1 8.44/8.47 -> 8.45/8.43s no cost; fidelity step a few % slower on spline files only (more reference points); Speed's native sampler untouched (fill runs after it). Step 2 (cleaner sampling) stays offered, needs Speed. Zero dev O-numbers.
- •Brick 34: import rotation -- the old CAM's 'Rotate Drawing' setting + open-part doors record — Built 2026-09-02 on Aristide's go, from Jordan's Import Settings screenshot: shop default 'rotate if taller than wider' stands every import's length on X; per-job override wins; part-list rows and nest placements open the referenced part. | HEAL EDITS ON TURNED PARTS 2026-10-16 (fix list item 7): the heal-edit save door now judges clicks in the turned frame like the replay -- see pin jordan-fix-list-2026-10-15.
- •Brick 35: the MASTER rotation option on a part list record — Built 2026-09-02 on Jordan's ask ('not more clicks than I want tonight, it's more clicks than I want ever'): one 'part frames' control on the Part list tab applies an import-rotation choice to every listed part; parts already in frame stay untouched; each part stays individually overridable.
- •Brick 36: Spread Y on part-list nests (+ hand-layout bridge fix 2026-09-19; + Spread X engine+door + button 2026-09-21) record — Built 2026-09-03 (Aristide 'Go', on Jordan's 'my next step would be Spread Y which I do not see in this part of the UI'): the ruled one-click gap evening lands on the part-list Nest screen -- per column, edges included, bridges respected, meshed groups rigid, X untouched; gated by the pack's own audit.
BRIDGE FIX 2026-09-19 (Jordan's Spread_Y_9-19-2 screenshot -- 'Spread refused: KeyError: bridge' on his hand-arranged LOGO-TREAD nest; his '2. Go.'): run_plhand persisted hand-edited placements WITHOUT their bridge ({id,x,y,rot,filler} only), while every layout reader expects the pack's own placement shape -- run_plspread and run_plrefresh both read p['bridge'] and pl_spread.spread_y ranks units by it, so Spread Y and Refresh envelopes CRASHED on any hand-edited part-list layout, the raw KeyError surfacing as the refusal toast. ONE helper server._pl_fill_bridges(pn): resolves each missing bridge from the pack report's own bridges table (gap seed the last resort -- the variant door's fallback), in place. Wired three ways: run_plhand fills before saving (new hand layouts carry bridge like packed ones), run_plspread and run_plrefresh fill after loading (pre-fix hand layouts already on disk -- Jordan's job -- spread fine and the next save heals the record). Answer to his question recorded: Spread Y is a one-shot evening of the layout as it stands, never a sticky mode -- a hand edit replaces the spread layout, clicking Spread Y again re-evens the edited layout at the ruled bridges, Pack again restores the packed form. Proven: NEW app/verify_srcdl.js regression checks (hand save carries bridge 4/4, spread 200 where it crashed, refresh 200) + plhand 18, plrefresh 16, refusal 16, pltabs 19, pldock 14 green; live API proof on a stripped pre-fix layout (spread 200, record healed on disk).
SPREAD X ENGINE + DOOR 2026-09-21 (chunk 3 of the column-join four-chunk Go -- Aristide's split-into-chunks instruction, Jordan's 'Go'; the ruled 'spread X' one-click of pin nest-spacing-operator-prompt: it deliberately SPENDS the clean remnant slab, so it is only ever the operator's click, never automatic): ENGINE pl_spread.spread_x -- the SAME evening core (_spread, one arithmetic both axes) transposed; the rigid unit is the COLUMN WHOLE (the same transitive X-overlap group spread_y stacks -- a naive Y-band transpose was measured WRONG in development: stacked members of a column do not overlap in Y, so banding split the column and shredded its shared X phase; never shipped), the whole sheet one band, the evened gaps = left edge + column channels + right edge, same required minimums (larger bridge governs AND the standoff), same left-as-packed honesty when the columns plus ruled channels exceed the width, lead envelopes ride per orientation. DOOR run_plspread gains body axis ('y' the default -- an absent axis keeps every old caller byte-compatible): axis 'x' evens across the width, RESTATES used_x per sheet from the moved envelopes (the slab is spent -- said honestly), pops report.free, same pln._audit + pl_tool.judge gate (separate arithmetic, the 3A76 lesson), a miss refuses whole with nothing saved, posted sheet programs drop with every O-number kept, one undo step on the door. PROVEN: test_pl_spread 32 -> 46 (even across the width edges included, rigid column meshing with Y untouched, larger-bridge channels, width left-as-packed wording, lead envelope in X, pack-audit pass, Y-then-X composition) + test_handspread 27 zero edits + in-process door checks (a 5-part lone column centers across the width, used_x 8.355 -> 64.075 restated, default y unchanged, bad axis refuses in honest words) + verify_srcdl 13 + verify_pltabs 24 zero edits; dev engine restarted, HTTP 200; zero dev O-numbers. Chunk 4 (the one-click Spread X button beside Spread Y on the Nest tab) rides the same Go.
SPREAD X ON THE NEST TAB 2026-09-21 (chunk 4 of the same Go -- the four-chunk build COMPLETE): the one-click Spread X button lands beside Spread Y on the part-list Nest drawer, client-only -- ONE machinery, runPlSpread parameterized by axis (Spread Y posts axis 'y', Spread X posts axis 'x' to the SAME /plspread door), busy seam / refusal toast / undo identical both clicks; the drawer states the trade honestly ('Spread X spends the remnant slab (used X is restated honestly); Spread Y keeps it. Pack again restores the packed form.') and the applied note names the axis (a pre-chunk Y-only spread record reads as Y). PROVEN: verify_srcdl 13 -> 16 (a REAL CLICK on the scratch instance drives the whole chain -- drawer says Spread X applied with the deliberately-spent wording, used_x 60.57 -> 100.1033 restated from the moved envelopes) + verify_pltabs 24 (Spread X counted beside Spread Y and Pack again on the Nest drawer). Client-only (app.js + the two suites), zero server/engine change, no restart needed; zero dev O-numbers; progseq untouched. The four-chunk Go -- column join, long proof battery, Spread X engine + door, Spread X button -- is COMPLETE. REGULAR-FORM ENGINE 2026-09-22 (chunk 1 of the regularization Go; Jordan's Spread_Y/X screenshots on his prod 44556B_57B_1 -- 'the purpose of Spread Y and Spread X are to make the gaps (edge of the sheet AND spacing between parts) even ... The job we're looking at here doesn't meet those criteria with the current functions, does it?' -- he was right: MEASURED on his job, both clicks degenerated to centering the one fully meshed unit (Y edges 0.5795/0.5795 with every between-part gap left at packed contact pitch 4.839; X edges 3.3378/3.3378, no channels), cause mine: the rigid-unit rule preserves meshing and this sheet is ONE transitive unit. His ruling note: his manual form is a 3(X)x12(Y) nest at 0 deg plus a 2(X)x12(Y) nest 180-flipped tucked between the columns, gaps even both axes, posting as 2 P9997 macros. NEW pl_spread.regular_form -- where the sheet IS a double array under scatter (one part id, 1-2 orientations, every column the same row count >= 2; anything else returns None and the unit spread stands), the evening is REGULARIZATION: rows ALIGNED on one shared Y pitch with g_y = (H - R*h)/(R+1) perfectly even edges included; X solved by bisection so the binding column-to-column clearances AND both edges all equal g_x (one shared column pitch P for both orientations + one tuck offset d; separations found on stacked 3-row envelope sets with a hash-grid clearance predicate -- construction arithmetic, the caller's audit stays the judge); both floors hold ruled clearance (no room = None, never a tightened pair). Frame lesson: a 180 placement's origin sits a whole part-width off its envelope min -- the B-cell offset j0 compares positions in the ENVELOPE frame, never mixed origins (the first run returned None on exactly this). PROVEN offline on the byte-reproducing 44556B kit: solve 0.5s, shared pitch_x 47.3538 both arrays, pitch_y 4.9707, gap_x 0.7337 = edge 0.7339, gap_y 0.3515 = both Y edges, pack's own _audit margins gap +0.1523 / lead +0.4511 / edge +0.1515, detect_macro_runs reads the result as exactly 2 real runs (3x12 rot 0 + 2x12 rot 180, one editable pitch each) -- Jordan's two-macro form falls out. test_pl_spread 46 -> 66, the old 46 zero edits (spread_y/spread_x byte-untouched). Engine-only, no caller yet -- door wiring + live proof + macro post ride chunk 2; zero dev O-numbers. CHUNK 2 BUILT 2026-09-22 (door wiring + live proof + macro post): run_plspread tries regular_form FIRST per sheet, BOTH axes -- where the sheet is a double array under scatter, EITHER click regularizes (both x and y move by construction, said honestly in the record); None keeps the unit-preserving spread byte-identical. Applied sheets land in the spread record as {sheet, regular: {arrays, gap_x, gap_y, edge_x, edge_y}}; used X is restated from the moved envelopes for any regularized sheet whatever the clicked axis (edges-included X evening spends the slab -- stated); free pockets pop; SAME gate (pln._audit + pl_tool.judge), refusal whole, one undo step, posted programs drop with O-numbers kept, Pack again restores. Client: drawer trade note names the regularized form, the applied record reads 'Regularized (Spread X/Y click)' with per-array rows (cols x rows at rot -- pitch X/Y, gaps edges included), regularized toast. PROVEN LIVE through the real dev doors on the 44556B kit rebuilt end to end (upload -> review -> list qty 50 rotate 180 filler -> lattice pack 60 placed used_x 113.5295 = chunk 1 byte-exact): Spread Y click regularized to 3x12 rot 0 + 2x12 rot 180 on ONE shared pitch_x 47.3382 / pitch_y 4.9707, gap_y 0.3515 = both edges, gap_x 0.7489 = edge 0.7496, audit margins +0.1523/+0.4511/+0.1515 (live leads differ a hair from the offline plan rows -- 47.3382 vs 47.3538, stated); plpost style MACRO = Jordan's two-macro form IN THE NC: O33400, G172+G65P9997 I47.3382J4.9707 K12Q3 (sub 75433) + K12Q2 (sub 75434). Suites: test_pl_spread 66 + test_pl_macro 25 zero edits; verify_pltabs 24 zero edits; verify_srcdl 16 -> 17 REWORKED HONESTLY -- its single-part uniform-grid fixture now regularizes on either click BY DESIGN (the ruled purpose; the axis path stays proven on declines in the engine controls), new fixed-point check (second click identical). Dev engine restarted, HTTP 200. Consumed dev O33400 + subs 75433/75434 (progseq committed). CHUNK 3 SEALED 2026-09-22 (Aristide: go for 3) -- the four-chunk-Go COMPLETE: the full long neighbour battery green with ZERO suite edits -- test_part_list 37, test_pl_free 42, test_pl_select 21, test_pl_sync 23 + verify_plhand 27 (scratch 8479), verify_plrefresh 18, verify_refusal 16; regular_form declines by design on every multi-id/partial-column fixture, so the unit-preserving spread stayed byte-identical everywhere the ruled double-array shape is absent. Zero dev O-numbers consumed; progseq untouched. Completion report sent to Jordan. || SPREAD ALL + JAM 2026-09-22 (Jordan's three: 'I would call that spread all, not spread Y' -- his catch that the regularization moved both axes off his Spread Y click on 44556b; 'should we not also have the opposite option, to jam X or Y? ... spread Y for best thermal behavior, but I might want to maximize the remnant of material in X'; his Go): (1) the regularization moves OFF the Y/X clicks onto its own Spread all button (door axis 'all') -- Spread Y and Spread X are PURE single-axis again, the mislabel gone; a sheet regular_form declines under Spread all falls back to the unit-preserving spread on BOTH axes (Y then X), said honestly; used X restated on any X move. (2) NEW pl_spread.jam_y/jam_x -- the SAME _spread core run in reverse (jam=True): gaps compressed to the ruled minimums (larger bridge governs, edges = own bridge, standoff floor), the whole leftover pushed to the top/right; Jam X restores or grows the clean remnant slab (used X restated), so Spread Y + Jam X = even thermal gaps AND the biggest slab for another job -- his stated use case; no partial-column cap in jam (the minimum is its own rhythm), left-as-packed honesty on a column that cannot fit, Y/X never cross-move, same audit gate (pln._audit + pl_tool.judge) refusing whole, one undo step, programs drop O-numbers kept, Pack again restores. Five one-clicks on the Nest drawer (Spread Y/X/all, Jam Y/X) through ONE runPlSpread machinery; drawer trade note and applied record name the click. Proven test_pl_spread 66 -> 80 (jam controls, old 66 zero edits) + verify_srcdl REWORKED 17 -> 20 (real clicks: Spread X pure, Spread all regularizes fixed-point used_x 100.0503, Jam X restores the slab 100.0503 -> 60.7, Jam Y leaves it) + pltabs 24, plhand 27, refusal 16, plrefresh 18 zero edits; engine restarted. | TRUE-GAP SPREAD 2026-10-12 (record; Jordan's 78017D04A catch 'Spread Y doesn't seem to work with multiple grids', his 'Build it'): on his 1/2in MS sheet (12 long parts + two side-by-side stacks of 3, bridge 0.375, standoff 0.5) the part+lead boxes sat ~0.10 apart because the lead-ins reach into the spacing while the metal cleared the ruled gap -- the box arithmetic called the column 3.82in short, moved every part 0.0000, and the client still toasted 'Gaps evened'. FIX: the box form stays wherever it fits (byte-identical, every existing sheet); a column the boxes refuse is re-spaced on the TRUE gap -- pl_spread._true_gap measures each in-reach pair on the audit's own rules (outline-outline >= larger bridge, lead-outline >= max(standoff, larger bridge) both ways, outline-edge >= own bridge, leads kept on the sheet) as the smallest verified-clear upward offset (scan + bisect, 0.0002 rounding guard), places every part on its own in a bottom-up DAG (side-by-side stacks = their own chains, a sub-column is a shorter chain) and gives each gap ruled-minimum + ONE even extra per column, leftover to the top on shorter chains; jam = extra 0; impossible = left as packed, said so. spread_y/jam_y take parts_by_id= (outline, leads apart; None = old behaviour); run_plspread passes it on Y/Jam Y/Spread all, and a click where nothing moved now REFUSES in plain words naming the left-as-packed columns, nothing saved, programs kept. Client toast counts true-gap and left-as-packed columns ('Nothing evened' when none moved). His sheet: evened extra 0.1404, long parts one uniform pitch, both small stacks evenly pitched and independent, audit pass (gap margin +0.12, lead +0.54), door 1.2s. Honest limits: true-gap applies to Y (Spread X / Jam X keep the column-whole box form); a column that fits on boxes keeps the box rhythm (side-by-side stacks there still pair rigidly). NEW test_pl_spread_truegap 13 (fixture testdata/spread_truegap_78017.json from his dev job; old road reproduces the defect) + test_pl_spread 80 / handspread 27 / plhand 25 / pl_macro 28 zero edits. | CONFIRMED 2026-10-12 (Jordan, Aristide present): true-gap Spread Y 'confirmed this is working' on his 78017D04A. Still open: extend true-gap to Spread X / Jam X and to columns that already fit on boxes (side-by-side stacks still move as pairs there). | 2026-10-12 (Jordan): extending true gaps to Spread X / Jam X and box-fitting columns 'needs to be tested' -- he will test it WITH us; nothing built until that session.
- •Brick 37: consolidation -- trailing columns move into later sheets' envelopes record — Built 2026-09-03 (Jordan's circled part on the Lathrup nest, 'Are we able to try a new nesting strategy?'): the pack itself now moves whole trailing columns off an earlier sheet's clean remnant slab into a later sheet's existing envelope -- accepted only when the target's used X does not grow (free material by construction), all-or-nothing per column, reported never silent.
- •Lead-aim consistency: circles at the clock, per-orientation part-list planning record — Built 2026-09-03 (Jordan's 'Why are the lead-ins facing random directions?' screenshots, his 'Go'): a TRUE CIRCLE takes the ruled clock start outright (candidate noise can no longer aim identical holes at random), the clear-air tie-break is rounded to a thou like every other tier, and part-list nests plan the toolpath PER ORIENTATION so a flipped placement reserves, draws and posts leads that read one way in the SHEET frame. OPEN QUESTION 2026-09-23 (Jordan's 302310-11 circled lead, diagnosed in his live job's own pack record through the app's read doors): every operator-placed start HELD its exact spot in every orientation (parts 5/6/7/9/10 verified) -- the circled lead was part 2's DEFAULT outer start (shop:start-default; the only recorded operator edit on parts 2/3 is a tab override on the slot), re-aimed on its 180 copy BY this pin's own sheet-frame rule; the kit carries four near-identical 16x8.8 twins (parts 2/3/5/9) and his placed outers live on 5 and 9, so a default read as a placed lead. His new wording 'What we see in Tooling should be what happens at the laser, regardless of how it's rotated' taken broadly would freeze DEFAULT leads too, superseding this pin's re-aim -- asked Jordan which he wants (overridden-frozen only = the built form, or freeze-everything); also offered drawing operator-placed leads visually distinct from defaults on Tooling and the Nest canvas so the two can never be mistaken again. RULING SUPERSEDED -- FROZEN LEADS BUILT 2026-09-23 (Jordan answering the open question: 'yes, we need to supersede the 9-03 re-aim ruling'): every lead now posts exactly as the Tooling view shows, DEFAULTS included -- _pl_build plans each part ONCE at 0-deg and every allowed orientation carries the SAME base-frame rows (by_rot; the placement transform rigidly rotates lead, pierce and start with the part -- the true-nest subs' O33286 form, now on the part-list surface; perf bonus: one check_drag per ref instead of per orientation); pl_post.write_sheet_subcall emits each ref ONCE and derives rotated bodies via emit._rot_lines about the part origin (center= kwarg added, default keeps legacy callers byte-identical); run_plpost gains the frozen-lead gate -- an old pack whose stored plans_rot rows still carry re-aimed leads refuses in honest words naming the part, remedy Update nest or Pack again (pre-plans_rot packs unaffected); slug rows ride the full placement transform. The honest trade, on his word: sheet-frame lead uniformity on rotated copies is RETIRED -- a 180 copy's lead points the opposite sheet way, exactly as Tooling shows. Proven test_pl_sync 23 -> 25 (plans_rot rows == plans rows; frozen holds across an override re-pack) + test_pl_macro 25 -> 28 (180 sub body == the 0-deg body rotated about origin, one emission per ref, nc_audit clean on placed geometry) + part_list 37 / pl_spread 80 / nestedit 38 zero edits + verify_plrefresh 18, plhand 27, refusal 16 (suite fix: fixture grow +2 -> +0.25 and tag rotation locked -- frozen envelopes pack that layout tighter, and a flipped copy's frozen lead can honestly refuse the in-place update; the refusal-on-miss path is plrefresh's own coverage), srcdl 20, pltabs 24. Engine restarted; zero dev O-numbers, progseq untouched. Point 4 (visually distinct operator leads on the canvas) stays offered, unbuilt.
- •Re-aim as an OPT-IN on the Nest tab -- the 9-03 sheet-frame re-aim returns as an operator option with truthful two-way Tooling sync; data model = plan variants keyed part x rotation, never a new part question — QUESTION 2026-09-24 (Jordan, the morning after the frozen-leads supersede: 'I think it would be beneficial to have this as an option in the Nest tab, but only activates if the operator choose so. The big caveat would be that the optimized toolpath from Nesting would have to follow to the Tooling tab, and vice versa'): the 9-03 re-aim returns as an OPT-IN with the display truthful both ways -- consistent with seq-display-is-the-program, since the defect the supersede killed was the SILENT re-aim on defaults, never re-aim itself. AGREED so far: (3) per-job toggle on the Nest tab, default off (frozen leads stay the default), recorded like every override; operator-set starts/anchors stay frozen either way (the 9-22 dragged-start incident stays dead) -- re-aim touches table/default leads only. OPEN, Jordan thinking: (1) per-ORIENTATION re-aim (uniform within each orientation, one re-aimed sub per orientation, P9997 macro form survives) vs per-PLACEMENT (each copy aimed at its actual neighbours, best clearance, part-by-part NC by construction); (2) when re-aim is on and the operator hand-edits a lead in Tooling, does the edit bind that one orientation or every orientation of the feature. DATA-MODEL ANSWER GIVEN on his 'new part or subcategories?' question: never a new part -- the part stays ONE record (geometry, review, overrides); a re-aimed lead set is a variant of the PLAN keyed by part x rotation (the 9-03 build's plans_rot rows are the existing home; the frozen-lead gate would accept such rows only when the recorded toggle is on), and since rotations are born from the nest the variants live with the JOB's pack, never in the part itself -- a part listed in several jobs re-aims per job. The mixed-unique-parts nest is the SAME key (each part x rotation gets its own aim; no macro constraint there anyway), so one model covers both of his scenarios; the only true fork is automatic per-placement aiming, which can stay the operator's manual per-placement move. Touches on any build: frozen-lead gate, pl_post, Tooling-view orientation picker, plans_match wording. NOTHING BUILT -- sitting on his answers to 1 and 2. LOCK REQUIREMENT ADDED 2026-09-24 (Jordan: 'certain parts may have a lead-in location requirement, so we should be able to lock the location of certain lead-ins in the Tooling tab, then the re-aim/optimize would have to obey the locks'): a per-feature LOCK on the lead location, set in Tooling, that re-aim must never move -- an operator-dragged start or start-anchor already outranks re-aim by the agreed model, so the new piece is locking a feature's lead WITHOUT editing it (the default-placed lead pinned exactly where it sits, recorded like every override, shown on the feature row); the lock rides the part's own tooling record so it holds in every job and every orientation.
- •Spread Y: partial columns cap at the full-column rhythm, leftover to the top record — Built 2026-09-04 (Jordan's sheet-10 catch: a 2-part column 'evened' at 11.81" gaps scattered its parts up the sheet and shredded the drop -- 'the 2 parts eating up the last remnant would not be a popular choice'; his 'Sounds good, let's do that'): a column with fewer units than the sheet's fullest caps its bottom and between gaps at the largest gap among the max-unit columns; all leftover accrues to the TOP edge as one clean recoverable rectangle.
- •Slug tabs size from the Rev2 row on every app post -- the blanket 0.018 fallback closed record — Built 2026-09-04 (Jordan's toolpath screenshot: '.018" slug retention tab where there shouldn't be one. Why is it there to begin with?' -- 'Something is broken, and it needs to be fixed'): the app's posts handed the engine tooling= but never a slug sizing table, so the writer fell back on its blanket slug_gap=0.018 for EVERY interior -- and the checker flagged our own fallback. The Rev2 row's slug_tab width + Small/Large limits (ingested 2026-08-31, never wired) now ride in tooling['slug'] and size every slug on every posting surface; both check surfaces judge with the same limits.
- •Colors & legend: the signal vocabulary explained, every color operator-definable record — Built 2026-09-04 (Jordan: 'explain the color scheme you're using in a legend... apply it to the settings; if we have a color blind operator, they may want to define their own colors'): ? Help -> Colours & legend -- one modal that IS both the legend and the editor: nine named signal roles (base layer / healed lines / healed arcs+toolpath / selection+tooling / clean-done / yellow / red / pending / secondary), each with its meaning in words, its glyph where one exists, and a colour picker. REFINED same day (Jordan): 'healed arcs & toolpath' split into two inputs (--toolpath its own variable); 'selection & tooling' DECOUPLED from the interface accent (--sel, canvas-only -- recoloring selection no longer restyles the app; a pre-split saved --accent pick migrates to --sel once); US spelling ('colors') on every user-visible string. Ten roles now. 10 live Playwright checks.
- •DXF mirrored entities (extrusion normal -Z): OCS flip applied at read; tilted normals refuse record — Built 2026-09-04 (Jordan's 44558B_7 catch -- 'a lot of the healing is offset the full width of the part to the left... why only for certain parts?'): when CAD mirrors an entity it may keep the entity's own coordinates and set the DXF extrusion normal (group codes 210/220/230) to (0,0,-1); the coordinates are then in that Object Coordinate System and map OCS (x,y) -> WCS (-x,y). The reader ignored the flag, so 33 mirrored ARCs + 4 mirrored CIRCLEs drew mirrored about x=0 -- a full part-width to the left -- while every LINE sat correctly (LINE and SPLINE store world coordinates by the format's own design; only OCS entities -- ARC, CIRCLE, LWPOLYLINE, POLYLINE -- carry the defect, which is exactly why the error hit only some of the part). | SHEET EXTRACTOR READS MIRRORED ENTITIES 2026-10-08 (record; Jordan's 'trust your judgement' on the fix-first offer): sheet_intake.load_ents now rewrites -Z-extrusion ARC/CIRCLE/LWPOLYLINE into flat XY once at the load seam (_ocs_to_wcs: x -> -x, arc 50/51 -> 180-51 / 180-50 CCW kept, bulges negate, LINE untouched, tilted normals left as read) -- the dxf_io rule, so clusters, the view pick, the extracted R12 and sheet_ink all read true positions. CHECK#4RAW REV D's 18 mirrored arcs/circles had landed ~60in left of the part, faking a second 'view': with them read right the file is ONE 5.459x3.922 part, detect() says part file, and it lands zero-click on the normal road -- heal PASS 0.00 thou, 0 jogs, QC 0 flags, 20 lines + 33 arcs. Sweep of all 132 distinct drawing sheets on the box (scale, extraction hash, ink hash, before/after): CHECK#4RAW no longer a sheet; camp-4 drawing.dxf (1448 mirrored) ink moves to its true place, still refuses for no scale; every other sheet identical. test_sheet_intake 81 -> 89 (OCS 1-8, rule-as-control); verify_srcunext re-fixtured onto NEW testdata/NOSCALE-SHEET-UNEXTRACTED.dxf (CHECK#4RAW with the mirror flags cleared = the old misread, still a no-scale sheet) + a check pinning the real file as a whole part, 11/11; srcfilter 15, origview 20, srcinsp 18, srcdl 20, dwgtray 20, test_srcsheet 6, test_sheet_draw 22 green; identity gate green; F1 8.09/8.13 -> 8.13/8.12s no cost; zero dev O-numbers.
- •Heal/QC panel: Delete edit op, per-job heal cache (lens lag fix), our own lens names record — Built 2026-09-04 (Jordan's three asks on 44558B_7: mark-lens lag, a missing delete, 'you used verbatim "mark open polylines" which is the old CAM language. Recreate these with our own names'). (1) CACHE: every lens click re-parsed and re-healed the source from scratch (6.6 s on 44558B_7); server _job_prims now caches the pure heal per job, keyed on the source file's stat + job tolerance, returned as a copy; run_pipeline primes it, so the first click after an upload is already warm -- measured 6.63 s -> 0.01 s. A changed source, tolerance or re-upload misses the key and re-heals. (2) DELETE: heal_edit gains op 'delete' -- an armed click removes the whole contiguous chain nearest the point (an open stray, or a closed contour on the operator's explicit click), recorded and replayed like every edit, the per-row remove is the undo. Reach gate 0.25 in (the dims panel's picking reach): a replayed delete whose chain left the geometry SKIPS with the refusal's words, never deletes whatever is nearest now; deleting the last geometry refuses. The deleted prims ride in the edit report and the pipeline's fidelity measure excludes deliberately removed ink from the source side (the sheet-intake drops precedent) -- without that the delete read as a giant bogus FAIL and the unmatched points sent the grid ring-search across the whole part (a 15 s hang on a 6-line fixture, caught by the live verify). The gray base layer still draws the deleted ink forever. (3) NAMES: the five lens buttons and three edit buttons now carry our words -- Find open contours / Find duplicate lines / Find tiny segments / Find kinks / Find oversize arcs; Close gap / Make true arc / Drop tiny segments; engine lens keys unchanged. Proven: test_healedit 23->29 controls + 8 real-mouse Playwright checks on a scratch instance; introt 20 / sheet_intake 36 / rules 14 / sketch 21 / ocs 12 / dragcheck 15 green. Server+engine changes live after the next owner-turn restart; the renamed buttons serve from disk immediately -- a Delete click before the restart refuses honestly ('unknown edit op'). EXTENDED 2026-09-24 (Jordan's catch: 'each time I now click on anything, it takes a lot longer to load: 30-60 seconds' -- the same lag ONE LEVEL UP): the pure heal was cached but the EDIT REPLAY never was, and once his 448 Towing M chain gained a drop_duplicates row every geometry-serving click re-ran the whole dedup proof (measured 25.5 s of the 25.8 s replay; _overlap_sweep's 10.9M _pt_prim_dist calls dominate) -- 23 server sites call _apply_healedits per request. FIX: the replay result is cached per job in _apply_healedits (_EDIT_CACHE, the _HEAL_CACHE design): key = hash fingerprint of the input prims AFTER intake rotation (covers source, tolerance, units and the rotation record in one number) + the healedits.json stat; any real change misses and replays, record=True still writes the replay report back and re-keys on the rewritten file's own stat, cached lists return as copies. Measured on the 448 M chain: 25.7 s -> 0.002 s per click, output proven identical, changed edits/prims miss honestly. An edit SAVE still pays one full replay (the busy seam covers it); the drop_duplicates sweep itself stays slow -- a spatial-grid speedup in the nc-audit-perf style is the offered next step. Proven: cache unit proof (hit/miss/record semantics) + live verify_healqc 14, verify_moveend 12, verify_undo 17 (the bytes-restore path must miss -- it does), verify_healadd 12, verify_drawline 32, verify_autoplan 17; engine restarted; zero dev O-numbers.
- •Heal/QC duplicates -- the lens, the one-click Drop fix, and the warn-at-the-door on operator adds record — Built 2026-09-07/08 (Jordan on B7787: assigned a toolpath, 'way too many cuts', clicked Find duplicate lines -- 64 found -- 'How do I fix it now?'; next day 'There are 5 features. Why 7 cuts?'). The lens existed with NO matching fix. heal_edit op 'drop_duplicates' -- ONE recorded edit, no point address: qc.find_duplicates is the SAME detector the lens draws (one detector per defect), so the button fixes exactly what the lens marked. THREE layers, each measured into existence on the real file: (1) PAIR DROPS -- per flagged pair the MORE-covered member is the victim (losing it loses the least unique ink; the detector's fracs ride on the flag now); ties pick the shorter, then the later; an already-dropped member resolves the pair, so chains of mutual copies keep exactly ONE span; victim choice is CHAIN-AWARE first -- a CLOSED chain keeps its member (a closed loop is a feature, the open chain overlapping it is the stray copy), between like chains the higher duplicated-fraction chain loses. (2) PARTIAL victims TRIM instead of dropping whole (_split_covered: coverage runs sampled on the victim against its kept twin at the detector's own DUP_TOL; sub-line/sub-arc on the victim's own geometry; runs under DUP_MIN_LEN absorb into their longer neighbour so boundary jitter never makes a sliver or pin-hole) -- unique ink is never removed. (3) RESIDUAL-OVERLAP SWEEP (_overlap_sweep): the pair gate is mutual >=55%, so a retraced curve segmented differently out vs back leaves sub-gate overlaps after the victims drop -- the sweep runs remaining prims pairwise (bbox prefilter) and trims the more-covered member's overlap to fixpoint; a welded/tangent joint's in-band run is always under the DUP_MIN_LEN floor, so real joints never trim (control 51: an out-leg of two segments + one-prim retrace back resolves to ONE copy, len exact). No duplicates = refusal in the engine's words; replay on clean geometry skips with the same words, never blocks. Removed ink rides the report as removed_prims -- and the fidelity exemption was REDESIGNED for it: exempt DEAD INK ONLY (near removed prims AND no healed counterpart in the band), because a dropped duplicate's KEPT twin still cuts -- the old source-side-only exclusion orphaned the twin's healed points and ring-searched minutes on B7787's 1.3M source samples; the new test keeps the twin measured and by construction can never orphan an output point either direction (the delete op rides the same test, strictly more honest). UI: 'Drop duplicate lines' one-click button in Manual edits beside the lens's own name. Proven: test_healedit 42->51 controls + the real B7787 through the server codepath on a scratch copy -- 64 dropped + the outer profile 1.32-in self-overlap trimmed (its dangling end closed itself), 194->131 prims, QC 139 flags -> 9 (all branch), heal fidelity PASS unchanged, every span cut ONCE -- the doubled lobes halve exactly (28.58->14.29, 53.22->26.61), review tools 11 contours 1 red/6 yellow. What remains on B7787 after the drop is the file's own truth: its strokes BRANCH (QC names them), so the operator resolves leftover construction strokes with Delete/Drop tiny segments -- aid the operator, never guess intent. Live after the next restart; the button serves from disk but rides the new engine. PROOF GATE 2026-09-10 (Jordan's RJB-DS catch on prod -- one flagged pair, his Drop click dropped a junction-wall arc whole, 2 dangling flags, the bridge deviated 27.98 thou; his 'Go' on the proposed fix): the drop must PROVE each removal harmless before it stands -- every removed span's samples must lie within the duplicate band (qc.DUP_TOL) of the ink that REMAINS (heal_edit._removal_dev, measured on the final candidate list so a victim whose cover was itself dropped cannot slip through; failures restore to fixpoint). The RJB failure was the absorption rule eating a diverging tip (0->~20 thou wedge, under the trim floor): a THIN JUNCTION WEDGE now refuses/skips in honest words ('thin junction wedge, not a retrace -- left untouched... use Delete to remove ink deliberately'), the _overlap_sweep proves every trim the same way before committing, and qc.find_duplicates carries the SAME wedge note on the flag itself (wedge field + 'Drop leaves it untouched') so the lens tells you before you click. Skip never force. Proven: test_healedit 51->57 -- the EXACT RJB pre-edit arcs as fixture (lens wedge note, strict refusal verbatim, replay skip, geometry untouched), RJB pair-2 sweep proof with independent sampling, and the full B7787 regression: all 64 real retraces still drop, output BYTE-IDENTICAL to the pre-gate code, worst removed-span deviation 0.00 thou, 0 wedge flags. Neighbour suites green (robust 50 / warns 17 / healedit_noop 8 / healadd 13 / sketch 21 / units_confirm 27 / sheet_intake 36 / dragcheck 15 / introt 24). REAL FILE WIRED 2026-09-10 (Jordan dropped the RJB-DS DXF; testdata/DWS-LH-2.5-LOGO-TREAD-RJB-DS.dxf is the committed fixture): first run on the true file caught a REAL GATE DEFECT the synthetic pair could not -- the proof sampled at 0.02 in and a 7.9-thou diverging bump slipped BETWEEN samples (near other junction ink the coarse samples all read covered), so the wedge dropped anyway; _removal_dev now samples at 0.002 in, well under the 6-thou band (a proof resolution, never a machine number). Proven on the real file end to end: heals 292 prims 0 open, exactly ONE dup flag = the wedge pair (49,50) wedge-noted on the lens; Drop leaves BOTH junction walls standing, the bridge survives, nothing dangles; the one harmless sweep trim proves at 0.56 thou under 0.001-in independent sampling; B7787 stays BYTE-IDENTICAL at the finer proof. test_healedit 57->60. WEDGE NOTES ON THE PANEL 2026-09-15 (Aristide 'Wedge note' -- the queue item offered to Jordan, built on the standing ratified order): the duplicate lens's flags now SHOW each pair's own note in the Heal/QC panel BEFORE the Drop click, client-only over the fields the engine already writes (note + wedge ride GET /healmarks verbatim -- no server or engine change). A wedge-noted pair renders FLAT in warn color, the engine's words verbatim ('thin junction wedge, not a retrace (diverges up to N thou); Drop leaves it untouched') -- unmissable where the operator is about to act; plain retraces fold under one chevron ('N retraces -- Drop duplicate lines removes the redundant copy of each', the grouped-findings pattern, so B7787's 64 never flood the panel); every row navigates -- click frames the pair's spot on the canvas, pulsed (the warnnav gesture); the canvas ring on a wedge flag reads warn instead of the retrace red, matching its note. Proven: app/verify_wedgenote.js 10 NEW live real-mouse Playwright checks over the public URL (both flag kinds on one scratch upload -- the RJB wedge arcs + a doubled line; note verbatim before any click, folded retrace opens to its own words, wedge row zooms 58.5->441.3, Drop takes the retrace and the wedge note + both walls STAND, zero page errors; fixture removed); verify_bandselgeo 13 + verify_snapdrag 10 re-run green. Client-only (app.js/app.css) -- serves from disk, live on refresh, no restart. WARN AT THE DOOR 2026-09-19 (Jordan's '3. I say go'; his doubled triangle edge -- 'I did not add any line twice, but I did click Add': the typed fields mirrored the drawn line and Add committed the span twice): an operator ADD that lands on existing geometry now warns the moment it commits. run_healedits runs qc.find_duplicates over the post-edit geometry (the SAME lens detector -- one detector per defect, so the door warning and the downstream net can never disagree) and names every add row in a flagged pair; the warning speaks on the row itself in the panel (yellow, with the row's own remove control as the one-click resolution) and in the commit toast ('the span would cut twice'). Warn never block: the save stands, the operator keeps or removes. dup_warns persists in healedits.json and recomputes on every save -- a cleared defect never keeps warning, a live one never stops. Customer dirty-CAD duplicates keep the after-the-fact road (lens + Drop duplicate lines) -- same defect class, different moment of detection. Proven: engine controls (add-on-edge warns, twin adds warn both rows, a clear-air add never warns) + verify_drawline 21 -> 24 (twin rows + a drawn-on-edge line warn at the door, removing the twin clears its warning while the live one stands) + healadd 12, gc56 25, healqc 14, setsize 13 green. WEDGE-TIP AMPUTATION QUESTION 2026-09-24 (Jordan's M_9-24-2 screenshot on prod DWS-LH-2.5-LOGO-TREAD-448 Towing.dxf -- the M's centre fork spike circled, welded outline stopping short of the gray source ink; he had already rebuilt the tip by hand with 3 add_line rows): MEASURED offline on the exact replayed edit chain (byte-identical report notes to prod's): the WELD IS INNOCENT -- it outlined exactly the ink it was handed. The spike was amputated one edit earlier by Drop duplicate lines: the source M carries a real needle spike whose two walls MEET at a shared endpoint (10.5518, 0.8723); the left wall was genuinely doubled (a line plus two near-straight retrace arcs -- dropped correctly), but the two CONVERGING walls sit within the 6-thou DUP_TOL band of each other over their last ~20 thou, so the residual-overlap sweep read the tip as a retrace and trimmed -- the contour now peaks 20.8 thou low at (10.5458, 0.8524) and the right wall (source-vertical) is bent 6 thou off. The 2026-09-10 proof gate did not catch it because the flagged-phase proof runs to FIXPOINT against the final ink but the sweep proves each trim only against the list AT THAT MOMENT -- the tip trim was proven against the partner wall that still reached the tip, and the loose-end join repair then pulled that wall down to the trim point; moment-in-time proof, not final-state proof. The contour stayed CLOSED throughout, so nothing flagged. Jordan's hand fix stands (his diagonal add_line is exactly the 20.6-thou lost span); his two vertical add rows are twins 0.4 thou apart and the door duplicate warning correctly flagged BOTH (rows 3/4) -- removing one is one click on its row. OFFERED FIX (unbuilt, awaiting a go): (a) a shared-endpoint junction guard in the sweep -- two prims that MEET at a mutual endpoint and converge into the band form a wedge TIP by construction, never a retrace, skip and count; (b) sweep trims re-proven to fixpoint against the FINAL remaining ink like the flagged phase, restoring any trim whose proof ink was itself later trimmed or joined away; (c) the loose-end join repair never spans more than the duplicate band. WEDGE-TIP FIX BUILT 2026-09-24 (Jordan's 'Go on 1' on the offered fix): all three pieces live in heal_edit, question->record. (a) THE WEDGE-TIP GUARD in _overlap_sweep -- two prims that MEET at a shared endpoint (weld tolerance) and EACH keep unique ink beyond the band converge into the band at that junction: a wedge tip BY CONSTRUCTION, never a retrace; the pair is skipped and counted. A true retrace leaves one member fully inside the band and still drops (the M's own doubled left wall, B7787's 64 retraces). (b) THE FINAL-STATE FIXPOINT -- the whole Drop pipeline (flagged drops, sweep trims, repair joins) now re-proves EVERY removal against the FINAL delivered ink; any failure vetoes that drop or sweep pair and the pipeline re-runs from scratch (restoring only ADDS ink, so it converges); a clean first pass is byte-identical to the old road. The moment-in-time hole is closed: no trim can ever again lean on ink a later trim or join pulls away. (c) THE BAND-CAPPED REPAIR -- the post-drop loose-end join never BENDS ink beyond the band (move_cap on _join): a flexible end moves at most the band; a wider gap closes with an exact rigid connector (RJB-DS's own recorded arc-arc form), nothing moved. PROVEN: the real 448 M -- Drop now keeps the spike (ink reaches the true tip at 0.00 thou, both converging walls END at the tip; dropped 3 / trimmed 6 where the old road trimmed 8), and Jordan's FULL prod edit chain replays right: his weld applies unchanged, his 3 patch rows read as duplicates of the restored walls (0.2 thou off, all flagged) -- three clicks to remove, the M right with zero re-drawing. B7787 old-vs-new BYTE-IDENTICAL (all 64 real retraces still drop). RJB-DS RECLASSIFIED honestly: its one residual sweep trim was itself a junction wedge (two arcs off one shared endpoint, both keeping unique ink -- the old road trimmed it and chamfered the junction with a 50-thou rigid connector); Drop on that file now refuses WHOLE in the lens's own words, both walls standing, geometry byte-untouched -- the suite reworked to the honest form. test_healedit 78 -> 85 (wedge-trio sweep control, full-op tip preservation, capped-join controls, real 448 M end-to-end -- the source now a testdata fixture) + 10 neighbour suites green (weld 24, qc_link 15, healedit_noop 8, healadd 13, setsize 27, setfillet 23, micro_refit, drift_cap, text_floor, isoedit 18); engine restarted; zero dev O-numbers. QUESTION 2026-10-15 (Jordan's mid-plate-1, 'attempting to clean the outer profile and I'm not having luck'): MEASURED -- the file draws the outer's middle V section twice; Drop duplicate lines removed the 5 copies correctly and the outline is geometrically ONE closed loop (36 prims, ends meet exactly), but the drop leaves the surviving pieces in list order as TWO runs pointing the same way, and every consumer groups contours by list order -- so Tooling reads the outer as two features (26 + 10 prims), the 10-prim piece is planned as an 'inside' feature with no lead (pierce on metal, clear air 0.000) and the RED comp-wrong-side on features 2+4 follows. Proven on a copy: heal.chain_contours over the saved geometry gives 3 closed contours (outer 36 + two slots), zero welds. Proposed fix: re-run chain_contours after the edit replay (nothing moves, ends already meet; contiguous lists come back in the same order). The two slot pierce yellows (0.0817 < 0.15) are honest -- 0.164in slots can't give clear air. Nothing built, awaiting go. ROOT-CAUSE QUESTION 2026-10-15 (Jordan, after the mid-plate-1 diagnosis: 'I sense something deeper here'; the job ran on app and the defect reached the end customer): (1) RED NEVER SURFACES DOWN THE LINE -- measured in code: every stage status is one word 'flagged' for red AND yellow (server stage writers; app.js DOT flagged='!'), so the tab glyph and plain tooltip 'has warnings' are identical for a do-not-run red and a routine yellow; the NC header is one count '(THIS FILE HAS N WARNINGS)' with no severity (nc_warn); mid-plate-1's red comp_wrong_side has been in review on every dev upload since 2026-09-25 (1790336856, 1790885163, 1792085853) and QC flagged 6 duplicates + 4 open-from-doubled-ink each time, same '!'. The prod run's exact path not seen from here (no prod access). (2) THE CLEANER NEVER COLLAPSES DOUBLED INK -- heal() has no duplicate step (only point-level _dedup); doubled ink is detected by QC and fixed only by the operator's Drop duplicate lines click, even when the copies sit 0.001in apart under a 0.010 cleaning tolerance; the drop's own proof gate already exists. (3) the re-chain gap after edit replay (diagnosis above). PROPOSAL (nothing built): A red is its own status everywhere (own glyph/colour on tabs, Part list card, Nest/Post/Deliver, delivery banner; red count named separately in the NC header) -- still warn-never-block, but impossible to miss; B cleaner auto-drops doubled ink proven inside the cleaning tolerance (same proof gate, recorded + removable, Intake note says what was dropped), the button stays for wider cases; C re-chain after every edit replay; D yellow audit -- measure which yellows fire on most jobs and are honest-but-unactionable (e.g. narrow-slot pierce) so yellow means something again. Awaiting Jordan's go per chunk. | 2026-10-15 JORDAN'S FOLLOW-UP (question): (1) 'It seems to do this on other parts' -- he is right, MEASURED on dev: 86 of 1006 cleaned jobs still carry doubled ink after the cleaner (QC 'duplicate' > 0; 40 with open contours caused by it), incl. the 23004 family (10-25 each) and the BNM 78598 grill (60) -- general, not mid-plate-1 only. (2) His narrowing of A: a red in Tooling must turn the Tooling tab indicator red, today it shows the same yellow '!'. Measured: review stages already record red/yellow counts (job.json stages.review.red), and the tab glyph comes from status only (app.js DOT flagged '!', rank blocked>flagged>pending>done) -- so the tab fix is client-side; 594 reviewed jobs on dev: 223 flagged, only 26 carry a red, 197 yellow-only all wearing the same '!'. (3) His shop note: operators ask 'why X warnings?' on every program and are told to ignore it -- supports D. Nothing built; awaiting his go on the tab-red chunk. | KITS ALREADY MERGE, SINGLE PARTS DON'T 2026-10-15 (question; Jordan: 'I thought we were already doing this ... how were the Torongo files handled?'): measured in code -- three roads. (1) heal() drops only EXACT twin entities (dxf_io.drop_duplicate_polylines, every vertex within 0.0001in, same bulges; TL-1016-93 lesson). (2) a multi-part file through the split door runs split_parts.close_scan_fragments at 0.020in (his 2026-08-11 TL-1016 ruling): an open chain whose every sample lies within 0.020 of other geometry is dropped, coverage-gated, one at a time -- and the child part files are written from that repaired ink, so kits (TL-1016 / Torongo style) DO get in-tolerance doubles merged. Deterministic code, no hand work. (3) a single-part file (split refuses 'this file is a single part') never reaches that step, so it keeps every near-double -- mid-plate-1's 0.001 V. My earlier 'nothing between 0.0001 and tolerance merges' was wrong for kits, owned. Downsides of merge-at-tolerance named: real features closer than tolerance (thin slits/webs, fine text), partial overlaps, which copy survives (up to tol shift), junction wedges (the RJB-DS/M wedge-tip cases). Proposal B refined: run the Drop duplicate lines op (its proof gate, wedge-tip guard, final-state fixpoint) automatically at the job tolerance on every upload, as a recorded removable row, count reported. Nothing built. SPLIT-ONLY REPAIRS: SINGLE-PART FILES MISS FOUR 2026-10-15 (pin `healqc-drop-duplicates` extended, question; Jordan: mid-plate-1 came in the Roush package, "why would a single part vs a kit ever be treated differently? what else have we missed?"): "kit" in the code means ONE file holding 2+ parts -- a multi-file package is split file by file, and every one-part file is refused by the split door and used as uploaded; all 47 Roush files on dev took that road (0 split). Repairs that live ONLY in split_parts.part_groups, so single-part files never get them: doubled prims within 0.005in, duplicate fragments within 0.020in, self-overlap overrun trim, gap bridging up to 0.020in (the general heal joins ends only within 0.0001in). Cause = the TL-1016 repair was built at the split door because that is where the -93 missing part showed, never moved into heal; my design gap. Proposal: move the four into the one road every file takes, at the job tolerance, as removable recorded rows. Nothing built, zero dev O-numbers. AUTO DROP OF DOUBLED LINES AT UPLOAD 2026-10-15 (pins `jordan-fix-list-2026-10-15` + `healqc-drop-duplicates` extended, Jordan '2. Go'): a NEW job's first heal runs Drop duplicate lines by itself -- same detector, same proof gate, recorded as ONE removable Heal/QC row (source auto, labelled 'done automatically at upload'); only when every removal proves within the 6-thou band and the job tolerance is not tighter; verdict on job.json so a removed row never re-adds; older/edited/sketch jobs untouched; qc.find_duplicates early exit 3-10x faster, flags identical (35 real jobs + random control); mid-plate-1 drops its 5 by itself, RJB wedge left with its reason; upload time unchanged (3.6->3.3 / 47.7->44.1 / 11.6->12.9s); test_auto_dedup 20 + healedit 99 / qc_link 15 / tol_door 14 / drift_cap / dashed_ink 22 / healunits_cancel 30 / sheet_dimpart 23 green, identity gate green, F1 8.92/8.12 + 9.09/8.22 -> 8.78/8.24 + 8.97/8.37s no cost, zero dev O-numbers. (Item 2 BUILT; mid-plate-1's outer still plans as two features until item 4.) AUTO-DEDUP NEVER INVENTS OPEN ENDS 2026-10-15 (Jordan 'Go on A', record): the upload-time automatic Drop duplicate lines now records NOTHING when the drop would leave an open end (gap or dangling) the file never had -- server._new_open_ends compares open-contour flags before vs after, skipping a there-and-back line's own true two ends (one duplicate pair as the only ink meeting there = honest, not new); a refusal lands on job.json auto_dedup in plain words naming the count and the first spot, left for the operator's own Drop click. Correction owed and given: grill part 41 was a bend line drawn there-and-back -- dropping one copy only shows its real two ends, it still drops. Measured on dev (41 jobs before the sweep was stopped): 18 drop / 23 refuse -- mid-plate-1 x3, 448-fork x3, b7787 and most grill parts still drop; grill parts 26/31/33/42/55/61 refuse (1-2 new ends each, 55 at (7.7632, 0.1339), 61 at the 14.664,0.7235 gap); 23004 unextracted sheets refuse with 5-20. TRADE stated: a refused part keeps its doubled ink and would cut twice until the operator clicks Drop duplicate lines. test_auto_dedup 20 -> 25 + healedit 99 / qc_link 15 / tol_door 14 green, identity gate green, F1 8.47/7.76 + 8.40/7.76s no cost, zero dev O-numbers. OUTLINES RE-JOIN AFTER AN EDIT REPLAY 2026-10-15 (pins `jordan-fix-list-2026-10-15` + `healqc-drop-duplicates` extended, Jordan '4. Go'): NEW heal_edit.rejoin_runs runs after every edit replay (_apply_healedits, the one road every stage reads) -- open pieces of one outline that meet end to end but sit apart in the list are put back together, reversed when needed; reorder only, nothing moved/added/dropped, 3-way nodes left alone, unsplit lists unchanged. Dev sweep 45 edited jobs: 43 identical, 2 changed -- mid-plate-1 4 -> 3 features (red wrong-side comp + needless tab gone), B7787 9 -> 5 features (his '5 features, why 7 cuts', red + 4 yellows gone); NEW test_rejoin_runs 12 + 11 neighbour suites green, identity gate green, F1 8.34/7.69 + 8.33/7.67 -> same, no cost, zero dev O-numbers | DOUBLED-CUT + SPLIT-OUTLINE AUDIT CHECK 2026-10-16 (item 5, Jordan '5. Go'): NEW rules.check_double_cut -- ONE rule, both surfaces (check_plan = Tooling review / drag judge / part-list pack; nc_audit = every posted program, macro copies folded by merge_copies). YELLOW doubled_cut: a feature lying within 1.5 thou of another feature's path (or of its OWN path further along -- B7787's outers retrace themselves) for 0.1 in or more, named with the shared length; YELLOW split_outline: an open feature whose end meets another feature's end within 2 thou (one outline cut as separate pieces). Etches ignored; warn never block; Colours label 'Doubled Cut' / 'Split Outline'. Works on the program's own lines/arcs on a 0.25 in grid, samples only pieces where two passes meet. Proven: mid-plate-1 raw = doubled 3+4 9.068 in, before item 4 = split 2+4, after = clean; B7787 raw = 5 self-retraces, before item 4 = 4 split pairs, after = clean; 604 stored dev review plans -> 17 jobs hit, every hit genuine (448 fork strokes, dirty CAD, mid-plates, front-wall open retrace); NEW test_double_cut 12 controls (kissing circles + tabbed loop silent, 0.001 flagged / 0.003 not, engine post -> audit -> header '2 YELLOW') + 20 neighbour suites + verify_warnnav 10 green; identity gate green (no golden case carries either); O33289 532 parts 0.53 s per audit pass; F1 8.35/7.67 + 8.36/7.70 -> 8.55/7.88 + 8.56/7.87s (+0.2s, under both thresholds); stated limit: a there-and-back reads up to one cell short at its turnaround; zero dev O-numbers. | AUTO CLOSE OF SMALL GAPS 2026-10-16 (fix list item 6 / fix B): new op close_gaps (heal_edit._close_gaps) recorded automatically at upload after the auto drop, at the job's heal tolerance -- see pin jordan-fix-list-2026-10-15. | DOUBLED-INK SWEEP 2026-10-16 (question; Jordan 'run it'): read-only sweep of 1018 dev jobs (9 skipped) -- 99 still cut doubled ink, all made before the upload auto drop; re-upload simulated on 96 (3 too slow): 35 come out clean, the rest leave five cases: (1) auto drop refuses, would leave open ends -- 30 jobs (grill bend-line parts, 23004 sheets, F1 RELEASE); (2) junction-wedge proof refuses -- 12 (RJB family, by design); (3) near copies 6-10 thou apart -- 33 jobs / 230 lines, mostly parallel pairs ~9-10 thou (grill bend lines, F1 RELEASE, 23004), outside the duplicate band AND the 1.5-thou double-cut warning, so nothing warns; (4) partial overlaps (short line on a long one, overruns) -- 12 jobs / 23, qc.find_duplicates' mutual-coverage rule misses them; (5) same curve drawn two ways (line over arcs, arc over facets) -- 11 jobs / 20, missed too (synthetic arc + 40 facets: 0 flags). Full circles caught (heal makes two halves). Layer/block copies not separable from cut geometry, unmeasured. Nothing built, zero dev O-numbers; scripts /tmp/dupsweep. | PARKED 2026-10-18 (Aristide "do 1 now"): the black-box drop-duplicates speedup WIP (heal_edit.py, was only in /tmp/fixA_speed, Oct 15) saved off-box as branch parked/drop-dup-speedup-2026-10-15 (39e3e3ee, base e7f418b, +104/-11). Not merged, not tested, predates cancel_poll -- merge by hand on a go. | 2026-10-31 O74 DUPLICATE CHECK SPEED (Jordan: BNM78598 upload sat 1000+ s on dev; "If you are confident ... we will try your fix"; tag pre-dupgrid). Cause: the duplicate finder (qc.find_duplicates), the drop sweep (heal_edit._overlap_sweep) and the removal proof (heal_edit._removal_dev) boxed every arc by its WHOLE CIRCLE and compared every prim with every prim; BNM78598 (mm DWG, 12,094 LINE + 8,121 ARC -> 9,956 healed prims) carries 2,341 near-straight arcs up to r=9916 in, whose circle boxes met every prim on the sheet. Fix, exact by construction: arcs boxed AS SWEPT (ends + axis points inside the sweep; a closed arc keeps its circle); find_duplicates takes candidate pairs from a grid of those boxes in the same (i, j) order; the removal proof measures each sample through _NearIndex (grid, then every prim whose box comes within the first distance -- the same minimum float the full scan gives). Per-pair tests unchanged. Proof: find_duplicates old vs new identical on 1,236 small + 22 large dev files and 300 random sets incl. giant arcs (4,719 flags); drop_duplicates old vs new identical on all 34 dev files with doubles; _NearIndex == full scan on 3,000 BNM points; test_auto_dedup 25/25, test_healedit 99 PASS, test_qc_link 15 PASS. BNM: duplicate check >1000 s -> 0.4 s (8 pairs); drop_duplicates 14.6 s (8 dropped, 57 wedges left); full upload not re-run (the cancel deleted the file -- Jordan re-uploads). F1 first click 7.72/7.74s -> 7.70/7.75s, repeat 7.52/7.55 -> 7.51/7.61 (no change). Identity gate green. | 2026-10-31 dev restarted 20:32:26 UTC on Jordan's 'restart' (both inflight 0 before), O74 dup-check fix (0e94c725) now live on dev; plnew probe 404 on made-up id as expected. Identity gate green.
- •Drag any healed endpoint and magnet it to the SOURCE layer's own points -- recorded move_end op, a shared corner drags AS ONE (Jordan's ask mid hand-repair of the 448 Towing M; his 'Drag as one. Go', 2026-09-24) -- BUILT record — RECORD 2026-09-24 (Jordan on M_9-24-26 mid hand-repair of the amputated M spike: 'I am able to insert new lines manually, but it would be nice to be able to click and drag the blue endpoint and magnet it to the corner from the source file'; his numbered answer same day: '5. Drag as one. Go'): the Drag end to point gesture now grabs ANY healed endpoint -- a loose end or a shared corner -- and a drop near a point of the gray SOURCE layer lands the end exactly THERE. ENGINE: NEW heal_edit op move_end {near, to} -- the endpoint node nearest `near` (qc._weld_nodes arithmetic, _SNAP_REACH replay gate in the op's own words) moves to `to`, and a SHARED corner drags AS ONE per Jordan's ruling: every prim end welded at that node moves together, any member's refusal refuses the WHOLE edit with nothing moved (atomic). Per-prim rule: a LINE end re-aims (pivots about its far end, zero-length collapse refuses); an ARC end keeps its RADIUS and its far end -- the center re-fits through both on the SAME side of the chord (minor stays minor, direction kept; a drop past 2r refuses naming the most the arc can span; closing onto its own other end refuses -- a full circle is add circle's job). A full circle never grabs, and a CIRCLE's own two-arc SEAM refuses in honest words (the CIRCLE diet's construction point is never a corner) -- engine guard + client filter, one judgment. Recorded/replayed/removable like every heal edit; strict=False skips in the same words. BOTH fidelity exemptions ride the row (removed_prims = the old aim's dead ink, joins the move_chain unconditional source-side exemption; added_prims = the re-aimed ink, output-side) and the moved endpoints join the find_jogs exact_pts exemption per the add-ops precedent -- the re-aimed corner's angle at BOTH its ends exists by the operator's design, never the fitter's hand (test control: jog without, clean with). CLIENT (Drag end to point mode): hqGrabEnds marks every endpoint node -- loose ends keep their full rings and their recorded carrier slide (snap_end, byte-unchanged on a free drop), junction corners draw small faint rings and ride the cursor free; the aim magnets to hqBasePts = the source layer's own endpoints + arc centers + full-circle QUADRANTS (grown this build), Alt suppresses the magnet (house convention), gc56 aim feedback names the grab ('grab this corner -- its N segments drag as one') and the drop ('lands on the marked source point' / 'corner moves as one'); a magnetted drop -- or any corner drop -- records move_end, so the end lands AT the customer's own ink, never carrier-projected near it. BAND SELECT grabs loose ends only (a corner grab would eat every band over dense geometry) and draws no corner rings there. DELIBERATE BEHAVIOR CHANGE stated: a LOOSE end dropped on a source magnet used to record snap_end (carrier-projected landing); it now records move_end and lands ON the point -- Jordan's exact ask; the carrier slide remains on every free drop and under Alt. Proven: test_healedit 85 -> 99 (drag-as-one, arc re-fit side/radius, atomicity, seam/reach/collapse/no-op refusals, replay skip, jog-exemption control) + NEW app/verify_moveend.js 12/12 live real-mouse (corner grab, magnet drop onto a source point both walls land, no fit-jog at the moved corner, replay + restore, Alt free + Escape, reach + seam refusals verbatim, band unbroken) + verify_snapdrag REWORKED 10/10 to the lands-on-the-point form + gc56 25, drawline 32, healqc 14 (first-run miss = the suite's own read race, rerun clean), healadd 12, ctxmenu 26 + globalband 13 / bandselgeo 13 (suite-fix only: their loose counts now filter the corner nodes the grab list carries) + 9 engine neighbour suites green. Engine restarted; zero dev O-numbers.
- •Upload door reads more than DXF: flat STEP exact, .ai/PDF at a stated width, DWG via LibreDWG conversion, honest refusals for the rest record — Built 2026-09-08 (Jordan: 'I need to be able to upload files other than DXF to the interface'). The app's one upload door now switches on extension; everything rides the SAME run_pipeline after conversion, nothing downstream knows the source format. FLAT STEP (.stp/.step): step_flat.py -- the proven build-151 path factored into an engine module. STEP carries true curves, so the top Z-normal planar face's outer+hole loops convert EXACTLY (full circle = the CIRCLE diet's two semicircle arcs), nothing healed away; units are the FILE'S OWN statement (CONVERSION_BASED_UNIT 'inch' = native inch untouched, else SI mm /25.4 in doubles), recorded and PINNED -- run_pipeline never re-infers a converted file's units from the written R12's magnitude (the sketch lesson generalized: job.units_pinned; the units-confirm modal stays off, the flip door refuses in honest words -- there is no unit question). A BENT part (cylindrical wall whose axis is off the sheet normal -- a bend, never a hole barrel) is a BLOCKED intake in the engine's words naming the K-factor (a materials-table value, ruled 2026-08-31) -- unfold is not wired into the door yet; the file is preserved. Broken topology / non-LINE-CIRCLE flat edges refuse rather than guess. VECTOR ART (.ai/PDF): the sheet-intake pattern -- the upload is PRESERVED as vector.<ext>, intake FLAGS with the stated-width door (an .ai/PDF carries no real-world dimension; the scale is NEVER a guess, PINLIST 14b's gate now an interface door). POST /api/jobs/<id>/vecextract {width} runs the proven vec_pipeline.read (true Beziers re-fitted to real arcs, specks dropped, fills/live-text counted) -> CAM-safe source.dxf -> run_pipeline; units pinned to the operator's statement; the conversion report (paths, Beziers->arcs+lines, specks, worst kink) renders on the Intake drawer with honest YELLOWs for live text (outline it and re-upload) and fills (strokes only, per the customer guidelines); re-convert at a new width always re-runs from the preserved file, the standing stale rule dropping downstream judgments with numbers kept. Refusals plain-400 in the engine's words, nothing changed. REFUSED AT THE DOOR (plain 400, nothing saved, honest words): DWG (binary, names the export-DXF ask), SVG (no reader yet), raster photos/scans (the 3A76 draft-only ruling -- ask for native CAD first), unknown extensions. Proven: test_upload_formats.py 17 NEW controls (build-151 numbers reproduced through the door: 37.15625 x 3.0 x 0.0625, 6 holes; bent BNM78651 blocked verbatim; EAGLES.ai at width 12 -> part measures 12.0000, re-convert at 24 re-runs; DXF path regression) + app/verify_upload_formats.js 8 live real-mouse Playwright checks on a scratch instance; neighbour suites green (units_confirm 27 / sketch 21 / sheet_intake 36 / healadd 13 / healedit_noop 8 / introt 24). Honest limits: STEP flats only (bent-part unfold delivery stays the board-script path until the K-factor column lands); .ai/PDF wants the width of the WHOLE artwork (one number, the vec_pipeline contract); SVG stays the recorded next reader; a drawing-sheet PDF print (pdf-dims-govern) is NOT this door -- vector art converts as drawn geometry, callout-driven rebuild stays its own goal.
DWG INTAKE 2026-09-19 (Jordan: 'are DWG files going to work?' before his 'Go' on the upload slate): .dwg joins the door. The server converts through LibreDWG's dwg2dxf reader (binary resolved from PATH, ~/.local/bin, /usr/local/bin, then app/tools; temp-dir conversion, 120s timeout) and the converted source.dxf rides the SAME pipeline as any DXF -- nothing downstream knows the source format, exactly the door's standing rule. The customer's original is saved as source.dwg beside the converted file and offered on the Geometry tab's Intake section (the job-file GET route serves it as octet-stream); jrec.dwg_convert records the conversion and the Intake drawer states it in plain words. A DWG that will not convert refuses in the converter's own words, including the honest 'no converter installed' when the binary is absent. PROD CAVEAT, flagged to Aristide for Sem: the converter is installed only on the dev box today (aarch64 build, deps libc/libm only); prod refuses DWG with the honest words until LibreDWG lands there -- decided NOT to vendor the 43MB binary into git. Proof fixtures: incoming ex_7.dwg (clean 2-part kit -> converts, splits, 2-row list on the one road) and the 3A76 DWG (dimensioned drawing -> converts, sheet-detected, direct door BY DESIGN). Trust boundary: LibreDWG's WRITER (dxf2dwg) emits broken files -- never fabricate DWG fixtures with it; only the reader is trusted. NEW app/verify_dwgtray.js 20/20 + multiupload 12, upload_formats 10, oneroad 17, srcdl 13, tray 18, plpick 17, pltabs 19 green. PROD CONVERTER REPORTED INSTALLED 2026-09-29 (Sem, via Aristide: 'all resolved'): dwg2dxf on the prod box -- the dev-only limit lifts; verify with the first real .dwg upload on prod (a miss still refuses in the honest 'no converter installed' words, nothing breaks).
- •Units confirmation on first open: autodetect proposes, the operator confirms; the BIG RED warning only on the extremes; 2026-09-20 -- per-card in/mm toggle on the part list (kit flips as a set), interrupting modal narrowed to the extremes, one-suspects modal at the tray door record — Built 2026-09-04 (Jordan, from the 44558B_7 lesson: 'we should ask the first person who opens the file to confirm the units ... a BIG RED warning ... only the extremes ... the extreme can go both ways'). ENGINE: dxf_io.to_inches(force='in'/'mm') -- the operator's statement outranks the header AND the magnitude inference (a header can lie: 44558B_7 declares $INSUNITS=1 on a metric part); note says 'operator stated'. SERVER: the intake record carries units_confirm -- what ran (in/mm), its source (header/inferred/operator), the part size under BOTH readings, confirmed flag, and the extreme red: fired ONLY when the reading that ran is wildly implausible AND the opposite reading is a plausible part (0.25 in to 2x the bed) -- both directions, exactly Jordan's two cases; an operator's statement clears it (their call stands). THE LARGE THRESHOLD IS THE MACHINE TABLE ITSELF (Jordan, 2026-09-04 refinement: 'Make the large threshold the table size, i.e.: greater than 120 inches with the GX 10K') -- read off tables.bed() at judgment time, never a literal; the message names the table ('bigger than the 120" machine table'); bed rides on /api/materials so the client's pre-block display mirror reads the same value. THE SMALL EXTREME IS PER-FEATURE CONSISTENCY (Jordan, 2026-09-04, the 50-unit-circle example: a 50mm ring whose perimeter holes read ~0.010" is the giveaway the file was inches -- 'a human would understand as being absurd'; the part itself is a plausible 2", so the whole-part bbox never sees it): the red also fires when at least 3 closed interior features, and at least half of them, each measure under 0.030" in the reading that ran AND read sensible (over 0.030") the other way -- both-ways gated per feature, so a couple of dirt artifacts on a correctly-read file never trip it, and the message reads the example back ('6 features measure ~0.010" -- absurdly small to cut; read as inches ~0.25"'). The 0.030" feature bar and the 3-and-half consistency counts are my picks, invited to change; the whole-part 0.25" rule stays as the degenerate case. Feature sizes come off the healed contours (heal chains them contiguously; open strays are dirt and stay out); the client pre-block mirror stays bbox-only honestly -- the authoritative feature judgment arrives with the server record. POST /api/jobs/<id>/units {units}: confirming WHAT RAN is RECORD-ONLY (downstream stages stand untouched -- a re-run would drop stages over a no-op); flipping re-runs the pipeline at the true scale and the standing stale rule fires (downstream drops, O-numbers kept, deliveries marked). Refusals plain-400 in honest words (sketch = typed in inches by definition; part list = no geometry of its own; junk value). The heal cache keys on the statement -- a flip can never serve stale-scale prims (_job_prims re-heals with the force). UI: the modal auto-opens on FIRST OPEN of a job whose fresh intake record is unconfirmed (once per session; Later defers) -- Inches/MM toggle preselected from autodetection, one click throws it the other way, the size shown under the selected reading, the red banner on extremes; records healed before the block confirm via the Intake tab's 'confirm / change units...' door (no nagging of already-worked jobs), which shows the server's red on the tab too. SAME BUILD (Jordan's two interface asks): a PROCESSING INDICATOR (spinner overlay) on upload and on the units flip -- before this an upload showed nothing until the job appeared; and the tool palettes carry a slight white glow in dark mode / a slight drop shadow in light. Proven: test_units_confirm.py 25 controls (6b: 150-inch fires under the table-size band; 6c-6f: Jordan's ring example fires as mm / clean as inches, genuine mm part clean, two artifacts stay quiet) + app/verify_units.js 16 live Playwright checks on a scratch instance (fixtures cleaned); introt 20 / healedit 29 / sketch 21 / ocs 12 / sheet_intake 36 / dragcheck 15 / rules 14 green. Server+engine live after the next owner-turn restart; CSS/indicator serve from disk immediately (the modal needs the restart -- it rides the fresh intake record and the new endpoint). UNITS FORCE RIDES EVERY RE-PARSE (same day, later -- found processing Jordan's bypass request, 6 x 44558B_10 on .080" steel): NINE server sites (run_review, dragcheck, quote, single-part post, postnest, both deliver DXF writers, the three part-list referenced-job heals) re-parsed source.dxf with a bare to_inches(), dropping the recorded statement -- on the lying $INSUNITS=1 header every one of those stages ran 25.4x too big under a confirmed mm force (44558B_10's persisted review carried coordinates to 59.55 on a 2.34" part while nest.json, reading part_bbox, sat at true scale). Fix: one helper _ufv(job) (sketch = never forced) passed as force= at all nine sites; _job_prims reads it too. test_units_confirm 25->27 (controls 21/22: a lying-header job flipped to mm reviews at its true 3.94" scale). The job re-ran at correct scale via the server codepath offline: review Mild Steel,0.08, nest 6 = 1x6 in Y, O33339 macro post, part DXF census PASS. Live after the next owner-turn restart. RADIO ROWS + STATED CONFIRM 2026-09-11 (Aristide's screenshot catch: the two-button toggle lit the UNSELECTED side brighter than the selected one -- inverted emphasis -- and the size consequence sat in small print; his pick of the offered options, 'be prepared to roll it back'): client-only redesign of the modal's selector -- radio-style rows, each carrying its reading's size IN the label at full size ('Inches (autodetected) -- reads 400.00" x 90.00" -- bigger than the 120" table' flagged red / 'MM -- reads 15.75" x 3.54"'; over-table flag is a display derivation off S.matopts.bed, the server's extreme judgment stays the red banner), and the commit button states the decision ('Confirm: Inches' / 'Confirm: MM') so a misread selector can never confirm the wrong thing unnoticed. verify_units.js updated to the new contract, 18/18 green on a scratch instance. Client-only (index.html/app.css/app.js) -- serves from disk, live immediately; one commit for a clean rollback if Aristide dislikes the look. FLOATING ELEVATION 2026-09-11 (Aristide, same thread: dark-mode modals and palettes must 'come off the screen a little better to indicate floating'): one shared --float recipe (dark: hairline light rim + soft glow + deeper drop; light: shadow alone) on all ten floating surfaces incl. floating panels, menus, every modal card and the toast; docked palette glow strengthened. Client-only, live immediately; verify_units 18/18 green. MOVABLE MODALS 2026-09-11 (Aristide, same thread, on the elevation screenshot: 'can you make these modals movable? so I can look behind the modal?'): all four modal cards (units, shop setup, colors & legend, bug report) drag by any spot that isn't a control -- the heading shows the grab cursor; the card moves over its centered base position, clamped fully inside the viewport (the panels' never-lost rule), and every fresh open re-centers it (position is transient, nothing stored); a drag starting on a button/input/label never moves the card, so no control loses its click. No backdrop-click-close exists on these modals, so a drag can never dismiss one. FIXED ON THE WAY (caught by the verify's real mouse): the shop-setup and bug cards had no max-height -- on a short window the wizard card overflowed BOTH screen edges, heading and buttons off-screen (its h4 measured at y=-111 in an 800px viewport); wizcard/bugcard/unitscard now carry max-height 88vh + inner scroll (the colcard precedent). Proven: app/verify_modaldrag.js 7 NEW live real-mouse Playwright checks (drag moves, off-screen throw clamps, button-drag no-op, reopen re-centers, wizard clamped at the bottom edge) + verify_units.js 18/18 re-run. Client-only (app.js/app.css) -- serves from disk, live immediately. UNITS PIN RIDES EVERY RE-PARSE 2026-09-15 (Jordan's Nest_9-15-1 screenshot -- the 7497/7498 part-list nest stacked parts on top of each other at qty 1): the pipeline honoured units_pinned (converted/split source.dxf written in inches by construction) but _ufv -- the one helper every re-parse site passes as to_inches(force=) -- only carried the OPERATOR'S force, so every re-parse re-ran the magnitude inference per site. 7497's split children carry giant-radius arcs whose full-circle padding inflated the written R12 header extents ~25x (the view-extents defect class, in the WRITER this time), the inference read those children as mm, and the part-list pack placed 25.4x-shrunk outlines at sliver pitches -- the pile-up on his sheet. Fix, both halves in one commit: _ufv returns force 'in' for any units-pinned job (one seam -- all thirteen to_inches sites fixed at once; run_pipeline's pinned branch keys the heal cache the same way), and emit.write_dxf_shop's $EXTMIN/$EXTMAX now run emit._arc_extremes (the one arc-extents arithmetic) instead of center+/-radius, so a written file's own header tells the truth. Proven: test_split_door 13->17 (child pinned, _ufv carries it, sketch/force regressions) + test_view_extents 8->9 (giant flat arc round-trips through the writer and reads inch) + units_confirm 27 / sheet_intake 36 / upload_formats 17 / part_list 28 / pl_deliver 27 / plhand 25 / pl_post 26 green. Jordan's list re-packed through the live server's own door: 14 parts over 2 sheets, zero overlaps, audit +0.005 over ruled. Restarted same turn -- LIVE.
PER-CARD IN/MM TOGGLE + EXTREMES-ONLY DOOR CHECK (2026-09-20, Jordan: 'wouldn't an in/mm toggle in the Part List next to rotation/etc be a logical idea? That way the operator can clearly see something is wrong by the overall X/Y dimension, and have a quick toggle?' -- his 'Go' on the three-part proposal): (1) every part-list preview card carries an in|mm toggle beside qty/rotate/bridge/filler showing the CURRENT reading; clicking the other flips through the same recorded /units door -- re-heal at the stated scale, plans drop by the standing stale rule, the packed nest updates itself on the next Nest/Post landing (the auto-update machinery), one heavy undo step. UNITS BELONG TO THE FILE, not the row: a kit-born row (split child) shows and flips its parent FILE's reading and the whole set moves together -- half a kit can never be metric; the card tooltip says so. (2) SERVER KIT CASCADE: run_units on a split child ROUTES to its parent file; a flip on a split parent rescales every live child IN PLACE via _kit_cascade -- the child keeps its job id and every list reference, its units_pinned gains the corrective scale (ratio of the parent's new scale to old; returns to exactly 1.0 on a flip-back), dxf_io.to_inches grew a NUMERIC force so the pin's scale rides ALL the _ufv re-parse sites identically, and the child re-heals through its own pipeline (a refusing child lands blocked and named, never silent). (3) EXTREMES-ONLY INTERRUPTION: the first-open modal now fires only when the server's own extreme judgment speaks (bigger than the machine table / absurdly small) -- routine files keep the question one click away on the Intake section and the card toggle (the LIST is the review surface; supersedes ask-every-file at the door on Jordan's word). The tray drop gets the same rule: after the batch, ONE modal (uxmodal) lists just the suspect files with the big red words and an in/mm pick each; Confirm posts through the same /units door (a flipped kit cascades server-side, split already done or not), Later leaves the question on the cards. Proven live on dev: two-part mm kit uploaded, split, flipped in<->mm through a CHILD's card toggle -- both children rescale 3.94in <-> 100.00in, pin scale 25.4 then exactly 1.0 back, parent record follows; tray drop of an extreme file ($INSUNITS=1, 300in) + a routine file -- only the extreme listed, MM pick re-healed it, the routine file sailed through unconfirmed-and-unnagged. verify_pltabs 24 + partnav 15 green same turn. Suites that WAIT for the routine-file modal (oneroad, units, dwgtray, multiupload lineage) are now design-stale -- QUEUED for rework, stated.
- •Inches-only display; splines ride the gray base layer; material dropdown = EVERY Rev2 row grouped by type record — Built 2026-09-04, Jordan's three screenshots on 44558B_10. (1) INCHES ONLY (Jordan: 'don't display results in feet, keep all the results in inches'): the units modal / extreme-red sizes read inches at any magnitude -- server _size_words and the client formatter both; test_units_confirm control 4 now asserts inches, verify_units.js updated. (2) SPLINES ON THE BASE LAYER (Jordan: 'the background original cad layer isn't displaying splines. Am I correct?' -- he was): SPLINE/ELLIPSE entities are never folded into the polyline model, and _seg_json_source only walked polylines, so the 44558B_10 slot end-caps drew on the healed overlay but not the gray original. The base layer now samples splines+ellipses off the analytic curve (~0.02" display spacing; fidelity keeps its own 0.001 path), and _rot90_parsed rotates spline ctrl points + ellipse centre/major vector -- closing a LATENT frame bug: the shallow dict copy shared the UNROTATED lists, so a quarter-turned spline file would have measured fidelity against the wrong frame. test_introt 20->24 (spline cap on the base layer, rotated frame, heal PASS both ways). (3) MATERIALS FROM OUR TABLE (Jordan: 'the drop down is missing most of the material from our tables ... present me in this dropdown based on material type first, then the values that apply to that material type in a sub-menu'): material_options() offers EVERY Rev2 row -- 71 rows, 6 groups -- labels from the table (the '(MSO7)' old-CAM suffix dropped); one shared client builder renders native optgroups (type first, rows under it) in all three material selects (Part review, Quote, Part list) -- works identically on the three lenses. The recorded Mild Steel<->MSO7 post pairing is kept where the materials.json row exists; ANY other row (Stainless, Aluminum, Brass, Copper, Galv, unpaired Mild Steel gauges) carries its own Rev2 key as the post key, so a stage needing materials.json values refuses IN THE TABLE'S WORDS naming the row ('a new material is a row someone types') instead of the row vanishing -- Jordan feeds the values for Steel, Stainless, etc. and rows come alive as they land. test_matoptions.py NEW 10 controls + verify_matmenu.js NEW 9 live Playwright checks on a scratch instance (grouped optgroups, honest Stainless refusal verbatim, MSO7-paired row still plans, base-layer spline ink); verify_units 16 green with the inches wording. Suites green: introt 24 / units_confirm 25 / matoptions 10 / sheet_intake 36 / healedit 29 / sketch 21 / ocs 12 / dragcheck 15 / rules 14 / tooling_doc 37. Server-side: live after the next owner-turn restart; the client optgroup builder + inches formatter serve from disk now (pre-restart payload degrades gracefully to the old 8 rows, grouped).
- •Full table lead on clear-air ties + honest lead source; part tabs from the Rev2 part_tab column; app declares all boundaries cut-critical (interiors G41) with a consumable per-feature comp override record — Built 2026-09-04 on Jordan's three 44558B_10 questions ('Go'). (1) SLOT LEAD LENGTH: emit._pick_lead judged clear air on raw floats, so in a narrow slot every pierce tied at the half-width and sub-thou sampling scatter picked the lead length (0.084 ran on a 0.15 table value beside Jordan's dragged right-cap start). The chooser now judges the clear-air TIER rounded to a thou (the lead-aim-consistency standard) and prefers the LONGER lead inside a tier -- his dragged cap start runs the full 0.15 down the slot axis; a genuine clearance difference still outranks length. The pierce-standoff yellow stays -- slot half-width physics, not the lead. (2) LEAD SOURCE HONESTY: the record said table:lead_len while 0.082 ran; now table:lead_len only when the full table length runs, else rule:shortened-to-fit -- the drawer stops claiming the table. (3) PART TABS FROM THE TABLE: the Rev2 part_tab column (0.030 on Mild Steel, in the sheet since the 2026-08-24 ingest -- the brick-19 'awaiting width table' record was STALE) now rides tables.rev2_tooling (blank raises in the table's words); the app passes it at every emit/judge site via ONE helper (_post_defaults), so outers post held with tab ran+source table:part_tab; the per-feature tab_width override (0 = suppress) wins as before. Jordan's question IS the 2026-08-12 go the record was waiting on. cl_post excluded -- band perimeter tabs stay open with Jordan. (4) COMP: the engine's cut_critical default ('outer' = interiors are art) dated from the art-file era and the app never set it, so slots posted G40 and cut ~2x offset undersize; the shop's own programs comp every boundary (33215.NC 44/44 G41, 33199.NC 287/287). The app now declares CUT_CRITICAL='all' at the same one helper, and 'comp' joined tooling_doc.CONSUMABLE in the same commit as the engine input: per-feature overrides {'near','comp':'on'|'off'} -- the EDIT_TOOLING walkthrough's per-feature comp-off, source operator, round-trips, junk value refuses in the engine's words; UI comp row in the review drawer (force off/on, clear). Legacy paths byte-identical: tooling=None, cut_critical default, part_tab=None all unchanged (control proves it). Proven: test_lead_tab_comp.py NEW 19 controls + scratch-instance run of the real job (slots G41, outer 0.030 tab, O33339 kept, full-length lead from the dragged start); suites green: drag 23 / tooling_doc 37 / rules 14 / nc_warn 12 / dragcheck 15 / units_confirm 27 / sketch 21 / healedit 29 / nestseq 12 / part_list 28 / pl_post 26 / pl_tool 18 / pl_seq 27 / cl_post 18 / traverse 10 / common_line 24. The real job re-ran offline with Jordan's dragged starts riding; delivered O33339.nc refreshed (all boundaries comped, tab riding, same standoff yellows). Live in the app after the next owner-turn restart -- a comp/tab click before the restart is consumed only after it.
- •G-code header notes from the Rev2 table: used conditions named, used-only D registers in numeric order, M100 default + blocked variants -- 'This is an old CAM feature, and as such, we can do better' record — Built 2026-09-04 on Jordan's three header notes (screenshot GCode_Notes_9-4-1.png, O33338's header) while awaiting Aristide's restart. (1) CONDITION NOTES: the old CAM marks the one condition a program uses with a bare '()' (the #107=107() corpus artifact); every condition number the program's boundaries actually USE now posts with its class name -- #108=108(PROFILE), #107=107(INSIDE), #106=106(SMALL) -- while the UNUSED lines stand untouched (#102=102 etc.), Jordan's ruling: 'so that the laser operator can still manually change one feature in a subprogram if they choose.' (2) D OFFSETS: only the registers the program uses post, in numeric D order, each noting its class -- #2001=.004(D1 - INSIDE) / #2003=.004(D3 - PROFILE); a register shared by two classes at different offsets refuses (one register holds one value on the control). (3) M100 FROM THE TABLE (Jordan: 'We will use the Rev2 table going forward. I just named it Rev2 to keep it straight on my end'): tables.rev2_tooling now carries the row's m100_default + variant columns (ingested since 2026-08-24, notes and all); the default posts noted (DEFAULT), the variants follow in sheet order blocked with a leading '(' so the control skips them, the sheet's own note riding inside the comment -- (M100[CRS1018,AI,ZHL,S25,GX,0.0800] High Pressure Air); the note's own parens are stripped so no comment nests parens (control-format hazard). The stale old-CAM-era key (M100[MSO7,0.080]) no longer posts as the machine word; it stays the internal lookup key and the (MATERIAL) line. Engine: emit._cond_lines/_dreg_lines/_m100_lines shared by the single-part AND nest main-program headers; shop dialect's OFFSET comments used-only in register order the same way. Legacy posts (tooling=None) stay byte-identical: #107=107(), single zero-padded (D07), M100[material]; a tooling dict without m100 (old callers/tests) also keeps M100[material]. The audit reads the annotated file clean (comment lines skipped by construction; control proves no structure anomaly). Proven: test_header_notes.py NEW 22 controls + 12 neighbour suites green (lead_tab_comp 19 / tooling_doc 37 / rules 14 / nc_warn 12 / drag 23 / dragcheck 15 / cl_post / pl_post 26 / traverse 10 / sketch 21 / units_confirm 27 / customer 26). The real 44558B_10 job re-posted via the server codepath offline: O33339 refreshed in viewer/44558B_10/ with the new header, same 9 yellows riding, number kept. Live after the next owner-turn restart.
- •Beam-offset toolpath display + per-feature condition class / custom D register overrides + rubber-band multi-select -- 'see the G41 doing its job', the tooling-pin D4 move record — Built 2026-09-04 on Jordan's two asks + multi-select ('Does this make sense?' -> both answered, built same turn). (1) OFFSET DISPLAY: 'show the toolpath, already offset from the table values, this way we can see the G41 doing it's job' -- emit._offset_path computes the beam-CENTRE path per boundary (line shifts parallel; arc keeps its centre, r -/+ d by travel direction x comp side; corner gaps joined with an arc about the shared source vertex, the control's own comp-B move), at the value the boundary's D register actually carries (class offset, operator d_offset, or legacy kerf); rides plan rows as offset/offset_val, review payload passes it through, and a fourth canvas layer 'Beam-offset path (comp)' (toolbar key B, ON by default) draws it fine-dashed under the nominal as-cut path. DISPLAY ONLY -- the program still posts nominal coordinates and the CONTROL applies the offset; nothing downstream consumes it; comp-off boundaries honestly carry none. (2) CUSTOM D REGISTER (the tooling-pin scenario: holes fitted to pins, operator dials the register at the control): per-feature override d_register (1..99) + optional d_offset (typed start value, 'maybe they want to start at .002'; blank seeds the class value) + optional d_label -- the header posts Jordan's exact form '#2004=.002(PIN CHECK)' (label uppercased, parens stripped -- no nested parens), the boundary posts D4, and the used-only rule follows: a class register nothing uses any more drops out of the header. The one-register-one-value guard covers operator registers too (forcing onto a class register at a different value refuses in the table-contradiction words). (3) CONDITION CLASS override, INDEPENDENT ('independent of the other selected options/overrides'): per-feature condition= profile/inside/small moves ONLY the #501 word to that class's condition number; the register stays its own knob; the used-condition header notes follow it. Both refuse without a Rev2 tooling row, in the engine's words. All four fields joined tooling_doc.CONSUMABLE in the same commit as the engine input (model rule); overrides_from round-trips them byte-identically; _feats_from passes them through review/dragcheck/quote/post/postnest; pl_post.assemble + the postnest part-by-part replication now carry comp/condition/d_* per copy (comp was a recorded replication gap -- closed). THE AUDIT KNOWS THE OPERATOR'S WORDS: nc_audit.audit(overrides=) binds each override to the boundary nearest its near point (bbox-min frame alignment, the geometry check's own rule) and judges it against the operator words -- no false 'table says' anomaly on a recorded choice; congruent twins (bbox within 2 thou) accept either word set, the honest form for expanded macro programs where one part-frame near stands for every arrayed copy; the same file WITHOUT overrides still flags, proven both ways. nc_warn.audit_and_inject passes overrides at every posting surface. (4) MULTI-SELECT: shift-click toggles features in/out, shift-drag rubber-bands (centroid-in-rect), the panel says 'N features selected -- edits apply to ALL selected', and every override edit fans through the one ovApply channel to each selected feature bound to its own centroid (sequence stays per feature; plain click collapses). Explicit selection outranks the identical-twin ALL fan. Proven: test_dcond.py NEW 17 controls (header form, class seed, used-only, independence, collision guard, refusal ladder, round trip byte-identical, audit both ways, offset at r-d on a CCW hole under G41 / outside on the outer, comp-off none, legacy byte-identical, pl_post replication) + app/verify_dcond.js 16 live Playwright checks on a scratch instance (real-mouse shift-click/band, D4 typed end to end, posted NC carries #2004=.002(PIN CHECK), audit clean); 14 neighbour suites green. Honest limits: server side live after the next owner-turn restart (a D/condition set in the app before it is consumed only after, the standing pre-restart note); offset corners are display-sampled (the audit still judges the nominal file); on a MACRO-mode nested post the audit's override sanction is congruence-scoped, not per-copy-bound. EXTENDED 2026-09-22 (Jordan's corner-petal screenshot -- 'What's with the corners displayed here? ... They do not reflect what the laser will actually cut, do they?' -- he was right, the laser cuts a clean corner; his 'Go'): the display drew EVERY offset corner gap as an arc about the source vertex -- correct at CONVEX corners (the control's own comp-B move) but at a corner turning TOWARD the comp side the two compensated moves OVERLAP and the control trims to their crossing; drawing the overshoot plus the vertex arc was the petal loop he screenshotted. My defect. Fix in emit: the join now classifies the corner by its turn angle (the offset endpoints sit on the comp-side normals of travel either side of the vertex, so their sweep about the vertex IS the turn) -- convex keeps the arc join, CONCAVE trims both segs to the in-span carrier crossing nearest the vertex (line/line, line/circle and circle/circle all solved exactly; no usable crossing leaves the plain overlap standing, never a vertex loop), arcs re-anchored exactly on their own circle. _offset_path now SAMPLES _offset_segs, so both display forms share ONE corner arithmetic and can never disagree. Display only, unchanged in kind: the program still posts NOMINAL coordinates and the CONTROL applies the offset. Proven NEW test_offset_corner.py 16 controls (concave trim both hands, line/arc + arc/arc crossings, out-of-span fallback, convex joins kept, sampled-vs-seg one-arithmetic, full circle untouched) + test_dcond 27, plan_display, dragcheck 15, header_notes 22, rev2_material 13 zero suite edits; engine restarted.
- •Lead chooser: band-vs-best clear air + full-length angle scan -- the table lead runs wherever it fits, sub-thou scatter never buys it away record — Built 2026-09-04 on Jordan's slot-2 catch on O33338 ('Why is slot 2 not using the table's lead-in value?' -> 'I'll take your word for it. Build it and I'll test it.'). His dragged start sat 1.2 thou off the cap pole and the lead ran 0.093 on the 0.15 table value. TWO defects, both in emit._pick_lead: (1) the morning tier comparison (round clear air to a thou, longer lead wins inside a tier) still split candidates whose clear air STRADDLED a rounding boundary -- 0.0776 vs 0.0772 read as different tiers, so a 0.0004in clear-air 'gain' bought away 0.057in of lead; replaced by a BAND AGAINST THE BEST reachable clear air (CLEAR_BAND 0.001): every candidate within the band competes on length, a longer lead displaces only when longer by LEN_GAIN 0.005 (keeps a hole's pierce at its exact centre -- proven), a genuine clearance difference over the band still outranks length, insertion order keeps the perpendicular-first tie. No boundary to straddle. (2) the aim that runs the WHOLE table lead down a slot's axis lies between the 10-deg fan angles once the start is a few thou off the pole, and the local refinement cannot walk angle+length that far together -- the full length was never sampled; a FULL-LENGTH ANGLE SCAN (1-deg over the fan range, length pinned to the table value, best candidate's angle polished to ~0.01 deg) puts it in the running, the band deciding whether it wins. Both values construction margins of the search, never machine numbers; the standoff gate stays the table's and the slot yellows stay (half-width physics). Proven: test_lead_tab_comp 19->22 (off-pole drags +1.2/-2 thou run the full 0.15; hole pierce stays centred); drags 10-50 thou off the pole verified 0.15 offline; 44558B_10 re-judged via the server codepath -- all 3 boundaries 0.15 at his recorded starts; all 26 suites green. Live after the next owner-turn restart.
- •O108-O110: lances (open lines) -- by default cut on the line, lead 0, no tab, before the outer; any lead the operator types runs record — O108 (Jordan 2026-11-12, on CP-6004-96: 'I need to be able to set the lead-in lengths to 0 on the open lines, these are lances'). The engine already took lead_length 0 (pierce lands on the line's start, source 'operator', audit pierce_standoff in yellow -- warn, never block); only the client's set button refused anything not above 0. KM.setLead now accepts 0 ('0 = no lead-in'). Measured on a copy (zz-lance-test): lead 0 + comp off on the 6 lances posts as rapid to the line end, pierce, G1 along it; with comp left on (G41) the audit says comp on the wrong side in red on 4 of them. Not changed, said to Jordan: the lances still default to G41 comp and a lead; three lances cut after the outer edge (audit outer_not_last); one lance overlaps the outer edge 0.145 in (doubled_cut). Identity gate green; client-only (no restart, no F1). O109 (Jordan 2026-11-12: '1. Yes' = open lines get lead 0 + comp off by default, overridable; '2. Yes' = cut them before the outer). emit._is_lance(con): an OPEN contour whose ends are far apart (gap over half its own length, or over 0.25 in) -- a nearly closed outline (broken ring) is NOT one and keeps comp + lead, so a heal miss never changes a part's size. Decided at pick time on the whole contour, so an O85 tab run (open piece of a closed outer) is never a lance. A lance: depth from the midpoints of its pieces, deepest wins, and open contours contain nothing (CP-6004-96's lances started ON the outer edge and read as depth 0 = outers, cut after the outline with G41/G42 and a lead); comp off (G40, source rule:open-line); lead 0 (rule:open-line); no tab. Operator values still win. Audit (rules.annotate, from the posted path alone): a boundary whose end gap is over half its length or over RING_LINK_MAX is open and skipped by the slug-tab rules (was a false 'tab on a sub-drop-through interior'). Measured: CP-6004-96 copy 2 red -> 0 red, 6 lances depth 1, G40, lead 0, outer last; dev corpus 1181 reviewed jobs, 5 with open contours: the two bnm78598 jobs already had G40 + lead 0 typed by hand on all 21 (3 move from depth 0 to 1), eds17942 (an O85 run) byte-same as before. Tests: new test_lance_open_line 17/17 (old code fails 7), identity gate green (no fixture has open lines), lead_tab_comp 22, approach, tooling_doc, rules 14, slug_ladder, auto_close 29, feat_report 17, rejoin_runs 11, tiny_runs 10, pl_select 28, seqexact 16, column_join 13, nestdeliver_rot 14, nestenv 19. F1 first click 8.83/8.81 -> 8.85/8.84 s, repeat 8.61/8.61 -> 8.63/8.61 s. Needs a dev restart. O110 (Jordan 2026-11-12: 'I want 0 to be the default, and I want to be able to override to any value for any feature'). Before: a typed lead above 0 on an open line mostly ran 0 -- the hole/outer scrap test looked for scrap INSIDE the line itself and found none (on the CP-6004-96 copy, 5 of 6 lances ran 0 on a typed 0.1). Now (emit._lance_lead): scrap = outside every closed part outline or inside a hole (lances never count); both sides of the start are fanned with the usual _pick_lead, the clearer pierce wins. A lance with a typed lead may start from EITHER end: the end whose lead lands in scrap wins (as drawn breaks ties); an operator start point keeps its end. No scrap within reach (a lance wholly inside the part): the lead runs IN LINE behind the start (the slit grows by the lead length), lead record in_part true, and the audit (rules.check_lance_lead, from the posted path alone, in check_plan and nc_audit) gives a yellow 'lead-in pierces inside the part -- it leaves a mark'. The lance flag comes from the pick (whole contour), so O85 tab runs never take this road. Default unchanged: lead 0 (rule:open-line). Measured: CP-6004-96 copy, 0.1 typed on all 6 lances -> all 6 run 0.1 and pierce outside the part (each lance runs in from the outer edge; looked at the plot with true arcs), no new warning; default settings byte-same as O109. Dev scratch corpus 27 jobs byte-same (incl. bnm78598 x2, eds17942). Tests: test_lance_open_line 26/26 (9 new), identity gate green, lead_tab_comp 22, approach, tooling_doc, rules 14, slug_ladder, auto_close 29, feat_report 17, rejoin_runs 11, tiny_runs 10, pl_select 28, seqexact 16, column_join 13, nestdeliver_rot 14, nestenv 19. F1 first click 8.74/8.72 -> 8.73/8.79 s, repeat 8.83/8.80 -> 8.80/8.82 s (noise). Needs a dev restart.
- •O111: right-click 'Change direction' on any feature -- cuts it the opposite way; comp side follows so the size holds record — O111 (Jordan 2026-11-12: 'I would like a right-click -> "change direction" tool that works on all features, which switches to the opposite cut direction'). Per-feature override direction='reverse' (the tooling doc's existing direction slot, now CONSUMABLE): emit binds it like every override and reverses the contour right after binding, BEFORE start/tab/lead are chosen (the reason the shop normalisation also runs early). Comp side is derived from the geometry (_comp_side), so a reversed hole/outer posts G42 and keeps its size; the audit's independent read finds no wrong side and gives its existing yellow comp_g42_norm (the shop's G41-only norm) -- warn, never block. Record: direction source 'operator', overrides.direction 'reverse'. O85 tab runs follow their outline. A lance with a typed lead keeps the operator's direction (O110's either-end choice stands down). Threaded through server _feats_from, the part-list pack (server) and pl_post copies, tooling_doc.overrides_from. Client (app.js): right-click 'Change direction' / 'Change direction back', a direction row in the feature panel, KM.setDir through ovApply (selection / ALL-mode twins), kept on re-plan and in the three 'override empty' checks. Ramification seen: flipping one feature moves where the head ends, so the NEXT feature's start can change (the cut-order planner reacting, as designed). Measured: test_direction_reverse 21/21 (hole/outer/lance reversed, G42, audit no wrong side, round trip byte-same, nothing unconsumed, tab runs, bad value raises, no override byte-same); server run_review/run_post on the CP-6004-96 copy: hole + outer reversed, 0 red; nested part-list post (F1 bench copy, refresh + post): diff vs O110 = exactly the reversed hole in both copies, G41->G42 and G3->G2, nothing else. Identity gate green; test_lance_open_line 26, lead_tab_comp 22, approach, tooling_doc, rules 14, slug_ladder, auto_close 29, feat_report 17, rejoin_runs 11, tiny_runs 10, pl_select 28, seqexact 16, column_join 13, nestdeliver_rot 14, nestenv 19, drag 23, dcond. F1 first click 8.74/8.74 -> 8.79/8.75 s, repeat 8.81/8.80 -> 8.82/8.84 s (noise). Seen, not from this change (same on O110): the audit calls CP-6004-96 lance 24 a PROFILE on the wrong register (#106/D2 vs table #108/D3) -- an anomaly line, not a counted warning. Engine on dev (not live until a dev restart); the client file is held in /tmp/o111 and goes in WITH the restart, so the menu item never shows before the engine can use it. LIVE: dev restarted 19:20 UTC 2026-11-12 (both inflights 0, speed restarted by Aristide 19:18) with the client in (dev 543590aa). Browser check (Playwright, zz-lance-test-1794496999): right-click feature 1 (inside) shows 'Change direction'; click -> direction cw source operator, comp G42, override direction 'reverse'; menu then shows 'Change direction back'; click -> ccw rule:shop, override cleared; no page errors. UPDATE O114 (2026-11-12): the yellow comp_g42_norm is retired -- a reversed hole/outer posting G42 now gives no finding; only a wrong side warns (red).
- •O117: runs of a tab-split outer take comp side and direction from the whole outline; Tab count and Change direction work from a run record — LIVE on dev since the 14:23 UTC 2026-11-13 restart (Jordan: 'Ok to restart'; inflight 0/0; active + 200). Checked on a copy of the live 2800X job after restart: start at top + 2 tabs, both runs cw G41, 0 findings. Jordan testing, not shipped to main. O117 (Jordan 2026-11-13, 2800X part: 'I tested add tab to the profile, and it gives a red warning: comp on wrong side. This should not happen when adding a tab, and right-clicking on the new half of the profile does not give me the option to change number of tabs, and change direction does nothing'). CAUSE (pre-existing since O85, on MAIN/production too, reproduced on km-main-wt code): emit took each run's comp side (_comp_side) and direction record from the run's own OPEN piece's signed area, which flips with where the tabs fall -- the 2800X operator start at the top flat made run 2 read ccw -> G42, and the independent audit rightly called it wrong side. FIX emit: before the split, _pk['whole_ccw'] = the whole outline's turn sense; every run (dict copy) carries it; gcomp and direction.ran use it when set (everything else unchanged). CLIENT app.js: on a run, Tab count and Change direction act on the outline it came from (wid = c.run_of): panel row + right-click; direction then reverses every run via O111. Measured: 2800X copy, start at top + 2 tabs -> both runs cw G41, 0 red, post audit no findings, NC G41 x4 G42 x0; outline reversed -> both runs ccw G42, 0 red. New test_tab_run_comp (T outer, 2 and 3 tabs, 8 operator starts, both directions, audit read): 8/8 on fix, 0/8 on old code (old: wrong side at 3-5 of 8 starts). Also direction_reverse 21, lead_tab_comp 22, lance 26, rules 14, drag 23, tab_irregular, pl_select 28, seqexact 16. Identity gate green (no golden uses extra tabs). F1 first 8.72/8.75 -> 8.74/8.74 s, repeat 8.44/8.44 -> 8.46/8.50 s. Client live at once; engine fix live with the next dev restart. Ramification: any job with extra tabs re-posts with corrected comp on the runs (that is the fix); jobs without extra tabs byte-same.
- •O113: Tooling feature panel shows the comp side (G41/G42/G40) and the cut direction (CW/CCW) beside their override links record — O113 follow-up (Jordan 2026-11-13: 'I do not see where I can manually switch between G40/41/42, nor can I confirm that switching directions actually flipped 41/42 appropriately without posting the gcode'): the rows were only in the classic panel; the Clear layout's Selected box (what Jordan uses) showed 'Outside · D3' only. Now its Cut side row names the G code (Outside · G41 · D3), a new Direction row shows CW/CCW (set by you / rule), and a second button row has Change direction / Direction back (acts on the whole outline for a run, O117) and Comp off (G40) / Comp on / Comp back. No direct G41-vs-G42 pick: the side follows the direction so the size holds (Jordan asked; question open). Browser-checked on a copy (zz-2800x-o113b-1794580000, profile 3): Direction back -> G41 CW; Comp off -> no comp (G40); Comp back -> G41; Change direction -> G42 CCW. Client only, live at once, no restart. Identity gate green; not a hot path, no F1 run. O113 (Jordan 2026-11-12: 'I see comp and direction, but not comp side (G41/42), shouldn't we display that in the same area so that this is clear to the operator?' -> '1. Yes'). app.js feature panel: the comp override row leads with the side the plan cuts (c.comp.side; G40 shows '(off)'), the direction row with CW/CCW (c.direction.ran). Display only: no engine, plan or NC change. Identity gate green.
- •O118: pick the comp side per feature -- G41 / G42 / G40 buttons beside the current side record — Words 2026-11-13 (Jordan: 'G41 should say offset left, G42 should say offset right, G40 is good with the note no comp'): buttons read 'G41 offset left' / 'G42 offset right' / 'G40 no comp' (two lines, current ticked); the Cut side row reads e.g. 'G41 offset left · D3' (Inside/Outside dropped there to fit -- the heading already names it); right-click 'Comp G42 offset right' / 'Comp G40 no comp'; classic row the same words. Browser-checked (route-served client on dev, zz-2800x-o118b, hole 1 and run 4), no page errors. Client only, live at once. Identity gate green. Fix 2026-11-13 ~15:10 UTC (Jordan, 2800X live job, screenshot: 'a check mark on G40 that I can't get to go away'): the second half (run 4) carried its own comp 'off' in S.ov -- a run's record echoes the outline's forced comp and the client rebuilds S.ov from it -- and a run's own setting outranks the outline's, so picks on the outline (3) never reached it. KM.setComp now also clears comp on every run of the outline; Auto shows when the run itself carries one. Checked live (route-served client) on a copy of his job (zz-2800x-o118b): start 3 G41 / 4 G40 off -> Auto: both G41, no ov -> G42: both G42 + red [3,4] -> Auto: both G41; no page errors. Client only, live at once. Identity gate green. LIVE on dev since the 14:54 UTC 2026-11-13 restart (Aristide: 'restart'; inflight 0/0; active + 200); client half copied in right after; live browser check on zz-2800x-o113b: G41 on CCW outer -> red, Auto -> G42; right-click hole 1 G42 -> red, back -> G41; no page errors. Jordan testing, not shipped. O118 (Jordan 2026-11-13: 'I want to be able to switch all of these as well as see their current settings'): the per-feature comp override takes G41 / G42 / G40 as well as on/off (emit: G40 = off; G41/G42 = comp on, that side, kept if the direction is changed later; a side that cuts into the part gets the red comp_wrong_side, warn never block). A run of a tab-split outline inherits the outline's pick (checked: start top + 2 tabs, G41 forced -> both runs G41 + red; G42 -> both G42, no red; NC G41x2 G42x2, audit clean). Client (Clear-layout Selected box): a G41 / G42 / G40 button row with the current side ticked, plus Auto when forced; the classic panel row says 'use G42 / use G40 / auto'; right-click lists the other sides + 'Comp back to automatic'; on a run all act on the whole outline. Browser-checked on a scratch engine (zz-2800x-o113b copy): G41 on CCW outer -> red; G40 -> no comp; Auto -> G42; Direction back -> G41 CW; G42 on CW -> red; Change direction -> G42 CCW no red; right-click on hole 1 G42 -> red, back to automatic -> G41. Tests: test_lead_tab_comp 25 PASS (3 new O118 checks; the junk-value message check updated), test_rules 14, test_tab_run_comp 8/8, test_direction_reverse 21/21; identity gate green. F1 first 8.76/8.76 -> 8.78/8.77 s, repeat 8.49/8.50 -> 8.53/8.51 s. Ramifications: older stored 'on'/'off' overrides read as before; the live engine before restart refuses G41/G42 (so the client half lands only after the restart); speed shares emit.py (memo line).
- •O119: Part list not saved -- yellow Save list, yellow bar on every tab, "not saved" on the Part list tab; dark ink on the yellow nesting-method banner record — Tabs 2026-11-13 (Jordan, asked 'yellow button enough, or a mark on the Part list tab too?': '2. Also mark the other tabs'): while the list has changes not saved, every tab gets a yellow bar along its bottom and the Part list tab a yellow 'not saved' chip, tooltip 'The part list has changes that are not saved yet'; same judgment (plDirtyDraft, incl. a part opened from the list) plus a half-typed row field; renderTabs and the Save list cue both refresh it; Save list clears it (plMarkSaved then renderTabs). The typed-field check now uses a typing flag (S.plTyping, cleared on change/re-render) -- the first cut compared with the rendered value and stayed on after a value was typed back. Browser-checked on dev (route-served client) on Jordan's list -2 without saving: loaded clear; typed qty -> all 7 tabs marked + chip; Nest tab -> still marked; back, typed 40 back -> clear; stored qty still 40; no page errors. Client only, live. Identity gate green. O119 (Jordan 2026-11-13: 'White on yellow is hard to read. Also, when I update the Part List, I need a visual cue to know that it is not saved yet'). (1) Clear layout, Nest drawer, yellow 'PICK A NESTING METHOD' banner: the outlined method rows (.kmclear .kmethp .btn, light ink) now take dark ink #0d1013 and a dark outline inside .banner.flag; outside the banner unchanged. (2) Part list: Save list turns yellow and reads 'Save list — not saved yet' while the list differs from the last saved copy (plDirtyDraft: rows + fill-even -- the same judgment as the leave-without-saving prompt) or a row field has been typed in and not left; back to 'Save list' when it matches again or is saved. Material/machine changes are not part of the cue (not in plSig; the material change re-assigns through its own door). Browser-checked on dev (route-served client) on Jordan's 2800X list -2 without saving: loaded plain; typing in qty -> yellow 'not saved yet'; typed back -> plain; stored qty still 40; banner rows read rgb(13,16,19) on the yellow. No page errors. Client only, live at once. Identity gate green. F1 n/a (client display). Ramifications: app.css + app.js are shared with speed (memo line).
- •O114: comp warns only when on the WRONG side -- the G41-only norm yellow (comp_g42_norm) is retired rulingmixed — O114 (Jordan 2026-11-12: 'The G41 rule was more for us; it really doesn't matter on the laser, as long as it's on the correct side. We don't need a warning flag unless it ends up being on the wrong side due to operator overrides'). rules.check_comp keeps the red comp_wrong_side (judged from the posted geometry, so the audit stays independent of the pipeline) and drops the yellow comp_g42_norm. Planning still normalises holes CCW / outers CW (G41) by default; only the warning goes. Ramification: NC headers on jobs that had a right-side G42 count one yellow fewer on re-post; a green flag on an old comp_g42_norm finding simply has nothing to match. test_rules 14, test_direction_reverse 21 (assert flipped), identity gate green. Live with the next dev restart. LIVE: dev restarted 20:49 UTC 2026-11-12 on Jordan's 'restart' (both inflights 0).
- •Post tab leads with the nested sheet program (Jordan's shaping of the two-doors confusion) record — Born Jordan 2026-09-04 after grabbing O33338 (single-part) when he wanted the nested-sheet form: 'there are 2 ways to post... a little confusing for my normal workflow.' SHAPED + BUILT 2026-09-07 (Jordan: 'post nested sheet should be option #1. The operator just spent all of his time optimizing the material usage and nest sequencing... individual part GCode as a secondary option.'): the Post tab drawer renders the Nested sheet program section FIRST, the single-part post below it under its own 'Single part program' header. Presentation only -- both doors stand, records/refusals/numbers per stage unchanged. Client-only (app.js), serves from disk, verified live on the 44558B_10 job same turn.
- •True-arc toolpath display; offset path is the main line, lead attaches to it; toolpath overlay on the Nest canvas record — BUILT 2026-09-05 on Jordan's asks 2+4 ('Can we fix the faceted display of the nominal so it represents your true arcs?' / 'we really should be able to see the toolpath' on the Nest tab; his 'Agreed' + 'Go'). ENGINE: plan rows (emit plan_samples) now carry `segs` -- the AS-CUT path as line/arc records (emit._seg_dicts, the /geometry seg shape; real centers+radii, tab gap survives) beside the sampled poly, which stays for old readers and the point checks -- and `offset_segs` (emit._offset_segs, the true-arc form of the beam-centre path: line parallel-shift, arc r+/-d, corner-join arcs about the source vertex at radius d) plus `lead_end_offset` = the offset path's start: comp engages ON the lead-in, so the display lead ends on the OFFSET path, never the nominal (Jordan: nominal attach 'is not representative of real life'). Display only -- posted coordinates stay nominal, the control applies the offset; NC bytes untouched. SERVER: run_review ships both seg sets + the attach point in the source frame (translation only, angles ride). UI: when comp is on the OFFSET path draws as the main severity-tinted line on Part review AND Cut plan (true-arc Path2D under the world transform -- arcs stay arcs at any zoom); the NOMINAL is its own layer, default OFF, key N, fine-dashed when shown (comp-off boundaries keep drawing nominal solid -- there is no offset path without comp); key B now also toggles the offset layer from the keyboard. NEST OVERLAY: every placement draws the reviewed plan's real paths + dashed leads + pierce dots by the SAME transform that places the geometry -- what the sheet program posts is what draws (parity with the part-list nest canvas). Pre-restart payloads degrade to the sampled poly. Proven: test_plan_display.py 12 NEW controls + app/verify_display.js 12 live checks on a scratch instance; 14 neighbour suites green. Live after the next owner-turn restart; the client serves from disk now and degrades gracefully. CUT-PLAN LEAD GAP CLOSED 2026-09-05 (Jordan: 'The Cut Plan tab is not displaying the lead-ins, why?' -- he was right: drawCutplan drew rapids + pierce dots but never the pierce->lead-end dashed segment, a brick-4-era display gap): the Cut plan canvas now draws each step's lead exactly like Part review (leadEndOf -- attaches to the offset path when comp is on). Web-only, live immediately, verified on his 44558B_10 cut plan.
- •Minimize warning nagging over minor issues -- acknowledge control proposed, not decided question — Jordan 2026-09-05, asked how to approve/clear the review warnings: 'We'll need to contemplate ways to minimize nagging over minor issues.' Recorded verbatim -- no mechanism built. Today: warn never block, findings ride into the NC as callouts (gcode-warning-callouts), no dismissed/acknowledged state exists. Proposed on the table: a per-finding acknowledge (who/when recorded, row dims, banner counts acknowledged separately; NC callouts still ride per the ruling -- dismissed is never erased). Physics findings (e.g. slot half-width pierce standoff) re-fire on every re-plan, so any acknowledge is per-plan unless ruled otherwise. Awaiting Jordan/Aristide shaping the ask.
- •Sequence numbers ride the toolpath -- pierce-anchored badges, Jordan's option-1 pick, BUILT record — Jordan 2026-09-14, the old CAM screenshot (boxes 1-7 riding the dotted rapid chain): 'The sequence number for each feature display on the toolpath rather than in the center of the geometry... easier for the human operator.' His pick same day ('Let's try 1. and we can change if we don't like it'): BUILT, client-only (app.js, serves from disk -- refresh, no restart). One helper seqAnchorFor: every sequence badge anchors at its feature's START point (the pierce), nudged 16px into clear air along the lead's own away-from-metal direction, so the numbers chain along the dashed rapids exactly like the head's route; overlapping badges slide further out along the same direction (proven crowded at 8px/in zoom, min gap 27.8px); anchors recorded per frame so a CLICK on a badge still selects its feature (reviewHit checks badges before geometry -- selection now works even where the badge sits off the part); Manual Sort pick badges ride 24px above the same anchor; the Part-review haloed seq labels follow the same spot (one vocabulary across both Tooling scenes). A degenerate lead falls back to an up-left nudge. Nest-tab numbered boxes STAY at part centers -- they number whole PARTS, not features, per the offer he accepted. Proven: app/verify_seqbadge.js 11 live Playwright checks (anchor at pierce+16, direction = along the lead, labels left the centroid, badge click selects, crowded nudge, Manual Sort pick lands by badge click, zero page errors; scratch fixture removed) + nav209 visual spot-check. Reversible on his word -- the anchor is one function.
- •Full 2D CAD suite -- Jordan asked, Aristide: yes but MODULAR; heal-only market raised question — Jordan 2026-09-06, verbatim: 'Before the next build, I have a fundamental question for you both: do we want to provide a full 2D CAD suite? Smaller shops would benefit because they would need no other 2D software, which is usually overpriced and underpowered. If we do a good job on the sketch tools, I don't see why this would be out of our wheelhouse. We would need a lot more than what we have now, however.' ARISTIDE same day: 'I do not mind that. but in that case build it modular... We have the healer. that is the engine. whether it is CAD that comes in from an outside source, or CAD from our own module, things will have to be healed (corrected for human error)... So what Jordan is asking in my mind is another module, that seamlessly fits of course, but doesn't HAVE to be there if someone just wants the healing/gcode generator? Some people may want the healing, but NOT the Gcode generator. we might have to consider that market too.' So: both partners YES in direction; the CAD suite = a MODULE over the one engine, never a fork -- and the same cut runs the other way: a HEAL-ONLY tier (intake -> heal -> QC -> dims -> CAM-safe DXF out, no machine tables needed) is a packaging cut the architecture already supports, since heal/QC demand no material x machine row -- tooling does. The sketcher's existing seam is the model: it compiles to a real source.dxf and nothing downstream knows it exists. My gap list stands (mouse drawing + snapping, trim/extend/fillet/chamfer/offset, mirror/pattern/move/copy, outlined text, driving dims in sketch mode, and the constraint solver as the one hard piece; brick-10 no-solver ruling would need superseding). Still a QUESTION: no bricks commissioned yet -- module boundaries and the tier cut get shaped by both partners before anything builds; per-nest sequencing stays the queued next build. | ANSWER 2026-10-12 (Jordan, Aristide present): scope is RUDIMENTARY -- most of it already exists, it needs touching up. No big-suite build; touch-up list to be proposed.
- •Manual nest placement -- operator can place/override/do whatever they need; commissioned as the next brick recordmixed — Jordan 2026-09-05, ruling on custom nests (asked how to add columns that don't finish max Y): 'Yes, we need to include this ability. If we are able to build the best of both worlds: superior automated nesting AND enabling the operator to manually place/override/do whatever they want or need, then we will be lightyears ahead of anyone else. Software developers want a one-size-fits-all product that forces the operators to adhere to their way of doing things, and as such (myself included), we end up hanging onto old, sub-par programs that allow us to do everything manually, at the cost of labor-intensive workflows, because the end result is what we ACTUALLY need. What other developers don't take into account: the cleanliness of theory rarely matches the messiness of reality; we don't know what the operators are up against in reality, so we need to provide every option and tool possible.' The aid-the-operator philosophy at nest level: automation seeds the layout, the operator may hand-place. COMMISSIONED as the next brick (mixed: the ruling stands; the editor is intent until built): drag placements, add/remove copies (e.g. extra columns short of max Y), positions persisted ran+source, the pack's own audit re-judging the hand layout (gap/lead findings warn never block), posted programs riding the hand layout with numbers kept per the stale rule. Today's levers recorded honestly: qty opens columns Y-first, finish-even-columns rounds up, X/Y spread + gap increments. BUILT 2026-09-05 (Jordan's 'Go' on 'How do I add columns for a custom nest?'): the true-nest Nest tab. ENGINE nest_rules.judge_layout -- the hand layout judged on the part's sampled TRUE outlines (never bounding boxes): off-sheet / crossing outlines RED, under-gap / under-margin clearance YELLOW, measured values in the words; contour jumps in the sample never read as segments. SERVER POST /api/jobs/<id>/nestedit -- the client sends the WHOLE layout ([x,y,rot] per placement, rot 0/180 only per the two-orientation ruling; malformed = plain 400 nothing saved, the nestseq pattern); a good save persists ran+source:operator on nest.json (layout_edit: date, findings, notes), recounts qty_filled, drops the posted nest program (every sheet keeps its O-number) and clears a clicked nest sequence (it indexed the old placements -- named, never silent); stage flagged on findings, WARN NEVER BLOCK (an overlapping layout saves flagged and posts flagged). THE TWO-SHAPES RULING HOLDS: a hand layout still forming regular arrays (an added column, a moved block) posts MACRO unchanged; one that breaks the lattice falls to PART-BY-PART with the why recorded in mode_why. UI: 'Edit layout by hand...' on the Nest drawer -- drag placements with the mouse (move cursor, empty canvas still pans, drop rounds to 4 decimals, draft only -- nothing saved until Apply), Add copy / Rotate 180 / Remove on the selection, Apply judges+saves, Cancel/Escape drops the draft, Re-nest = back to automatic; findings render red/yellow in the drawer with the HAND-EDITED banner. Proven: test_nestedit.py 28 NEW controls (engine judge, refusal ladder verbatim, program dropped number kept, macro-vs- part-by-part both ways, overlap red, re-pack replaces) + app/verify_nestedit.js 11 live real-mouse Playwright checks on a scratch instance; nestseq/rules/tooling_doc/nc_warn/sketch/ drag/matrecord/units_confirm/healedit suites green. Honest limits: the editor moves WHOLE placements (per-feature overrides stay on Part review); no live judge while dragging -- Apply judges (the posted-NC sheet-wide audit stays the final gate); per-job sheet size is the commissioned next brick (pin sheet-size-input). Live after the next owner-turn restart. V2 BUILT same day (Jordan's three asks + 'I say build it and let me test it'): (1) SNAP-TO-SPACING on drag -- free move stays the default; a 'snap to spacing' toggle (X/Y values seeded from the ruled gap, typed-overridable) eases the dragged part against a neighbor at the set spacing or into line with its row/column once it comes close; Alt holds the move free. Snap measures rotated bboxes (a placement convenience); the judge on Apply still measures true outlines. (2) ANY-ANGLE ROTATION -- +90/180 buttons plus a typed free angle; [x,y,rot] turns about the part centre, ONE convention shared by the judge (nest_rules.rotated_outline -- off-sheet/pair measures on the rotated true outline), the placed geometry (server place()/wpt()) and the posted sub (emit._rot_lines: text-level rotation of the emitted body about the part centre, modal one-axis moves post both axes after the turn, I/J rotate as offsets, G2/G3 and comp side untouched; 0/180 keep the exact closed forms byte-identical). (3) ARRAY STAMP -- count X x count Y at typed pitches seeded from the selected orientation's bbox + snap spacing, stamps a grid from the selected part (the old CAM's Edit Array move, draft-only until Apply). SNAP MEASURES THE TOOLING ENVELOPE -- 2026-09-05 (Jordan: 'Snap offsets should go to the tooling boundaries (i.e.: lead-ins), not part geometry'; the nest-objective-function rule -- the unit is part + lead + pierce envelope, never bare geometry): the editor's snap-to-spacing and the array-stamp pitch seeds now measure the part bbox UNIONED with every planned pierce point and lead end from the reviewed plan (the very leads the sheet program posts), rotated with the placement's own orientation -- on the real 44558B_10 part the X envelope grows 2.3386 -> 2.4886 (the outer lead's pierce) so a 0.2 snap leaves lead room instead of the 0.050 clear-air yellow his hand layout posted with. Client-side only (falls back to the bare bbox when no plan is loaded, honestly); the judge on Apply still measures true outlines and the posted-NC audit stays the final gate. Serves from disk, live now. SAFETY SET BUILT 2026-09-05 (Jordan's three asks after his 46-pc hand layout, his 'Go'): (1) UNDO + WHOLE-NEST DRAG -- every draft change (drag, add, remove, rotate, stamp, spread) pushes a snapshot; Undo button + Ctrl+Z step back one change at a time (a grab that never moved pops its own snapshot); dragging moves the WHOLE nest by default as one rigid body -- his 'default click should select the entire nest' -- with 'single part' the explicit pick, so an accidental nudge is either harmless or one Undo away. (2) RE-NEST SAVES THE HAND LAYOUT (his 're-nest deletes all the changes made by the operator'): run_nest stows a replaced layout_edit's sheets as nest.hand_saved (carried across further re-packs, superseded only by a newer hand edit); the Re-nest button confirms first when a hand layout exists; POST /nestrestore puts it back through run_nestedit's own door -- re-judged on true outlines, ran+source:operator, posted programs drop with every O-number kept, repeatable. (3) SPREAD Y ON THE DRAFT (his screenshot ask 'can I copy the spacing of your ideal spread Y to my custom nest?'): nest_rules.spread_hand_layout -- a thin adapter over pl_spread.spread_y, ONE evening arithmetic with the part-list screen (even gaps top/bottom/between, required minimums max(gap, margin) never violated, partial columns capped at the fullest column's rhythm with leftover to the top as one clean rectangle -- exactly his 17+10+10 screenshot shape); extents measure the TOOLING ENVELOPE (outline + the reviewed plan's lead/pierce points, the 2026-09-03 lead-envelope lesson) with the pierce standoff joining every between-gap minimum; POST /nestspread is READ-ONLY (the dragcheck pattern) -- the spread lands on the DRAFT, Apply saves as ever, X never moves. Proven: test_handspread.py 22 NEW controls + app/verify_handsafe.js 11 real-mouse Playwright checks on a scratch instance; nestedit 38 / seqcorner 13 / progstyle 24 / nestseq 20 / pl_spread 32 / rules 14 / sketch 21 / nc_warn 23 / tooling_doc suites green. Undo, whole-nest drag and the re-nest confirm serve from disk now; Spread Y and Restore ride the new endpoints -- live after the next owner-turn restart. ENTITY GROUPS 2026-09-05 (Jordan, after his layout redo: 'I hit "add copy" ... and my copy moves along with the original nest next to it. Each nest should behave as its own entity so that we can move them around and change them independently'; his 'Go'): every placement in the draft belongs to a GROUP -- the packed layout opens as one, each Add copy starts its own, a Stamp is one block (base included) -- and the default drag moves the grabbed part's own group as one rigid body; 'single part' and 'the whole sheet' are the explicit picks. Groups ride the saved layout (layout_edit.groups, validated to mirror the placements -- mismatch is a plain 400, nothing saved), survive Apply/reload, the re-nest stow AND the restore; the judge and every posted program read the flat placements only -- a group never changes what cuts. Undo snapshots carry them. Proven: test_handspread 22->27 + app/verify_groups.js 12 real-mouse checks on a scratch instance. The grouped Apply and the reload round-trip ride the new server -- live after the next owner-turn restart (pre-restart the editor still groups in-session; a pre-restart Apply saves the layout but drops the groups honestly). ENTITY-DRAG SNAP FIX 2026-09-05 (Jordan's catch the next morning: 'the X-spacing doesn't appear to use the tooling boundary instead of part geometry. This matters.'): the entity-groups build had made the group drag ('its own nest', the new DEFAULT) skip snap entirely -- so an added copy never eased to the tooling boundary, the exact workflow the snap was built for; what he got was eyeballed part-geometry spacing. Fixed: a group drag snaps AS A WHOLE -- the moving nest's union TOOLING envelope (lead-ins + pierce included, each member rotated with its own orientation) eases against every stationary placement's tooling box at the set X/Y spacing, one rigid adjustment for the whole entity; in-line candidates align part GEOMETRY (tooling edges would misalign 180s by the lead); Alt keeps the move free; a whole-sheet drag has nothing stationary to snap to. Single-part snap unchanged. Proven: app/verify_groupsnap.js 9 NEW real-mouse checks on a scratch instance (the snapped gap holds the 0.15 lead room -- 'NOT bare geometry + spacing' asserted directly; Alt stays free; part-mode regression lands the same slot) + verify_groups 12 / verify_handsafe 11 re-run green. Client-only -- serves from disk, live now. BAND SELECT + DELETE + REGROUP 2026-09-05 (Jordan's ask after his restored pre-groups layout came back as ONE entity: 'What would be nice is if I could rubber-band select entities and delete them. Then it would be easier to start over with just one copy of a part'; his 'GO!'): shift-drag on the edit canvas rubber-bands PLACEMENTS by center-in-rect (the review multi-select gesture, one UI language; shift-click toggles one; a plain click or empty-canvas click collapses the selection); the selection row offers Delete (button or Delete/Backspace key -- strip to one copy in two gestures), Make one nest (the selected parts become ONE entity -- the regroup tool a restored pre-groups layout needs) and Split into parts (each selected becomes its own nest; with no band, a clicked part's whole nest splits into singles). All draft-only until Apply, every move snapshots first so Undo/Ctrl+Z steps it back; deleting everything is allowed in the draft with an honest toast (Apply refuses an empty layout in the server's own words). Selected parts carry the accent box; groups ride Apply exactly as before. Proven: app/verify_bandsel.js 13 NEW real-mouse checks on a scratch instance (band selects 3-of-6 center-in-rect, shift-click toggles out, grouped pair drags as one with outsiders untouched, split carves it back, band+Delete key to one copy, Ctrl+Z restores parts AND groups, empty-draft honesty, 5-part Apply round-trips groups) + verify_groups 12 / verify_groupsnap 9 / verify_handsafe 11 re-run green. Client-only -- serves from disk, live now. | NEST HAND-EDIT / SPREAD READ THE TURNED PART 2026-10-18 (Aristide 'yes' on housekeeping item 5): run_nestedit (the hand-edit judge) and run_nestspread (draft Spread) sampled the outline from _job_prims bare -- no intake turn, no replayed hand edits -- the only two of 21 _job_prims callers outside the _apply_healedits seam. A part turned 90 at intake was judged standing up: nav209 sampled 1.26 x 7.803 while the nest lays it 7.803 x 1.26, so the hand editor called the engine's own legal layout overlapping on every part, and Spread evened around the wrong envelope. Both now walk the seam (+6 lines). NEW test_nest_turnframe 4 (old code fails 3 of 4: 'placements 1 and 2 outlines cross'); unturned jobs sample unchanged; test_handspread 27, test_nestedit 38, test_healedit 99, nestenv 19, nestseq 27, nestdeliver_rot 14 green; test_nest_default fails identically on the old code (its nest-method roster check, pre-existing, unrelated). Identity gate green. F1 n/a (not on the F1 path); spread click on nav209 0.113 -> 0.114s. Live on dev after the next dev restart; prod via the normal deploy.
- •Nest macros: one P9997 sub PER ORIENTATION at any angle; only a one-off buried among arrays forces part-by-part ruling — Jordan 2026-09-05, correcting the claim that a non-180 rotation drops the macros: 'when it comes to the GCode, a new orientation of the part, at any rotation, would become a new subprogram and will be able to be called out by a new P9997 if it is "nested" meaning repetitions of that orientation in X or Y. Mitsubishi lasers will let you use as many P9997 or P9996's in a row that you want, but will not like it if you have a "one-off" part buried in there (G52...), in which case we'd have to switch to part-by-part.' So macro eligibility is NOT 0/180-only: every orientation whose placements form regular arrays posts as its own P9997 sub (server groups placements by rotation, subs numbered main+42000+k in angle order; the 2026-08-31 two-orientation alternation ruling stands as the AUTO fill pattern's shape, this governs what the POST accepts). WIRED same day into run_postnest (any-angle groups through _lattice_arrays; irregular lattice still falls to part-by-part with the why) and proven on a 0+37.5+90 hand layout: three subs, audit clean on the expanded program vs placed geometry. K1Q1 ANSWERED (Jordan 2026-09-05, same message as the Main Program Style ruling): 'I like your idea that if we're in Nest Macro mode we should use P9997 with K1Q1 so it's a single part inside of a nest macro' -- a lone placement STAYS a 1x1 P9997 array in macro mode, the bare-G52 one-off is never emitted; the operator who wants G52-per-part switches the Main Program Style toggle (pin main-program-style).
- •Main Program Style toggle: Nest Macro (P9997, K1Q1 for a lone part) vs Part-by-Part (G52 + M98P sub call per part) record — Jordan 2026-09-05 (ruling, same message as his K1Q1 answer): 'Can we make a toggle for Main Program Style: Nest Macro vs Part-by-Part? I like your idea that if we're in Nest Macro mode we should use P9997 with K1Q1 so it's a single part inside of a nest macro. Switching to Part-by-Part mode would skip the macros and just give a G52 for each part.' BUILT same day. The toggle rides the nested-sheet post (POST /api/jobs/<id>/postnest {style: 'macro'|'partbypart'}; junk value = plain 400, nothing saved), persists on job.json so re-posts keep the choice, and is recorded on postnest.json as program_style {chosen, source, ran} -- chosen beside ran, because an override (Manual Sort / nest-level clicks) still FORCES part-by-part in macro style per the 2026-08-28 two-shapes ruling; the choice stands recorded and macro returns when the override clears (proven in controls). MACRO (default): the P9997 form unchanged, a lone placement = a 1x1 K1Q1 array. PART-BY-PART: emit's g52 nest style -- one G52X..Y.. per part shifting the work frame to the placement (Fanuc local-shift semantics, absolute replacement), the SAME part-local reviewed toolpath inline per copy rotated to its own orientation via _rot_lines (every per-feature override -- Manual Sort order, tab size, lead length, dragged start, comp/condition/D -- consumed ONCE on the one body, so a forced start lands at the same relative spot on every copy by construction), FEATURE numbers global in file order so audit callouts name boundaries the operator finds in the shipped file with no macro mapping, G52X0Y0 clearing the shift before M30. This REPLACES the old fully-expanded absolute part-by-part form (brick 8) on the true-nest post. AUDIT: nc_audit.expand_g52 expands the shifts to the absolute frame (I/J untouched -- relative offsets) and the same audit judges it against the placed geometry; a single-G52 program (single-part margin line) is never this form and keeps its path byte-identical. UI: 'main program style' select on the Post tab's nested-sheet section. Proven: test_progstyle.py 24 NEW controls (structure, rotated section on placed geometry, persistence, forced-override interplay, K1Q1 lone part); nestedit 38 / nc_warn 23 / nestseq 12 / tooling_doc / rules 14 / drag 23 / sketch 21 / dcond / pl_post 26 / lead_tab_comp 22 / header_notes 22 / matrecord 30 green. Part-list programs (pl_post) keep their own one-program absolute form -- a different surface, unchanged. SUB-CALL FORM 2026-09-06 (Jordan, ruling: 'G52 part-by-part should still use a main program with a sub-program callout' -- refining his 'skip the macros and just give a G52 for each part': skip the NEST macros, keep the subprogram form; BUILT same day): the part-by-part main is one G52X..Y.. + M98P<sub> per placement, subs carry the part-local reviewed toolpath ONCE per orientation (numbered main+42000+k in angle order, the same corpus convention as the macro subs; every per-feature override still consumed once on the one body), G52X0Y0 clears before M30 -- short program, one edit in a sub reaches every copy, the same editability the macro form has. nc_audit.expand_g52 splices the called subs shifted (an M98 call to a sub not in the file, e.g. the pierce macro, passes through), renumbers FEATUREs globally, and returns the call list so the audit folds findings per (sub, local bnd) and nc_warn's spot markers land INSIDE the sub -- the macro program's callout discipline, extended. The 2026-09-05 inline form (body per copy, global FEATUREs) is legacy: delivered programs stand and still expand/audit (calls=None). boundaries_program now records the one part's count, the macro form's own convention. Proven: test_progstyle 24->29 controls (M98 main form, sub-local FEATUREs, call mapping, spot marker inside the sub, legacy inline regression, subs on postnest.json) + nc_warn 23 / seqexact 16 / nestedit 38 / seqcorner 17 / nestseq 27 / tooling_doc / rules 14 / drag 23 / sketch 21 / pl_post 26 / dcond green. STICKINESS FIX 2026-09-06 (folded into the per-nest sequencing build): the Post tab's style select used to snap an un-posted pick back to the persisted value on any drawer re-render, and every post sent the select's value so an untouched default flipped the record to source:operator. Now the pick rides client state until the post consumes it or another job opens, and the style is sent ONLY when it differs from what the job carries -- an untouched default posts with the record staying rule. Proven in verify_gseq.js checks 8/9.
- •Typed condition number + note per feature -- #501=#102 with the operator's own header note record — BUILT 2026-09-05 on Jordan's ask ('If I wanted to make this feature use condition class #102, how would I do it? Could I put my own note like how we do with custom offsets?'; his 'Go'). The custom-D-register move on the condition side: per-feature overrides `cond_number` (raw #-var, 102..111 -- #112-#120 do not exist on the control and #121/#122 carry the part size, refusal names that) + optional `cond_label`; the boundary posts #501=#102 and the header's used-only rule notes the line with the typed label -- '#102=102(ETCH TEST)' -- or OPERATOR when none typed (label sanitized like every header note: uppercased, parens stripped). A vacated class condition goes back to its bare line (hand-editable, per the header-notes ruling); a number shared with a used class or a second operator note carries all names '/'-joined on the one line. EXCLUSIVE with the class knob per feature ('one condition knob per feature' refusal); the D register stays its own decision. Both fields joined tooling_doc.CONSUMABLE in the same commit (model rule); overrides_from round-trips byte-identically; _feats_from passes them through (review, drag judge, every post read them identically); pl_post.assemble + the postnest part-by-part replication + run_partnest carry them per copy; nc_audit binds the override and judges the posted words against the operator's number -- no false 'table says' anomaly, and the same file WITHOUT the override still flags. UI: 'custom condition' row in the review contour panel (number + note inputs, set/clear; a class pick clears a typed number and vice versa -- one condition word per feature, enforced in ovApply's channel). Proven: test_dcond 17->27 controls + app/verify_condnum.js 14 live Playwright checks on a scratch instance (his exact #102 + note end to end, refusals, round trip across a fresh page, re-post moves the header notes); 14 neighbour suites green. Live after the next owner-turn restart.
- •Macro-program warning callouts group per sub boundary with copy counts; CONDITION-CLASS / M100-SELECT header renames record — EXTENDED 2026-09-17 (Jordan's O33342 screenshot -- 219 near-identical header lines, 'Can we not list every single warning in the GCode? No human wants to see this'): the header now GROUPS identical finding classes -- nc_warn.inject strips the per-instance parts of each sanitized message (sub number, ALL-k-COPIES count, spot coordinates); findings that then read identically are ONE numbered header line with honest totals ('-- N INSTANCES ACROSS M SUBS'), a lone finding keeps its full words, and the top callout reads '(CONTAINS 219 WARNINGS -- 12 DISTINCT)' when the counts differ (the ruled real-total callout stands). Spot markers carry the GROUP number so header and in-body marks stay in step; the audit-transparency recheck is untouched (comments only). Proven: test_nc_warn 23 controls on the new format incl. the O33286 macro fixture; synthetic CAMP-shaped control collapses 42 findings to 6 lines. Applies to every posting surface through nc_warn.audit_and_inject. --- ORIGINAL RECORD: BUILT 2026-09-05 on Jordan's O33339 catch ('the warnings in the header of the main program do not refer to the real BND numbers in the posted GCode... you should have exactly 2 yellow warnings. Am I wrong?' -- he was right). The audit STILL judges the expanded part-by-part form the machine executes (ruling unchanged), but the header callouts on a MACRO program now speak the shipped file's own language: expand_p9997 records boundaries-per-sub, nc_audit maps every expanded bnd back to (sub, local bnd), rules.check_pierce_nest groups tight pierces per sub boundary -- one finding per (sub, local), WORST clear air across copies, honest copy count, no 8-worst cap or rollup needed ('PIERCE BND 1 OF SUB O75339 CLEAR AIR 0.0778 < 0.15 STANDOFF -- ALL 36 COPIES') -- and rules.merge_copies folds arrayed repeats of every other rule the same way (all expanded bnds kept so spot markers still cover the array; one marker per sub bnd now, not one per copy). Proven on his exact file: 9 lines naming phantom bnds 76..97 -> exactly 2 warnings, and the old header had actually hidden slot 2's own worst (0.0784, buried in the rollup -- all 8 named lines were slot 1 instances). Single-part programs unchanged. SAME BUILD, his two renames: (CONDITION-VARIABLES) -> (CONDITION-CLASS), (MATERIAL-SELECT) -> (M100-SELECT) in every dialect's header (no parser read either string; one test filter updated to match the M100[ variant form). Proven: test_nc_warn 12->17 controls (O33286: 10 findings = 5 holes x 2 subs covering all 950 instances) + 12 neighbour suites green. Live after the next owner-turn restart.
- •The plain-words MATERIAL RECORD replaces the (MATERIAL : MSO7,...) header line -- job-card traits in the code and on the floor pages record — Jordan 2026-09-05 ruling on O33339's '(MATERIAL : MSO7,0.080)': 'I think that particular line could be replaced. MSO7,0.080 serves no purpose. Our M100s offer the laser operator adequate options, but right now we rely on a paper job card to identify specific material traits, and this could enhance that by putting that information both in the code, and on the pdf with the nest and parts.' Field list confirmed same day: type, grade, thickness, customer-supplied vs shop-procured, plus lot/heat ('put a place to include lot/heat number, but it is not used by us often. Not saying it's never used.'). BUILT same day. ENGINE: emit.write_gcode_macrob(mat_record=) -- emit._mat_lines replaces the bare post-key line with job-card comment lines in that order ((MATERIAL/GRADE/THICKNESS/SUPPLY/HEAT/LOT : ...), values sanitized like every typed header note, blank fields never post a line); M100 untouched -- it stays the machine word; mat_record=None byte-identical (legacy callers, board scripts). cl_post passes it through (one kwarg, the shared writer). AUDIT COMPAT: nc_audit._header_material returns a key only when the line's value is key-form ('<name>,<thickness>'); a plain-words header yields None and the explicit material= every app surface passes governs -- legacy delivered programs still parse. SERVER: job.json material_record (typed fields + provenance, 'who typed it awaits operator accounts'); GET/POST /api/jobs/<id>/matrecord = annotation only, record-only (saving drops nothing -- the next post carries it; delivered programs stand per the no-redelivery precedent); junk field/supply/over-60-chars refuse plain-400 with nothing saved. ONE effective dict (server._matrec): typed fields over table seeds -- type + thickness seed from the assigned Rev2 row (seed never bind), sources recorded per field (operator vs table:material-row). Every app posting surface passes it: quote, post, postnest (macro + part-by-part), plpost, commonlinepost. PAPER: the same dict rides packet.json and renders on all three floor packets (single/nest/part-list) -- 'in the code, and on the pdf with the nest and parts'. UI: 'Material record (job card)' section on Part review AND the sales Quote drawer (one renderer, sales and operator share it). Proven: test_matrecord.py 30 controls + 16 neighbour suites green. Honest limits: part-list jobs carry seeds from the list's material but have no typed-entry surface yet (their two tabs); the board deliver scripts stay legacy-line (mat_record=None, byte-identical); customer-sheet material sentence unchanged (already plain words by derivation).
- •FEATURE replaces BND in posted programs -- Jordan's word, swept end to end, both markers parse record — Jordan 2026-09-05: 'Can we replace all the BNDs with something a bit more modern? It feels so 90s.' -> same day, 'Let's go with FEATURE' -- his own ruled vocabulary (2026-08-28: the old CAM's entities are called features going forward). BUILT same day: emit.write_gcode_macrob and cl_post mark every boundary (FEATURE:n); finding/anomaly messages say 'feature n' (rules.py comp/tab/pierce/outer-last wording, nc_audit tooling-mismatch/micro-block/geometry-deviation wording, cl_post's common-line findings, the app's cut-plan step rows and unconsumed-override lines). The parsing contract holds BOTH markers -- nc_audit (_load stop line, _comp_words, _tooling_words, _short_blocks, expand_p9997's per-sub counts + renumbered re-emit), nc_warn (_macro_map + spot-marker anchors), pierce_clear.parse_nc, cl_post's band splitter/timer/audit, compare_nc (dialect sniff, parse, header) all accept (BND:n) too, so every delivered program still audits byte-for-byte (proven: O33286's macro expansion + ex2's plain audit unchanged; a FEATURE post rewritten to BND markers judges identically). Internal dict keys (bnds, bnd ids) stay -- they are code, not shipped words. test_nc_warn 17->23 controls; 20 suites green. Live in the app after the next owner-turn restart.
- •Per-job sheet size: sales inputs sheet size(s) at quoting; operator changes it easily at any time while nesting record — Jordan 2026-09-05 ruling (his drop/reorder scenario): 'While quoting: sales team should input sheet size(s). While nesting: operator should be able to change sheet size easily at any time.' BUILT 2026-09-07 on his 'Go on all': POST/GET /api/jobs/<id>/sheetsize -- {w,h} inches (w along machine X, the operator's word never auto-swapped) or {clear} back to the machine bed; RECORD-ONLY save (the units-confirm precedent: nothing drops, an existing layout stands byte-identical and the drawer names it stale in a yellow until a re-nest -- the operator's work is never silently moved); junk refuses plain-400 in honest words nothing saved; an over-bed sheet saves WITH the yellow in words (warn never block -- the physical call stays the operator's). All three pack-time doors consume it via one helper server._sheet_wh: the TRUE nest (run_nest), the PART-LIST pack (run_partnest) and the COMMON-LINE plan (run_commonline); nest.json/partnest.json record sheet ran+source (operator vs machine bed); quote's auto-nest and every downstream reader (judge, spread, delivery, canvas) ride the persisted record unchanged. UI: one Sheet size renderer on three doors -- Nest drawer, part-list Nest drawer, Quote drawer (the ruled sales door). Proven: test_sheetsize.py 20 controls + app/verify_sheetsize.js 10 live real-mouse Playwright checks (typed 48x48 end to end, stale-layout yellow, over-bed, back-to-bed, sales lens). Live after the next restart; the drawer UI serves from disk but rides the new endpoint. Honest limits: ONE sheet size per job today (the ruling's 'size(s)' plural -- several stock sizes with the packer choosing -- is a later extension); who typed it awaits operator accounts. | QUESTION 2026-10-10 (Jordan, beside the leftover-default answers): 'when nesting, we should be able to add a sheet of a different size' -- his Roush case: a 48x120 sheet of 1/2 aluminum plus a 36x48 DROP of the same stock, and another job's 1/2 aluminum parts he wanted to try nesting together with the Roush parts. Measured today: a part-list pack runs ONE sheet size for every sheet (partnest.json sheet {w,h}); parts from other jobs CAN already join one list (Add from existing jobs). Proposal: a per-pack SHEET INVENTORY -- rows of {w x h, count or 'as many as needed', stock vs drop}, the packer fills in an order (drops first by default, so remnants get used up), each sheet program/quote keyed to its own size; the quote prices a drop as stock on hand. Open questions to Jordan before building. Nothing built. | SHEET LIST ENGINE BUILT 2026-10-10 (record, chunk 1 of 4; Jordan '1. Can we do a priority list? 2. different prices to each sheet size? 3. typed in per nest ... 4. If everything is clear, then go'): NEW part_list_nest.pack_sheet_list(items, entries, table_gap, standoff, pack_fn=) -- an ORDERED list of sheet entries {w, h, count (None = as many as needed), kind stock|drop, price}; list order IS the fill priority; each entry packs the parts still to place that fit it through the ONE pack function (strategy road unchanged via pack_fn), a finite count keeps that many sheets, placed parts are subtracted, a part too big for an entry waits for a later one, parts left after the last entry refuse in plain words; one unlimited entry = exactly the plain pack + sheet_sizes; report carries sheet_sizes per sheet (size, kind, price, entry) for per-size programs and quote. Honest limits: priority is a fill order not a global optimum; filler extras only top up while that part's asked copies are still being placed. Engine only, no caller yet -- chunks 2 door+storage, 3 Nest UI, 4 per-size post + quote price. NEW test_pl_sheet_list 22 + test_part_list 41 zero edits; identity gate green; F1 8.08/7.44, 8.08/7.38 -> 8.05/7.37, 8.09/7.41s (no cost); zero dev O-numbers. | SHEET LIST CHUNK 2 -- DOOR + STORAGE 2026-10-10 (Jordan 'Go on chunk 2'): the per-nest sheet list records on the job through the existing sheet-size door -- POST /api/jobs/<id>/sheetsize {sheet_list: [{w, h, count (null = as many as needed), kind stock|drop, price}]} validated by pln.norm_sheet_list, stored job.json sheet_list {entries, source, date}, null/[] clears; part-list jobs only (a one-part nest refuses in plain words); record-only like the single size -- the next pack consumes it, an existing layout stands; junk refuses plain-400 with nothing saved; over-bed sizes warn. run_partnest packs over a recorded list through pln.pack_sheet_list, each entry running the SAME method resolution (operator pick > job method > shop default > audition; one select_pack per line, cancel threaded); no list = the single size byte-identical; a run-out blocks the stage naming the parts left, layout untouched; the remembered-winner memo neither reads nor writes on a sheet-list pack (its fingerprint is one size) -- the existing memo is carried untouched. Pack record: report.sheet_sizes per sheet, sheet = sheet 1's size + source 'sheet list' + mixed flag, rep.sheet_list_note. ONE-SIZE DOORS on a MIXED-size layout refuse in honest words naming the sizes (NEW _pl_one_size): Spread/Jam, Update nest (incl. the landing auto-update), hand editing, the variant fork, the list quote, delivery (sheet prints). Posting needs no guard (programs are per sheet, sheet size never enters the NC). A same-size list is not mixed. Honest limits: Nest canvas still draws every sheet at sheet 1's size until chunk 3; no UI yet. NEW test_pl_sheet_door 28 + test_part_list 41 / pl_sheet_list 22 / plforget 14 / pl_cancel 11 / nest_default 18 zero edits + verify_partlist 19 (suite-only unstale: Quote after Nest since the list-quote build) + verify_plsel 30 on scratch; identity gate green; F1 8.08/7.40, 8.05/7.37 -> 8.05/7.37, 8.08/7.37s (no cost); zero dev O-numbers. Dev restart needed for the server half. | SHEET LIST CHUNK 3 -- ON THE NEST TAB 2026-10-10 (record; Jordan's answers '1. separate', '2. gray it out', '3. a quantity setting... grayed out when we click "use as many as needed"' + 'go ahead with chunk 3'): the part-list Nest drawer carries a Sheet list editor in every state (packed, unpacked, blocked) -- each line a two-row card: W x H, stock|drop, up/down/remove, count (greyed while 'as many as needed' is ticked), price per sheet ($ accepted); '+ sheet' starts the first line from today's single sheet (stock, as many as needed) and later lines blank as a drop with count 1; Save only records through POST /sheetsize {sheet_list} (Pack stays its own click), server refusal shown on the drawer in its own words with the draft kept and nothing saved; discard changes / clear list; the single sheet size greys under a list with 'overruled by the sheet list below'; honest notes when the layout on screen was not packed on the recorded list or was packed on a since-cleared one. Packed drawer: each sheet's own size, kind and price, what each list line was used for (n of count / as many as needed / why skipped), MIXED SHEET SIZES banner naming the features that still refuse. Canvas: every part-list sheet draws at its own report.sheet_sizes[i] on one pitch = the widest sheet (a one-size layout keeps the old arithmetic), labels carry the kind, extents fit the tallest sheet; hit tests use the same pitch. Hand editor refuses at the gesture on mixed sizes (toast), the Nest-landing auto update stands down on mixed sizes and the stale banner offers Pack again instead. Client-only (app.js/app.css), no server change. NEW app/verify_sheetlist.js 24/24 on scratch + partlist 19 / pltabs 24 / plhand 27 / plrefresh 27 / refusal 16 / plsel 30 / plcancel 18 zero edits; identity gate green; F1 n/a (client-only); zero dev O-numbers. Chunk 4 (per-size quote + delivery prints, then lift the guards) remains. | SHEET LIST CHUNK 4 BUILT 2026-10-10 (record; Jordan 'If it's clear, let's build chunk 4'): the part-list quote prices every sheet at its OWN size and price -- a typed list price wins for its line ('typed on the sheet list'), an untyped line falls back to its size's shop-table cost, a missing row blocks naming that size; the leftover rule runs per sheet against that sheet's own width; usage = net area over the summed sheet areas; no list = chunk 3 byte-for-byte. Delivery draws every sheet at its own size (sheet DXF unchanged, shop/customer previews name the size, operator PDF page per sheet at its size, 'drop' named), v.sheet_sizes + usage.sheets_in2 recorded. _pl_one_size lifted from the list quote and pldeliver; it stays on Spread/Jam, Update nest, hand edit, variant. RULING (Jordan, same message): those four get solved PER SHEET (each reads its own sheet's size) -- next chunk, intent. QUESTION (Jordan, same message): 'where a sheet would ideally be used more than once ... run this nest/sheet/program X times' -- no identical-sheet detection exists today; one program per sheet still posts; design questions asked (collapse identical sheets into one program + run count vs message only), nothing built. | RUN-X-TIMES ANSWERS 2026-10-10 (question, Jordan's numbered reply): (1) yes -- identical sheets post as ONE program with a run count, and the count must be clear throughout the process (Nest tab, G-code header, operator PDF, Deliver, quote; quote still charges every sheet and load); (2) 'If the quantity of each part is the same, then why bother writing another program? Let's use the same one multiple times' -- read as: sheets carrying the same parts in the same counts (same size + material) should share one program even where the packer placed them differently, i.e. the layout is standardized onto one sheet's arrangement; awaiting his confirm on that reading; (3) independent of the per-sheet Spread/Jam/Update/hand-edit chunk; a manual edit that changes part quantities on a repeated sheet must WARN the operator. Follow-ups asked: edit one repeat vs all repeats, partial last sheet, whether the packer should aim for repeats. Nothing built. | RUN-X-TIMES SECOND ANSWERS 2026-10-10 (question, Jordan): (2) CONFIRMED -- sheets carrying the same parts in the same counts share ONE program, the packer's layout standardized onto one representative arrangement; (4) RULED -- the operator sees ONE sheet with an obvious 'run X times' note, so editing that nest edits every run by construction (one program); the warning fires when an edit changes part counts (totals move by X per part); (5) yes -- a partial last sheet stays its own program; (6) his question 'wouldn't the optimal pack yield the same quantities every time?' -- MEASURED no on mixed kits: the packer fills each sheet tight with whatever fits, so contents differ; dev's lathrup-rfq 10-sheet pack (29 distinct parts) has exactly ONE natural repeat (sheets 6+7, 8x LV00151-2604 each); repeats come naturally on single-part and long same-part runs; aiming for repeats on purpose stays a later option that shows its material cost; (7) agreed -- same size, stock/drop and material too. Nothing built; chunk plan offered. | RUN-X-TIMES: FAVOR REPEATED NESTS (Jordan, 2026-10-10 -- question): Jordan's example -- 3 huge + 6 medium fit one sheet, order is 9 + 18 -> ONE optimal pack run 3 times; 'easier, less prone to human error, and more efficient to run the same program multiple times'; 'we ought to favor having fewer nests run multiple copies. Think about this?' Today's sequence (measured from part_list_nest.pack): greedy -- fill sheet 1 as full as it goes with the biggest parts first, then sheet 2 with what is left, so a run like his comes out as sheets with different mixes even when a clean 3x repeat exists. PROPOSAL (unbuilt): a REPEAT candidate joins the method audition -- for each run count k that divides the order (or nearly: k runs + a small leftover sheet), pack ONE sheet holding qty/k of each part; if it fits, that is k runs of one program + leftover sheet(s). Rule proposed: same sheet count or fewer -> the repeat form WINS by default (no material cost, fewer programs); costs extra sheets -> both shown with the material/cost difference, operator picks, with a shop setting for how much extra the shop accepts. Supersedes the 'no aim-for-repeats for now' line of the second answers once ratified. Awaiting Jordan's answers; nothing built. | RUN-X-TIMES: FAVOR REPEATS -- JORDAN'S ANSWERS + HOLD (2026-10-10, question): (1) found ambiguous -- restated: when a repeat pack uses the same sheet count as the best pack, take it automatically or ask each time; read from his (3) as automatic, awaiting his correction. (2) NO extra material for repeats -- optimize material first, so a repeat that costs an extra sheet is not taken (no shop 'accept extra' setting). (3) YES -- at the same overall sheet count, a close repeat (slightly less full sheet) counts and wins. HOLD (Jordan): this touches the nest algorithms Project Speed is working on, so nothing is built until it is worked out with Aristide (and the speed chat) first. Nothing built. | RUN-X-TIMES Q1 CONFIRMED 2026-10-10 (question; Jordan, his answer to the restated Q1: "Yes, I think this would favor repeats, which we've agreed is better overall"): when a repeat layout uses the same number of sheets as the best mixed layout, the software PICKS THE REPEAT by default -- no ask each time (operator can still choose another method, as with every pick). Jordan defers the rest (build timing, who owns it) to Aristide so nothing undoes Project Speed progress. STILL HELD: awaiting Aristide on (1) build on dev now as its own candidate vs wait for Speed's packer merge, (2) whether the speed chat owns it. Nothing built. | RUN-X-TIMES OWNER ANSWERED 2026-10-12 (Jordan, Aristide present): 'You own it. And yes, you build it. Speed will pick it up after you're done.' -- the dev chat builds run-X-times; the speed chat optimizes after. Rules standing: repeat only at no extra sheets, picked by default at equal sheet count. Not yet built. || RUN-X-TIMES CHUNK 1 BUILT 2026-10-12 (Jordan 'Sounds good. Go.'): NEW nesting method 'repeat' (repeated sheet -- one layout run several times), last in the audition roster. part_list_nest.pack_repeat: the unit = floor(qty/k) of each part, k tried upward from the true-area lower bound until the unit packs on ONE sheet with the 'runs' method (k+1 also tried when a remainder exists); remainder on partial sheet(s); best = fewest total sheets, then no partial, then least used X. Report is EXPANDED (k copies + partials) so posting/quote/delivery run unchanged; report.repeat {runs, copies, partial, unit, inner, tried, note}. Ranking: repeat wins at sheets <= the best plain method's (Jordan's Q1 -- no ask), else shown 'costs N more sheet(s) than <method> -- never picked automatically; pack with it to use it'. Filler extras not offered on a repeat (said in the note). Refusals plain: no part qty >= 2 / no one-sheet layout. repeat_holds drops the label (repeat_dropped) once spread/hand edit/variant make the copies differ. Nest drawer: green REPEATED SHEET banner, sheet 1 'run k times', copies skipped in the rows, partial sheets named; canvas draws copies faint. HONEST LIMITS: posting still one program per sheet (chunk 2 = one program + run count, partial its own program); edit-one-edits-all + qty-change warning = chunk 3; a new roster key changes judge_fp, so remembered winners re-audition once. Proven NEW test_pl_repeat 22 + roster edits test_pl_select 28 / test_pl_free 42 / verify_plsel 30 (5->6 candidates) + judge_cap 28 / part_list 41 / pl_sheet_list 22 / pl_cancel 11 / pl_sheet_door / verify_judgecap 9/9 zero edits; Jordan's 9+18 kit -> (3+6) run 3 times CHOSEN; live scratch 78017D04A x16 -> 3 runs of (32+64) picked; identity gate green; audition 78017D04A 2.2 -> 2.2s, BNM78604 159.7 -> 159.5s (no cost); F1 n/a (pack path); zero dev O-numbers.
RUN-X-TIMES CHUNK 2 BUILT 2026-10-12 (Jordan 'Go on chunk 2'): a repeated sheet POSTS ONCE -- run_plpost posts the first copy sheet as ONE program carrying its run count (header line '(RUN THIS PROGRAM k TIMES - k IDENTICAL SHEETS)' right under the title, label 'sheets 1-k/N run k times'), the copy sheets get no program, each partial sheet keeps its own program; programs carry runs + sheets_run, plpost.json a repeat block {program, runs, sheets, note}; O-numbers keep BY PROGRAM POSITION (pl_onums per program); the run count holds only while pln.repeat_holds (copies placement-identical) and no clicked sequence sits on a copy -- otherwise every sheet posts alone, honestly. Delivery: coverage counts sheets_run, parts/usage count every run, part map lists every run's placements under the one program, floor packet 'Sheets 1-k: O... RUN IT k TIMES', board line names the run, customer sheet 'k identical sheets' (no program numbers), operator PDF one page 'sheets 1-k of N' + red 'RUN THIS PROGRAM k TIMES' + 'parts per sheet, x k runs', part copies counted per run. Post drawer green REPEATED SHEET banner + 'sheets 1-k -- O..., run kx' rows; Nest banner wording updated. runs=None on write_sheet_subcall = byte-identical. Proof: NEW test_pl_repeat_post 26 (30x40 x10 -> 3 runs + 1 partial = 2 programs / 4 sheets, broken copy -> 4 programs, plain pack untouched) + pl_deliver 28 / post_cancel 30 / pl_repeat 22 / pl_macro 28 / pl_origin 13 / pl_sheet_price / part_prints 6 zero edits; operator PDF page read visually; identity gate green; F1 n/a (probe times the plan door; post change is bookkeeping on plain packs, a repeat posts k-1 fewer sheets); zero dev O-numbers (scratch progseq). Chunk 3 (edit the shown sheet = edit all runs + qty-change warning) stays intent.
RUN-X-TIMES CHUNK 3 BUILT 2026-10-12 (Jordan 'Chunk 3 of run-X-times. Do that now.'; his 2026-10-10 ruling 'the operator sees ONE sheet with an obvious run-X-times note, so editing that nest edits every run'): NEW part_list_nest.mirror_repeat -- a hand edit (run_plhand) on any run of a holding repeated sheet is written onto EVERY copy sheet before judging/saving (one layout, one program); edits on two runs that DIFFER are both kept and the label drops honestly (nothing thrown away); partial sheets never mirrored. Per-run count changes recorded on hand.repeat {mirrored, runs, source, counts{per_run, total}, note} and repeat.unit restated; asked-beside-filled qty override unchanged. Variant fork (run_plvariant) on a repeated placement repoints the same placement on every run, note names the runs. Client: hand bar says 'sheet 1 runs k times -- an edit on it applies to every run'; Apply asks a confirm when the per-run counts change, naming each part 'a -> b per run (A -> B across the k runs)' (warn, operator picks); toast 'applied to all k runs'. Spread already kept copies identical (proven). HONEST LIMITS: a clicked nest sequence is not mirrored (chunk-2 rule stands: a sequence on a copy posts every sheet alone); the confirm counts the k runs, partial sheets not in that total. Proof: NEW test_pl_repeat_edit 24 (move on sheet 1 / on run 2, add copy 0->1 per run = 0->3 total, two differing edits drop, variant on all 3 runs, spread keeps, plain pack untouched) + pl_repeat 22 / pl_repeat_post 26 / pl_select 28 + verify_plhand 27 / plvariant 10 / plhrot 11 zero edits + real-browser probe (remove on a 3-run sheet: confirm text, 3/3/3 -> 2/2/2, label holds, toast); identity gate green; F1 n/a (plan door untouched; mirror is O(placements) on the hand door); dev restarted (inflight 0/0, Jordan's standing OK); zero dev O-numbers. MIXED-SIZE SPREAD QUESTION 2026-10-15 (question; Jordan on a large job on app -- Spread X/Y/All refuse 'mixed sheet sizes', 'I do need it to be a feature that we can use somehow. Let's discuss'): the refusal is the chunk-2 honest gate _pl_one_size (Spread/Jam, Update nest, hand edit, variant fork still read ONE sheet size); measured: the spread loop already runs per sheet, only sheet_w/h + the closing pln._audit take the first sheet's size -- per-sheet form = each sheet evens to its OWN edges, audit per sheet at its own size, single-size byte-identical. Open questions to Jordan: each sheet to its own edges vs aligned across sheets; one click = all sheets vs the sheet on screen; Spread All regularization per sheet; order of the other gated doors. He uploads the job to dev as the test fixture. Nothing built, zero dev O-numbers. MIXED-SIZE PACK MEASURED 2026-10-15 (question): Jordan's 47-row / 118-pc Stainless 0.105 list on the sheet list (9 x 120x48 stock, 7 x 96x48 drop), method 'runs' (his pick), packed in 25m46s (16:04:34 -> 16:30:20 UTC) -- a defect against perf-target-seconds-everywhere; cause unmeasured (suspect: pack_sheet_list re-packs per sheet line), profile on a copy queued. Result: 13 sheets = all 9 stock + 4 of 7 drops, 118/118 placed, used X 65.6-118.6. Spread Y on it refuses at the mixed-size gate, partnest.json byte-unchanged (md5). Nothing built. MIXED-SIZE SPREAD PROPOSAL 2026-10-15 (question; Jordan 'how do you propose we solve the spread functions when using multiple sheet sizes?'): every sheet is spread at its OWN size -- each sheet reads its width/height from the pack's per-sheet sizes, the closing clearance audit runs per sheet at that sheet's size; Spread Y/X/All and Jam Y/X act on every sheet in one click as today, each to its own edges; Spread All snaps a grid per sheet; single-size layouts byte-identical; then Update nest, hand edit, variants unblock one chunk at a time. Speed profiling handed to Aristide + speed chat (standing-reminders). Nothing built. PARKED 2026-10-15 (Jordan: 'park this for now ... I don't want to affect anything that speed is working on. But we do need a quick way to spread parts on jobs like this'): per-sheet Spread/Jam on mixed-size layouts parked; need stands, form open to whatever does not touch Speed's work. Nothing built. | MIXED-SIZE SPREAD/JAM BUILT 2026-10-17 (Aristide 'go ahead now' on Jordan's parked 2026-10-15 ask): Spread Y / X / All and Jam Y / X now run on sheet-list layouts with mixed sizes -- each sheet spreads at its OWN size and is audited against it (new _pl_sheet_wh + _pl_audit_sized; one size = the single pln._audit call exactly, so ordinary jobs are unchanged); refusals name the sheet and its size; Update nest, hand edit and variants still refuse on mixed (next). Found and fixed on the way, older than this change: Jam held gaps exactly at the ruled minimum so 4-decimal rounding landed a hair under and the audit refused (Jordan's job, and a one-size copy with the old code) -- Jam now keeps two counts (0.0002) of room per gap where the column has it, the true-gap road's own guard; jam outputs move 0.0002 per gap by intent. Jordan's 118-pc Stainless 0.105 job (9 x 120x48 + 4 x 96x48): all five clicks pass, ~11-12s each (the existing part re-plan cost, D6). NEW test_pl_spread_mixed 14 (old one-size audit misses a part off a 96 drop -- the defect twin), test_pl_spread 80 (jam controls updated to bridge + guard), test_pl_sheet_door + verify_sheetlist 24 updated to the intended change (sheetlist check 19 was already stale since chunk 4), truegap 13, repeat_edit 24, sheet_list 22, sheet_price, pl_free 42, column_join 13, verify_srcdl 20 green; identity gate green; F1 n/a (spread door, not on the first click); zero dev O-numbers. | MIXED SIZES PER SHEET -- UPDATE NEST / HAND EDIT / VARIANT FORK 2026-10-18 (Aristide 'can both these be done in one run? if not do just one first' -- this one first): the three last one-size doors now judge every sheet at its OWN size; _pl_one_size removed. run_plrefresh audits via _pl_audit_sized (now with misses= collect mode, each Update-anyway miss on its real sheet named 'sheet N (WxH)'); run_plhand + run_plvariant judge via pl_tool.judge_pairs(sizes=_pl_sheet_wh(pn)). One size = the old arithmetic exactly (controls 1d/2b). Client: hand editor opens on mixed layouts, drop/band/dock pitch = plPitchW (widest sheet), dock edges = that sheet's own size; the mixed stale banner and the auto-update skip are gone (Update nest runs in place); mixed banner now says every door works per sheet. NEW test_pl_mixed_doors 14 (on Jordan's 118-pc job copy: x that is legal on 120 and off a 96 drop flags only the drop; the one-size judge/audit missed it), test_pl_sheet_door updated to intent ALL OK, plhand 25, plvariant 23, spread_mixed 14, spread 80; browser on scratch sheetlist 25, plhand 27, plrefresh 27, plvariant 10. Identity gate green. F1 n/a (pack/post unchanged); Update nest on Jordan's mixed job 12.6/12.4s (new -- the door refused before; time is the re-plan of 47 parts). Live on dev after the next restart.
- •Sub-program numbers TRACKED in the shop sequence + manual override -- never handed out twice, kept per job, typed on the operator's call record — EXTENDED 2026-09-18 (Jordan: 'In the Post tab, it's not letting me override the program number, why is this?'; Aristide 'go'): measured cause -- the field's own placeholder shows the number AS 'O33342', so operators naturally type the O, and the single-part and nested-sheet doors read the field with a bare parseInt -- 'O33344' parsed NaN and the post SILENTLY ran with the job's kept number, no message (the part-list door already stripped the O since the 2026-09-17 build; the asymmetry was the proof). Fixed client-only in app.js: ONE shared parser (onumField) on all three doors plus the per-orientation nest sub fields -- strip a leading O/o and whitespace, then digits only; text that still does not parse REFUSES on the drawer in honest words naming the typed text (doorRefused, the persistent-banner seam from prod-post-loss-incident) and posts NOTHING -- a typed override is never dropped silently again (no-slop). NEW app/verify_onumparse.js 13/13 on the scratch instance (O-typed main/sub/part-list numbers take with source operator; bad text refuses and the posted program stands untouched; bare digits unchanged; lowercase o too); verify_refusal.js 16/16 green. The Sep-1 one-shot probe verify_onum.js (old URL, manual job id) stands as history. --- EXTENDED 2026-09-17 (Jordan: 'Where can I change the program number? We are out of sequence with our real shop, and remember, we should always have the option to override'): the PART-LIST post gets the same program-number door the single and nest posts carry -- run_plpost already took onum/onum_mode on sheet 1 (operator outranks the job's kept number; use-once vs new-sequence, reserved/used yellows ride as callouts) but the part-list Post tab never rendered the field and sent an empty body. Now: program-number input + override-mode select on the part-list Post section (app.js plOnumFields, placeholder = the job's current number), runPlPost sends {onum, onum_mode} when typed. Client-only + existing server door; seed never bind. --- ORIGINAL RECORD: Jordan 2026-09-06, his #6 on the 'Go on all' (proposal approved verbatim: 'record every sub number in the shop sequence file so nothing ever hands one out twice, and add a sub-number override on the Post drawer, recorded source:operator like the main'). BUILT 2026-09-07. Before this build subs were purely DERIVED (main+42000+k in angle order) -- two consecutive mains with two orientations each would COLLIDE (33339 -> 75339/75340 while 33340 -> 75340), and a program made outside kerfmaster could not be declared to the sequence at all. Now: server.next_subnums assigns every sub -- SEED stays main+42000 (the corpus convention, so existing jobs keep their exact numbers on the first re-post), but the auto counts past every number recorded in progseq.json ('subs' list), every used main (last + used_once), the reserved ranges (9000-series macro space, parked numbers) and the main itself; every number it hands out -- auto, kept or typed -- is RECORDED under the same lock the main sequence uses, so nothing is ever issued twice. A job KEEPS its subs across re-posts AND re-nests (stage record sub_onums, per sheet keyed by orientation -- _drop_postnest stashes them exactly like the mains; an orientation that survives a re-nest keeps its sub, a new one draws fresh). OVERRIDE: 'sub_onums' on POST /api/jobs/<id>/postnest maps orientation -> number (sheet 1, the main-number convention), recorded source:operator and kept thereafter; a collision with a recorded sub / used main / reserved range posts on the operator's call with a YELLOW riding in the NC as a header callout (warn never block -- the ruling-B precedent). Broken-program shapes are plain 400s in honest words, nothing saved: two subs sharing one number, a sub carrying the main's own number (the M98 would call the program into itself), junk value, an orientation the layout does not have (refusal names the layout's own orientations). The MAIN sequence knows the subs too: next_onum's auto counts past recorded subs, and typing one as a main warns it is a sub-program number. Both program styles ride it -- macro (P9997 subs) and part-by-part (G52 + M98 sub calls). UI: per-orientation 'sub number' inputs on the Post tab's nested-sheet section (placeholder = this job's current sub; an untouched field never flips source), per-sub source tags + collision yellows in the drawer. Proven: test_subnum.py 21 NEW controls (the old collision reproduced-and-gone, keep across re-post/re-nest, override end to end incl. the O90210 bytes in the posted file, refusal ladder verbatim, warnings riding in-file, main-sequence awareness both directions); neighbour suites green (progstyle 29 / seqexact 16 / seqcorner 17 / gseq 18 / sheetsize 20 / nestedit 38 / nestseq 27 / nc_warn 23 / nestenv 19). Honest limits: the override door is sheet 1's program (further sheets keep their tracked autos); pl_post part-list programs have no subs (part-by-part by construction, absolute one-program form); the pierce macro M98P9011 is a control-resident program, not ours to number. The nest-name-prog-number open question narrows: sub reserved-ranges handling is CLOSED (tracked + skipped); sequence SCOPE (shop-wide vs per machine) stays open with Jordan. | TYPED FIRST SUB NUMBER 2026-10-16 (Jordan's fix list item 8): 'sub_start' on postnest/plpost numbers the subs from the typed start in posting order, each judged like a typed override; per-orientation sub_onums and sub_start together refuse ('type either'); a sub/main collision inside one post refuses before recording. See pin jordan-fix-list-2026-10-15.
- •NC download filename = bare program number (33385.nc, no O) record — Jordan, 2026-09-17: 'When we download the GCode, the filename does not need the O at the beginning, so just 33385.' The O is Fanuc's program-word INSIDE the file; the shop's own corpus files are bare numbers (33199.NC, 33215.NC), so downloads now match the shop's filing convention. Applied everywhere an NC leaves the app: single-part post.nc, nested postnest.nc, common-line and part-list sheet program download buttons (app.js download= attrs + visible labels), and all three delivery writers (run_deliver / run_delivernest / run_pldeliver) name the shipped file {onum}.nc. Delivered versions are immutable, so pre-existing sets keep their O-prefixed names; new deliveries carry the bare number. Suites: pl_deliver 27 / nestdeliver_rot 14 / matrecord 30 / robust 50 green (robust check 40 expectation also refreshed for inject()'s added 'distinct' key -- stale from the 2026-09-17 grouping build, caught here).
- •Automatic true nest spaces on the TOOLING envelope; stamp replaces its own block; delete follows the entity record — BUILT 2026-09-05 on Jordan's three asks in one message -- his 'Yes.' on the standing question (does the AUTOMATIC nest's X spacing use the tooling boundary?) plus two hand-editor notes. (1) TOOLING-ENVELOPE SPACING on the automatic true nest -- the brick-3 bare-bbox honest limit closed: nest_rules.tool_envelope(bbox, plan, symmetric=) unions the part bbox with every reviewed-plan pierce point and lead end (nest-objective-function: the unit is part + lead + pierce envelope, never bare geometry; a segment's bbox is its endpoints', no sampling); run_nest spaces the grid, per-sheet capacity and pitches on the envelope -- 180-symmetrized about the part centre for the alt patterns so both orientations ride one regular lattice, the plain all-0 grid keeping the tight one-sided envelope -- and recorded placements stay part-bbox anchors inset by the lead room, so postnest array decomposition, the judge and every canvas read unchanged conventions. nest.json carries tool_env {w,h,pts,symmetric,source}; no plan points = bare bbox, source says so honestly. (2) STAMP REPLACES ITS OWN BLOCK (Jordan: rotate, stamp, change the repetition -- 'each step created a new nest on top of the old one. Maybe just keep one?'): stamp-made entities are tracked (draft E.stamped, persisted as layout_edit.stamped -- validated whole-number gids, pruned to the groups, junk = plain 400 nothing saved); re-stamping from a part of a stamped block deletes the block's other copies first and stamps fresh -- one stamp per base, never a stack; a packed or hand-made nest is never touched by the replace; undo snapshots carry the flags; survives Apply + reload. (3) DELETE FOLLOWS THE ENTITY (Jordan: deleting duplicates one at a time 'doesn't jive with our select-nest function' -- he was right): with no band selection, Delete/Backspace and the Remove button take the clicked part's WHOLE nest in the default nest-drag mode, one part in single-part mode; the button labels itself 'Remove nest'/'Remove part'; band selections delete exactly as before; every path snapshots for Undo. Proven: test_nestenv.py 19 NEW controls (envelope math incl. symmetric mirror, run_nest pitches = envelope + gap on a live fixture whose outer lead extends the box 4.0 -> 4.15, placements at margin + inset, capacity honest, stamped persistence + refusal ladder) + app/verify_stampdel.js 15 NEW real-mouse Playwright checks (auto nest records the envelope, stamp 2x2 -> re-stamp 2x3 = 9 parts never 12, replace survives reload, nest-mode Delete takes 6, part-mode Delete takes 1, undo restores); suites nestedit 38 / seqcorner 17 / handspread 27 / nestseq 27 / progstyle 24 / sketch 21 / customer 26 / nc_warn 23 / tooling_doc / rules 14 / drag 23 / tuck 22 green; verifies bandsel/groups/groupsnap/handsafe re-run green. verify_nestedit2 found STALE two builds deep (bare-bbox pitch expectation vs the snap-to-tooling seeds; a group-mode snap drag moving the whole stamp block), not a code defect -- updated to current semantics, 10/10. Server+engine live after the next restart (Jordan can /restart); the client half serves from disk immediately.
- •Seq display IS the program: the posted G-code executes exactly the order the interface shows -- NO EXCEPTIONS (0-tolerance, 'NO SLOP') ruling — Jordan 2026-09-06 on O33339 (second array cut bottom-up while the boxes showed 37 starting top-left): 'the GCode must be an EXACT representative of what we set in the interface: NO EXCEPTIONS! This software will be advertised as NO SLOP... If 37 is displayed as the second grid's starting point: top-left corner, then the GCode MUST reflect that. I will have a 0-tolerance policy with this.' The code follows the display, never the reverse; and 'the macro can absolutely reflect the displayed order -- if you post it correctly': negative J-values ARE accepted by the Mitsubishi ('Mitsubishi will read the code you write, let's make sure we write it correctly').
- •Tab consolidation -- one Geometry tab (sketch/intake/heal/QC), one Tooling tab (review+cut plan): Jordan's workflow shape; BOTH pieces BUILT record — Jordan 2026-09-06, verbatim: 'The purpose of my question to both of you: in my workflow, sketch, intake, heal, and QC would all be on the same tab with a full set of tools to insert or modify primitives. The cutting-edge that we would bring to the market is having the customer supplied source in a background layer so that we could always review whatever automatic healing, or manual editing against the original. I want to keep that, and build a user-friendly, comprehensive interface on it. Second, in my workflow, part review and cut plan would be the same tab. Again, a full stack of tools including sequencing, modifying lead-ins, tabs, offsets, condition classes, etc. all in one. Are there any flaws in my logic? If not, let's talk about doing this in the next build.' His use case for inserting on an uploaded job: 'If we have an existing job, and the customer says they want to add a hole or change one feature, but they don't have a cad file to give us, then this enables a quick solution.' GO given ('Why not both?' queued it behind per-nest sequencing; 'Go' 2026-09-06 started it). PIECE 1 BUILT same day -- ADD PRIMITIVES on any job: heal_edit add_line / add_circle / add_arc ops in the SKETCHER'S OWN typed forms (line by endpoints, circle by center + DIAMETER landing as the CIRCLE-diet semicircle arcs, arc by center/radius/start-end degrees), recorded on the heal-edit list, replayed verbatim on every re-heal (typed absolute coordinates -- nothing point-addressed to go stale), removable per row, refusals EditInvalid in the engine's words (zero diameter/length/sweep, junk numbers) plain-400 nothing saved; the pipeline's fidelity measure EXEMPTS deliberately added ink on the OUTPUT side (the delete-op exemption inverted -- the source never carried it, by the operator's design), the gray base layer keeps the untouched original, QC judges added geometry like any other (an open added line flags honestly), the standing stale rule fires on the add, and the added feature rides the NORMAL pipeline (review plans it, it posts). UI: 'add feature' block in the Heal/QC panel -- kind select, LABELED typed fields per the sketch-labels ruling, pick-position canvas click filling the coordinate fields (typed values stay the record), Add. Proven: test_healedit 29->42 engine controls + test_healadd.py 13 NEW server e2e controls + app/verify_healadd.js 12 live real-mouse checks on a scratch instance. PIECE 2 BUILT same day (Jordan 'Go'): the two tab MERGES, PRESENTATION ONLY -- client-side only (app.js/app.css, zero server/engine change; stages, gates, stale rules and records stay separate underneath). The strip is now Geometry / Quote / Tooling / Nest / Post / Deliver; a merged tab carries one dot PER constituent stage (per-stage status never hides -- strip, drawer sections and home job cards all keep stage-level dots); the Geometry drawer stacks Sketch (sketch-born jobs) + Intake + Heal + QC as sections each opening with its own dot+name, the Tooling drawer stacks Part review + Cut plan the same way. Review and cut-plan behaviors COEXIST on the one Tooling tab via stage-coverage guards (onTab): drag-handle/pick-start/band-select run as on review, Manual Sort click-in-order as on cutplan, a plain click selects a contour on either scene; the canvas draws the cut-plan scene when the sequence is judged and the review scene otherwise (the post/deliver precedent -- a re-plan drops the judgment and the scene follows). A sketch job's Geometry tab draws the TYPED preview until the sketch is applied and current (sketchPreviewOn: not-done or stale), then the healed geometry -- the compiled sketch -- is the on-screen truth and heal-edit/dimension tools work on it. Old #tab=heal / #tab=cutplan deep links land on the covering tab (tabAlias -- verify scripts and bookmarks keep working); sales lens strips to Geometry + Quote (same stages as the ruled set); firstAttentionTab walks STAGES in pipeline order and opens the covering tab; the tour's stage step teaches the merged vocabulary. Proven: app/verify_tabmerge.js 20 NEW live real-mouse Playwright checks on a scratch instance (merged strip, per-stage dots on strip/drawer/home card, all four old deep links, review plan + cut plan judged + contour click + Manual Sort on the one Tooling tab, sales lens, sketch preview->healed switch); test_sketch 21 / test_healadd 13 green (server untouched by construction); Jordan's live job renders intact over the public URL. Client serves from disk -- LIVE IMMEDIATELY, no restart needed. || PLAIN-WORDS TAB TOOLTIPS 2026-09-22 (the same Jordan catch): the tab-dot tooltips render for a person -- STAGE_PLAIN/STATUS_PLAIN maps in renderTabs ('Delivery: has warnings', 'File intake: complete', never 'pldeliver: flagged'); the recorded stage keys stay the machine truth underneath, the green-flag stand-down suffix untouched. verify_tabmerge REWORKED 20/20 -- its per-stage-dot asserts were stale since the 2026-09-17 one-glyph collapse; now assert the collapsed dot + plain names. Client-only.
- •Busy feedback on EVERY slow action -- any api call still running after 600ms raises the processing overlay, with elapsed seconds ticking; BUILT record — Jordan 2026-09-09: 'Give the user visual feedback: when the button takes about a minute to do its job, somehow indicate that on the screen.' BUILT same day, client-only (app.js -- serves from disk, live immediately). ONE SEAM instead of touching every handler: fetch itself is wrapped -- any POST to our api still pending after a 600ms grace raises the SAME processing overlay the 2026-09-04 build added for uploads (units-confirm-modal), with honest per-endpoint words (healedits 'Applying geometry edits -- re-heal, QC, downstream re-check...', nest, post, deliver, partnest, vecextract, sheetextract, quote... ; unknown endpoints say 'Working...'); fast calls never flash it. After 5 seconds the card ticks elapsed seconds ('-- 12s') so a minute-long job visibly stays alive. dragcheck is EXCLUDED (the live drag judge fires under the mouse -- an overlay would eat the drag); GET healmarks is INCLUDED (a first lens click on a big file computes). busyShow/busyHide are now show-COUNTED so the explicit sites (upload, units flip, vector convert) compose -- the wrapper defers when an explicit indicator already speaks. The modal overlay doubles as a double-click guard while a pipeline re-run is in flight. Proven: app/verify_busy.js 14 live Playwright checks on a scratch instance (route-delayed calls prove every timing branch deterministically: show/hide, 600ms grace, dragcheck exclusion, seconds tick, explicit-compose, fallback words, healmarks GET, plain-GET exclusion, real-call round trip) + verify_units.js 16 re-run green (the explicit-overlay flows unchanged).
- •Multi-file upload + whole-window drag-and-drop on the Jobs home; BUILT record — Jordan 2026-09-09 (screenshot of the single-select browse dialog): 'When we are uploading a file, we can only select one at a time. I would also like to have a feature where we can just drag and drop our files in, rather than having to browse and select.' BUILT same day, client-only (index.html + app.js -- serves from disk, live immediately, no restart). The browse input takes SEVERAL files (multiple); the drop target is the WHOLE WINDOW, not the dropzone box -- dropping anywhere uploads (only real OS file drags, dataTransfer type Files, so panel/canvas drags are untouched; the dropzone keeps its highlight as the affordance). A batch uploads SEQUENTIALLY -- one pipeline run at a time, per-file progress on the busy card ('2 of 6: name -- intake -> heal -> QC...'), then the Jobs list refreshes in place and ONE summary toast counts the landings and names every refusal in the server's own words (a refused file -- DWG, SVG, junk -- never stops the rest; the format door rules of upload-formats-door apply per file unchanged). A SINGLE file keeps the exact old flow: its job opens when it lands. Same-file re-pick fires again (input value cleared); long refusal summaries hold the toast up to 12s. Proven: app/verify_multiupload.js 11 live Playwright checks on a scratch instance (multi-batch, stays-home, single-opens, drop on the job LIST far from the dropzone, DWG refusal named while the good file lands). Three-lens clean: plain DOM input[multiple] + drag events, no browser-only API.
- •View/intake extents measure TRUE arc sweeps, never full-circle padding; FIXED record — Jordan 2026-09-09 (7497.dxf screenshot): pressing 'f' fit the part as a speck at 0.4% zoom and the Intake drawer read extents 1280.646 x 2535.75 on a part whose real ink spans 115.181 x 58.090 -- 'we thought that maybe there was either an open contour, tiny segment etc. out at the edge... nothing to see. Why?' He was right to trust the lenses: NO stray geometry existed. The defect was ours: server._extents padded EVERY arc by its full circle (center +/- radius, both axes), and 7497 carries 1140 native arcs whose nearly-straight edges are drawn as giant-radius arcs -- the worst a 640.32-inch radius under a 0.19-inch chord, single-handedly inflating the box by its whole 1280-inch circle. The same padding was already known WRONG for nesting (part_bbox, brick 3) but the code comment claimed it 'fine for view fit' -- Jordan proved it is not. FIX (his 'Go', same day): _extents now delegates arc extremes to emit._arc_extremes -- the SAME cardinal-point arithmetic the slug-size bbox has always run (an arc reaches center +/- radius on an axis only when its sweep passes that compass point; coincident-end full-circle segs still box whole) -- ONE arithmetic, never a second that could disagree with the slug gate. Fixes the Intake extents line AND the 'f'/fit box in one place (both read job.extents). Proven: test_view_extents.py 10 NEW controls (the giant flat arc boxes as chord + sag; CW/CCW representations agree; mid-quadrant arc = endpoints only; two-semicircle circle diet; the REAL 7497 source segs measure 115.1813 x 58.0896 exactly) + neighbour suites green (healadd 13 / healedit_noop 8 / units_confirm 27 / introt 24 / sheet_intake 36 / upload_formats 17 / sketch 21 / emit_extents). Jordan's live 7497 job record recomputed under the job lock via the new codepath -- extents now equal part_bbox to the digit (two independent arithmetics agreeing), serving live immediately. Server-side change: NEW uploads get true extents after the next owner-turn restart; older jobs correct on their next re-heal (extents is a display/record value -- nothing downstream drops). WRITER HEADER JOINED 2026-09-15 (the same defect class found in emit.write_dxf_shop by Jordan's stacked part-list nest): the old CAM writer's $EXTMIN/$EXTMAX padded every arc by its full circle -- a split child carrying 7497's giant flat arcs wrote a header ~25x its ink and to_inches' magnitude inference read the written file back as mm. The header now runs emit._arc_extremes like the view fit and the slug bbox -- one arithmetic everywhere. test_view_extents 8->9; full story on pin units-confirm-modal.
- •Toolpath planner performance pass: chunk bbox prefilter under the clear-air scans -- 11.5 min to ~70 s on 7497, output bit-identical record — Jordan 2026-09-09 ('Is this stuck or is it really taking this long?', the 116-feature 7497.dxf; his 'Go'): the review plan ran 11.5 minutes (started 15:40:53, review.json landed 15:52:23) with one core pinned. Measured cause, not guessed: ~2000 _pick_lead calls (116 boundaries x up to 18 start candidates), and inside each probe emit._ray_clear and emit._pierce_clear scanned EVERY segment of the whole flattened drawing -- tens of thousands of segments touched per probe on a 115-inch sheet where a lead reaches a fraction of an inch. The fix is a PREFILTER, never a second arithmetic: emit._chunk_polys builds a per-poly bbox index (32-segment chunks) once per post; _ray_clear gates polys on a padded slab test (_ray_box) then chunks the same way, _pierce_clear gates polys and chunks on padded squared point-to-box distance. Every rejection is conservative by construction -- a chunk is skipped only when nothing inside it could better the running answer -- so the picked lead, its length, the pierce, the tab span and every finding are bit-identical with the index on or off. PROVEN both ways: test_plan_perf.py 6 NEW controls (whole-plan JSON identity, chunk partition, slab-test conservativeness on a 500-ray seeded sweep, _ray_clear/_pierce_clear exact equality, degenerates); chunked-vs-unchunked identical on the real nav209 / 44558B_10 / b7787 jobs; the new engine's 7497 plan compared field-for-field IDENTICAL to the live tooling.json the old engine spent 11.5 minutes writing. Measured: 7497 plan 660 s -> 61 s (plus 10 s heal), nav209 1.19 -> 0.37 s. 16 neighbour suites green (drag 23 / dragcheck 15 / lead_tab_comp 22 / tooling_doc / rules 14 / nc_warn 23 / sketch 21 / plan_display / dcond / header_notes 22 / progstyle 29 / seqexact 16 / pl_post 26 / cl_post / traverse 10 / nestedit 38). Honest limits: the planner stays single-threaded -- the remaining ~60 s on a 116-feature sheet is Python loop floor; spreading candidate starts across the box's 4 cores (~4x more) is the recorded next step if big sheets stay slow. Engine change: live after the next restart.
- •Planner multi-core fan-out BUILT 2026-09-17 (7497 plan 61.5 s -> 27.3 s, 2.25x, whole-plan identity proven on real fixtures); the full ratified five-lever performance conversation (Aristide 2026-09-15) stands recorded below: bigger box = money question, PyPy = measured trial, numpy/C rewrite parked, caching mostly done recordmixed — BUILT 2026-09-17 (Aristide 'ok, now start on the core split up'): STEP-0 RE-PROFILE ran first, per the spec's own stop condition -- cProfile on the real 7497 source: _choose carries 114.2 s of the 115.5 s profiled plan (98.9% cumulative), _cut_order absent from the top 30 -- the target had not moved, the build proceeded. THE SEAM AS SPECIFIED: the picks loop now runs through emit._parallel_picks(choose, n, parallel) -- fork-start multiprocessing Pool (Linux, stdlib, no new dependency); _choose is a closure and not picklable, so it is stashed in module global emit._PAR_CHOOSE and forked children inherit it copy-on-write, running the top-level _par_choose trampoline; pool.map collects in index order, so the parallel plan IS the serial plan -- same arithmetic, no second implementation. GUARDS as ruled: engages only at >= 12 boundaries (_PAR_MIN -- small parts and the throttled dragcheck judge stay serial); workers = min(3, cores-1, n); a parallel= kwarg on write_gcode_macrob (None=auto, False=forced serial, True=engage at any size) rides through rules.check_drag's **post_kwargs untouched; ANY pool failure falls back to the serial loop COUNTED in stats['parallel_picks'], never silent; a parent-side threading.Lock serializes concurrent stash+fork from the threaded HTTP server (children stay lock-free pure compute -- the ruled fork-safety guard); the outer approach= re-pick stays serial per spec. GATES (the plan-perf-pass discipline): test_plan_perf 6 -> 10 controls -- parallel-vs-serial WHOLE-PLAN JSON identity (stats['parallel_picks'] popped and asserted separately -- the one legitimate difference) on the synthetic fixture; a threshold-path control; a forced-failure fallback control (module-level raising stub, pickled by reference); real-source identity on nav209 / 44558B_10 / b7787 (serial -- under threshold) / 7497 (parallel, identical). Nine neighbour suites green (drag 23 / dragcheck 15 / lead_tab_comp 22 / tooling_doc / rules 14 / nc_warn 23 / pl_post 26 / cl_post / traverse 10). MEASURED: 7497 plan 61.5 s serial -> 27.3 s with 3 workers (2.25x) -- inside the honest Amdahl expectation below (ordering, emission and audit stay serial; concurrent big-sheet plans serialize on the stash lock by design). Engine change: kerfmaster-app restarted, live smoke on dev.kerfmaster.com. Levers 2-5 stand as recorded. --- THE ORIGINAL RATIFIED CONVERSATION (2026-09-15): NOTHING BUILT YET -- this pin is the WHOLE ratified performance conversation (Aristide 2026-09-15, 'agreed with recommendation' then 'document the whole conversation, not just the planner fan-out'): all five levers with the pros and cons as discussed, PLUS the full execution detail for the fan-out night build, written so a fresh session after compaction can execute it without re-deriving anything. It closes the where-does-the-time-go discussion after the 62-suite full test. SLOW SPOTS TODAY: big-sheet toolpath plan ~60 s on 7497's 116 features (the Python loop floor left after pin plan-perf-pass); first heal of a big file ~6 s then cached; a few test suites 30-50 s each because they run whole pipelines over HTTP; Playwright verifies 30 s - 3 min of real browser time. THE FIVE LEVERS, PROS AND CONS AS DISCUSSED. (1) MULTI-CORE PLANNER FAN-OUT (build on trigger, spec below). PRO: stdlib multiprocessing on the box's 4 cores, no new dependency; bit-identical by construction and PROVEN by gates (same arithmetic, just concurrent -- no second-arithmetic risk); ~a day of work; hits the slowest thing Jordan actually waits on (big-sheet plans). CON: Amdahl -- only the boundary-picks loop parallelizes, ordering/emission/audit stay serial, so expect ~2.5-3x on the picks share (7497's ~60 s lands roughly ~25-30 s, not 15); forking from the threaded HTTP server needs the pure-compute-worker guard; the box is shared with the bridge, so workers cap at 3. (2) BIGGER DEV BOX. PRO: the ONLY lever that meaningfully helps the test/verify sweeps -- those suites are slow by nature (full pipelines over HTTP, real-browser Playwright) and parallelizing them on this 4-core / 7.6 GiB box would thrash it; more cores also raise the fan-out's ceiling; zero code risk. CON: money, and a platform migration question (provider side) -- Aristide decides separately; on its own it does not fix the single-threaded Python floor. Nothing to code. (3) PYPY TRIAL -- a quiet-turn measured experiment AFTER (1). PRO: the engine is pure-stdlib Python, the ideal PyPy case -- typically 3-7x on loop-heavy code with ZERO code change; multiplies with the fan-out rather than competing with it. CON: a second runtime to keep honest between dev and prod; JIT warm-up penalizes short runs; nothing is trusted until the gate passes -- run the full suites under PyPy and diff real-job plan/NC outputs byte-for-byte against CPython (proof, never assumption). (4) NUMPY/C REWRITE OF HOT LOOPS -- PARKED, recommended against. PRO (why it tempts): the biggest raw speedup potential on the geometry inner loops. CON (why it parks): it creates a SECOND ARITHMETIC beside the one every gate and audit shares -- construction and judgment must run the SAME arithmetic, and the drift risk buys back the exact class of bug our controls exist to prevent; plus a new dependency and a large rewrite while levers 1-3 are still unspent. (5) MORE CACHING -- mostly done already (heal cache keyed on source+tol, plan reuse, the plan-perf-pass chunk prefilter); the remaining wins are small, not worth a build. THE RATIFIED RECOMMENDATION, in order: go on (1) -- a day of work, provable, helps Jordan directly; decide (2) as a money question -- it is the only fix for slow test/verify sweeps; trial (3) as a measured experiment some quiet turn; park (4). THE FAN-OUT BUILD SPEC. STEP 0, RE-PROFILE FIRST: the 61 s on 7497 predates this build -- time the picks loop vs _cut_order vs emission (perf_counter on a scratch plan of the 7497 source, jobs/7497-1789412543/source.dxf); if ordering now dominates, STOP and report -- the target moved. THE SEAM: emit.py ~line 3039, picks = [_choose(i) for i in range(len(cons))] -- each _choose(i) reads only cons/depths/polys/pboxes/pchunks/tooling/overrides, all frozen by that point, and boundary picks never read each other (verified in code 2026-09-15; the outer re-pick with approach= at ~3080 runs AFTER the ordering, serial, outers only -- leave it serial). MECHANISM: multiprocessing with the FORK start method (Linux, stdlib, no new dependency; threads are useless here -- GIL). _choose is a closure, not picklable -- the fork trick: stash it in a module global (emit._PAR_CHOOSE = _choose) immediately before creating multiprocessing.get_context('fork').Pool(workers); children inherit it copy-on-write and run a top-level _par_choose(i) that calls the global; pool.map preserves index order; the returned pick dicts (prim tuples, floats, bools) pickle fine. DETERMINISM: same CPU, same code, index-ordered collection -- bit-identical by construction, and PROVEN not assumed (gates below). GUARDS: engage only at len(cons) >= ~12 boundaries (small parts stay serial; dragcheck's throttled live judge stays cheap); workers = min(3, cpu_count()-1, len(cons)) so the box -- bridge and server share it -- never pegs; a parallel= kwarg forces serial (tests compare both paths); ANY worker failure falls back to the serial loop, counted in stats, never silent; the worker path stays lock-free (no logging, no imports inside _choose) -- we fork from the threaded HTTP server, pure-compute children are safe, a held lock would not be. GATES (the plan-perf-pass discipline): test_plan_perf extended with parallel-vs-serial WHOLE-PLAN JSON IDENTITY on synthetic fixtures AND the real nav209 / 44558B_10 / b7787 / 7497 sources; a forced-failure fallback control; a threshold-path control; neighbour suites green (drag / dragcheck / lead_tab_comp / tooling_doc / rules / nc_warn / pl_post / cl_post / traverse at minimum); measure 7497 wall time before and after and report the real number; sudo systemctl restart kerfmaster-app; live smoke on dev.kerfmaster.com. EXPECTED HONESTLY: ~2.5-3x on the picks-dominated share of a big sheet (Amdahl -- ordering, emission and audit stay serial); state the honest limit wherever the number lands. TRIGGER: Aristide or Jordan saying 'Go: planner fan-out' (or any clear go naming the planner fan-out or this pin) starts the build; this pin flips to record in the SAME commit as the code, per the standing rule.
- •NC-audit performance pass: mechanical speedups in the parse/grid/annotate/geometry hot paths -- reports byte-identical, ~1.6x on the heaviest real programs record — BUILT 2026-09-18 (Aristide '5' on the standing queue; the go was on record). Profiled first, never guessed: cProfile on the 3192-boundary expanded macro sheet (O33289) put the time in pierce_clear (Grid build over ~2.2M flattened chord segments + per-pierce nearest), rules.annotate (bbox/area/point-in-poly over the same flattened contours), parse_nc's per-line regex builds, and the audit's geometry-vs-source candidate scan. EVERY change is mechanics, never arithmetic -- the same expressions evaluate in the same order on the same operands, so every distance, every finding and every reported number is bit-identical by construction AND by proof: (1) parse_nc precompiles its X/Y/I/J and motion patterns; _arc_pts becomes a comprehension of the identical per-point formula; (2) Grid.__init__ computes each point's cell ONCE and reuses it across adjacent segments (floor is monotonic, so the segment's cell range is exactly the min/max of its endpoint cells), with a fast path for the single-cell chords that dominate; bucket contents and their order are unchanged; (3) Grid.nearest scans only the NEW perimeter cells of each ring (a rescan can never win under the strict d<best gate; new cells visited in the same dx-major order, so ties resolve identically) with the _seg_dist arithmetic inlined verbatim; (4) rules._signed_area/_point_in_poly drop their per-edge list copies and indexing, same terms in the same order; annotate reuses the bbox it just computed; (5) the audit's geometry check breaks out of a sampled point's candidate scan as soon as one distance drops to <= the running worst -- the update gate is strictly >, so worst/worst_at land identical to the full min, and on a clean program almost every point sits ON its first candidate. PROVEN: full audit reports (anomalies+info+findings, sorted JSON) byte-identical old-vs-new on six real programs -- the O33289 3192-bnd P9997 macro (18.65 s -> 12.00 s), O33286 1140-bnd (2.81 -> 1.79), the CAMP part-list sheet O33342 with placed source + Rev2 tooling (2.45 -> 1.52), a single-part post, the brazen legacy program, tl101681 (1.35 -> 0.81); PLUS a distorted-source case (scaled 1.001) that exercises the cut-path-leaves-source anomaly branch, old modules from git HEAD vs new in the same interpreter inputs -- IDENTICAL including geom_max_dev 0.0502 and the worst_at point. Suites green: nc_warn 25, warns 20, rules 14, drag 23, dragcheck 15, tooling_doc, pl_post 26, cl_post, traverse 10, seqexact 16, pl_sync 23. The savings DOUBLE at every posting door: nc_warn.audit_and_inject audits twice by design (the transparency recheck gate stands untouched). Honest limit: the remaining time is the pure-Python floor of flattening arcs at the ruled ARC_STEP 0.004 and building the segment grid -- a further big step means PyPy (the ratified quiet-turn trial) or coarser sampling, which would CHANGE measured numbers and is not on the table.
- •Treat-as-text BUILT + REFINED (one gesture: comp off + curve-run arc consolidation, true corners stay SHARP) AND the deterministic AUTO-DETECTOR BUILT (measured signatures propose a text group, one-click ratify fans the same gesture -- seed never bind) record — Jordan 2026-09-09 (7497 screenshot, verbatim): 'Is the codeset able to recognize text features and remove beam comp automatically without the use of AI? How can I select a set of features and indicate to treat is as text? If it is text, then I want to round the arcs and take out beam comp.' BUILT 2026-09-09 on his 'Continue' go; SEMANTICS CORRECTED same day by his letter-R spec (verbatim): the R 'would have on the top left corner a 90-degree corner, and on the bottom of the vertical stick on the left side of the R it would have two. These corners should not be "smoothed" but the half-circle that makes up the upper right should have at minimum one arc, but depending on the font it could have multiple tangent arcs.' So emit.round_text_corners is CURVE-RUN ARC CONSOLIDATION, never corner filleting (the first build's fillet-every-corner reading is retired): true corners stay sharp -- the healer's own neighbor-consistency rules (classify_corners constants) applied at the prim-junction level with arcs carrying real end tangents, a lone ~90-deg break ALWAYS a corner -- and each corner-free run re-fits into the FEWEST tangent arcs: one true arc through the run's exact endpoints first (his 'at minimum one arc'; center = the healer's least-squares circle snapped onto the endpoint bisector), heal.fit_biarc_run as fallback. This folds both raw line facets AND the many small wiggly arcs healing threads through text facets (the in-app form -- proven: a 16-facet sketch bowl healed to 6 arcs consolidates to ONE, worst dev 0.0023). Budget = the audit's own geometry gate max(0.005, beam_comp); every fit MEASURED both ways on parametric samples (a _poly-based measure aliased onto facet vertices and read 0.0 -- caught and replaced); a run whose fit misses the budget, grows a prim under beam comp, or needs AS MANY prims as it replaces keeps its source form -- which also preserves clean geometry exactly (circle diet, stadium: byte-identical, proven). Per-feature override text:'on' in tooling_doc.CONSUMABLE; record carries text ran+source + arcs-fitted count + worst deviation. Comp stays its own knob: the UI gesture (review contour panel, fans over band-select/twins via ovApply) sets {text:'on', comp:'off'} in one click -- the recorded G40-on-text convention -- clear takes both back; pl_post + the doc round trip replicate per copy. Proven: test_text_treat.py 27 controls + verify_texttreat.js 12 live real-mouse checks (square hole marked text keeps all four 90s SHARP end to end; the faceted D bowl consolidates to one arc through the real heal pipeline). STILL INTENT (the mixed flag): the deterministic no-AI DETECTOR -- measured signatures (small closed contours, arc-heavy, similar height band, collinear row, nested counters) PROPOSING a text group for one-click ratify, seed never bind -- is the next block, commissioned by his 'Continue, using logic' 2026-09-09. DETECTOR BUILT 2026-09-15 (Aristide 'go in that order: First' on the standing go): engine text_detect.py (docstring = design record) -- PROPOSE NEVER APPLY, measured signatures only, no AI: closed chains cluster by agreeing size (bbox max dim within 40% of the group median), ONE straight baseline in any direction (PCA centroid fit within 0.35 x size -- rotated and vertical words detect; curved/multi-line text = the recorded honest limit), letter spacing (2.0 x size along the line), and >= 2 DISTINCT congruence signatures via emit._congruence_sig (the ONE identical-shape arithmetic) -- so bolt rows, slot arrays and different-drills-on-a-line NEVER read as text ('III'/'OOO' do not detect either: the conservative side of seed-never-bind); an off-baseline straggler sheds one at a time, so a hole beside a word costs the hole its membership, never the word its proposal; a chain CONTAINED in a member (the A's counter) rides its letter's group and never proposes on its own; every threshold is a proportion of the group's own measured size, never a machine number. SERVER GET /api/jobs/<id>/textdetect -- READ-ONLY (the dragcheck pattern): the same edited prims every stage consumes, nothing persisted, no stage record; a part list refuses in honest words. UI: 'Text detected (proposal)' block on the Part review drawer -- the engine's measured note verbatim, mark-all-as-text / select / dismiss; the ratify IS the recorded gesture automated (select the word, setText) so ovApply fans one per-feature entry per member ({text:'on', comp:'off'}, source:operator, bound to its own centroid); dismiss is session-only presentation state, stated on-screen; a ratified group hides itself by its members' own record. Proven: test_text_detect.py 23 NEW controls (every gate one by one + HTTP e2e: read-only, no stage flip, refusal ladder verbatim) + app/verify_textdetect.js 15 NEW live real-mouse checks over the public URL (nothing applied before the click, dismiss session-only across a reload, ratify fans 4 features to source:operator, persistence across a fresh page, bolt-row control proposes nothing; scratch fixtures removed); neighbour suites green (text_treat 27 / tooling_doc 37 / drag 23 / dragcheck 15 / rules 14 / sketch 21). Both halves of the 7497 ask are now record -- the mixed flag is cleared. MERGE FLOOR 2026-09-23 (Jordan 'Go on 2' on the offered suggestion): treat-as-text comp-off features stop merging at the material's beam comp -- the micro merge exists solely for the comp interference alarm and a G40 feature cannot raise one, so the full-comp merge flattened fine print for an alarm that cannot fire. A feature whose override carries BOTH text:'on' AND comp:'off' (the one-click gesture's own record) now merges at the control's own floor -- NEW machine number text_merge_floor (machine.json 0.001 in, provenance decided; read via tables.text_merge_floor, never a literal in Python) -- bound to the named feature PRE-merge by the same binding arithmetic the override loop runs (emit._near_bind: the nearest-centroid + concentric-twin tie rule extracted to ONE function, two call sites one truth). merge_micro_segments grew floors= (contour index -> floor; floors=None byte-identical to the old signature); the text consolidation's no-prim-under-min_len discipline keys on the same floor for comp-off text; stats record text_merge_floor {floor, features}; sub-floor debris still drops whole; text with comp ON, and comp-off WITHOUT the text mark, both keep the alarm-honest beam-comp merge (the floor is scoped to exactly the gesture Jordan approved); a floor at/above comp is an honest no-op. nc_audit needs ZERO change: _short_blocks already counts only compensated blocks (G40 sub-comp detail exempt by physics) and the geometry gate only tightens. Measured on the Cleaner repro's fine print (33 features marked): merge-step worst deviation 6.79 thou -> 0.35 thou, 832 of 922 source prims survive vs 691; the ruled Q27 consolidation budget is untouched. Proven NEW test_text_floor.py 16 controls + old-vs-new full-plan sorted-JSON diff EMPTY on all 12 dev jobs carrying real recorded overrides (the binding extraction byte-identical) + 14 neighbour suites green (micro_refit, text_treat 27, tooling_doc, drag 23, start_anchor, setsize 27, offset_corner 16, start_defaults, healedit 78, pl_sync 25, nc_warn 25, pierce_sub, matrecord 30, qc_link 15); engine restarted; zero dev O-numbers. Still offered, unbuilt: suggestion 3 (the named per-feature drift-cap warning) and the weld-to-outline build.
- •Text entities (TEXT/MTEXT) into cuttable geometry -- does not exist yet intent — INTENT (Jordan 2026-10-31, B2b ruling 3 'ANYTHING can be added. Text might need to make its way to the cut' + 'Text to usable primitives was something I thought already existed, so we'll need to figure that out. It doesn't have to be part of this build.'). Today: a drawing's TEXT/MTEXT is kept as position + string (sheet_draw) and drawn by the screen's own font; nothing turns it into lines/arcs. What exists is treat-as-text (pin text-feature-treatment), which tools letters ALREADY drawn as geometry. Open questions for Jordan: single-line etch vs outlined cut-through letters; which font (the file's named style vs a shop default); letters must be true arcs (pin resolution-floor). fontTools 4.46 + system TrueType fonts are on the dev box (not checked on prod). Not built; own chunk after B2b.
- •Aristide's interface visibility list (2026-09-11) — all 9 items BUILT same day record — Aristide, 2026-09-11, screenshots on the RJB job: 'a few interface issues I would like to address... Just take inventory. you can then execute on my mark.' The list: (1) panel-header icons (grip dots, collapse dash, tear-off arrow) too small — make larger. (2) Left tool palette: the one-letter key labels (V/F/O/H/J/B/N) too small to read; the layer-toggle buttons all share one circle-dot icon and one color — give each a DISTINCT icon from a real icon library (not emojis), and tint each layer button with the color the user assigned to that layer in Colors & legend (picker changes follow onto the button; V/F tools stay neutral — no layer color). (3) Repeated findings group by KIND under a chevron: rows differing only by which feature they hit collapse to one row per kind with a count ('pierce clear air 0.1311 < 0.15 standoff — 6x'), chevron opens to the individual rows which still navigate (ui-warnnav-brick17); collapsed by default; the RED/YELLOW banner keeps the true total. His RJB case: 8 yellows -> 2 rows (0.1258 x2, 0.1311 x6). (4) Numbered sequence callouts on the canvas too small AND they shrink with zoom-out into the geometry — hold a readable SCREEN-FIXED size at any zoom. (5) Dimension value labels ('6X R0.1330') same treatment — readable screen-fixed size. (6) Move dimension numbers to any arbitrary spot — ALREADY BUILT (drag-to-place, 2026-09-09, pin ui-dims-brick27): verify it works for him; the tiny grab target is likely the real obstacle, fixed by (5). (7) One-click SCREENSHOT of the visible canvas only (never the toolboxes/panels), two modes: copy to clipboard, or save via a file dialog the operator navigates (three-lens note: Chrome/Edge have a real save-anywhere picker, Firefox/Safari fall back to a named download honestly; native shells get the native dialog; clipboard works on all three). (8) Recorded-edit rows in the Heal/QC panel ('Drop duplicate lines' + tiny x) read as a clarifying note, not an actionable item — give each recorded edit a proper actionable row treatment (card/bordered, distinct from the gray explanatory text) with a clearly visible remove button instead of the tiny x. (9) Dimension-kind buttons crowd edge to edge — the active button's highlight ring overlaps its neighbors (his Diameter screenshot); space button groups so the active state never overlaps, or keep the active style inside the button footprint (applies to any group using the ring style). NOTHING BUILT YET — execute on his mark. BUILT 2026-09-11 on his mark ('go ahead and execute'), client-only (app.js/app.css/index.html — serves from disk, live immediately, no restart): (1) panel-header grip/collapse/tear-off icons 10->15px, buttons 12->16px. (2) tool-palette key letters 11px bold; every tool button carries a DISTINCT inline SVG icon vendored from Lucide (ISC — move/maximize/file/spline/alert-triangle/target/route, no emojis, no runtime CDN); each layer button is tinted by its own Colors&legend CSS variable read live (picker changes follow; V/F neutral; off-layers dimmed). (3) findrows(): findings grouped by KIND (severity + message with feature numbers/coordinates normalized away — measured VALUES stay distinct, his 8->2 example) under a <details> chevron showing 'SEV ×N'; rows inside still navigate (brick 17); open-state survives the re-render a child click triggers (S.fgOpen); singles render flat; banners keep true counts; wired on Part review, Cut plan, Post (single + nested — nested rows stay honestly non-navigable, renumbered expanded bnds). (4) canvas sequence callouts = screen-fixed circled badges (panel disc, severity/selection ring, bold 13px — the drawer's own vocabulary) on the cut plan; review labels bold 13px with a panel-color halo; seq-pick badges and both nest numbered-box renderers enlarged (bold 12px, 20px boxes) — all already screen-fixed, now readable. (5) dimension value labels 13px in a padded bordered chip. (6) drag-to-place verified working; the grab target grew with the label (±9px pad) — the tiny target was the obstacle, as suspected. (7) two canvas-only screenshot buttons in the zoom bar (icons swapped to camera glyphs 2026-09-11 -- Aristide missed the copy/save forms: camera = copy, camera-with-down-arrow = save): copy-to-clipboard (ClipboardItem, honest toast when unsupported) and save (showSaveFilePicker real dialog on Chrome/Edge; Firefox/Safari fall back to a named download and SAY so; canvas element = panels excluded by construction). (8) recorded-edit rows are bordered cards with a visible 'remove' button replacing the tiny x. (9) active-button ring moved inside the footprint (inset box-shadow) + spacing between small buttons — no overlap in any group. Proven: app/verify_visibility.js 15 live Playwright checks over the public URL (7497's 9 yellows -> 2 groups + 5 distinct-value flats, all 9 accounted, child-click navigation with the group staying open, 7 distinct SVG icons with 5 layer tints, real PNG capture 22KB, ex2 cut-plan badges clean, b7787 edit card + remove, dims job clean). Screenshot spot-check on ex2's cut plan confirms badges/tints/buttons visually. FOLLOW-UP FIX 2026-09-11 (Aristide's zoomed screenshot -- 'seems aligned too far to the right'): the item-1 icon enlargement made the 56px Tools panel header overflow -- measured scrollWidth 65px vs 55px available, the tear-off arrow clipped ~10px off the right edge and the row read as crammed right. Fix = tighter padding on THIS narrow header only (app.css: tools pgrip 5px 4px gap 4px, tools pbtn 0 2px; icon sizes untouched -- readability stands): all three glyphs now fit (arrow ends at x=51, zero overflow docked AND floating; collapsed strip + wide panel headers unaffected, verified by screenshot). Client-only, live immediately. ITEM-3 GAPS CLOSED 2026-09-11 (Aristide's screenshot ask, 'the nesting of these doesn't carry across tabs. is that possible?'): four finding lists still rendered FLAT outside the grouped renderer -- the Nest drawer's hand-layout judge findings (12-row cap) and the part-list Nest drawer's per-part / sheet-wide / per-program audit findings (4/8/4-row caps) -- all four now run findrows() like review/cutplan/post, so the nesting carries across every tab; the caps go (a same-kind group folds to one chevron, so full lists render without flooding -- the no-silent-caps spirit), flat=true keeps nest-side rows honestly non-navigating (their coordinates live in sheet/part frames, not review contours). Proven: app/verify_findnest.js 8 live Playwright checks (the screenshot's exact 8 yellows fold to x2+x6 through the shipped renderer, Lathrup part-list rows intact, zero page errors). Client-only, live on refresh. NOTE: the screenshot's own Tooling tab already groups on the current client -- a flat Tooling list means that browser tab predates the morning build; refresh.
- •Windows installable version — preliminary challenge inventory intent — Aristide, 2026-09-13: 'this is all preliminary right now' — the challenge inventory for a PC-installable kerfmaster, documented on his ask. Nothing commissioned; the two strategic decisions need a sitting with Aristide + Jordan before any building. | RULING 2026-10-12 (Jordan, Aristide present) on shop-server vs per-PC: BOTH roads -- many small shops have no server, so a ONE-STATION install must work; the intake wizard asks whether they have multiple stations and/or a server, and from the answers either makes one of their workstations the server or uses their existing server. Licensing/update model still open.
- •kerfmaster.com security page — DRAFT exists, publish blocked on Aristide's checklist record — Aristide, 2026-09-13: a public security page for kerfmaster.com, adapted from his MyVideoTracker template to what is TRUE of kerfmaster today. The draft lives at docs/security-page-kerfmaster.md — deliberately OUTSIDE the auto-deploy dirs so nothing ships until his word. EBS ANSWER LANDED 2026-09-29 (Sem, via Aristide): prod's volume IS encrypted at rest -- vol-031e4d22e8c6d2980, Encrypted: True, AWS KMS key in the MCA account, 50 GB gp3. The draft's checklist item is checked and an 'Encryption at rest' paragraph added (plain fact on the page; the volume ID stays in the checklist as provenance, never public). Still blocking publish: security@/info@ addresses + the two roadmap keep-or-hold calls + Aristide's word to style it into kerfmaster-site/. | 2026-10-12 (Jordan): the security@ and info@ addresses are CREATED. Still blocking publish: keep-or-hold on the two roadmap sections + Aristide's word to style it into kerfmaster-site/.
- •Prod link parameterization -- board link fixed by hostname; audit found the app already clean; two riders open recordmixed — Aristide 2026-09-22 ('which one can you start on... ready to go') on the standing KNOWN FOLLOW-UP: hardcoded dev links sending prod users back to dev. MEASURED FIRST -- the 'hundreds of links' note was stale for the runtime app: server.py 0, index.html 0, app.js exactly ONE (BOARD_BASE, the delivery drawers' board-build links). The remaining mycloudally hits are dev-only surfaces by design: verify suites' own BASE, the pins/rates pages (ruled 2026-09-09: keep old links until *.dev DNS exists), docs, and the pins-page generator scripts (build_questions/build_defects/approval.py -- parked with the pins ruling). FIX BUILT same day, client-only: BOARD_BASE derives from location.hostname -- app.kerfmaster.com -> https://view.kerfmaster.com/ (each box links its OWN viewer; runtime data never crosses boxes), dev.kerfmaster.com -> /viewer/ (same origin), any other origin (suites, localhost) keeps the legacy mycloudally URL byte-identical. PROVEN: verify_deliver 12, verify_delivernest 13, verify_pldeliver 14 all green zero edits (two first-run check-2 blips re-ran green and reproduce on the stashed baseline -- timing flakes, stated); live dev render shows /viewer/builds/... hrefs and the path serves 200; prod branch is the same one-line map. TWO RIDERS OPEN: (1) shops.json tenant hostnames -- upload.kerfmaster.com claims NO tenant, so the prod upload site deliberately shows nothing (intake resolves None); adding it to the demo tenant would put the demo storefront on the public prod domain, and that entry's own provenance says never present it as a real shop -- OUTWARD-FACING call, awaiting Aristide (or Jordan's real shop entry lands and takes the hostname). (2) the pins/rates/uploader dev tools keep mycloudally links until the *.dev DNS ruling resolves. CORRECTION same day: the proof suites DID consume dev numbers -- verify_delivernest re-post fixtures took O33401-33402 + subs 75435-75436 (progseq committed in commit 62f7bf3f); the sealing commit's zero-O-numbers claim was wrong, stated here honestly. RIDER REWORKED 2026-10-03: the upload.kerfmaster.com tenant call is superseded by the client-platform plan (pin client-platform-registry, docs/client-platform-plan.md) -- under it shops.json derives from the client registry and the bare hostname's redirect-or-retire call is that plan's open question 6.
- •Split into parts — a multi-part file becomes one job per part (BUILT 2026-09-14) record — Jordan, 2026-09-14 (his 7497/7498 part-list screenshot, each sheet reading 1 pcs): a DXF carrying a whole kit was packed as ONE giant rigid part. His ask, from the August TL-1016 precedent: split them into individual components. Go given same day (Go on all). NEST DOOR BUILT 2026-09-15 (Jordan's go: 'I need this feature to complete my job here... build what you think matches our overall goals'): 'Nest these parts...' button ON the split record (Geometry tab, Intake section) -- one click creates the part list from the split children, files members inside the list's home group (the grouped-upload-tray shape) and lands on the Part list tab; the operator picks machine x material there, then Save list + pack sheets. AUTOMATIC QUANTITY GROUPING, his 2a ruling in the same message ('if some parts are 100% identical (all contours considered), then why wouldn't we group those together as an increased quantity automatically?'): 100%-identical parts fold into ONE row with qty = count. The arithmetic is NEW engine split_parts.congruent_parts -- whole-part rigid congruence, NEVER outer-profile-only: one rotation + translation must map EVERY contour (interior cutouts AND their positions) within PART_MATCH_TOL (0.005 in, a construction margin over healing scatter, never a machine number); verification measures densely sampled points against the other part's EXACT prims so identical holes healed with different arc splits still group; MIRRORS NEVER GROUP (rotation-only search -- a mirrored copy fails unless the part is itself symmetric, where the mirror IS a rotation and grouping is correct). Rotated-in-the-drawing copies group (a part's identity never depends on its drawn orientation; the pack's Rotate column stays what the PACK obeys). GET /api/jobs/<id>/partgroups serves the grouping over the living split children -- READ-ONLY (the dragcheck pattern), refusals plain-400 in honest words (not split / no healed children); unhealed children left out NAMED, never silent. Proven: test_partgroups.py 21 NEW controls (hole-MOVED variant never groups -- Jordan's exact inside-cutout concern; sizes-swapped, mirror, arc-split, 2-thou-groups/10-thou-splits, read-only byte-identical) + app/verify_splitnest.js 10 live real-mouse checks over the public URL (3 identical + 1 hole-moved variant -> 2 rows qty 3 + 1, home-group binding, fresh-page persistence; scratch removed); split_door 17 / part_list 28 / isoserver 17 / healedit_noop 8 green. Live check on his real kit: 7497 9 parts + 7498 5 parts = ALL genuinely distinct, zero false folds -- matching his own statement that they are not identical.
HISTORY (the gap as recorded 2026-09-15 morning): POST-SPLIT NEST DOOR -- OPEN GAP (Jordan 2026-09-15, on his CAMP#4 sheet: 'When I click the tool to split these into individual parts, how do I navigate the workflow to get to the nesting stage? I'm still not seeing this in the interface.'): the split lands the children on the Jobs home and lists them in the Intake section, but no door leads ONWARD -- the operator must know to go Home > New part list > machine x material > 'add all parts from: <file>' > Save list + pack, or (identical parts) open ONE child and true-nest it from its own Nest tab with the sheet-size door. OFFERED (awaiting a go): a one-click 'Nest these parts...' button on the split record itself -- creates the part list, adds one row per child, opens the Part list tab; client-only over the standing endpoints. Recorded same turn as born, nothing built yet. | 2026-10-08 OLD-CAM-CLEAN COMPARISON + SPLIT DEFECT FOUND (question; Jordan sent BNM78598_SHOP_CLEAN.dxf, no words): the old CAM's clean = 50.40x12.82, 43 closed contours + 2 short cut lines on layer 0 + 19 bend lines on a separate 'Mark' layer, still faceted (1497 line segs, 415 under 0.002in, 479 arcs). Ours (part 1 of the 16-part split of 'cleaned WITH BEND LINES.dwg') = same frame and outline, true arcs (166 lines + 1233 arcs, 27 tiny), where both draw ink they agree to a median 0.1 thou -- BUT ours has only 37 closed contours: 6 of the 20 long 6.5x1.03 slots are MISSING. Measured cause (split_parts.part_groups): the bend lines ride as cut ink; close_scan_fragments seam-bridged two bend lines with a 0.137in connector the customer never drew (not in source, not in heal), and part_groups let that OPEN 3-prim L own contours -- the 6 slots fall inside its implied polygon, its test point fails the outer, so it became its own 'part' (the eight 14.83x8.87 children, parts 9-16, one per grill copy) carrying the slots away. All 8 grill copies lose 5-7 slots the same way. The invented connectors also ride in our cleaned DXF. Proposed fixes, unbuilt: (1) only CLOSED runs may own contours or be part outers; open ink attaches to the part whose outer holds it; (2) seam bridges must never join ink across a gap that wide (or not at all on open bend-line ink); (3) bend lines as Mark/etch, the old CAM's form, rides the bend-line-etch thread. Nothing built. | 2026-10-09 SPLIT: A BRIDGE ONLY STANDS IF IT CLOSED SOMETHING 2026-10-09 (pin `ui-split-parts-door` extended, Jordan '1. Sounds good, but let's be cautious... 2. Yes, go.'): close_scan_fragments' seam bridge joined two of the grill's bend lines with a 0.137in span, the result stayed open, and part_groups let that invented L own the long slots -- every grill copy lost 5-7 of its 20. NEW step 4b: a run still open after bridging gets its bridges taken back out (the ink returns to the pieces the customer drew); runs the bridge CLOSED untouched (TL-1016 class); a run open by <= BROKEN_OUTER_GAP keeps its bridges + holes and is REPORTED (gap + place) in repair + the split record, never silently closed. Threshold: his 0.020 is the closure line itself (would never fire), set 0.25 = under the smallest gap the rollback takes apart anywhere in the corpus (0.3125, a title block) -- flagged to him, one named constant. Proposed rule 1 (only closed runs own holes) DROPPED on measurement: it shattered CAMP#4's link part (open 0.66, 4 holes). Corpus 110 files: 79 identical; flat grill 16 -> 8 parts, all 8 copies 20/20 long slots + 43 closed contours (= the old CAM's clean); changed otherwise only drawing-sheet ink (20x 23004 + 9x F1 title blocks) + the partly-unfolded bend-lines DWG (62 -> 75 fragments, garbage-class). NEW test_split_bridge_rollback 15 (grill fixture fails on old code) + partgroups 21 / lineage 26 / part_list 41 / pl_free 42; identity gate green; F1 8.04/8.09 -> 8.06/8.09s no cost; zero dev O-numbers. | BROKEN-OUTER LIMIT = OPERATOR KNOB QUESTION 2026-10-09 (question; Jordan on 0.25: 'I don't know... one of those numbers the operator will need quick access to, to trial-and-error clean on a case-by-case basis... I don't think we can quantify this honestly for a one size fits all solution'): BROKEN_OUTER_GAP stays 0.25 as the SEED only; proposed = a per-job 'open-outline limit' field on the split door (Part list / Intake), re-split at the typed value, recorded set/was like the cleaner-tolerance door, old children replaced as one undo step. Awaiting his go. Dev restarted same day on his 'Go for it' (inflight 0/0) -- the bridge-rollback split is live on dev. | HELD 2026-10-09 (Jordan: 'keep this issue logged on the pin for now. I want to test this with a wide variety of examples so we get it right. Let's not jump the gun'): the operator-knob field stays unbuilt until his wide-example testing; 0.25 seed stands. | 2026-10-31 FOUND (Jordan: why did some BNM78598 copies lose bend lines?): the whole-drawing heal keeps all 11 long bend lines in every copy; the SPLIT drops 14 of them as 'debris' (job.split.debris 14). split_parts.part_groups decides which part owns a contour by testing ONLY its first sample point; these bend lines run edge to edge and their first point sits 0.004-0.006in from the outline, a hair outside the sampled outline on some copies, so they become lone groups and are thrown away as debris; the middle of each line is inside the part. Same rule, different outcome per copy. Fix idea (not built): test the line's middle / most of its points, not its first point; would touch every split, needs a corpus sweep. Also: 14 dropped lines only show as a count in the split record. | 2026-10-31 BNM78598 bend-line ends measured: of 88 long bend lines in the healed parent, 80 have at least one end 0.003-0.004in PAST the outline (into the small relief arcs, r 0.05-0.12in), 8 past at both ends; the cleanup did not move them (0.0000) and they sit the same distance from the drawing's own outline -- drawn that way. Dropped = the 14 whose FIRST point is the overshooting end (8 overshoot both ends); 10 more start outside but survive only because the 0.05in-sampled outline cuts the relief curve. Jordan asked how a middle-point rule handles crosshairs in/around holes: proposed instead 'most of the length inside, points within the job tolerance of the outline count as on it, a loose line that is mostly outside every part or straddles two is flagged, never silently dropped'; needs fixtures (crosshairs in holes, crosshairs past holes, centre marks on the edge, bend lines into reliefs, dimension lines between parts). Nothing built. | 2026-10-31 RULING (Jordan): crosshairs and centre marks are DROPPED (not cut). Today only partly covered: centre marks on a notes layer are set aside (dxf_io), drawing-sheet intake drops centre-mark crosses (drawing_extract.crosshair_centers, test_sheet_intake 19e); a crosshair on the cut layer of a plain DXF is not known to be dropped -- unmeasured. Jordan asked if the loose-line ownership fixtures can be tested without him: yes for synthetic fixtures + dev corpus sweep (1,559 jobs on dev); Jordan only needed for a look at the files whose split changes. | 2026-10-31 O75 WIP on branch o75-looseown (d5cbff82, NOT on main/prod; Jordan: 'build it and test it, roll back if band-aid'): a loose line a closed contour holds ALL of (within OWN_TOL 0.010) belongs to it whatever its first point says; only ever adds a home; set-aside slivers named in job.split.debris_items + shown on the job. Tests: new test_split_loose_owner ALL PASS (old code fails the overshooting-end bend case), split rollback/door/side-view tests pass, identity gate green. BNM78598: 8 copies x 64, 0 dropped (was 62/63, 14 dropped). Dev corpus 1,381 files: 1,345 same; 36 differ, all lines GAINED by a part: BNM grill files, 79602 (3 loose arcs join their 1.0x0.578 parts), and 29 plate files (20x 23004-*, 9x f1-release-lv00151-*) where a 5.95x0.562 piece (and on f1 a 5x1.2 and 8x0.45 group) that used to split off as its own part now stays in the 16.75x10.75 plate -- NOT yet looked at; f1-release files are F1 bench fixtures, F1 not yet timed. Crosshair drop (Jordan's ruling) not in this chunk. | 2026-10-31 Jordan could not open the 23004 jobs from search. Measured: the 20 jobs (uploaded 2026-10-05 as one drop, Lathrup drawing sheets, flat view never extracted) open by direct link and card click on dev; their job.json still points at group '23004-344 + 19 more' (23004-344-19-more-1791229615) and split children (e.g. 23004-344-part-1/2) that are no longer on disk (not in Trash, no record found of who removed them), so the Part list tab / group link lead nowhere (404). O75 correction: the '16.75 x 10.75 plate' in the 29 sweep files (20x 23004 + 9x f1-release) is the drawing-sheet BORDER, not a plate; the 5.95 x 0.562 piece is drawing ink inside it. Fix B (2026-10-12) already blocks these unextracted sheets from splitting, so O75's change there reaches no part list. Measured only, nothing built. | 2026-10-31 O75 checks finished (Jordan: drop the 23004 tab issue, it's not a current build issue; continue O75). The 29 'plate' files rendered old vs new (board dev.kerfmaster.com/viewer/builds/o75-plates/): the 16.75 x 10.75 group is the drawing-sheet border; what used to split off is title-block / revision-box ink (5.95 x 0.562 revision box top right; on F1 also 5 x 1.2 and 8 x 0.45 title-block cells) -- O75 keeps it with the border instead of making it a 'part'. These sheets are blocked from splitting by Fix B (unextracted flat), so no part list changes. F1 first click 7.69/7.69s -> 7.71/7.69s, repeat 7.51/7.48 -> 7.50/7.50 (main vs branch module): no cost (F1 part jobs don't go through part_groups). Branch o75-looseown still off main; merge awaits Jordan. | 2026-10-31 O75 MERGED TO MAIN (Jordan: '1. Yes, those red lines belong in the part. 2. Yes.' -- on the BNM78598 before/after board, dev.kerfmaster.com/viewer/builds/o75-plates/). split_parts.part_groups: a loose run is owned by the smallest closed contour that holds ALL its samples (inside, or within OWN_TOL 0.010 of its edge) -- replaces first-point ownership; it only adds a home, never takes one away. server.run_split records job.split.debris_items [{len, at}]; app.js lists loose lines >= 0.25in left out of every part. Measured: BNM78598 8 copies x 64 shapes, 0 debris (was 62/63 and 14 bend lines dropped); corpus 1,381 dev files, 1,345 identical, 36 only gain lines (BNM grill files, 79602 x3 loose arcs, 29 drawing sheets whose title-block boxes stay with the border -- those sheets are blocked from splitting, no part list reached). Tests: test_split_loose_owner ALL PASS (old code fails the overshooting bend), split_bridge_rollback ALL PASS, split_door 17/17, split_side_views pass; identity gate green; F1 7.69/7.51 -> 7.71/7.50s, no cost. Touches: every multi-part split (upload/split door), not single-part files, not nest/post. Rollback tag pre-o75-merge. Still open: crosshair/centre-mark drop on plain DXFs (Jordan's ruling, own chunk). | 2026-10-31 dev restarted 21:49 UTC on Jordan's 'Yes' (both inflight 0); O75 live on dev. Prod gets it via deploy from main (d855475c). | 2026-10-31 Jordan after O75 went live: 'all the lines made it through correctly, but it's still splitting the file into 8 different parts. Why?' Measured on his re-upload (list bnm78598-...-flat-sh-1793483599, 8 rows qty 1, merge tol 0.001): all 8 copies 64 contours, but congruent_parts says no even at 0.010 -- the per-contour signature pre-check (emit._congruence_sig: multiset of piece lengths/radii) differs on copies 2-8 because each healed copy is built from different pieces (the source draws each copy with a different entity count). So no merge tolerance can join them today. Fix = the middle option (match copies on the SOURCE drawing, every matched copy uses one healed result); re-offered, awaiting go. Nothing built. | O76 BUILT on branch o76-srcmatch (NOT on main, not live), 2026-10-31, Jordan 'Go on the middle option': the copy-merge (server.run_mergecopies) also matches copies on the ORIGINAL drawing. split_parts.congruent_flat compares two drawings as flat bags of drawn pieces in BOTH directions (piece counts, splits and doubled pieces don't matter; duplicate-blind footprint for the start move; point-to-line ICP; every sampled point within the merge tolerance). group_congruent(sources=) adds it as a second way into a group: a source match only ADDS a merge, never removes one; sources=None byte-identical. Guards: same healed contour count; healed contour areas/lengths within 1%; a copy with an operator (non-auto) heal edit is judged on its cleaned-up shapes only (server._job_source_prims returns None). The merged row cuts from the representative's cleaned-up result. CORRECTION: my earlier '8 copies match within 0.0005 in the source' was wrong -- measured both ways on Jordan's re-upload the drawn copies differ by up to 0.0043 at 4 small spots (a small arc near the top, a diagonal at bottom right, two points); healed copies differ by the same 0.0040-0.0042, so healing is faithful. BNM78598 re-upload result (scratch copies, real jobs untouched): merge tol 0.001 -> 5 rows (part 2 qty 4 + 1,4,5,7 singles); 0.002 -> 3 rows; 0.005 -> 1 row qty 8; setting back to 0.001 regroups. Corpus (18 split files, 441 copies, tol 0.001): only BNM uploads change (8->5, 8->6, 13->9) plus one pair of 0.09in D-shaped bits in the old 60-part BNM upload (43->42); all 14 other files unchanged. Cost of the merge step: BNM 0.2s -> 2.2s; Camp-4 91 copies 2.8s -> 7.4s (162 near-identical test-pattern pairs searched). F1 n/a (not on the first-click path; only mergecopies passes sources). Tests: test_merge_source 17/17, test_partgroups 21/21, test_qty_text 37/37, test_split_door 17/17, test_split_loose_owner pass. Identity gate green. Rollback tag pre-o76-srcmatch. Not touched: run_partgroups (split modal grouping, still healed-only), nesting, post. | 2026-10-31 O76 addendum (Jordan go 1-3): default merge tolerance 0.001 -> 0.005 in (split_parts.MERGE_TOL_DEFAULT; run_mergecopies docstring; app.js Part-list field fallback). Same number as the split screen's PART_MATCH_TOL. Only lists with no stored merge setting pick it up; a stored tol (e.g. Jordan's BNM list at 0.001) is kept until typed over. Proof: BNM78598 scratch copy with merge record removed -> 1 row qty 8 (2.8s); corpus sweep at 0.005 earlier: BNM latest 8->1, pre-O75 BNM 8->3 and 13->6 (real differences), 60-part 43->42, Camp-4 stays 16, rest unchanged. Tests: test_merge_source ALL PASS, test_partgroups 21/21, test_qty_text 37/37, test_split_door 17/17, test_split_loose_owner PASS. Identity gate green. F1 n/a (merge step only). Rollback tag pre-o76-default. | 2026-10-31 22:45 UTC: O76 merged to main (028f4a49, tag pre-o76-merge), identity gate green; dev restarted (inflight 0/0 both sides, Jordan OK), active, serves the 0.005 field default.
- •Annotation ink (dimensions/text) visible to the operator -- how to spot a dimensioned preview part (Jordan 2026-09-15) record — Jordan, 2026-09-15, on his CAMP#4 pre-nested customer sheet (91 parts + one lone dimensioned 'preview' copy in the upper-left, known only from his own DXF readers): 'How would the operator know that the upper left part was a dimensioned preview if all of the source dimensions and outlines are not visible?' HONEST STATE TODAY: dxf_io.parse never reads DIMENSION/TEXT entities (they are not cut geometry), so the gray base layer cannot draw them; the ONLY tell is the sheet-intake yellow's counts ('2 dimension entities, 16 text entities, 434 separated view clusters' on his file) -- the operator learns the file CARRIES annotation ink, never WHERE it sits. OFFERED (awaiting a go): (1) parse DIMENSION/TEXT ink for DISPLAY ONLY and draw it on the gray base layer -- the customer's original stays the review-against-source spine, annotation ink rides it dimmed, never healed, never cut; (2) mark the cluster that OWNS the dimension entities on the canvas ('this copy carries the print's dimensions -- likely a preview, not a production part') so the operator sees the preview at a glance before splitting or nesting. Nothing built until Jordan or Aristide says go. DESIGN PROPOSED 2026-09-15 (Jordan 1a: 'on one hand we want to clean the cad to reduce human labor inputs, on the other we want to show the operator as much of the source file as possible, without nagging or inducing unnecessary input'): annotation ink as its OWN silent display layer -- parse DIMENSION/TEXT display-only (never healed, never cut, never QC'd), draw dimmed beside the gray base layer with its own layer toggle (default ON, one key like the other layers); the part cluster owning the dimension ink gets a quiet 'likely a dimensioned preview' caption on canvas; the intake yellow's counts become a click that frames the ink. ZERO prompts, zero required input -- pure display, the cleaning pipeline untouched, so both goals hold: the cut geometry stays clean automatically AND the operator sees everything the customer drew. BUILT 2026-09-16 (Jordan 'Go on all'): engine annot.py (docstring = design record) -- whole-file scan reads ENTITIES-section TEXT/MTEXT (MTEXT formatting stripped, %%c/%%d/%%p decoded) and DIMENSION entities' anonymous *D block ink (LINE/ARC/CIRCLE/SOLID/LWPOLYLINE/POLYLINE/TEXT rendered as drawn, arrowhead SOLIDs as closed chains; a missing block falls back to a counted marker + the dimension's own text, never silent); DISPLAY ONLY by construction -- dxf_io/heal/QC/nest/post untouched, no number read here ever becomes geometry (pdf-dims-govern stays its own deliberate door). SERVER: run_pipeline persists geo.annot scaled by the SAME units statement and turned by the SAME intake rotation as the gray base layer (one frame, every layer; a display aid never breaks the pipeline -- failures log and serve empty); older geometry.json backfills on first GET from the job's RECORDED scale/rotation, cached once -- Jordan's CAMP parent shows its ink without a re-heal. UI: 'Annotation ink (display only)' joins the layer bar (key A, default ON, dimmed var(--dim), text drawn at its own height/rotation) -- the button appears only on jobs that carry ink; the ink's own footprint carries the quiet 'likely a dimensioned preview' caption (a caption, never a prompt). Proven: test_annot.py 15 NEW controls (block ink, stripping, missing-block fallback, part-geometry never in the ink, mm scale, rot90 exact quarter turn, backfill-and-cache) + app/verify_annot.js 8 live Playwright checks over the public URL (button/key/caption path, bare job shows nothing; fixtures removed). Honest limits: ink draws from the SOURCE frame (a moved/edited part leaves its ink where the customer drew it); MTEXT wraps and special dim styles render approximately -- display, never authority. DASHED INK IS ANNOTATION 2026-09-30 (Jordan's BNM bend-line kits -- his 12-DWG prod upload: the 10 'WITH BEND LINES' files shredded into 3-82 'parts' each, a 151-row list, while the 2 'NO BENDS' controls split clean; his 'Yes, go on both fixes'): a broken linetype (DASHED / HIDDEN / CENTER / PHANTOM / ...) is drafting annotation by convention -- bend lines, fold marks, centerlines -- never cut ink. ENGINE dxf_io.linetype_is_annotation classifies by the EFFECTIVE linetype: the entity's own code 6 beats its layer, BYLAYER resolves through the LAYER table (parse now scans it), an unknown layer resolves SOLID -- when in doubt the ink STAYS cut geometry and QC judges it, never a silent drop. parse() routes every dashed entity type (LINE, ARC, CIRCLE, LWPOLYLINE, POLYLINE, SPLINE, ELLIPSE -- splines/ellipses sampled off their true curves; OCS mirror applied before routing) into parsed['dashed'] as display point-chains and OUT of the cut lists, so heal/QC/split/toolpath/nest/post never see them -- ONE seam, every re-parse site inherits it unchanged. SERVER: run_pipeline merges the chains into geo.annot (new 'dashed' key + counts.dashed) in raw source coordinates BEFORE the units statement and intake rotation apply -- one frame, every layer; the backfill door gains the same merge, so old jobs show their bend lines on first read. CLIENT: the annotation layer strokes them WITH setLineDash -- a bend line looks like a bend line; same toggle (key A), same dim role, zero new controls. Proven NEW test_dashed_ink.py 17 controls (classifier tiers, every entity type, entity-override-beats-layer, unknown-layer-stays-cut, continuous-only file parses untouched) + the real 78598: exactly the 105 measured bend-line entities routed to annotation, 723 polylines + 70 splines + 75 ellipses kept as cut ink + live dev upload + neighbour suites qc_link 15 / micro_refit / drift_cap / weld 24 / healedit 99 / sheet_intake 36 / annot 15 green. HONEST LIMITS stated: dashed ink inside a BLOCK insert is not reached (parse's ENTITIES-section scope rule); dashed ink of any color stays dashed annotation. COLOR-SET PICK AT THE DOOR BUILT 2026-10-01 (fix (b) of the same go, Aristide 'Go'): overlaid same-region contour sets distinguished only by COLOR get the pick-the-cut-geometry question at upload -- seed never bind, every color cuts until the operator says otherwise. ENGINE dxf_io: _effective_aci resolves every entity's color (own code 62 beats BYLAYER; 0/BYBLOCK reads 7; BYLAYER through the LAYER table's own color column, which parse now scans beside the linetypes; a frozen layer's negative color reads absolute; unknown resolves 7), parse() censuses every SOLID entity into parsed['colors'] ({aci: count, bbox, cut}), and color_question asks ONLY when 2+ real sets (>= 2 entities each) overlay the same region (bbox-pair intersection >= half the smaller) -- a kit merely drawn in several colors side by side never nags; dashed ink is never censused (linetype outranks color). THE PICK IS A SIDECAR beside the source (source.dxf.colors.json {cut, who, date}) read at the ONE parse seam, so every re-parse site inherits it with zero caller change (the units-force nine-site lesson); unpicked colors route to parsed['colorink'] as display chains; no sidecar = byte-identical cut lists (the real kit reparses to exactly the dashed-fix numbers). SERVER: the intake record gains the colors block (sets sorted, question suppressed once answered, pick provenance); geo.annot gains colorink + counts in the one frame (annot.scaled/rot90 carry it); the heal-cache key gains the sidecar stat so a pick never serves stale prims; NEW POST /api/jobs/<id>/colorpick {cut:[aci...]} | {clear:true} -- refusals plain 400 naming the file's own colors, picking ALL colors = the clear (absence IS the state), a real pick re-runs the pipeline (standing stale rule, numbers kept), journalled HEAVY undo door. CLIENT: the question fires INSIDE roadGroup BEFORE the split (a pick lands before the file's parts become rows -- the shred prevention), ONE modal listing the suspect files with color-swatch chips (ACI map approximation, a display aid), all chips on by default, the last cut color refuses to untick, Later keeps everything cutting with the question standing on the Intake drawer (yellow row); the drawer carries the pick/provenance/change rows and the annotation layer strokes colorink SOLID in the dim role (key A hides it with the rest). Proven NEW test_color_sets.py 25 controls (resolver tiers, census, ask/never-nag gates, every entity type routes, dashed-outranks-color, garbage sidecar = honest default; the real 78598 kit COMMITTED as testdata/78598-BENDLINES.dwg: 7 overlaid sets censused, question fires, picked 150+163 -> 283 entities to the annotation layer, 723 -> 483 cut polylines) + live dev door proof + neighbour suites dashed_ink 17 / annot 15 / qc_link 15 / units_confirm 27 / sheet_intake 36 / healedit 99 / micro_refit green; engine restarted; zero dev O-numbers. HONEST LIMITS stated: split children predating a pick stand as recorded (re-split is the operator's move after a pick); older jobs gain the census on their next pipeline run; colorink draws bulged polylines as their vertex chains (display only); truecolor (code 420) entities resolve by their ACI fallback; the browser click-through suite (verify_colorpick.js) is queued, the verify_plcancel precedent. DOOR QUESTION OFF 2026-10-02 (Jordan '6' on the switch-off offer, after his main_gusset_rh confusion -- the pop-up fired on 2 gray splines with nothing to decide): client-only, the upload door no longer opens the color modal (CK_DOOR_ASK=false, ckDoorCheck kept), every color cuts by default as before 10-01; the Intake drawer keeps the optional pick/change row, demoted from a yellow finding to a plain row. Server census, /colorpick door and recorded picks untouched. The broader source-anomaly handling is pin source-truth-view. QUEUED SUITE RETIRED 2026-10-03 (Aristide 'Yes' on the retirement assessment): verify_colorpick.js is dropped unbuilt -- it was scoped to click-prove the upload-time color modal, which Jordan's '6' turned off the next day; the engine side stands proven (test_color_sets.py 25 + the live door proof in the build record). The one uncovered remainder, the Intake drawer pick/change row click, is a one-or-two-check fold-in for an existing intake-area suite if ever wanted, never a suite of its own. EXTENDED 2026-10-05 (the F1/SolidWorks regression -- Jordan's 29-file F1 RELEASE upload dead on app; Aristide's two-fold ruling: a good fix without rolling back the good improvements, plus prevention added to the golden rule; Jordan 'Go'): the 2026-09-30 classifier was a NAME WHITELIST (only ''/CONTINUOUS/BYBLOCK read solid), so SolidWorks' custom-named solid linetype 'SLD-Solid' classified EVERY cut entity annotation -- all 29 uploads starved to zero cut prims and died as 'min() arg is an empty sequence' (blocked intake) and split-door IndexError; the record's own doubt rule ('doubt stays cut geometry') was implemented INVERTED for unknown names -- my defect, wrong from birth, tests mirrored the code not the record. REBUILT: the judge is the file's OWN LTYPE table -- parse() scans each linetype's declared dash element count (group code 73) and linetype_is_annotation(dashes=) annotates on declared dashes > 0, reads SOLID at 0 whatever the name; only a name the table never declares falls back to the canonical broken-name families (DASH/HIDDEN/CENTER/CENTRE/PHANTOM/DOT/DIVIDE/BORDER prefixes); any other unknown name stays CUT GEOMETRY. Both crash sites are now honest refusals naming where the ink went (run_pipeline zero-cut ValueError in plain words; split door plain 400). PROVEN: all 29 F1 files parse (file 304: 188 cut + 10 dashed = the pre-regression 198 total); BNM 78598 regression exact (105 bend-line entities routed, 868 cut); test_dashed_ink 17 -> 22 (verbatim rule-as-control checks: unknown name stays cut, the table governs both ways, end-to-end LTYPE parse, the SolidWorks fixture); NEW testdata/solidworks-linetypes.dxf (real F1 LTYPE+LAYER tables verbatim, proven discriminating -- zero cut under the old classifier); 760-source corpus sweep old-vs-new = ONE census change, the new fixture itself; identity gate 22 cases green incl. NEW solidworks adversarial (census ASSERTED before the byte gate), full --make-refs left all 20 prior references byte-identical; F1 first click 8.31/8.23 -> 8.22/8.28s A/B same session, no cost (the recorded 84s dev baseline predates the Speed graduation merge); color_sets 25 / square_up 23 / ocs 12 / view_extents 9 / sketch 21 green; units_confirm's 2 fails proven pre-existing on the stashed baseline. Prod deploys on the commit; Jordan's 29 files re-upload after.
- •The hand editor on part-list nests -- drag, rotate, cross-sheet move, Alt-drag COPY (BUILT); true-nest snap-rewire retired by stage-4 door convergence record — Jordan, 2026-09-14, Go on all: the manual-nest-editor gestures land on the part-list Nest canvas — grab any placement and drag it anywhere, click a part and rotate/flip it freely (Illustrator shapes), drag a part from one sheet to another, and Alt/Option-drag COPIES it. ONE-CLICK ROTATE BUTTONS 2026-09-15 (Aristide go for next in his ratified order): +90 and 180 buttons join the hand-editor bar beside the typed angle -- the true-nest editor vocabulary (180 IS the nest flip, the flip-every-other-column form; a mirror is not a placement move); both drive the SAME draft-rotate arithmetic as the typed slot (one function, turn about the part own centre, draft until Apply, disabled without a selection). Client-only app.js, live on refresh; verify_plhrot.js 11 live real-mouse checks (compose 90+180, typed -270 parity back to zero, world centre fixed, other copies untouched, Apply + fresh-page persistence, disabled-without-selection) + verify_plhand.js 18 re-run green. TOOLPATH DOCK, BUILT 2026-09-19 (record; Jordan: the old CAM's dock 'magnets parts to a bounding-box boundary around the adjacent parts, with an easily overridable offset value. We could do one better, and use the toolpath rather than a bounding-box'; his 'Go'): the dragged copy magnets to the position where its TOOLPATH sits exactly the dock gap off a neighbour's toolpath -- true as-cut segs (tab gaps included) PLUS pierce and lead line, sampled per orientation from the pack's own plan rows (plDockSamples; old packs without segs honestly fall back to the true-bbox perimeter, exactly the old CAM box dock this improves on). Sliding-profile arithmetic client-side (dockProfile/dockContact -- per-bin X/Y extremes, 0.25 bins widened one step so a bin-edge point never lands the dock closer than the gap; conservative, the judge on Apply still measures true outlines), so concave parts genuinely tuck into each other's reliefs (proven in the suite: a mover docks INTO a recess a bbox dock cannot enter). Gap per pair = the larger of the two parts' bridges (the recorded pairwise rule, read from report.bridges), sheet edge = the part's own bridge (the ruled per-part margin, exact); ONE typed field on the hand-editor bar overrides all pairs (isoinp = the Excel-entry seam, placeholder shows the bridge seed); Alt slides free, the house convention. Client-only app.js. NEW app/verify_pldock.js 14/14 (exact solver controls incl. the no-Y-dock-without-X-overlap null, live checks on the real 7497/7498 job draft-only -- Apply never clicked) + plhand 18/18, plhrot 11/11, plvariant 10/10, ctxmenu 26/26, partnav 15/15, pltabs 19/19 green. Honest limit: the TRUE-NEST hand editor still runs its 2026-09-05 box-envelope snap -- rewiring it onto this same contact solver is the stated next step, offered. RESOLVED 2026-09-19 (stage-4 door convergence, pin job-style-unification): the rewire RETIRES instead of building -- every new upload is a part list, so new jobs never reach the true-nest hand editor (the one road's pl hand editor carries the toolpath dock); old jobs keep the box-envelope snap as a legacy surface.
- •Illustrator-style isolation drill-down editing -- application-wide, full treatment (COMMISSIONED) ruling — Aristide, 2026-09-15 (nest screenshot of the big plate): grab a shape and move it with ALL its elements grouped; then, like Illustrator, double-click drills INTO the group -- edit one hole alone, drill into a letter A, then into the hole of the A itself. 'Make it clear in the interface that I am drilling down, just like in illustrator.' RECORDED LIMIT 2026-09-15 (found answering Jordan's 2a -- all-contours identity): the apply-to-all-identical twin test at the feature-with-children level matches the parent sig AND the children's SIG MULTISET but not the children's POSITIONS -- two bosses whose holes are the same shapes at different spots would falsely twin. LIMIT CLOSED 2026-09-16 (Jordan 'Go on all'): /isogroups now carries featsig -- chain + descendants grouped as one PART through split_parts.congruent_parts (the nest door's whole-part arithmetic: one rigid rotation + translation must map EVERY member contour, positions included), the cheap sig test kept only as a prefilter; the client's feature-level twin test reads featsig (sig-multiset stays the honest fallback on a pre-restart payload). Two features whose children merely share shapes at different spots never twin; a rotated true copy still does. Proven: test_isofeat.py 9 NEW controls (the old defect proven present via the prefilter, moved-hole never groups, rotated copy groups, read-only deterministic); isoserver 17 / isoident 12 / partgroups 21 green. Standing limit unchanged: mirrored copies group with their mirror (the per-chain sig's own recorded limit). GRANULAR SIZE EDITS BUILT 2026-09-18 (Jordan's drilled-circle screenshot -- 'the ability to, once I'm drilled down, to change the diameter of the circle ... if this were an arc ... change its radius. I'm missing the granular detail modification ability.'; his 'Go' -- also the tolerance-center ruling's promised manual hole-size lever, first built form): ENGINE heal_edit ops set_diameter (nearest TRUE circle -- closed all-arc chain on one center+radius sweeping a full turn; every piece scales radially about the untouched center so split points keep their bearings) and set_radius (the single arc under the click re-fit at the typed radius, ENDPOINTS HELD -- refuses under half the chord naming the smallest radius that fits; the new center keeps minor-minor/major-major, the bulge side being fixed by the direction of travel; a broken tangency is QC's honest flag, never hidden). Recorded heal edits exactly like move/rotate: replayed on every re-parse, removable per row, both fidelity exemptions on the report row, one Undo away, the standing stale rule fires downstream. CLIENT: right-click any healed arc -- a circle offers 'Set circle diameter (now O ...)', any other arc 'Set arc radius (now R ...)', prompt seeded with the current value, unit suffixes accepted, 4-decimal floor; the isolation bar grows a diameter field on a drilled TRUE circle (seeded live; Set commits through the identical-shape all-or-one modal, fanning the same diameter to every twin; the level re-drills through the radial map); Heal/QC panel rows name both edits in plain words. Tangent fillet resize (endpoints sliding along the neighbour walls to keep tangency) = the stated next step, offered. Verified: NEW test_setsize.py 27 controls (CW/CCW, minor/major sense, refusal words) + NEW app/verify_setsize.js 11/11 live on dev + neighbours iso 15/15, isoident 9/9 x3 (two earlier blips proven the suite's own isoReload race under load, baseline checked), ctxmenu 26/26, globalband 13/13, healqc 14/14, undo 17/17, gc56 25/25, test_healedit 78/noop 8/healadd 13; dev engine restarted. TANGENT FILLET RESIZE BUILT 2026-09-22 (Aristide 'go ahead for the next one' off the standing offer): the stated next step lands -- heal_edit op set_fillet, the tangency-KEEPING sibling of set_radius. The typed radius slides the arc's endpoints along its two straight neighbours (trimmed toward, or extended back from, their shared corner V; tangent points at r/tan(half-angle) from V, center on the bisector), so both seams stay smooth at the new radius -- set_radius keeps endpoints and its broken tangency stays QC's honest flag. Scope today: an arc blending two LINES (the tangent-rad corner); every other case refuses in honest words naming the right edit -- arc-to-arc blend, non-tangent jog corner (2-deg picking gate), open chain end, true circle (set diameter), parallel/collinear straights, too-big radius naming the largest that keeps both straights, same-value no-op. Recorded/replayed/removable like every size edit, both fidelity exemptions cover all THREE touched prims, self-audit with separate arithmetic proves the rebuilt center sits exactly r off both lines before anything changes. CLIENT: right-click a non-circle healed arc now offers 'Set fillet radius (now R ..., tangency kept)' beside the endpoints-held item, same seeded prompt road; panel row in plain words. Proven NEW test_setfillet.py 23 controls (grow/shrink/CW/60-deg corner/list-seam wraparound/stacked edits/lenient replay + every refusal) + verify_setsize.js 13 -> 17 live on dev (both items offered, endpoints slid to the exact seams, door refusal saves nothing) + test_setsize 27, healedit 78, isoedit 18, ctxmenu 26, healqc 14, healadd 12 zero edits; dev engine restarted; zero dev O-numbers, progseq untouched.
- •grouped upload + the sorting tray -- the group is declared at upload, granularity on demand (SESSION 1 BUILT) ruling — Jordan, 2026-09-14: uploading several files should let the START of the upload say whether they become individual jobs or one grouped job (a part list). The split/add-all doors stay as break-in granularity; they are no longer how the flow starts. His bar on the tray design: 'make this the best damn interface you've ever designed. Think Apple ease of use and intuitive.'
ONE GROUP BY DEFAULT 2026-09-19 (Jordan: jobs with 25 or more files are common for him, so the common case should not need 25 drags -- his 'Go'): a multi-file drop now opens the tray with EVERY file already stacked into ONE group; the operator confirms and the whole batch lands as one part list. Two one-click reshapes on the tray: 'Separate all' unstacks to per-file cards (the previous default, for the drop that really is unrelated files) and 'Stack all' restores the single stack; the drag-to-stack granularity is unchanged once separated. verify_tray.js asserts the one-stack open, then Separates to prove the classic per-file flow still works; verify_multiupload.js separates before both confirms. Suites green same commit as the DWG intake.
- •Part-list display format -- 'hard for me to read' (Jordan 2026-09-15, awaiting Aristide) question — Jordan, 2026-09-15, on misreading his own 7497/7498 list ('My mistake, the list is hard for me to read. We will need to work on the display format to make things easier on the eyes. We will need Aristide's input on this.'): the Part list tab's row form needs a readability pass -- his misread was real evidence (he thought parts were missing that were listed). Nothing designed yet; waits for a sitting with Aristide (the ui-visibility-pass precedent: his items, our execution). Candidates when they sit: thumbnails per row (the jobs-home-filing ruling already says the shape is how the archive is browsed), stronger row separation, name-first columns.
- •Shop's one-sheet 7497/7498 nest MATCHED AND EXCEEDED: our pack lands all 14 parts on one sheet at less used X (2026-09-16) record — Jordan, 2026-09-15: 'we were able to get all of these parts onto one 60"x120" sheet on our end with manual nesting in the old CAM... See if we can do better, and I will send you our nest tomorrow morning.' His nest arrived 2026-09-16 (PDF, NC 33365): all 14 parts (7497 x9 + 7498 x5, qty 1 each) on ONE sheet, extent 119.564 x 58.585 measured off his own print. Ours had spilled 7497 parts 2+3 to a second sheet (banded packer, bbox density 95% -- only true-shape pockets close the gap; a probe proved ~305 legal pocket spots existed). The TRUE-POCKET SPILL RESCUE (pin pl-pocket-rescue, built same day on his 'I expect your nesting to match, or better yet, exceed what we humans can do') closes it: ONE sheet, 14 parts, used X 119.2614 -- 0.30 in less material than his hand nest, every always-apply rule on (ruled gaps on true outlines, lead/pierce envelopes reserved, audit +0.005 over ruled). The invariant derived, not the layout transplanted (nest-objective-function): his layout spends concave mouths between parts; the engine now sees them. The CAMP alternate-180 pairing (pin pl-pack-alternate-180) is a SEPARATE standing question -- untouched by this build, still awaiting its own go.
- •Congruent-outline runs pack as the MEASURED regular form -- the CAMP#4 staircase fixed (Jordan's go, 2026-09-16) record — BUILT 2026-09-16 on Jordan's go ('Go, and let me know when you're done building all'), from his CAMP#4 catch ('This nesting is illogical. It should be uniform alternating every other part flipped 180'). ENGINE part_list_nest._form_runs (the design record): parts whose OUTER outlines are congruent under translation (point-to-segment both directions at RUN_TOL 0.003 -- under the construction PAD so a twin's outline can never eat it; interiors free, the outline is what nests; an item without an ordered outer never groups -- conservative) pack through ONE shared proxy = the mini-nest common denominator (nest-alt-two-true-nests): the shared outline + the UNION of every member's lead envelope so any member sits in any slot, bridge = larger governs across members. The form is MEASURED, never assumed (_run_form): uniform(a) and alternating(a, a+180) columns are each simulated with the pack's own slide arithmetic, metric = real X per part over two columns (column widths AND inter-column spacing both land in the second column's top); a tie prefers the alternating pair only when the outline is 180-asymmetric -- a symmetric outline stays uniform, the flip would only flip interiors. The winner is FORCED: every column runs one fixed angle cycle (try_rows parity), so the lattice is regular by construction and the greedy staircase cannot form; a lone qty>=2 row with rotation freedom is its own run (regularity is for every same-outline stack, one row or many). Members return at _run_remap BEFORE the audit -- each placement takes its member's own id, bridge and frame delta, so the separate-arithmetic audit judges each member's OWN outline + leads at the ruled values (construction at the union/larger values holds a fortiori); filler extras remap to the run's filler members; the report carries runs [{members, qty, form, bridge}] and each placement names its run -- never silent. Unlike-outline parts keep the slide packer untouched. Proven: test_pl_alt.py 14 NEW controls (the staircase fixture -- same outline, two lead sets -> ONE run with strictly alternating columns and pair-period pitch; symmetric rectangle -> uniform; a 50-thou-different outline never twins; locked-rotation multi-member run uniform-0; frame-delta twin lands at the right world spot; larger-governs construction with per-member bridges recorded; filler member; mixed run + odd part) + 12 neighbour suites green. Jordan's CAMP#4 job lives on prod -- a re-pack from its Nest tab after the auto-deploy shows the regular lattice. Honest limits: congruence is translation-only in the shared part frame (a twin drawn ROTATED in its own file packs as its own run); the alternating pair meshes within the column -- the cross-column tuck channel (tuck_alt_flip) stays the true-nest engine's own.
- •INTERLOCKED run form in the part-list packer -- raised sub-columns measured as a candidate; CAMP#4 46.33 -> 46.15; the old CAM Algorithm 3 still wins at 42.65, verified legal, the oblique-lattice gap named (2026-09-16) record — BUILT 2026-09-16 on Jordan's 'Go', from his three the old CAM algorithm exports on the CAMP#4 kit (incoming/1789591653/55/57, Algorithm 3 = the winner, extent 42.65 x 35.05). ENGINE part_list_nest._run_form REWRITTEN: a form sequence is now [(angle, raise), ...] (position 0 always raise 0) and the candidates are uniform / alternating / INTERLOCKED -- the second cycle position raised d in real X so the 180 sub-column interpenetrates the 0 column, d SWEPT coarse (h/24) then refined (step/8), k-step cycles (2,3,4,6) with staircase raises; a skew family (same angle raised) rides per {a, a+180} class; ties prefer the simplest form (alternating < uniform < interlock < skew) and a 180-symmetric outline demotes to the same-angle name. try_rows unpacks (angle, dy); _pair_asymmetric REWRITTEN to a two-way congruence test (_haus) at RUN_TOL -- the old bin-profile test charged sampling scatter on slanted edges as asymmetry. Proven: test_pl_interlock.py 12 NEW controls (diamond checkerboard NEEDS the raise and beats any flat form; d in the name matches the measured level gap; chevron-with-flip proves flat alternating still wins when it should; leads/audit/regularity/mixed/spill) + test_pl_alt controls 2/3 updated (the L run now legitimately measures interlocked -- the deeper tuck; stale-verify precedent) + 12 neighbour suites green. THE REAL JOB re-packed via run_partnest under the job lock: 1 sheet, used_x 46.3284 -> 46.1469, all 15 runs interlocked 0/180 (sub-columns 1.80-1.92 apart), audit gap +0.005 / edge +0.005 over ruled, program dropped per the stale rule with O33342 kept. THE BENCHMARK VERIFIED BEFORE CONCEDING (the no-pleasing-shortcuts discipline, both directions): their export's 90 outlines are ONE congruent shape (perimeter 16.8525 on all 90, no interior holes) = our part 36 within 0.014 in mean after alignment -- like-for-like on part size (the prior session's 5.371 x 3.563 reading was a measurement error; theirs is 5.4621 x 3.8871 vs our 15 parts' 5.457-5.467 x 3.805-3.969); their tightest true-outline gap is 0.2883, LOOSER than our ruled 0.2, so the win is legal -- and a 0.288 channel holds our 0.13 lead with the pierce at standoff, so their layout is compatible with our tooling rules. APPLES-TO-APPLES: our packer on THEIR problem (90 copies of the one shape) measures 45.82 geometry span / 46.27 used_x vs their 42.75 -- the multi-shape kit is NOT the deficit. THE NAMED GAP (the honest concession, its own future build): their lattice is an OBLIQUE 2D form -- Y pitch 3.898 with the 180 sub-column at (+2.40, +2.61), lattice vectors not axis-aligned -- plus an irregular pocketed freeform tail on the right of the sheet (26 X-clusters, mixed orientations); ours is an axis-aligned column interlock with one raise parameter. The invariant to derive next: 2D lattice-vector search (both basis vectors free) per run, plus freeform pocket fill for the remainder -- not a transplant of their layout.
- •Rev2 offsets ARE the beam comps -- every filled Rev2 row packs/posts without a hand-typed materials.json duplicate record — Jordan 2026-09-16, on the CAMP#4 pack refusals (Mild Steel 0.040, then Stainless 0.125 -- both filled Rev2 rows with no materials.json backing): 'I'm lost. My Rev2 spreadsheet should have provided all the information you need' / 'It most certainly does have those beam comps.' RULING + BUILT same turn: the per-row calls he and Aristide already made for MSO7,0.375 (2026-08-31) and MSO7,0.135 ('Refer to the tables I provided', 2026-09-02) are now the STANDING RULE in tables.material() -- a key with no typed materials.json row derives kerf = beam_comp = the Rev2 row's offset (where the three class offsets differ, e.g. the Brass rows, the LARGEST governs: beam_comp is the interference gate and the biggest offset the control runs is what the gate must clear), lead length = the sheet's OWN Lead-in column (Stainless 0.125 runs its 0.125, not the derived 0.150 floor), provenance decided/Jordan/2026-09-16 riding every derived value. TYPED WINS field by field (seed rule): a complete typed row is untouched (MSO7,0.125 keeps its measured .007 over the sheet's .004), a partial row fills ONLY its gap (MSO7,0.060: typed kerf .007 stands, missing beam_comp fills .004 -- previously refused to post). Blank Rev2 cells stay TBD and refuse; an unknown key still refuses MaterialUnknown naming BOTH tables ('no row ... and no filled Rev2 sheet row for it'); the humanTableWords 'Material Not Defined' translation still matches the new wording. The MSO7<->Mild Steel post pairing rides (_REV2_CODE_GROUPS); one machine sheet today -- if a second machine's sheet ever carries a different offset for the same row, that becomes a per-machine materials question, recorded not guessed. Proven: test_rev2_material.py 13 NEW controls + neighbour suites green (matoptions 10 / etch 9 / rules / lead_tab_comp / tooling_doc / drag / nc_warn / matrecord / part_list / dragcheck / sketch / units_confirm / pl_post / pl_tool / pl_deliver / sheetsize). Engine change -- live on dev after this turn's restart; prod picks it up on the auto-deploy, then Jordan packs CAMP#4 with no new rows typed. Etch feedrates, asked in the same message: already recorded 2026-09-06 (etch_default #111 @ 100 in/min in machine_tables.json, tables.etch() serves it; a row's own etch columns win when the workbook grows them) -- the etch STEP consuming it is still its own future brick.
- •True-pocket spill rescue in the part-list packer (Jordan's 7497/7498 one-sheet benchmark beaten, 2026-09-16) record — part_list_nest.pack now runs _pocket_rescue after consolidation: the LAST sheet's parts move into TRUE 2D free pockets of earlier sheets -- concavities between placed outlines the banded full-height-column packer cannot see -- all-or-nothing per spill sheet, looping while whole sheets empty. Search: per rotation variant, x-then-y scan at 0.5 in step, leftmost first (slab-preserving); coarse pass = thinned points vs 1.0 in point grids at the smallest possible pair requirement (no false reject); exact pass per neighbour = cheap containment/conservative rejection FIRST (ray cast on ordered outer polys where known; missing outer = conservative bbox rejection, never nests inside a part), then full-resolution _mind at larger-governs + PAD, leads both directions at max(standoff, pair req). An interior cutout is NEVER a pocket (outer-contour containment test refuses it -- nest-in-hole stays the operator's option, pin nest-pocket-backfill). GATE CLOSED IN THE BUILD: distance-to-outline reads a lead point DEEP INSIDE a neighbour's metal as a large passing distance (the banded slide can never produce that -- contact stops at first touch; free 2D placement can) -- lead points now containment-tested both directions, and bbox-conservatively when no outer exists. Pocket placements carry pocket:true; used_x includes pocket extents past the column frontier (honest slab spend); moves recorded kind:pocket, never silent; the pack's own separate-arithmetic audit judges pocket placements like every other and raises on any miss. Outer outlines ride in from server._pl_build (split_parts.part_groups root outline per distinct part, None fallback = conservative). Proven: test_pl_pocket.py 10 NEW controls (mouth tuck, no-outer conservative, hole-is-not-a-pocket, all-or-nothing, two tucks clear each other at the ruled gap, audit, lead-envelope refusal with the bare part tucking, single-sheet no-op, rotation lock, used_x honesty) + 10 neighbour suites green (part_list 28 / pl_tool 18 / pl_consolidate 13 / pl_spread 32 / pl_post 26 / pl_seq 27 / plhand 25 / pl_deliver 27 / plvariant 23 / partrotate 19). THE REAL KIT: Jordan's 14-part 7497/7498 list (Mild Steel 0.125, GX 10K) packed ONE 120x60 sheet, used X 119.2614 vs his old CAM hand nest's 119.564 (NC 33365) -- 7497 parts 2 and 3 tucked into true pockets at (43.205, 48.705) rot 0 and (70.705, 56.9834) rot 180, audit gap/lead/edge all over ruled. All rules on (no-rule-dropping-to-beat). Pack runtime ~80 s on the real kit -- the busy overlay covers it; speedup is future work if big lists stay slow.
- •Within-sheet FRONTIER TUCK in the part-list packer -- the last partial column moves into the sheet's own pockets (Jordan's 'I say build it', 2026-09-16) record — Born from Jordan's old CAM three-algorithms screenshots (CAMP#4 outers-only, 36x60, 90 parts each): Algorithm 1's remainder trick -- the parts that do not fit the lattice tuck into frontier pockets instead of spending a full column advance of X. Named as the build candidate in the head-to-head thread; Jordan: 'I say build it.' ENGINE part_list_nest._frontier_tuck, called in pack() AFTER _pocket_rescue (rescued pockets are in the clouds the tuck must clear): for each sheet, the last column's parts each seek a true free pocket through the SAME _pkt_find arithmetic as the spill rescue -- one new gate, max_x = the vacated column's base (a used-X ceiling, not a sheet edge, so no bp margin against it), so the whole placed envelope (outline + leads) stays at or left of it and used X shrinks by the vacated advance. The remnant slab GROWS, never spends, so it runs automatically (the auto-never-spends-the-slab rule satisfied, not excepted). All-or-nothing per column with rollback (a partial move never strands the frontier); members try big-first so a full-rhythm column's hardest part fails its one ceiling scan and the attempt aborts cheap -- no count heuristic (on a mixed list a small-part column legitimately holds more parts than a big-part one); cascades while a frontier empties; a pocket already past the new frontier = no gain, skip. Moves recorded kind 'frontier' with the ceiling named, never silent; the one final _audit judges tucked placements exactly like every other. Proven: test_pl_frontier.py 8 NEW controls (tuck into C-mouths shrinks used_x with the ceiling respected on every tucked envelope, all-or-nothing rollback at five-parts-four-mouths, full-rhythm same-part column stands byte-identical, single-column sheet untouched, filler flag + asked/filled survive, lead envelopes ride the tuck with audit lead minima non-negative, bounded _pkt_find proven both ways) + 11 neighbour suites green (part_list 28 / pl_pocket 10 / pl_consolidate 13 / pl_spread 32 / pl_tool 18 / pl_post 26 / pl_seq 27 / plhand 25 / pl_deliver 27 / plvariant 23 / partrotate 19). Real CAMP#4 90-part job re-packed via the server codepath: layout byte-identical at used X 46.3284 -- its alternate-180 columns end EVEN, no remainder to tuck (the honest no-op regression; 66 s pack, tuck cost negligible). The tuck pays when a remainder exists -- the Algorithm 1 case (84 lattice + 6 remainder) and any ragged qty. QUESTION 2026-10-13 (Jordan on CP-6005-04/-03, O33466 dev / 33471 prod -- 8 macros): 'the packer isn't favoring simple nests when we choose regular columns?' -- measured: 'runs' built regular columns, then this tuck (runs on every strategy but free) moved the 7-part frontier column one part at a time to each part's leftmost legal spot, no uniformity term, X scatter 6.8 thou + pitch 3.367-3.465 -> detect_macro_runs honestly 5 arrays; the selector ranks sheets/used X/pocket, never program simplicity. Line-up fix proposed, HELD by Jordan pending Aristide (packer speed). Nothing built. LINE-UP BUILT 2026-10-13 (Aristide: fix (a) go, fix (b) HELD for the one 'what makes a nest better' ruling with Jordan): NEW part_list_nest._tuck_line_up, called by the tuck on FULL packs only (coarse judge untouched, rankings unchanged) -- each same-part same-rotation group of 2+ tucked parts re-seats onto ONE X (the members' own envelope Xs, rightmost first, envelope right edge kept at or left of the vacated column's base so used X never grows) and ONE even 4-decimal pitch (smallest legal inside the group's own measured spacing range; 5-thou coarse scan then 1e-4 refine; stack keeps its bottom Y, else its top), every slot through the same _pkt_ok arithmetic against the sheet and the members already re-seated; no legal candidate = the group stays exactly as tucked; moves kind 'lineup'. Jordan's CP-6005 kit re-packed offline through _pl_build: 7 parts -> X 5.9264 pitch 3.3672, macro arrays 8 -> 4, used X 6.6967 unchanged, audit clean. EXPECTED CHANGE: any full pack whose tuck moved 2+ copies of one part now lines them up (layout + posted NC differ for those jobs); golden corpus has no tucked case -- identity gate green, zero refs changed. NEW test_tuck_lineup 13 + 21 packer suites zero edits (test_pl_consolidate fails IDENTICALLY on the untouched baseline -- stale 'later sheet only' move assertion, pre-existing). Cost: CP-6005 full pack 10.86 -> 11.27s (+0.4s, one-time per full pack); F1 8.43/8.42 -> 8.41/8.39s (repeat 7.74/7.77 -> 7.76/7.77) no cost. Zero dev O-numbers. PIN STAYS OPEN until the speed chat times F1 on :8475 before/after this commit (Aristide's item 4). | CONFIRMED 2026-10-13 (Jordan on dev, re-packed CP-6005: 'This looks good now'). Speed-chat F1 timing on :8475 still owed; pin stays open for it.
- •Tab unification -- every job kind carries the ONE tab strip (stage 1 BUILT 2026-09-16); stage 2 COMPLETE 2026-09-20 -- the selected part rides the tabs: Geometry/Tooling tab clicks OPEN it, sibling strip on the part's drawer, converged sheet-tab clicks land on the list; NOTHING VANISHES 2026-09-20 -- a group member part carries Part list as its FIRST tab, the back chip retired recordmixed — Jordan + Aristide sitting together, 2026-09-16. Aristide's observation on the part-list screen: 'the screen we're looking at is in a "sub-program" with no clear path (crumb trail) back to the main interface' -- correct, and by a design the product outgrew: brick 21 ruled exactly two tabs (Part list + Nest) when the list had nothing else, then posting (29), delivery (30), sequencing (31), spread, the hand editor all landed INSIDE the Nest drawer -- a whole sub-application with a different vocabulary, which is also why Jordan could not find his posted NC. Jordan's ruling ('In my mind, I would think Part List would be the first tab, and we can treat each job the same. If we only have one part, no problem. If we have many parts, also no problem.' -- his Go on the staged plan): one tab strip on every job kind. STAGE 1 BUILT same day (record): a part-list job carries Part list / Geometry / Quote / Tooling / Nest / Post / Deliver -- the sheet programs re-homed from the Nest drawer onto the POST tab (verbatim rows: O-numbers, warnings, downloads, post/re-post), the versioned delivery chain onto the DELIVER tab; the Nest drawer keeps pack/spread/part-order/hand-editor and points to the new homes; Geometry/Quote/Tooling render honest not-wired notes (brick-1 pattern) with NO false pending dots (stagesFor returns empty for them); Post carries a REAL stage record now (run_plpost writes stages.plpost done/flagged, _drop_plpost pops it -- a dropped program never keeps serving a dot; pre-record jobs derive the dot from the living post_doc, never lying pending); deep link #tab=post lands uniformly; canvas shows the sheet scene on Post/Deliver view-only (interactions stay guarded to the Nest tab); topbar names the kind ('Part list -- <name>') and a member job carries an 'in group <name>' crumb chip back to its list (groupChip). Proven: test_pl_post 26 / test_pl_deliver 27 / test_pl_seq 27 green + app/verify_pltabs.js 18 NEW live Playwright checks over the public URL (real 7497/7498 list, single-part regression; the hash-only SPA lesson re-hit in the verify and fixed with fresh pages). STAGE 2 (intent): row-select drives Geometry/Tooling in place -- the list job carries a current-part selection, a picked row renders that part's own record through today's renderers, edits land on the part's own job (one truth, stale rules unchanged). STAGE 3 (intent): one nest door -- the list shape picks the pipeline (one distinct part = true nest with macros, several = part-by-part), recorded ran+source, operator-overridable; the engines converge piece by piece, each merge its own proven brick. Single-part jobs gaining their own one-row Part list tab rides stage 2's design. Related: jobs-home-filing, ui-partlist-brick21, grouped-upload-tray. RETURN CHIP ON EVERY PART-OPEN DOOR + BROWSER BACK/FORWARD AS REAL NAVIGATION, BUILT 2026-09-19 (record; Jordan's live session on the 7497/7498 list -- he opened a part from the canvas right-click menu and had no marked way back, and browser Back left screen and address out of step; his 'Go'): (1) every canvas door that opens a part sets the SAME return chip the Part-list row door does -- the ctx-menu 'Open part detail' and the brick-34 deferred single-click door both route through plOpenPlacement -> KM.openPart with placement context (sheet/index/item/copies over the saved layout, so the isolation variant fork keeps working); the hand-editor drill already did. (2) the hash names the screen (#job=id&tab=k): opening a DIFFERENT job pushes ONE history entry, tab switches and same-job rerenders replace in place (navHash), leaving a job for home pushes; a popstate handler re-runs the hash router, and a Back landing on the stashed part list rides KM.plBack so unsaved draft rows survive the trip; a tab in the hash is honored only when the hash addresses the job being opened, so another job's tab never leaks into a fresh open; our own pushState/replaceState never fire popstate -- no loops. Client-only (app.js). NEW app/verify_partnav.js 15/15 on the real 7497/7498 list (read-only, every door a GET) + pltabs 19/19, ctxmenu 26/26, refusal 16/16, undo 17/17 (fresh scratch) green. STAGE 2 RESHAPED 2026-09-20 (Jordan: 'it would feel natural for the operator to carry that list over to the Geometry tab, and be able to open each from there'; his 'Go'): the Geometry tab of a part list carries the SAME preview-card list the Part list tab renders (one component, never a fork) -- a part list still has no geometry of its own, so opening a row from the Geometry tab lands on that part's own Geometry screen (the open button rides the hash, one history entry, the back chip returns to the list); the earlier 'edit the selected row's part in place' stage-2 wording is superseded by this list-carry shape on his word. SELECTED PART RIDES THE TABS 2026-09-20 (Jordan: "wouldn't it be easier for the operator if when we have the selected part from the Part List up on the canvas, when we go from tab to tab it's already 'open' for them to do modifications?", his 'Go' -- plus his Tooling-tab catch 'Tooling tab already has a nest... I was under the impression that it wouldn't nest until we get to the Nest tab'): the open click is GONE -- on a part list, clicking the Geometry or Tooling tab OPENS the selected part's own job on that screen (KM.openPart rides the tab click, back chip set, edits still auto-update the nest on return); the listed parts ride the part's Geometry/Tooling drawer as a thumbnail SIBLING STRIP (plSibStrip, stash road only -- one click hops parts on the same tab, shared-prefix tail rule via the shared plSharedPrefix helper, unsaved draft rows survive every hop; a part opened cold shows no strip, the group crumb stays the way in); the mirror move -- a converged member's Nest/Post/Deliver tab CLICK goes straight to the list's matching tab (plBack grew a tab landing with the same fit + auto-nest-update rules a tab click runs; the plgoto pointer stays for deep links); the sheet stops drawing on the list's Tooling tab (plPreviewOn grew tooling -- Jordan's catch was the preview-cards gate covering only Part list + Geometry), the Tooling fallback drawer carries the same card list, and the stale 'open the referenced part jobs' wordings on the Heal/QC and Dimension panels now say the new road. Supersedes the open-button-as-the-road form of 2026-09-20 morning on his word; the open buttons stay as working shortcuts. Client-only (app.js/app.css), zero server change. Proven: verify_pltabs REWORKED to the new design 19 -> 24 (tab click lands on the part + chip + strip; the honest notes moved to the deep-link fallback checks) + verify_converge 17 -> 18 (member Post tab CLICK lands on the list's Post) + plreturn 11, partnav 15, plpick 17, fork 24 (dev) + plrefresh 18, refusal 16, oneroad 17, undo 17 (fresh scratch) + settled live walks on the real 7497/7498 list (redirect, 14-sib strip, sibling hop, part Tooling native) and a scratch one-road job (chip 'back to cvsolo', Post click riding plBack onto the list's Post tab, honest pack-first drawer).
NOTHING VANISHES (2026-09-20, Jordan's Geometry_9-20-2 catch -- 'when I select a part from the Part List, and click the Geometry tab, then the Part List is no longer a tab? It's honestly a bit confusing', his 'Go'): a part living on a list keeps the LIST'S OWN STRIP -- tabsFor prepends a Part list tab (first, the list job's own position) on any group-bound member and on any part opened from a list (the plReturn stash road), so the strip reads identically on the list and on the part. The tab click is the way home: the stash road rides KM.plBack('partlist') so unsaved draft rows survive, a cold-opened member opens its group's list plain (one pushState entry). The BACK CHIP RETIRED -- plChip now only removes the element; the tab says the same thing in the same row as every other screen (the stash + plBack machinery stay, the chip was a second voice). stagesFor gives the member's Part list tab NO stages (pure navigation, no dot -- Jobs-home cards unchanged); deep links naming #tab=partlist on a member fall back honestly (openJob + popstate guards). The group crumb and the sibling strip stay. Client-only. Proven: verify_pltabs REWORKED to the design 24/24 (chip checks became first-tab checks; the single-part regression now asserts Part list first exactly when the job is group-bound) + verify_partnav REWORKED 15/15 (both part-open doors assert the leading tab, not the chip) + live walk on a scratch kit list (stash road, cold member open, round trips). verify_plreturn + verify_plvariant still assert the retired chip -- QUEUED for the same design rework, stated honestly. QUEUE CLEARED 2026-09-21 (Jordan's 'Continue'; SUITE FIXES ONLY, zero app/engine change): plreturn REWORKED 10/10 -- the tab road replaces the chip (draft row survives the trip via the leading Part list tab, chip asserted absent everywhere); plvariant REWORKED 10/10 -- the drill waits on the plReturn STASH (the surviving machinery) not the chip element, and the return rides the hash road (location.hash -> the popstate router's KM.plBack branch), stated honestly in the suite: a SKETCH-born member carries no leading Part list tab (tabsFor excludes sketch), the hash/Back navigation is its way home; oneroad REWORKED 17/17 for the extremes-only units ruling -- a routine file sails with no modal (asserted), the confirm path moved to a NEW extreme fixture (400-inch square with $INSUNITS=1 injected -- the old CAM writer declares no units and an undeclared 400 reads as plausible mm; measured), the kit path drops its modal click; multiupload REWORKED 13/13 -- the routine drop path drops its modal wait and asserts no interruption, the extreme single (LARGE_ARCS, measured 122.27in > the 120in table) keeps its door question, and check 6 scoped to THIS run's jobs (the scratch server accumulates jobs across runs -- the global name regex double-counted, fixture pollution never an app defect). verify_units 18 + verify_dwgtray 20 measured ALREADY GREEN -- the queue note was over-broad, recorded. Zero dev O-numbers; progseq untouched. LIST-OPENED PART GAP AUDIT 2026-10-07 (Jordan: parts are only ever opened from a part list -- 'look into any other features that won't appear'): code read, NOT click-tested. Every Geometry/Tooling tool (heal/QC, draw, dims, source mode, isolation, band, right-click, units/rotation/square-up, downloads) reaches a list-opened part unreduced -- the part is its own job; the reductions are on the LIST screen itself (no geometry of its own, deliberate) and Nest/Post/Deliver routing to the list (door convergence, deliberate). Five likely-ACCIDENTAL gaps found: (1) Quote's auto-nest on a member records stages.nest, which flips doorsConverged off and gives the member back its own single-part Nest/Post/Deliver doors; (2) sketch-born members are redirected to the list but get no Part list tab back (tabsFor excludes sketch, doorsConverged doesn't); (3) Split / 'Nest these parts...' on a member gives children no group and re-groups the member into a NEW list silently; (4) the drawer's 'Open ... Nest/Post/Deliver' pointer button and (5) the '^ in group' crumb use plain openJob, dropping unsaved draft rows and leaving a stale plReturn stash. Question: fix which, awaiting Jordan. Nothing built. | JORDAN'S ANSWERS 2026-10-10 (question): 'All parts are list-opened. Make it consistent' -- fix all of (a)-(e). (a) quote born from the Part list tab, agreed; (b) New job -> name -> blank Part list -> 'add new part: blank sketch'; (c) split / Nest these parts PROMPT to create a new job; (d)+(e) tabs are the navigation -- proposed: remove the drawer go-to-list button, crumb becomes a label (or rides the draft-keeping tab road), plus a leave-with-unsaved-rows guard. Nothing built; awaiting go per chunk. | RULING (Jordan, 2026-10-10): 'everything starts with a Part List no matter what' -- EVERY job in EVERY scenario carries the same tabs so the operator never feels he is in a different program; the only differences are role access (sales without Post, laser operator without Quote), consistent per role. | (d)+(e) BUILT 2026-10-10 (record, Jordan's 'Yes' on the plan): the member drawer's 'Open <list>' button (plgoto) RETIRED -- the converged note now says 'Click the <tab> tab above'; the topbar group crumb is a LABEL (span, no click) -- both opened the list cold and dropped unsaved draft rows; the tabs (riding KM.plBack, drafts kept) are the one road. Client-only, no restart. verify_converge REWORKED 18/18 (checks 7-8 now assert no button + label crumb) + partnav 15 + pltabs 24 green; identity gate green; F1 n/a; zero dev O-numbers. Next chunks: (a) quote from the Part list, (b) New job -> blank Part list -> blank sketch part, (c) split/Nest-these-parts prompts a new job, plus a leave-with-unsaved-rows guard (the Jobs-home road can still drop drafts). | LEAVE-WITH-UNSAVED-ROWS PROMPT BUILT 2026-10-10 (record, Jordan "Good idea. Do it."): leaving a part list with draft rows not yet saved now asks -- Save and leave / Leave without saving / Stay -- on the Jobs-home road (brand + job-name click), browser Back/Forward off the list (Stay restores the address), and from a part opened off the list (the stash carries the draft; the Part list tab still brings it home); reload/close gets the browser's own prompt (it cannot offer Save). Dirty = rows (job/qty/rotate/bridge/filler) + fill-even vs the last server copy, marked on every server load/save of the list; Save and leave posts the same /partlist body Save list posts (material/machine from the screen or the stash, else the list's record; no material = refuses, stays). Clean lists leave without a word. Client-only, no restart. NEW app/verify_leave.js 14/14 (scratch) + converge 18 + partnav 15 + pltabs 24 + plreturn 10 green; identity gate green; F1 n/a; zero dev O-numbers. | (a) SCOPED 2026-10-10 (Jordan "Go on (a)"; intent, not yet built): quoting a part list is a real engine piece, not routing -- run_quote is single-part (own review + run_nest). PLAN: list Quote tab prices from the list pack (fresh pack reused; otherwise the job method packs, Cancel offered), firm tier = each distinct part counted from its own review x qty filled, sheets/usage from the pack, same quote.price/rollup; fast tier summed per part; a member Quote tab points at the list like Nest/Post/Deliver so a member quote never records a nest on the member; old member quotes stay as records. Trade: an unpacked list waits for its pack. Also Jordan "Why not both?": the leave prompt PLUS a Save list button that shows on any screen while rows are unsaved -- offered, next. | LIST QUOTE BUILT 2026-10-10 (record; Jordan's go on plan (a) with two refinements -- 'Quotes are going to have to use Nest no matter what... Maybe the Quote tab needs to scoot down... landing after Nest' and 'Choose one style or audition all styles is a choice for them to make'): Quote now sits AFTER Nest on every strip (single part and part list). A part list's Quote prices its OWN packed nest -- server _run_plquote (run_quote branches on source partlist): no pack = plain 400 pointing at the Nest tab (the method stays the operator's pick there, the quote never packs behind their back -- the 'pack with the job's method' half of the plan dropped on his refinement); each distinct part gets an O1 counting program planned the way the pack plans it (list material x machine, the part's own overrides, the list's start/approach defaults), audited, quote.count x copies placed; sheets, size, usage from the pack; ONE quote.price + rollup.compose; members untouched, no program number spent. Fast tier NOT offered on a list (one-file phone-call number, floors each file at one sheet) -- said on screen; this departs from the plan's 'fast tier summed per part'. GET /quote serves stale_pack live (sha over material/machine/sheet/placements) -> 'QUOTE PREDATES THE CURRENT NEST' banner; stale part tooling named. A member's Quote tab converges on the list (note + click lands on the list's Quote) unless it carries its own quote record. 'Save list' chip on any screen while list rows are unsaved (stands down on the Part list tab), same door as the leave prompt. Honest limits: quote has no Cancel (measured 1.2s on 8 parts, 1.4s on a 41-part kit); per-part rows only, no per-part price split. NEW verify_plquote 18/18; pltabs 24 + tabmerge 20 (order expectations updated, intended), converge 18, partnav 15, leave 14, sheetsize green; verify_quote/verify_customer fail on pre-existing staleness (Sept-1 tab counts; delivery needs a post) -- verify_quote's run also wrote test rates into rates.json, restored from git. | LIST-OPENED (b)+(c) NAMED 2026-10-12 (Jordan): (b) = 'Build New Part List for Sketcher' (New job -> name -> blank Part List -> 'add new part: blank sketch') ON THE BUILD LIST, Jordan gives the order when ready -- remind him 2026-10-13 if not given. (c) = 'New Job': Split / 'Nest these parts...' on a listed part asks to create a new job; build later. Neither built. | NEW SKETCH PART ON A LIST BUILT 2026-10-13 (list-opened gap (b) 'Build New Part List for Sketcher', Jordan 'Go on 1'): record -- the Part list drawer gains 'New sketch part...' beside Add from existing jobs: a name prompt (seeded '<list> part N'; cancel creates nothing) makes a blank sketch job, binds it to the list (/group), adds it as a DRAFT row (qty 1, locked, table bridge; Save list stays the record) and opens it on Geometry through openPart so the stash carries every unsaved row; tabsFor no longer excludes sketch -- a sketch-born member (list-made, cold-opened, or opened from a row) carries the leading Part list tab, the way home. Save list with an unapplied sketch row refuses in plain words ('sketch part X has no geometry yet -- open it, draw it on its Sketch screen and press Apply, then save the list'), nothing saved. New job -> name -> blank Part List = the existing home 'New part list' door. NEW app/verify_plsketch.js 17/17 (scratch) + converge 18, leave 14, sketchdraw 17, plvariant 10 (comment unstaled), pltabs 24, partnav 15, plreturn 10, plpick 17 green; identity gate green; F1 n/a (client + one refusal string); zero dev O-numbers. Server refusal wording live after the next dev restart; (c) 'New Job' stays build-later. JOBS-HOME NEW SKETCH RETIRED 2026-10-13 (record; Jordan: 'Remove "New Sketch" from Jobs Home. New Part List first, then New Sketch from that Part List'): the Jobs-home 'New sketch' button + name field and their handler are gone -- a sketch starts only from a part list ('New sketch part...', KM.plNewSketch); existing sketch jobs untouched, server POST api/jobs?sketch=1 stays (the list button rides it). Client-only; verify_sketch now creates its job through the server door (13/13, consumed dev O33467-33468), plsketch 17 + converge 18 + pltabs 24 green, identity gate green, F1 n/a. NEW JOB FROM A LISTED PART BUILT 2026-10-13 (record; list-opened gap (c), Jordan 'Yes, go'): on a part that sits on a list, Split into parts / 'Nest these parts...' now ASK first -- one prompt names the list and says the parts become a NEW job (cancel = nothing happens); unsaved list rows then get the leave prompt (Stay = nothing); on a name the split runs and a new part list holds the parts in one go (identical parts folded as qty via the same partgroups door), only the CHILDREN file under the new job, the parent stays on its old list and that list's rows are untouched (the silent re-group is gone), landing on the new job's Part list tab with the return chip cleared. A part on no list keeps the old road unchanged. Client-only. NEW app/verify_splitjob.js 16/16 (scratch) + plsketch 17, converge 18, pltabs 24, leave 14, partnav 15, split 11 + splitnest 10 (run on scratch) green; identity gate green; F1 n/a; zero dev O-numbers. All five list-opened gaps (a)-(e) now closed.
- •Global controls -- band select, delete, context menu, undo/revert, copy, aim feedback are APPLICATION-WIDE (Jordan 2026-09-16); items 1+2+3+5+6 BUILT 2026-09-18, undo/revert landed under pin global-undo; WINDOW (left-to-right, inside only) vs CROSSING (right-to-left, touching) selection BUILT 2026-10-08 rulingmixed — Born from Jordan's Geometry-tab ask (rubber-band delete a dimensioned preview part): band select existed but was parked inside the Heal/QC panel's armed mode. His ruling: 'These types of functionality should not be limited to one panel, these are global controls that I need.' AGREED GLOBAL SET (his 'agree with all' 2026-09-16): (1) shift-drag band select on every canvas, selecting what the screen shows -- geometry segments on Geometry, features on Tooling, placements on Nest; (2) Delete/Backspace acts on the selection globally (Geometry: recorded delete edits via the standing /healedits door; nest draft: remove placements; Tooling: honest 'nothing to delete'); (3) right-click context menu on anything anywhere (the per-contour right-click ruling generalized); (5) Alt-drag copy extended to the true-nest hand editor (one copy gesture app-wide, the pl-nest form is the reference); (6) the dimension tool's magnet/aim feedback (snap marker + hint chip) extended to every armed click -- Join, Fit Arc, drag-end-to-point, add-feature pick. UNDO/REVERT MODEL (his Illustrator counter -- ~100 undos + revert -- answered with the per-JOB shape; points 5 and 6 AGREED 2026-09-16, point 4 clarified same day: undo of a geometry change DOES affect downstream -- it IS a geometry change, so the standing stale rule fires, downstream judgments drop and re-run, O-numbers kept, delivered files untouched, the toast says so in plain words; non-geometry undos such as a dimension label move touch nothing downstream): one chronological journal PER JOB of every recorded change across all tabs (heal edits, override sets, dim moves, nest layout saves, sequence clicks); Ctrl+Z anywhere undoes the job's last change with a toast naming what+where and a jump link; redo Ctrl+Shift+Z on the same stack; depth ~200, journal persists on the job record (survives reload); REVERT with two anchors -- 'back to fresh upload' (drop every recorded change, pure automated heal) and 'back to delivery vN' (the job-versioning chain is the save history; restores the working state a delivered version shipped with, delivered files immutable forever); NEVER in the stack: deliveries, assigned program numbers, shop tables and rates, customer filing. THE OPERATOR NOTE (Jordan's explicit ask, this pin is its home): no operator accounts exist yet, so two stations working the same job share ONE undo history -- last change is last change, whoever made it. Jordan: 'We'll deal with the operators once we add that as a feature.' When operator accounts land, the undo journal gains per-operator attribution (who made each change, whose change an undo takes back) -- fold that into the operator-accounts build, and this pin carries the context so it is not re-litigated. STATUS: discussion phase ('Let's discuss before you build') -- nothing built; proposed build order awaiting his word: items 1+2 first (his immediate need), then 3, then journal + Ctrl+Z/redo, then revert, then 5+6. ITEMS 1+2 BUILT 2026-09-18 (Aristide '1. Go' on the staged build, docs/staged-2026-09-16-global-controls-build.md): shift-drag band select needs NO armed mode -- on the Geometry scene the gesture starts the armed bandsel's OWN band state (one machinery, never a fork; guards: geometry tab showing healed prims, never a part list, never the sketch preview, never with a Heal/QC or Dimension mode armed -- an armed pick keeps its own gesture; plain drag stays pan, shift is the discriminator), release/draw/Delete/Escape paths accept 'selection exists' instead of 'mode armed' (Delete tab-guarded to the geometry scene so it never acts on a selection the screen is not showing); Tooling and nest-draft shift-bands already global, unchanged. Delete/Backspace global: Geometry = recorded delete_seg rows through the standing /healedits door (one save, per-row removable, engine refusals verbatim); nest hand draft = trims the draft (already live); Tooling = honest no-op toast in plain words ('Nothing to delete here -- Tooling features are the judged cut geometry'). The panel button still arms the mode for discoverability; armed behavior byte-identical. NOTE the undo model here is superseded on scope by pin global-undo (Aristide 2026-09-18: TRUE GLOBAL, one stack crossing jobs, navigate-to-the-spot per step) -- the journal design lands there. Item 3 (context menu) queued next; items 5/6 later sessions per the ruling. ITEM 3 BUILT 2026-09-18 (Aristide 'Go for 1' on the offered queue): RIGHT-CLICK CONTEXT MENU everywhere -- the per-contour right-click ruling generalized. One floating menu; every item calls the SAME function its drawer/panel button calls (one machinery, never a fork), so the menu can never drift from the drawer; the browser's own menu is suppressed ONLY when we have something to show -- empty space keeps it. Scenes: TOOLING/POST features (right-click selects like a left-click but PRESERVES a multi-selection containing the hit, so a banded word still marks as text whole; items: 'Start / pierce here' applies the clicked point through the standard ovApply channel + re-plan, start-anchor corner pick, start-default modal, focus-the-drawer-input items for lead length / tab size / condition class, force/clear comp, treat-as-text, apply-to-all-identical toggle when the engine's record names twins; the Post tab's menu is the one-item door back to Tooling), GEOMETRY healed segments (recorded delete_seg / join / fit_arc heal edits at the clicked point through the standing /healedits door, 'Delete N selected segments' on a live band, remove-dimension on a dim label; an armed mode keeps its click -- the menu offers only the way out, the Escape ladder's own clearing), TRUE-NEST placements (enter the hand editor / click-in-order from the saved layout; inside the editor rotate 90/180, add copy, delete, and group/split/delete on a band selection), PART-LIST placements (open the part's own job, enter the hand editor; in hand mode rotate 90/180, duplicate, remove -- all the bar's own functions). A right-button press never starts a canvas gesture any more (grabs and pans are left-hand; the press belongs to the menu). Armed picks (start pick, corner pick, click-in-order) answer with a single cancel item. Client-only (app/web/app.js + app.css), serves on refresh. Items 5/6 (Alt-drag copy in the true-nest editor; magnet/aim feedback on every armed click) stay queued per the ruling. ITEMS 5+6 BUILT 2026-09-18 (Aristide 'Global control items 5+6'): (5) ALT-DRAG COPY in the true-nest hand editor -- the part-list hand editor's gesture is the reference form: Alt at the GRAB clones the placement first, the copy is its OWN entity (new group id, like Add copy) and rides the cursor alone whatever the move-mode pick says; an Alt-click that never moved keeps its copy in place, and the grab-time snapshot is KEPT so one Undo removes a copy either way; plain grabs byte-identical. GESTURE MOVED, recorded: Alt at the grab used to mean 'drag free, no snap' -- that form is now Alt pressed AFTER the grab (Alt during the move still suppresses the tooling-envelope snap, so a held Alt-copy drags free until released); verify_groupsnap updated to the surviving form. (6) the dimension tool's magnet/aim feedback (snap ring + hint chip, ONE shared chip renderer aimChip so the two surfaces can never drift) extended to every armed Heal/QC click: Join aims at the nearest segment END, Delete and Fit Arc at the nearest point ON the curve the click will address, drag-end-to-point rings the grabbable loose end within the grab's own reach (warns when none; the live end-drag carries the chip too, naming where the drop lands -- its own carrier or the snapped base point), the add-feature pick carries the full corner/centre/edge magnet. Same contract as the dim magnet -- a PICKING aid only, the raw click still goes to the engine whose own nearest-entity arithmetic stays the authority -- EXCEPT the add pick, where no engine snap exists: there the magnet FILLS the typed position fields (what the ring shows is what lands), typed stays the record, Alt places at the raw click. Empty-reach chips warn in plain words; band select with no loose end in reach shows nothing (the band is the gesture). Client-only (app/web/app.js), serves on refresh. Verified: NEW app/verify_gc56.js 25/25 on scratch; neighbours green same run -- nestedit, groupsnap 9/9 (suite gesture update), stampdel, handsafe, healadd 12, bandsel, iso 15/15, undo 17/17 (fresh scratch), globalband 13/13, bandselgeo 13/13, snapdrag 10/10, dimdrag 10/10, dimaim 12/12, dimarm 12/12, ctxmenu 26/26, plhand 18/18. Pre-existing stale, NOT this build (fail identically on the stashed baseline): verify_nestedit2 (free-angle Set + macro-sub expectation, checks 4/10) and verify_groups (drawer serpentine-select timeout) -- queued to unstale. The ruled global set is now fully built; the undo/revert model lives under pin global-undo. SKETCH-SCREEN BAND 2026-09-22 (Aristide picking the offered follow-up, his '1'): shift-drag band select lands on the Sketch screen, no armed mode -- the band selects typed sketch ROWS by their drawn ink (any sampled point of the prim inside the rect, hqSegSamples over sketchSegs, 1:1 with the rows), small shift-drag = shift-click toggle on the nearest prim, selected rows highlight on canvas (warn accent over the preview's own blue) AND in the drawer row list, Delete removes every banded row in ONE recorded save on the sketch door (one undo step, proven against the journal), Escape clears, plain drag stays pan, a live draw chain keeps its own gesture. Client-only (app.js/app.css). Proven NEW app/verify_sketchband.js 10/10 (scratch 8479, real mouse) + sketchdraw 17, sketch 13, globalband 13, bandselgeo 13 zero edits (verify_sketch's own posting fixture consumed dev O33403, stated; progseq committed). REMAINING offered surface: the part-list CARD LIST (a DOM list, its own chunk) -- queued next. CARD-LIST BAND 2026-09-22 (chunk 2 of Aristide's pick, his 'go for chunk 2' -- the LAST unbanded offered surface closed; rubber banding is now global on every offered surface): shift-drag band select lands on the part-list CARD LIST. The list is a DOM list, not a canvas scene, so the band is a document-level overlay div over the drawer: shift-drag with NO armed mode selects every card the rectangle touches (client rects, so it works wherever the drawer is scrolled), a small shift-drag = shift-click toggle on the card under the press, banded cards highlight with the same warn accent the sketch rows carry, Delete removes the banded rows from the DRAFT (the per-row x button's own semantics -- Save list + pack sheets stays the record, honest toast says so), Escape cancels a live band drag then clears the selection, plain click collapses to the single card, and a shift-press on a control inside a card (qty, rotate, bridge, buttons) never starts a band -- controls keep their own clicks. Selection invalidates honestly: row splice, list save and job switch all clear it (shifted indices would lie). Client-only (app.js/app.css), no restart. Proven NEW app/verify_cardband.js 13/13 (scratch 8479, real mouse incl. reload proving Delete never touched the saved list) + pltabs 24, plpick 17, partnav 15, plhand 27 zero edits; zero dev O-numbers, progseq untouched. | BANDS ADD, NEVER REPLACE 2026-10-16 (Jordan: 'When I band-select from any direction, it deselects what I had already selected. This is difficult, not user-friendly'): record -- shift is the band key everywhere, so the band could never tell 'add' from 'start over' and every band replaced the selection. Now every band surface ADDS to what is selected (Geometry, Tooling, Sketch, Source mode, true-nest editor, part-list nest editor, part-list cards), window/crossing rule unchanged; a small shift-click on Geometry toggles the ONE segment under the pointer (it used to clear everything); Escape still clears; the armed Band select tool keeps plain-drag-replaces / shift-adds. Client-only. verify_globalband 14 -> 16 (second band adds 2+1=3; shift-click 3 -> 2; old code fails both) + bandselgeo 14, bandsel ALL OK, sketchband 11, cardband ALL PASS (window checks now clear first -- suite fix for the intended change; cardband caught a real crossing-band double-count in my first cut, fixed before ship), plhand 27, srcfilter 15, srcinsp 18, ctxmenu 26 green; identity gate green; F1 n/a; zero dev O-numbers.
- •PACK PERFORMANCE ON MANY-DISTINCT-PART KITS -- Jordan's 302310-11 pack ran 2100+ seconds; measured cause = the strategy selector judges every candidate with a full coarse pack and nothing amortizes on distinct parts; the three ruled pieces BUILT 2026-09-28 (run-less candidate skip, 3-worker judge fan-out measured 2.63x on Jordan's live 100-distinct-part kit, honest progress line on the busy card); the judge TIME BUDGET stays parked for Aristide's own yes/no; POST CACHE PAIR BUILT 2026-09-28 (heal on the cached road + per-part plan cache, post click 177.7s -> 86s warm, NC bytes identical); PROGRESS NAMES THE STILL-RUNNING CANDIDATE 2026-09-28 (Jordan's 4-of-5 read) recordmixed — QUESTION 2026-09-23 (Jordan's TIME_9-23-1 screenshot on prod 302310-11-1790105482 -- 'Why is this still loading after 2100+ seconds?'; his follow-up: 'I defer to Aristide to answer this; it's out of my wheelhouse'): the pack was genuinely still computing, not hung -- prod API answered fine, no partnest.json written, progseq untouched. MEASURED on dev with his exact 28 source DXFs pulled through the prod API: planning is cheap (all 28 parts heal+plan in ~50s total), the pack is the cost -- the kit is 28 DISTINCT parts, every row qty 1, all quarter rotation = 112 part x orientation variants with ZERO congruent runs to amortize, the worst shape the selector has seen (every benchmark to date was a same-part or few-distinct-part kit). Per-candidate COARSE judge packs alone: free 108.3s (1 sheet, used_x 90.2342), runs / mixed / deep each blew a 120s cap; lattice declines honestly in 0.2s (no runs). select_pack whole ran past 9m50s on dev without finishing; 30-60+ min total is realistic with the winner's full pack + settle refinement on top. Cause mine: the selector judges every candidate by running a full coarse pack and the scan caches (nofit memo, _pkt_pvars) key per part+rotation, so 28 distinct parts amortize nothing. OFFERED FIX (unbuilt, awaiting Aristide's go): skip run-shaped candidates on run-less kits (runs/mixed spending 2+ min each to lose is waste), a time budget on the judge, candidate fan-out across cores (the planner-parallel-fanout pattern), and an honest progress line ('judging strategy 2 of 5') instead of a bare timer. Interim guidance given to Jordan: the server keeps packing even if the tab gives up -- the result lands on the Nest tab when done; a second click starts a SECOND full pack and slows both. GO GIVEN 2026-09-24 (pros/cons laid out for Aristide per piece; Aristide 'We can schedule to run this fix tonight or now. Your call.' deferring timing to Jordan; Jordan: 'Tonight.'): build SCHEDULED for tonight (~22:07 ET one-shot cron on the dev box; this pin is the durable record -- re-arm the cron if the session restarted). RULED SCOPE = the three no-quality-trade pieces only: (1) skip run-shaped candidates on run-less kits, the has-runs test being the strategies' OWN run detector, never a second arithmetic; (2) candidate fan-out across cores -- same arithmetic, ties broken by candidate order never finish order, worker count capped because judge candidates can trigger planning and the planner already forks 3 (planner-parallel-fanout); (3) honest progress line ('judging strategy 2 of 5') instead of a bare spinner. The JUDGE TIME BUDGET is EXPLICITLY PARKED -- the one piece that can trade nest quality for speed (a candidate cut off mid-judge might have been the winner), it awaits Aristide's own yes/no after tonight's build is measured; it may prove unnecessary. BUILT 2026-09-28 (Aristide 'go' -- the scheduled 9-24 one-shot never fired, a session restart dropped it and nobody caught it, owned to Aristide plainly; his go re-issued the build): the three ruled pieces, nest quality untouched by construction -- the winner's FULL pack is byte-identical, the speedup is judge-phase only. (1) RUN-LESS CANDIDATE SKIP: select_pack probes the kit with NEW _kit_has_runs -- probe copies through the pack's own _bp seeding into _form_runs, the strategies' OWN run detector, never a second arithmetic; on a kit with zero congruent-outline runs the 'mixed' candidate is SKIPPED with honest words on its report row ('no congruent-outline run in this kit -- with no runs to form, 'runs' builds the identical greedy columns, judged once') -- 'runs' itself still judges (it IS the greedy column pack) and lattice already declines itself; a forced strategy= pick is NEVER bound by the skip; the skip's honesty is identity-gated in the suite (on a run-less kit pack('runs') == pack('mixed') placement-for-placement). (2) JUDGE FAN-OUT: NEW _judge_candidates forks the per-candidate coarse judges across a fork-Pool of min(3, cores-1) workers (the planner-parallel-fanout pattern -- module-global stash _SEL_STASH, apply_async with completion callbacks), results keyed per candidate so RANKING STAYS CANDIDATE ORDER never finish order; a pool failure falls back serial COUNTED in _SEL_POOL_FAILS, never silent; _SEL_FANOUT=False is the serial gate; parallel-vs-serial whole-report identity proven in the suite; worker count capped at 3 because a judged candidate can trigger planning and the planner already forks 3. (3) HONEST PROGRESS: run_partnest writes packprog.json in the job dir (PLAIN open/json.dump + os.replace, deliberately NOT _save_json -- a progress heartbeat must never ride the undo journal), lines 'planning N listed parts (heal + toolpath per distinct part)', 'judged k of 5', 'full-packing the winner: X'; NEW lock-free GET /api/jobs/<id>/packprog serves the file while the pack POST holds the job lock (GET doors are lock-free by design); the client busy card polls it at 1.5s while a partnest POST is pending and appends the stage line to the busy words; the file is removed in finally so a finished pack leaves nothing behind. MEASURED on Jordan's live wing-99 kit (100 distinct parts qty 1 -- the exact 302310 shape at scale), first 28 rows: judge phase 357.6s serial -> 135.9s fanned = 2.63x, per-candidate results identical; 12-row probe 5.1s -> 3.0s. Proven test_pl_select 22 -> 26 (run-less skip + pack identity, parallel-vs-serial whole-report identity, progress lines serial and pooled, counted pool-failure fallback via monkeypatched get_context, force='mixed' never bound) + NEW app/verify_packprog.js 8/8 (scratch, 12 distinct sketch parts qty 1 = genuinely run-less: busy card speaks the stage line, mixed skipped in the drawer's own words, packprog cleaned up) + live dev door proof (planning line -> judged k of 5 -> full-packing the winner -> file gone) + neighbour suites ZERO edits: test_part_list 37, test_pl_free 42, test_pl_sync 25, test_pl_macro 28 + verify_plsel 20/20, verify_pltabs 24/24; engine restarted healthy; zero dev O-numbers. REMAINING LEVER, still parked for Aristide's own yes/no: the judge TIME BUDGET -- the one piece that can trade nest quality for speed (a candidate cut off mid-judge might have been the winner); the 2.63x may prove it unnecessary. POST CACHE PAIR BUILT 2026-09-28 (same pin, Aristide's numbered go '1. The post cache pair -- route the part-list post's heal through the cached road, big speedup on post clicks'): run_plpost's per-part loop carried its OWN parse/units/heal block -- a raw-heal site on the posting road -- and re-planned every distinct part on every click. Both halves now cached, SERVER-ONLY, engine untouched: (1) the heal rides the ONE cached road every geometry-serving door runs (_job_prims = the identical parse/to_inches/heal arithmetic the loop carried verbatim, plus _HEAL_CACHE; _apply_healedits already carried the intake rotation + the cached edit replay -- byte-identical by construction); (2) NEW _plpost_plan caches the check_drag re-plan per referenced part -- key = the post-edit prims' own fingerprint (the _EDIT_CACHE arithmetic: source, tolerance, units, rotation and the edit replay in one number) + a sha over EVERY other input (recorded overrides, material post key, the Rev2 tooling row which also derives _post_defaults, resolved start/approach defaults); any real change misses and re-plans, a hit returns a DEEP COPY with tuples kept (a json round-trip would silently turn the stats' tuples into lists and a cached click would differ from a cold one), unhashable prim forms re-plan plain never a wrong hit. MEASURED on the 8-part towing fixture (perf-towing-16): post click 177.7s old -> 178s new cold (primes both caches) -> 86s warm = 2.07x; the heal+plan share (~92s) is gone from a warm click, the remaining 86s is the audit+writer (nc-audit-perf-pass territory -- the ratified PyPy trial stays the recorded next step there). NC BYTES PROVEN IDENTICAL old-vs-new on both the cold and the warm click. Proven verify_plpost 14/14 + verify_refusal 16/16 (scratch); CAMP's re-post honestly refuses on the frozen-lead gate (pre-ruling pack), stated. Consumed and stated: subs 132001-132012 (the towing fixture's kept 90001 main posting its subs for the first time) + verify_plpost fixtures dev O33410-33411 + subs 75445-75448; progseq committed. HONEST LIMIT + OFFER: run_pldeliver carries the same raw parse/heal block in its delivery rebuild -- the identical one-line routing is offered, unbuilt (the go named the post). PROGRESS LINE NAMES THE STRAGGLER 2026-09-28 (Jordan's PACKER_9-28-1 screenshot -- 'It seems that it's still getting stuck on 4 of 5 when packing. Am I right?'; his confirm 'Yes, it's been completing it. Just taking the longest on that part'): he read the display right -- the tick fires only when a candidate FINISHES, and the last-started candidate (deep fill, the heaviest) has no heartbeat while it runs, so the longest silence sat exactly on 'judged 4 of 5' and read as stuck. The judge tick now closes over its candidate key and every line lists the UNFINISHED candidates by their roster names' short heads -- 'judged 4 of 5 candidate strategies -- still judging: deep fill' -- so waiting reads as work; the final tick and the full-packing line are unchanged, the serial fallback already named each candidate as it starts. Engine-only (_judge_candidates), zero result change by construction (progress never touches the judge). Proven test_pl_select 26 + verify_packprog 8/8 on the restarted scratch + a direct fanned-path probe printing the full line ladder; zero dev O-numbers. BASELINE FOOTNOTE 2026-09-29: the 357.6s/135.9s numbers were measured on the FIRST 28 ROWS of the wing-99 kit (the commit record says so; summary compressions dropped it). The full 100-item kit's judge cost is dominated by _square_up in coarse judge packs -- measured record on pin pypy-audit-adoption.
- •KERFMASTER-VS-OLD-CAM PART MISMATCH ON 16-240283-100 INNER FIXTURE -- traced to the two programs showing DIFFERENT GEOMETRY, not a KerfMaster render defect; awaiting the exact file the old CAM had open (2026-09-23) question — QUESTION 2026-09-23 (Jordan's side-by-side screenshots -- 'The parts look drastically different. Why did this happen? How can we fix it?'): MEASURED, and KerfMaster is faithful to the file it was given. The dev job (16-240283-100-inner-fixture-1790187621, source.dxf 447,934 bytes, md5 4710446980ed643d717088919d0b8475) was re-parsed INDEPENDENTLY of the app straight from the DXF bytes: 2214 entities (1155 LINE + 1059 ARC), no INSERTs, empty standard blocks, no TEXT (the PARAGON tag is stroked lines), clean EOF -- total extents exactly 110.2578 x 14.2500 in, 9 closed parts, heal fidelity 0.0006 in with 0 jogs, and a pixel-render of the raw bytes matches the app's nest canvas shape for shape (the marks rectangle measures 22.500 x 14.250 = 1.579 aspect; the nest screenshot shows it rotated at 0.627, the expected 0.633). The old CAM screenshot CANNOT be this file: its marks rectangle measures 2.01 aspect (ours 1.579), it carries tall ~3:1 panels and THREE IDENTICAL bump-rail pieces (the dev file has no duplicate parts at all), 11+ pieces where the file holds 9, and the layout spans roughly 90+ in of Y -- a 30 in tall part cannot exist in a file whose entire Y span is 14.25 in. The three identical pieces plus parts hugging the red sheet-edge axes suggest the old CAM view may be a NEST of the order (quantities applied), or a sibling/revision file (DWG vs DXF, INNER vs full fixture). OPEN with Jordan: confirm the exact file the old CAM had open (name, size, date) and whether that view is the raw drawing or the old CAM's own layout; send that exact file to dev and I diff the two byte-for-byte. Nothing to fix in KerfMaster until the source file question is answered.
- •OPEN-CONTOUR/DUPLICATE FORK CROSS-REFERENCE -- Jordan's Cleaner M closed: an open flag a SIMULATED Drop duplicate lines proves away now names the doubled ink and carries the one-click fix on the lens rows and the QC drawer (proof, never proximity) (2026-09-23, built on Jordan's '4. Go') record — QUESTION 2026-09-23 (Jordan's Cleaner_9-23-1 screenshot on prod dws-lh-2-5-logo-tread-448-towing-1790188233 -- 'Can you take a look at this M? It has many toolpaths and appears to be open'): he was right on both counts, MEASURED on his exact prod file pulled to dev. The M (~0.25 in tall text) arrives as ~19 separate 2-point polylines PLUS extra chord segments laid EXACTLY on top of collinear runs (measured 0.0001 in off the fine path) -- at four junctions THREE line-ends meet, the stitcher honestly refuses to guess at a fork, and the letter plans as FOUR features (30-33): two open half-outlines plus the two chords, each with its own toolpath -- the review's own findings (comp on the WRONG SIDE on 30/32/33, pierce clear air 0.0000, tab on sub-drop-through) are the same defect speaking. THE FIX ALREADY EXISTS AND IS PROVEN: qc.find_duplicates flags both M chords (overlap 56%/100%), and heal_edit drop_duplicates on this file drops 3 + trims 8 to unique spans -- open chains 11 -> 2 file-wide, the M box goes 4 -> 0 and the letter closes into one contour; the two remaining opens are 0.2/0.3-thou gaps on another letter (one Join click each). Operator road today: Geometry tab -> Find duplicate lines -> Drop duplicate lines -> re-plan. OFFERED then BUILT same day (Jordan '4. Go'): when an open-contour finding's loose ends sit on a flagged duplicate's junction, the open-contour note NAMES the duplicate and points at the one-click fix ('open because doubled ink forks here -- Drop duplicate lines closes it') -- today the two findings sit in the panel unconnected and the operator has to ask. Honest note stated to Jordan: this text is ~0.25 in tall with 0.02-0.08 in strokes, so tight-pierce warnings survive the fix; treat-as-text / etch may be the right treatment for the small line -- his call. BUILT 2026-09-23: ENGINE qc.link_open_to_duplicates(prims, opens, dups) -- PROOF, not proximity: the one-click fix (heal_edit._drop_duplicates, the exact move the Drop duplicate lines button records) is SIMULATED on a copy and the open flags re-measured; only a flag the drop ACTUALLY clears gains dup_fix=True + the note suffix 'doubled ink forks the contour here: one click of Drop duplicate lines closes it'. Proximity measurably under-counts: a partially covered twin is TRIMMED and the trim dissolves forks whose node no duplicate endpoint touches -- on the Cleaner file endpoint membership finds 6 of the 9 the drop clears; the simulation marks all 9 and leaves the two genuine 0.2/0.3-thou Join gaps untouched. Runs only when both defect kinds coexist (clean files pay nothing); a drop refusal links nothing, never lies. Wired at BOTH surfaces off ONE linker: qc.analyze (review/drawer; summary gains open_from_doubled_ink) and heal_edit.marks('open') (the lens speaks the same words). CLIENT: the QC drawer section says 'N of the open flags are doubled ink forking a contour -- one click of Drop duplicate lines closes them'; the Find open contours lens renders one fork row per flag (navigates like every finding row, warnnav gesture) under a head carrying the REAL one-click button (data-hq=dedup -- the same recorded move, one machinery); genuine gaps never join the list, so the panel never sends Drop at a real gap. PROVEN: NEW test_qc_link.py 15 controls (fork marked, genuine gap untouched, no-dup pass-through, M-shaped 3-end junctions, summary count, lens==review, note is a suffix, marked==exactly-what-the-drop-clears) + NEW app/verify_qclink.js 7/7 live (scratch sketch, doubled-bottom square: drawer note, 2 fork rows, one-click Drop closes the contour, no stale claim after) + Jordan's exact Cleaner file offline: 9 of 11 flags marked, the 2 Join gaps clean + test_healedit 78 / healedit_noop 8 / isoedit 18 / setfillet 23 / sketch 21 / setsize 27 + verify_healqc 14/14, healadd 12/12, drawline 32 green, zero suite edits. Engine restarted; zero dev O-numbers. His prod job needs no migration: the lens computes fresh on every click, so Find open contours on the Cleaner job carries the fork rows as soon as the deploy lands; the drawer note appears on its next re-heal/pipeline run.
- •NESTING STRATEGY SELECTOR -- candidate algorithms judged coarse on the outer toolpath, the measured winner full-packs; every candidate's numbers beside the winner (Jordan's 'Go' 2026-09-16 session 1; session 2 Aristide '6' 2026-09-18: freeform pocket fill; session 3 Aristide '8' 2026-09-18: oblique lattice; session 4 Jordan's beat-my-nest 'Go' 2026-09-20: DEEP FILL -- five candidates) record — BUILT 2026-09-16 (session 1) on Jordan's numbered go ('1. I agree, we need to judge the outer toolpath, not the geometry. 2. I trust your judgement. 3. Perfect. 4. Go.') -- his framing: the old CAM offers three algorithms and the operator trial-and-errors them; ours runs every candidate itself and picks by the measured number, keeping the old CAM's versatility while dropping the labor. ENGINE (part_list_nest): pack() gains strategy= ('runs' = the standing default, congruent runs as their measured regular form; 'mixed' = greedy mixed columns, no run forcing -- the pre-run form, can win material on some kits at the cost of the regular pattern; unknown strategy refuses in honest words) and coarse= (rank-only judge mode: the final separate-arithmetic audit is SKIPPED and the report says coarse -- the layout is never shipped). select_pack() = the shell: every candidate packs COARSE (_coarse_items: fresh dicts, outlines thinned every 2nd point above an 80-point floor -- chord sag stays under RUN_TOL so coarse run grouping matches full, proven by control 11; LEAD/PIERCE points kept WHOLE per Jordan's ruling -- the judge ranks the outer TOOLPATH, never bare geometry), rank = (sheets, total used X, -largest clean free pocket -- the third key added 2026-09-20, pin nest-free-area-product) with FULL ties keeping candidate order so the regular pattern wins a tie (the consistency objective); the WINNER then packs at FULL resolution with every rule and the refusing audit -- a coarse approximation can never ship a layout, only pick which algorithm ships one. report.strategies carries every candidate with its numbers (estimate:true on coarse losers; the winner's numbers are the full pack's own), report.strategy_source names measured vs operator; a candidate that refuses records its words, all-refuse re-raises the first (engine words). SERVER run_partnest: body.strategy = the operator's forced pick for THIS pack (plain-400 on junk naming the candidates; a plain re-pack re-judges -- stated on-screen). UI: 'nesting algorithm' block in the part-list Nest drawer -- per-candidate rows with sheets/used-X and estimated-vs-measured labels, CHOSEN marker, 'pack with this one' button per rejected candidate (aid-the-operator: the pick is one click, recorded source operator). Proven: test_pl_select.py 12 NEW controls (winner report byte-equal to a direct full pack of that strategy, force path, refusal ladder verbatim, coarse thinning honesty incl. lead points whole + run congruence preserved, tie order, all-refuse) + the real CAMP kit probed offline through the server's own _pl_build (no writes -- the live layout and O33342 stand). Stale test_pl_alt control 9 updated same commit (the locked L legitimately measures interlocked since the interlock build). NEXT SESSIONS (the go covers them): the oblique 2D lattice-vector search and the freeform pocket fill join STRATEGIES as candidates -- the Algorithm 3 gap; deeper coarse tuning measured, not assumed. SESSION 2 BUILT 2026-09-18 (Aristide '6' on the standing queue): the FREEFORM POCKET FILL candidate joins STRATEGIES ('free', deliberately LAST so a regular pattern wins any tie) -- every copy drops as a free 2D first-fit placement, leftmost-then-lowest-then-rotations, through the SAME _pkt_find clearance arithmetic the spill rescue and frontier tuck already run (larger-governs bridges on true outlines, lead envelopes both directions at max(standoff, gap), containment tested -- never nests in a hole, that stays the operator's option per pin nest-pocket-backfill); no columns, no runs, so it can win material on irregular kits at the cost of BOTH regular-pattern objectives (breakout consistency, one-value-editable G-code) -- which is why it only ever ships by measurement or the operator's pick. Its filler pass fills open sheets only (never a new sheet); the spill rescue and frontier tuck are skipped by construction, not exception (first-fit already tried every earlier sheet with the same arithmetic and sheets only ever fill, so a rescue scan can never find a spot the placement pass just rejected; the tuck needs columns); used_x honestly reports the widest placed envelope per sheet. Server door and drawer block needed ZERO change -- both are driven by STRATEGIES / report.strategies, the one-machinery rule paying out. Proven: test_pl_select.py 12 -> 16 controls (three candidates in order, free full pack under the separate-arithmetic audit, the ring-and-plug never-in-hole control, force='free' with the others honestly skipped, refusal words name all three) + 13 neighbour suites green (part_list 28 / pl_alt 14 / pl_interlock 12 / pl_pocket 10 / pl_frontier 8 / pl_consolidate 13 / pl_spread 32 / pl_tool 18 / pl_post 26 / pl_seq 27 / pl_sync 23 / plvariant 23 / partrotate 19); the REAL CAMP kit probed offline through the server's own _pl_build, NO writes (the live layout and O33342 stand): runs 1 sheet 44.69 used-X CHOSEN full, free 58.16 estimated, mixed 59.60 estimated -- free honestly beats mixed on this kit and loses to the regular pattern, and the judge now says so in numbers instead of anyone guessing; the third candidate adds ~28 s of coarse judge time on the 90-part kit (stated, never hidden). The session-1 rider landed: NEW app/verify_plsel.js 17/17 LIVE on scratch 8479 (three candidate rows with estimated-vs-measured labels + CHOSEN marker, one-click 'pack with this one' forces free recorded source operator with the skipped candidates saying so on-screen, plain Pack again re-judges back to measurement) + verify_refusal 16/16 + verify_pltabs 18/18. Honest limits: the oblique 2D lattice-vector search stays the remaining candidate (session 3 -- a genuinely different construction, the true-nest double-lattice search generalized to multi-part kits, never a transplant); free's x/y scan cost grows with sheet count, so the shared coarse-scan speedup rides that session too. SESSION 3 BUILT 2026-09-18 (Aristide '8' on the standing queue): the OBLIQUE LATTICE candidate joins STRATEGIES ('lattice', SECOND in candidate order -- it is a regular pattern, so it outranks mixed/free on ties) -- trial_lattice.py's true-nest double-lattice search GENERALIZED to part-list kits, a real generalization never a transplant. It forms the SAME congruent-outline runs as 'runs', then _lattice_form() MEASURES each run's lattice: the cell is one allowed angle or an a/a+180 pair slid to contact; Y pitch py by contact over ALL interacting multiples; column advance vx by contact for each of 8 swept oblique vy values -- every accepted offset proven exact on FULL sampled lead/pierce envelopes (_lat_ok probes the same _pkt grids; _lat_contact scans down then bisects so contact can never tunnel; containment both ways, never-in-hole stands). Cells tile big-run-first as full-height columns, column j at Y-phase (j*vy) mod py, so a verified clearance is inherited by its whole lattice residue class; runless parts, leftovers and fillers drop through the SHARED _pkt_find machinery (fronts per sheet); a kit with NO congruent run refuses in honest words and the selector records the refusal while shipping another winner. Score = material per cell (py*vx/ncell), straight advance wins ties. RIDING IT, the shared coarse-scan speedup for EVERY strategy: _pkt_pvars identity-keyed envelope/thinned-set cache + a per-sheet-data no-fit memo in _pkt_find (sound: a sheet's constraint set only ever grows, rollbacks discard whole data) -- multi-sheet free pack 8.2s -> 3.5s (2.3x), placements proven BYTE-EQUAL warm vs cold, cache invalidates on geometry swap. Server door + drawer: again ZERO change (STRATEGIES/report.strategies drive both). Proven: test_pl_select 16 -> 21 controls (full lattice pack under the separate-arithmetic audit; the HEXAGON kit where lattice STRICTLY beats all three -- 7.38 used-X vs runs 7.81 / free 7.71 / mixed 8.41, advance (3.178, 1.835) = the genuinely oblique close-pack with vy = py/2; no-run refusal recorded + another winner ships; the locked-lone-part honest limit -- cross-part skew gains live in runs' interlock, control 20 pins it; speedup byte-equality + geometry-swap invalidation) + the same 13 neighbour suites green; REAL CAMP kit probed offline via _pl_build NO writes: runs 44.69 used-X stays CHOSEN, lattice 55.91 est honestly beats free 58.16 / mixed 59.60 and loses to runs' interlock on this kit -- the judge says it in numbers; lattice adds ~72 s of coarse judge time on the 90-part kit (stated, never hidden). app/verify_plsel.js updated to FOUR candidates: 17/17 live on scratch 8479 + verify_refusal 16/16 + verify_pltabs 18/18 (both live dev, dev O-numbers consumed). Refusal words name all four candidates. The candidate roster from Jordan's old CAM framing is now COMPLETE: runs, lattice, mixed, free. DEEP FILL joins STRATEGIES 2026-09-20 (session 4; born from Jordan's hand move on his re-packed 26342 nest -- he dragged a column square into the bumper's centre notch: 'Look what I did in a couple of seconds, using my human mind. We want to exceed human nesting potential, right?'; his ruling recalling the selector's own promise: 'you said that we could have many nesting algorithms to meet many scenarios, and beat human nesting capabilities with the added bonus of selecting the best algorithm for the job at hand... I expect you to beat my nest... Go'): strategy 'deep', fourth in candidate order (regular patterns still outrank it on ties; free stays last). The design closes the exact gap his move exposed: the pocket-drop pass (pin nest-free-area-product) judges PER PART and never touches a frozen column, so his sheet-level move was refused BY DESIGN, not missed. _deep_fill runs as the strategy's own pass (coarse judge included -- the pass IS the algorithm, so its estimate carries it): EVERY placement may move, columns may break; each part is offered the lowest legal spot via the same _pkt_find_low clearance arithmetic (max_x = the sheet's used X, so used X never grows); acceptance is judged at SHEET level -- used X shrinks, or the measured clean free rectangle grows, or the plateau clauses (falls at least 0.25 with the pocket held, or pulls left at least 0.25 without rising, pocket held) that unlock joint gains no single move can show. Termination: gravity strictly lowers an envelope top and a left-pull never raises one, cap 256; moves kind 'deepfill', notes carry used-X + a0 -> a1 pocket numbers and say 'columns may break'. Measured on the saddle-kit control: runs leaves the frozen 2+2 column standing, ZERO moves, pocket 1281.2; deep makes 4 deepfill moves, both squares land inside the saddles' notches, pocket 1436.2, used X equal 51.065 -- and the selector CHOOSES deep on measured numbers (runs 1286.6 / lattice 1391.8 / mixed 1281.2 / deep 1436.2). On the BG synthetic repro deep TIES runs exactly (2296.1 both) and runs keeps the full tie -- the regular pattern wins, as ruled. Deep subsumes the pocket drop (same 1436.2 on the stray control). Honest costs: select_pack 141.5s -> 198.2s on the BG kit (the deep coarse candidate, stated never hidden). Honest limits: the selector's estimates decide which algorithm full-packs (the recorded selector design -- a kit whose deep gain only shows in the full pack keeps the regular winner); Jordan's own prod hand layout is unreachable from dev, so the beat is proven on the synthetic control, his 26342 job judges deep on its next Pack again. Proven: test_pl_free.py 31 -> 42 controls (runs-frozen zero moves, deep breaks the column into both notches, pocket beat > +100 sq in, used X equal, audit passes the moved sheet, 5 candidates, deep CHOSEN, refusal words name deep) + test_pl_select 21 (roster edits only) + part_list 28, pl_macro 25, pl_sync 23 zero edits + verify_plsel.js FIVE candidates live on scratch + plrefresh, refusal, pltabs, plhand. Zero dev O-numbers (packs never post). JUDGE CHANGE 2026-09-21 (Jordan's 26342 Fill catch, recorded on pin part-list-nest-columns): coarse judge packs NEVER fill -- the selector ranks every candidate on the ASKED layout; filler extras ride only the winner's full pack, after consolidation and the rescue. JUDGE NOTE 2026-09-21 (the Nest_9-21-3 missing-parts fix, full record on pin nest-free-area-product): coarse judge packs run UNREFINED (refine=False -- no settle-to-contact, no column-continuation) by the selector's own design -- estimates rank the candidates and only the winner's full pack pays true-contact arithmetic; refining the discarded candidates measured ~3x judge time and was gated out. JUDGE SKIPS THE POLISH + REMEMBER THE WINNER 2026-09-30 (Jordan's plate_5 32-distinct kit, twice killed by deploys and 25+ min at 1 of 5 candidates -- 'we need a different approach for the nesting. This will not work as acceptable in the field', his 'Let's fix it'; the perf-target-seconds-everywhere ruling makes the wait a DEFECT): two cuts, zero quality trade on anything that ships. (1) COARSE JUDGE PACKS SKIP _square_up (joining _pocket_drop and _column_join, already judge-skipped) -- the judge's job is a RANKING and the polish was 92% of the measured 6536s wing-99 'runs' judge (bench_judge_profile) spent on layouts that are DISCARDED; strategy 'deep' keeps its own _deep_fill (the pass IS the algorithm), and the winner's full pack runs every pass as ever -- the shipped arithmetic is byte-untouched. Measured on the wing-99 fixture, native gate (bench_out/judge_skip_native.log vs judge_instr_cpython.log): runs 3263.9s -> 235.6s (13.9x), mixed 2698.6s -> 24.4s (110.6x), identical sheets/used_x; deep/free/lattice native timings land in the same log (bench running at record time -- HONEST LIMIT: 'free' never ran the square-up by construction, so its 1040.4s judge and deep's own _deep_fill remain the heaviest candidates; the ruled step-2 compiled/PyPy _pkt loop or the parked judge time budget is the next lever, awaiting a ruling). (2) REMEMBER THE WINNER: NEW pln.judge_fp = sha1 over EVERYTHING the judge reads (items as built incl. lead envelopes, sheet, gap, standoff, candidate roster) at the 4-decimal floor; run_partnest re-uses the recorded judged winner on a plain re-pack of an UNCHANGED list -- partnest.judge {fp, winner, when, source}, reused stamped -- full-packing it straight (seconds), the last audition's numbers kept beside the fresh full pack on the drawer, strategy_source saying 'remembered winner' in honest words; a list edit re-judges BY ITSELF (the fp moves), body.rejudge + the drawer's 're-judge all candidates now' button = the explicit door back to the full audition; an operator-forced pack stays for-this-pack, writes no memo, carries a still-matching one forward. Honest limit: the fp covers the judge's INPUTS, never the engine's own arithmetic -- an engine change rides the old memo until the next list edit or explicit re-judge. Drawer wording updated (supersedes 'Pack again re-judges' on Jordan's word). PROVEN: test_pl_select 26 -> 28 (polish-skip move-kinds control incl. deep's kept _deep_fill; judge_fp floor/sensitivity control) + test_part_list 41 + test_pl_free 42 zero edits + verify_plsel.js reworked to the new recorded behavior 20 -> 24/24 live on scratch (plain re-pack = remembered winner re-used fast, explicit re-judge re-auditions, a qty edit drops the memo). Zero dev O-numbers (packs never post). FORGET DOOR 2026-10-01 (pin pl-nest-methodology, sitting item 3): the winner memo is visible and mortal -- provenance line on the Nest drawer + POST /api/jobs/<id>/plforget pops partnest.judge (memo only, layout/programs/recorded methods untouched; one undo step back). | JUDGE TIME BUDGET RULED 2026-10-12 (Jordan, Aristide present): 'Audition all five' caps at 2 MINUTES; methods finished by then rank and the best wins; the operator may then click CONTINUE on the unfinished ones (his '4 and 5') to see if they beat it -- the design operator's call, never automatic. Not built; awaiting a go. | JUDGE TIME CAP BUILT 2026-10-12 (Jordan 'Build the 2-minute audition cap'): an audition (no recorded method, or re-judge) stops waiting at part_list_nest.JUDGE_CAP_S = 120 s; the best FINISHED candidate wins and full-packs as ever; every unfinished candidate is marked 'unfinished' with its elapsed time, never ranked, never dropped; the cap never fires with zero finished. Fanned path terminates the still-running workers with the pool; serial fallback stops the running candidate at its next cancel check past the cap. The winner keeps its coarse numbers beside the full-pack ones (only when capped). CONTINUE = POST partnest {continue_judge:true}: judges ONLY the unfinished candidates with no cap and ranks them against the finished ones' recorded coarse numbers (select_pack resume=); refuses in plain words when the list/sheet changed or nothing is unfinished. Drawer: unfinished rows + 'judge cap' note + 'Continue judging' button. budget=None byte-identical; forced/recorded/remembered packs never capped; sheet-list entries capped per entry, Continue not offered there (refuses). KM_JUDGE_CAP env = test override only. NEW test_judge_cap 28 + NEW app/verify_judgecap.js 9/9 (scratch, cap 1 s) + test_pl_select 28 / pl_cancel 11 / part_list 41 / verify_plsel 30 zero edits; identity gate green; F1 8.31/7.64, 8.32/7.70 -> 8.32/7.68, 8.32/7.65 no cost; zero dev O-numbers. Dev restart pending (server change). || REPEAT CANDIDATE 2026-10-12 (pin sheet-size-input, run-X-times chunk 1): sixth roster entry 'repeat' (repeated sheet) -- never ranks on the plain key; wins at sheets <= the best plain method, else not_picked with the sheet cost stated; wins if no plain method succeeds. Roster suites edited 5 -> 6 (test_pl_select 28, test_pl_free 42, verify_plsel 30); remembered winners re-audition once (judge_fp changes). Audition timing unchanged (2.2 -> 2.2s, 159.7 -> 159.5s).
- •FREE AREA IS A PRODUCT -- the packer squares up strays, measures every sheet's clean free area (slab + largest on-sheet pocket), and the strategy judge ranks by it on a used-X tie (Jordan's BG-BUMPER ruling 2026-09-20: 'the large empty area in the upper right of the nest could be used for other jobs of the same material ... it would be both logical and efficient to maximize that space'; his 'I want you to make all 3') recordmixed — BUILT 2026-09-20, all three pieces of the offered brick. (1) SQUARE-UP pass in part_list_nest.pack (after rescue/tuck, before _run_remap): stray placements -- any placement NOT in a same-part+rotation left-edge column of two or more -- are pulled left through the SAME _pkt_find clearance arithmetic every pocket move uses, capped at their own envelope's right edge so used X never grows; columns and arrays never move (the consistency objective stands), lattice moves only its pocket drops, and strategy 'free' SKIPS the pass by construction (measured on the 36-pc kit: 0.15 in of gain for 39 s of judge time -- the free packer's drops are already left-greedy; honest limit stated in code). Moves recorded kind 'squareup', one placement per pass, cap 256. (2) MEASURED FREE REPORT: report.free per sheet = the full-height remnant slab (sheet width minus used X, measured from placed ENVELOPES via _wbox -- row bookkeeping overstated after square-up) plus the largest clean rectangle inside the used area (classic left-edge sweep over envelope boxes, floor 1 sq in); used_x itself now measures placed envelopes. (3) THE JUDGE'S THIRD KEY: select_pack ranks (sheets, total used X, -largest free pocket) -- on a used-X tie the candidate leaving the biggest clean pocket wins instead of list order; full ties keep candidate order (consistency narrowed, not retired); every candidate row carries free_pocket beside its numbers, the forced-pick path too. STALENESS HONEST: run_plspread and run_plhand pop report.free before saving (spread moves Y, hand moves anything -- measured pockets would lie); plrefresh keeps placements so free stands (tiny envelope drift accepted, stated). CLIENT: Nest drawer states per sheet the slab WxH and the clean pocket WxH (area) 'usable by another job of this material'; candidate rows carry 'clean pocket N sq in'; judge note names the third key. MEASURED on the BG-BUMPER synthetic repro (one 76-in pinned bumper + 15 small): runs/mixed/free all tie used_x 76.355 -- the old judge picked by list order (a coin toss dressed as a judgment, stated to Jordan); now runs/mixed measure 2667.4 vs free 2161.2 and the pick is a real decision; full pack reports slab 43.64x60 plus pocket 58.15x39.59 = 2302.2 sq in. PROVEN: NEW test_pl_free.py 23 controls (rect arithmetic, BG kit square-up + audit, pocket genuinely empty, columns never move, judge third key end-to-end, forced pick) + test_part_list 28, test_pl_select 21, test_pl_macro 25, test_pl_sync 23 (zero suite edits) + verify_plsel.js 17->20 on scratch. Zero dev O-numbers (packs never post). POCKET DROP added same day (session b; Jordan's circled small parts on the 26342 nest -- 'I circled a couple of small parts that could easily fit between the two large parts', his 'Yes' on the offered build): a fourth piece of the same brick. _pocket_drop runs after the square-up on FULL packs only (the coarse judge ranks the algorithms' own forms, every non-free candidate skips it equally): every stray is offered the LOWEST legal spot on its own sheet via _pkt_find_low (the same _pkt_ok clearance arithmetic scanned y-major at 2x the grid step, its own nofit key; max_x = the sheet's used X so used X can never grow), and the move is accepted when the part lands strictly lower AND the measured clean free rectangle does not shrink -- GRAVITY WITH THE POCKET HELD HARMLESS, not growth per move (measured on the saddle-kit control: two strays stacked left of the pocket buy nothing individually and 155 sq in jointly, so a growth floor deadlocks; the plateau move unlocks the pair). Every accepted move lowers an envelope top by a quarter inch minimum, so the loop terminates; a0 -> a1 pocket numbers ride every move note; frozen columns (same part, same rotation, same left edge, 2+) never move -- proven by control, the saddle column stands while the squares fall into the valley BETWEEN the two large parts (Jordan's picture exactly). Honest limits: concave pockets are reachable only where both parts carry outer polygons (_pkt_ok stays bbox-conservative otherwise -- control: no outer, zero moves, never a guess inside a concave part); an alternate-180 PAIR of 2 reads as two rotation-singletons and may drop (4+ alt members freeze), the square-up's own shipped semantics. Measured: BG synthetic repro 4 pocketdrop moves, pocket 2302.2 -> 2338.1 sq in, used X unchanged 76.355; full-pack cost 25.9s -> 50.7s on that kit stated honestly, select_pack 141.5s unchanged (coarse + free exempt). Proven: test_pl_free.py 23 -> 31 controls (drop into the valley, frozen column stands, pocket grew >= 1400, audit judged the drops, no-outer refusal) + part_list 28, pl_select 21, pl_macro 25, pl_sync 23 (zero suite edits) + verify_plsel 20, plrefresh 18, refusal 16, pltabs 24, plhand 18 live. Zero dev O-numbers. SETTLE TO CONTACT + COLUMN CONTINUATION 2026-09-21 (Jordan's Nest_9-21-3 catch on his prod 44556B_57B_1 pack -- 'Looks to me like we're still missing 3 parts from the far right row. Figure out why, and change the code so it doesn't happen again'): the cause was MINE and twofold. (1) The free-drop scan (_pkt_find/_pkt_find_low) worked on the 0.5in grid step and took the first legal GRID spot, so stacked free drops sat up to a full step above true contact (pitch 5.0 where contact is 4.839). (2) Where a drop interlocks with a placed lattice column the legal x-window is NARROWER than the grid, so the scan missed the uniform column phase entirely and landed copies at drifted phases the grid could reach -- and the drifted neighbours killed the remaining slots DEAD (probed at 0.05in resolution: no rescue pass could ever win them back; the fix must prevent drift, never rescue it). FIX in part_list_nest: NEW _pkt_settle -- every accepted grid spot brackets and bisects down to true contact via the same _lat_contact arithmetic (axes y then x then y, fine step _PSTEP/8, every settled spot re-passes _pkt_ok); NEW column continuation -- every real placement writes a hint (exact x, top y, angle) keyed per part+rotation (_pkt_hkey), and the next copy tries the hint column FIRST, before the nofit memo (deliberate -- nofit records grid-scan failure, the continuation spot is off-grid): fine upward scan to the first legal y, then a bisect of the last fine step down to true contact, so a column continues at its own EXACT x and true pitch (without that bisect the pitch quantized a sixteenth high and the drift re-lost a slot -- measured 59 not 60); a failed continuation memoizes (hintdead, keyed hint + ceiling -- sound, a sheet's constraint set only grows, a new placement writes a new hint). refine= threaded through _pkt_find/_pkt_find_low and every consuming pass (rest-drop, rescue, frontier tuck, square-up, deep fill); pack passes refine=not coarse -- COARSE JUDGE PACKS STAY UNREFINED BY DESIGN (the selector's estimates rank candidates and only the winner's full pack pays true contact; paying it on discarded candidates measured ~3x judge time -- the first cut of this fix did exactly that and was gated same session); refine=False is the old arithmetic exactly, and _pocket_drop + the filler keep refine on (full packs only). Measured on the reproducing kit (his exact items through the server's own _pl_build: qty 50 rotate 180 Fill ticked, Mild Steel 0.04, 120x60 sheet, gap 0.2, standoff 0.15, lattice chosen): 57 -> 60 placed (50 asked + 10 fillers, was +7), the far-right stack a uniform 12-column at one exact x with pitch 4.839 true contact -- exactly the even rows he ruled -- used X 113.5295 vs prod's 114.0285 (slightly better), sheet count unchanged. His old layout's dead gaps stay dead (they were placed drifted); the fix lands on his job's next Pack again after deploy. Proven: test_part_list 37, pl_select 21, pl_macro 25, pl_sync 23, pl_free 42 (6m47 -- back at baseline after the refine gating; ZERO suite edits anywhere) + live verify_plsel 20, plrefresh 18, refusal 16, pltabs 24, plhand 27; dev engine restarted; zero dev O-numbers (packs never post). COLUMN JOIN 2026-09-21 (Jordan's Nest_9-21-s catch on the re-packed 44556B_57B_1 -- 'The upper-right most part appears to be in its own nest, rather than part of the right-most column ... I could see in a nesting algorithm that is designed for irregular nesting, but in this case it seems out of place to me'; Aristide's split-into-chunks instruction, Jordan's 'Go' -- chunk 1 of 4): he was right, and this entry's own 'uniform 12-column' claim above was OVERSTATED -- the shipped pack's far-right stack was 11 in column plus ONE stray at (88.64, 54.653), an inch left and off pitch. CAUSE (mine): the spill rescue places each part at the leftmost legal spot (_pkt_find x-major -- the spend-the-slab-last objective) and that greedy rule has no UNIFORMITY term; high up beside the flipped far column its taper opens a pocket one inch left of the eventual column phase, and the FIRST rescued part took it (no column existed yet -- the continuation hint is written by placements, and the column was born from the SECOND rescued part plus the fillers). FIX (part_list_nest.py): NEW _column_join pass, LAST among the on-sheet passes (the fill pass has built the columns it extends), full packs only, strategy 'free' skipped with the block (uniformity is not freeform's objective): a stray -- not in a same-part same-rotation column of 2+ -- whose envelope OVERLAPS a uniform column's next slot (one pitch above the top or below the bottom; overlap is the 'sitting in the slot, just off-phase' test, so a genuinely separate stray never moves) is offered that slot through the same _pkt_ok clearance arithmetic as every placement, and takes it only when the slot is legal and the envelope right edge stays within the sheet's used X (the slot x IS a placed member's own x, so used X cannot grow); irregular-pitch columns are never extended (no guessing); a thou-level outward escape scan absorbs the settle arithmetic's contact scatter, never a visible drift; on lattice only pocket placements move; moves recorded kind 'coljoin', never silent. MEASURED on the byte-reproducing 44556B kit: exactly 1 coljoin move, (88.64, 54.653) -> (89.64, 54.395), the far-right stack a TRUE uniform 12 (x spread 0.001, pitch 4.839 +/- 0.001), 60 placed and used X 113.5295 unchanged, and the clean free pocket GREW 91.8 -> 108.3 sq in (the stray no longer pokes into the top band -- the free-area product wins too). PROVEN: NEW test_column_join.py 13 controls (repro shape into top and bottom slots, separate stray never moves, irregular pitch never extended, clearance-refused slot stays, part-id and rotation gates, lattice pocket-only gating, successive-slot iteration, filler flag rides) + test_part_list 37 zero edits. CHUNK 2 SEALED 2026-09-21: the long proof battery green on the coljoin change, ZERO suite edits -- test_pl_free 42, test_pl_select 21, test_pl_macro 25, test_pl_sync 23 + live verify_plsel 20/20, verify_plrefresh 18/18, verify_refusal 16/16, verify_pltabs 24/24, verify_plhand 27/27 (the three scratch-instance suites ran against a freshly started scratch_bandsel server -- their first run failed only because that server was not up, an environment fact, not a regression); dev engine restarted and health-checked; post-restart repro smoke reproduces chunk 1 exactly (60 placed, used X 113.5295, pocket 108.3 sq in, far-right a true uniform 12-stack). Zero dev O-numbers. Chunks 3-4 remain on Jordan's same Go: Spread X engine + door, then Spread X on the part-list Nest tab.
- •CLAUDE.md trimmed 2026-09-17 (Aristide 'trim it'): 99 build/fix records moved VERBATIM to docs/brick-history.md; CLAUDE.md 373 KB -> 142 KB, one summary line per record left behind record — Aristide caught the session window filling minutes after a compact; the audit found CLAUDE.md at 373 KB (~56,780 words) -- loaded whole into every session, roughly half the context before the first message. The trim (2026-09-17): the full verbatim records of UI bricks 1-37 and every follow-up build/fix entry (99 entries, ~265 KB) moved to docs/brick-history.md -- nothing edited, nothing dropped, git history holds the original file. CLAUDE.md keeps every standing ruling and rule (Rev2 master source, jobs-home filing ruling, the open work queue, staged briefs) plus ONE ~300-char summary line per moved record pointing at the history file. NEW STANDING DISCIPLINE recorded in CLAUDE.md beside everything-gets-a-pin: a build record lands in THREE places in the same commit -- the pin (authoritative prose), docs/brick-history.md (full verbatim entry, appended), and one summary line in CLAUDE.md. Never write a full record into CLAUDE.md again; never delete history, it moves verbatim.
- •No nested parens in NC comments (Jordan 2026-09-17): a paren inside a comment ends it early on the control -- every operator-typed name is bracket-sanitized at the emit boundary record — RULED AND BUILT 2026-09-17 (Jordan's O33342 header screenshot -- the job name 'CAMP#4 nest 36x60 (circled part removed)' rode into '(PART NAME : ...)' and nested parens: 'you can't put parenthesis inside of parenthesis'; on a Fanuc control the first close-paren ENDS the comment, so this is a machine-facing format error, not cosmetics): emit.nc_txt() turns parens to brackets in free text bound for an NC comment -- applied to part_name and label at the top of write_gcode_macrob (covers the O-line comment, the label line, PART NAME, and every nest sub header) and to pl_post's main label / PART NAME / per-sub part names. Typed header labels (_san_note) and warning text (nc_warn._san) already stripped or bracketed parens -- this closes the remaining door, the operator's own job name. Case and wording otherwise untouched; fixed literal comments unaffected. Proven in test_nc_warn's no-nested-parens control + header/progstyle/matrecord/pl_post suites green.
- •Operator PDF on every part-list delivery -- one letter page per sheet program + one dimensioned print per distinct part record — Jordan, 2026-09-17, third ask ('Again, I need a pdf of the nest/program for the laser operator, and this should be 1 page of standard letter paper'): every part-list delivery carries a PDF the laser operator can hold -- ONE page, standard letter -- showing the nest layout (true outlines, placement->part map per the 2026-08-31 rule) and the program facts (O-numbers main+subs, material/thickness, sheet size, counts, warning summary in the new grouped form). make_prints.py already draws letter nest pages for true-nest deliveries -- reuse its drawing, not a parallel renderer. NOT YET BUILT -- commissioned this turn, next build in the queue; multi-sheet jobs get one page per sheet (each still letter, the one-page promise is per sheet/program). SCOPE EXTENDED 2026-09-17 (Jordan: 'Where can I find the dimensioned printout for each part?' -- honest answer: nowhere in the app yet; dimensioned part prints exist only on the old bespoke board builds via make_prints, and the app's part-list delivery ships packet/customer/NC/DXF with no print PDF): the commissioned PDF therefore follows the standing nest-print ruling (2026-08-26) in full -- the sheet page(s) up front AND one dimensioned print per distinct part at the back, separately paginated, reusing the make_prints drawing machinery; lands with the same build. BUILT 2026-09-17 (Jordan's 'Go'): engine `pl_prints.py` (docstring = design record) renders from the job's own documents and REUSES make_prints' page machinery -- make_prints._part_fig split so part_fig_from_prims(prims,...) is the ONE dimensioned-part-page renderer shared by board builds and the app (never parallel implementations); engine prims convert to make_prints tuples in _mp() (a CW arc becomes the same arc walked CCW -- identical ink). SHEET PAGE per posted program: true-outline nest with the part labelled per contiguous group (make_prints' cluster rule; labels drop the shared filename prefix, noted on the page, so the identifying tail reads), nest X/Y extent dimensioned, O-number + every sub-program call (sub / part / rotation / copies, spill-guarded), material/machine/sheet size, and the GROUPED warning summary QUOTED VERBATIM from the posted NC header via nc_warn_header() -- the print proves what was delivered, never recomputed. BACK PAGES: one dimensioned print per distinct placed part (overall dims, lettered holes, hole table), the 2026-08-26 nest-print ruling. WIRED: run_pldeliver writes {stem}_operator.pdf into every delivery version (packet.json operator_pdf key), zip included; Deliver tab renders an 'operator PDF' button first in the row. Proven: test_pl_deliver 28 controls (new 8b: PDF magic + page count = sheets + distinct placed parts); CAMP v2 delivered through the running app -- 16 pages (1 sheet + 15 parts), 90 placements, O33385 shipped as 33385.nc. FIX same day (Jordan's 'Pdf is not working on my end' -- Chrome 'Failed to load PDF document' on the delivery URL): the delivery-file GET route served every non-html/json/zip file as text/plain, so the browser's PDF viewer refused the (valid) bytes; .pdf now maps to application/pdf in server.py's delivery ctype table. Verified application/pdf end-to-end through dev.kerfmaster.com; file itself was always valid (16 pages). LABELS FIXED 2026-09-21 (Jordan's Pdf_9-21-1 catch on his towing kit -- red text on EVERY part, covering the ink; the rule was one label per unique part per group): the cluster rule joined copies only when their boxes sat under a fixed 1in gap, and his spread layout's same-part gap measured ~1.18in, so every copy became its own 'group' -- contiguity is now judged by the nest itself (make_prints._label_spots: two copies group when NOTHING of another part lies in the rectangle spanning them and the gap stays under one part-size +1in, so a spread column is one group at any gap and a same-shape block past other parts still re-labels), and the label reads BESIDE the part (new make_prints._label_pos: right/left/above/below, first side whose text rectangle covers no part and stays on the sheet, labels already placed count as obstacles; a genuinely full sheet falls back to the old centred-on-the-part form -- covering the OWN part still labels the right part). Both surfaces, one machinery: the operator PDF sheet page and the board nest-print pages. Proven NEW test_label_spots.py 12 controls (towing repro 12 -> 6 labels, foreign-between splits, tight-gap parity, beside picks, full-sheet None) + test_pl_deliver 28/28 (2 pre-existing stale refusal wordings unstaled, suite-fix only) + rendered repro page and build-164 dense-sheet page read visually. 2026-11-17 ~21:10 UTC JORDAN on O33701's sheet page (incoming/1794950194_766705_Program_sheet.PNG): 'I thought we did away with the part #'s being displayed on the nest display?' and 'the total number of each part is what we need on the right column, not how many at each rotation. A human has to be able to read this and make sense of it.' Found: no record of a ruling that removed the names; the last ruling on the sheet page is 2026-09-21 (one label per group, beside the part), and this page breaks it too (each of the 3 rails labelled, big and centred). Right column today = PROGRAM CALLS, one row per sub (part x rotation), names cut at 24 characters, and 'O76011' in monospace reads as '076011'. Proposal sent: 'PARTS ON THIS SHEET', one row per part, total quantity (78836 x6, 77975 x6, the rest x3 = 33), the sub calls moved to the back. Question out on removing names from the drawing. Nothing built. 2026-11-18 ARISTIDE on the same sheet: one name per part (80 copies = 1 name), the current way is messy; asked for a few better ideas -- never cover other parts or features inside parts, only one name per part, callouts if needed, definitely not 2 names per part. Ideas sent (A key letters + legend with totals, B callouts to the margin with leader lines, C one name in free space with a leader as fallback); recommended A with B as the fallback. Waiting on the pick (Aristide + Jordan). Nothing built. 2026-11-18 O128 BUILT on dev (Jordan: 'I like A'): option A. The sheet page now carries ONE red letter per distinct part (A, B, C ... AA after Z), on one copy, placed by a raster of the sheet (pl_prints._letter_layout): a letter only sits on cells with no ink, no other part's metal and no earlier letter -- on its own part's metal first, else free sheet beside the copy; holes are not metal, so a part nested in a hole is never covered by its host's letter. Sizes 8 / 6 / 4.5 pt; if none fits, a callout: the letter above the sheet with a thin line to the copy, shown red in the list. Right column = PARTS ON THIS SHEET: letter, part name (40 chars), total copies on the sheet (x6), and per sheet / all runs on a repeated sheet (x2/6). The sub-program calls moved to a PROGRAM CALLS page after the sheet pages (program, sub, letter, part, rotation, copies). _label_spots/_label_pos untouched (the board printers still use them). G-code unchanged. Checks: NEW test_o128_letters.py 15/15 (one entry per part, letters never on ink or another part, tiny part with no room -> callout, nested part in a hole lettered and not covered, off-sheet neighbour solid, A..Z then AA); test_pl_deliver 28/0 (8b page count now allows the one PROGRAM CALLS page); test_label_spots 12/12; test_pl_sheet_price ALL OK; test_part_prints 6/0. Identity gate green (G-code byte-identical). F1 n/a (first click untouched; operator PDF is delivery only). Operator PDF time on the grill copy (zz-grill-o127, 27 parts): 0.50 / 0.49 s -> 0.80 / 0.70 s. Read by eye: the grill sheet (9 letters, none on ink or another part, totals x3), a repeated 3-run sheet (x2/6), a forced callout. Ramifications: printed PDF only; every new delivery gets the new page; stored deliveries keep their old PDFs (immutable); board printers keep _label_spots. O128 LIVE on dev 2026-11-18 13:33 UTC (Jordan: 'Yes and Yes' -- looks right, restart OK; both inflights 0; restart active + 200). The engine imports pl_prints fresh after the restart; no live delivery run to check it (a delivery would take real program numbers), the in-process grill render is the proof. 2026-11-18 ~15:00 UTC SHIPPED TO MAIN on Jordan's word ('Looks good to go on main'): only O128's pl_prints.py + its tests (test_o128_letters, test_pl_deliver 8b); O124-O127 stay on dev. On the main tree: test_o128_letters ALL PASS, test_pl_deliver 28/0, test_label_spots 12/12, test_pl_sheet_price OK, test_part_prints 6/0, identity gate green; grill render through main's pl_prints identical, 0.81 / 0.73 s.
- •The old CAM Part Settings > Cutting preset -- per-shape-class START POINT defaults (circled), cut direction, tooling switches record — Jordan's screenshot 2026-09-17 (Defaults_9-17-1): the old CAM's Part Settings dialog, Laser CAM > Preset > Cutting, the Start point block circled in red. START POINT is a per-CLASS shop default -- three pickers, 'For outer shapes' / 'For inner shapes' / 'For circles', each setting where a cut starts by default, chosen VISUALLY (diagram: outer default = mid-right of the square, pierce dot outside, lead entering horizontally). Maps onto our recorded pieces: circles = start_clock 4:30 (already a setting destined for Preferences), outers = the lower-right BIAS (Jordan 2026-08-14), inners = today only the lead-aware clear-air chooser -- a distinct operator-settable inner-shape default is the piece our shop profile does not carry. CUT DIRECTION defaults: Outer CW / Inner CCW -- exactly the shop's G41-norm convention (holes CCW, outer CW); the old CAM's own default agrees with our recorded comp convention. SWITCHES: 'Retain all nodes of polyline in profile tooling' (off -- their face of our micro-segment/never-polyline cleanup); 'Convert tangent approach to 90 deg approach' (on) + 'Don't do this conversion at a line-line corner' (on) -- lead-in ANGLE policy defaults, ties to the per-contour lead angle override slot; 'Use marking for all open polylines' (off) -- open contours as etch, ties to mark-vs-cut; 'Suppress machine macro shapes' / 'Break macro shapes if L > 0 x W' (greyed) -- nest-macro knobs, ties to macro-per-orientation/main-program-style. Joins EDIT_TOOLING / Layout Array / Add-Toolpath / Basic-tab as a reference feature set -- record, don't build. Open with Jordan: whether the circled block is an ask (per-class start defaults as shop-profile settings seeding the chooser, biases staying biases) and the exact semantics of each class's picker.
- •Approach defaults -- scoped lead-in record per feature class + the three-way GROUP save both modals share, BUILT (Jordan 2026-09-20) recordmixed — Jordan, 2026-09-20: 'we still need to establish a way for the operator to choose default pierce/lead-ins which we discussed using screenshots from the old CAM' -- then his refinement on the old CAM's save options: 'each change can be saved for that specific material, or for every material listed under that machine. We could do one better... save for the specific material, all the material listed under that machine, or select a group of materials to save the default preference' (his example: inner lead-ins for .500/.625/.750 steel on the GX 10K, 'without affecting their other settings'). His 'Go' on the offered one-brick shape. EXTENDED 2026-09-22 (Jordan on the drawer's lead-in defaults link -- 'it's a dark purple link against the dark background. Is this user-friendly?'): it wasn't -- the drawer carried NO link color rule, so the approach-defaults and start-default 'change...' links rendered in the browser's default visited-purple, near-invisible on the dark theme; that is why the road stayed unseen. One CSS rule now paints every drawer link in the accent role (#drawerbody a:not(.btn) rides var(--accent), obeying the Colours & legend editor; buttons keep their own ink). Client-only, no restart needed.
- •Start-point defaults -- sticky per-class engine anchor + scoped storage + magnet modal, BUILT (Jordan 2026-09-17) record — Jordan, 2026-09-17, on the old CAM Part Settings reference (pin old-cam-part-settings-cutting): 'A nice feature in the old CAM is the ability to set default pierce/lead-in locations... I can click and drag the pierce/lead-in shown, and it magnets to mid-points, quarter-points, and corners, and on circles it magnets to quadrants and 45's. I know we have a default set in your code somewhere, however, we now have evidence that it's not always applied. I'm hoping that writing it up this way that we get a modal for this too. It is going to be more sticky.' THE EVIDENCE, measured on his Detroit Wrecker 6-plate part-list job (prod): all six plates share the identical 17.38x3.25 outline, yet 4 outers pierce at bottom-CENTER and 2 (DE TOWING-PS, RJB-PS) at the bottom-RIGHT end. Structural cause read from emit's chooser: the ruled lower-right preference is the LAST tiebreak of a seven-term score (safety, clean, clear-air band, tipping/crossings ... lowright, right), so thou-level upstream differences between near-identical parts flip the winner -- the default is a tiebreaker today, not an anchor. THE BUILD (three pieces): (1) shop profile gains start_defaults per shape class {outer, inner, circle}, seeded from the recorded rulings (lower-right for shapes, 4:30 for circles), provenance recorded; (2) ENGINE goes sticky -- the class's default position wins OUTRIGHT whenever it passes every safety gate (pierce clear-air, tab-centred-on-flat, never a sharp corner, lead lands in scrap); the ranked hunt runs ONLY when the default spot is unsafe, and any departure is reported per feature (warn never block); safety tiers still outrank the default, the per-feature drag handle still overrides on top -- seed never bind; (3) the MODAL: one picker per class, drag the pierce/lead marker on a sample shape, MAGNET snapping to mid-points, quarter-points and corners -- quadrants + 45s on circles -- exactly the old CAM's gesture; lives with the shop profile (wizard/preferences), per-station theme-style persistence is NOT enough, it is a shop value. Identity risk named: the chooser is inside the planner fan-out hot path -- the build ships only with the parallel-vs-serial identity proofs and the standing fixture suites green. NOT BUILT -- commissioned, next build in the queue. ENGINE SLICE BUILT 2026-09-17 (Jordan's numbered go: wizard-asked BUT overridable per material/machine/job by right-click; 'it's a bias, not a hard coordinate'): emit.write_gcode_macrob(start_defaults={'outer'|'inner'|'circle': clock}) -- class follows the old CAM's split (true circle at any depth = circle, else outer/inner by depth); among candidates passing EVERY safety gate (usable lead, clean tab span, full standoff clear-air, zero held-slug crossings on the outer approach) the winner is PROXIMITY to the preferred bearing first, legacy score only breaking ties -- the anchor, not the last tiebreak; no gated candidate anywhere -> the ranked hunt decides and the contour row reports applied: False; a gate rejecting the nearest-to-preference candidate slides the anchor to the closest SAFE side and reports moved: True (proven on the approach-rapid-over-held-slug case); operator forced starts outrank and never read as departures; circles route the class clock through the quadrant rule. stats['contours'] rows carry start_default + start.source shop:start-default. start_defaults=None keeps every legacy path byte-identical (proven). test_start_defaults.py 13 controls; drag 23 / tooling_doc / robust 50 / plan_perf identity 10 all green. SLICE 2 BUILT same day (Jordan's 'Finish'): STORAGE -- shop.json start_defaults {shop, machine: {<machine>}, material: {<Rev2 key>}} + job.json start_defaults, every entry {clock, source}; RESOLUTION server._sd_resolve, job > material > machine > shop > the recorded rulings (seed outer/inner/circle = 4.5, lower-right / 4:30), the winning scope named per class; DOORS GET/POST /api/jobs/<id>/startdefaults (scope job|material|machine|shop, values {class: clock|null-to-clear}; material/machine key off the assigned review and refuse without one; junk plain-400, record-only -- the NEXT plan/post consumes it, the sheet-size precedent) and POST /api/shop accepts start_defaults (wizard = shop level; scoped overrides PRESERVED across wizard saves -- a larger scope never stomps a narrower one); WIRING -- all ten planning/post sites pass the resolved dict (dragcheck, review, quote count, single post, both postnest forms, _pl_build's per-orientation plans, plpost's per-part check + pl_post.write_sheet_subcall post_kw), so single parts, true nests and part-list sheets all anchor; WIZARD gains 'Where should cuts start?' -- three magnet shapes (square outer, square-hole inner, circle) live in the card; the MAGNET itself: SVG drag, marker snaps to corners, mid-points and quarter-points (quadrants + 45s on circles), stores the snapped CLOCK BEARING (12=top, 4.5=lower-right) -- a bias never a coordinate, side words shown; SCOPED MODAL from the feature drawer's 'start default ... change' row (the right-click dialog): that feature's class magnet + apply-to just-this-job / this-material / this-machine, Save / Clear-this-scope; VERDICTS surfaced -- Part review summary line (per-class default + winning scope + N moved for safety / N departed) and the per-feature row (applied / moved-for-safety / departed -- no safe spot), warn never block. Verified live on 44558B_10 (review verdicts 1 applied / 1 moved / 2 departed on the known narrow slots, post O33338 clean) and the CAMP part list (repack + plpost O33385 re-posted clean through the sd-wired seams); suites green: start_defaults 13, drag 23, tooling_doc, robust 50, plan_perf identity 10. Jordan's six DWS plates converge on the next re-plan: same outline, same gates, one anchor. EXTENDED 2026-09-22 (Jordan's right-click screenshot -- 'I still don't see the magnet we're discussing?'; his 'Go'): the 'Change start default...' context-menu item was GATED on the feature's plan carrying a start_default record, so on a plan from before the per-feature wiring (pre 9-17, e.g. a pack-handed review never re-planned) it silently vanished -- a message never delivered, my defect. The gate is dropped: the item is ALWAYS offered and KM.sdOpen's own guard speaks the honest words on an old plan ('Re-plan the toolpath first -- this plan predates start defaults'). Rides with the drawer-link accent fix (see approach-defaults-group-save) that made the row's 'change...' link visible at all. Proven verify_ctxmenu 26, setsize 17, approach 18, warnnav 10, draghandle 13 -- zero suite edits. EXTENDED 2026-09-22 (Jordan's Approach_Defaults_9-22-3 catch -- circles opened the modal, his freshly re-planned slots toasted 'plan predates start defaults'; his 'Go'): those slots carried his own DRAGGED starts, and the engine's forced-start path deliberately recorded a null verdict ('never report their own choice as a departure'), which the guard could not tell from an old plan -- the wrong words at the wrong situation, my defect. The verdict now RECORDS the outranked default on a forced feature: {class, clock, applied: false, overridden: true} -- the anchor ranking stays dark (NC byte-identical with or without the default on a forced feature, proven), no defaults configured still records None (seam dark). Drawer row says 'outranked by your start override (default <clock>)'; the review summary counts outranked beside moved/departed, never swelling departed; KM.sdOpen OPENS the modal on an overridden feature (the save is per CLASS, not per feature) with an honest note -- 'this feature carries your own start override; the default saved here will not move THIS feature until its override is cleared' -- and the null-verdict old-plan case keeps the re-plan toast. Proven test_start_defaults 13 -> 17 (reworked check 6 honestly: exact overridden dict, byte-identity, no-defaults None; NEW 6b = Jordan's slot via a per-feature dragged start) + NEW app/verify_sdover.js 12/12 live through the real review door (drag, re-plan, drawer words, outranked-never-departed count, modal + note, old-plan toast) + start_anchor/drag/tooling_doc/offset_corner/dcond/robust and verify_ctxmenu 26/draghandle 13/snapdrag 10/approach 18 zero suite edits; engine restarted; zero dev O-numbers, progseq untouched.
- •Warnings: short labels + class chevrons + operator green-flags + one-line NC summary -- BUILT 2026-09-17 (ruled same day) recordmixed — 2026-11-06 JORDAN: the green-flag for QC spots (Geometry checks panel, scrolled down: "x19 - Warning: Duplicate Line ... green-flag all") is "hidden in my opinion, so we will fix that later". Not built. | Jordan, 2026-09-17, verbatim rulings on warning verbosity: (1) SHORT LABELS -- 'right now they are too verbose. When a small hole... forces the lead-in to be too short and the pierce too close to the contour... All I would like to see is: "Warning: Short Lead-in". Now, make these clickable if the operator wants to have the detail, he can click on it and see your verbose warning.' The row shows the CLASS in a few words; the full engine message is one click away, never gone. (2) CLASS CHEVRONS -- 'right now you are already nesting under a chevron identical warnings. However, if they're even one thou different, I get 2 types of warnings. I'd rather see that all lead-ins regardless of the length in error still are compiled in one chevron.' Grouping keys on the warning CLASS (rule + severity), never on the message string's numbers -- one chevron per kind. (3) GREEN-FLAGS -- 'the operator needs to be able to click on the warnings, browse through them, and either individually green-flag them, or globally all of them in the chevron. This will prevent warnings in the gcode.' A green-flag is the operator's recorded sign-off on a finding (who/when once accounts arrive); green-flagged findings post NO callout. Warn never block stands -- the flag silences the callout, never the judgment. (4) ONE-LINE NC SUMMARY -- 'Rethinking about it. What we should do, if the operator chooses to not green-flag the warnings, is to put all warnings for a particular job in one line in the gcode. Example: "this file has 31 warnings"'. This SUPERSEDES the per-spot markers + numbered header list of pin gcode-warning-callouts (his own earlier ruling): un-flagged findings compile to ONE header line with the honest count; the detail lives in the app, not the program. BUILT same day (verification in the detail). EXTENDED 2026-09-18 (Jordan's Yellow-or-Green screenshot -- 'Why still yellow when I dismissed as green?'; Aristide 'Go'): the sign-off now SHOWS at a glance, judgment text unchanged. Flagged findings and fully-flagged chevrons render in the green-flag colour ('all green-flagged' wording); every 'N red / M yellow' count line carries a green suffix with the flagged share (shared sevCounts renderer: review/cutplan/post/postnest banners, part-list nest drawer part rows, sheet-wide judge, hand-layout judge); tab dots STAND DOWN to the done glyph when a flagged stage's every finding is signed off -- stageFindings reads the stage's own loaded document (review/cutplan/post/postnest/plpost/partnest), the tooltip stays honest ('flagged -- all green-flagged'), an unflagged or new finding puts the yellow back, and an unloaded document keeps the recorded status (honesty over guessing). Client-only (app.js/app.css); the NC form is unchanged. Verified live on the dev CAMP part-list: Nest and Post dots stand down with honest tooltips, drawer counts green-suffixed. EXTENDED 2026-09-20 (Jordan's 26342 'Go on both' -- his Q2: 'How can we have short lead-in warnings if I didn't change your default toolpaths? And why aren't they under just one chevron?'): (a) the pierce_standoff class label RENAMED 'Short Lead-in' -> 'Tight Pierce' -- the check is pierce CLEAR-AIR (rules.check_pierce), not lead length; the old name read as if the lead was cut short when the defaults were untouched. Label only; keys, messages and the NC form unchanged. (b) ONE CHEVRON ACROSS THE LIST: on the part-list Nest drawer the per-part plan findings roll into ONE chevron per warning class across ALL listed parts (previously each part's section grouped alone -- five parts with the same physics showed five chevrons). The per-part count lines stay; every row inside names its part (shared-prefix tail rule, full name in the tooltip) and still navigates/green-flags individually; the chevron header's green-flag-all keys on the class exactly as before. Client-only (app.js) + verify_warnnav suite label update. Proven live on the dev CAMP list: 73 findings on 15 parts = ONE Tight Pierce chevron, 73 rows each naming its part; verify_warnnav 10/10, verify_pltool 13/13, verify_pltabs 24/24; zero dev O-numbers consumed. RED VISIBILITY BUILT 2026-10-15 (item 1, Jordan '1. go'): an unflagged RED finding now shows red -- the dot reads '‼' on red (yellow keeps '!'), the whole tab turns red, the drawer stage head and the Jobs-home card dots too (loaded findings decide, green-flagged reds stand down; unloaded falls back to the stage record's red count); the NC header splits the count: (THIS FILE HAS N WARNINGS - R RED Y YELLOW), both counts always present; warn never block, display + comment only. Identity gate: 13 refs rewritten BY INTENT, the ONLY delta is that header line (git diff: 13 lines, nothing else), green after; scoped pass-2 proof still holds on the new header; test_nc_warn 26 (new red-count control) + robust 50 + progstyle 29 + warns 20 + subnum 21 + cl_post updated; browser: mid-plate-1 Tooling tab red, 53 red home dots, verify_warnnav 10 + tabmerge 20; F1 n/a (planning untouched); zero dev O-numbers.
- •Global undo BUILT -- one stack, crosses jobs, navigates to the spot, heavy steps warn and ask record — Jordan, 2026-09-17, answering 'where are the undo controls?' honestly (a true Undo + Ctrl+Z exists only in the manual nest editor; everywhere else the model is recorded edits with per-row remove/clear): 'Undo should be global.' Ruled: one app-wide Undo (button + Ctrl+Z) stepping back the LAST recorded change regardless of which channel it rode in (heal edits, tooling overrides, sequence, start defaults, sheet size, nest edits, green flags...). SCOPE ANSWERED (Aristide, 2026-09-18): 'True global.' -- one journal, one stack; Ctrl+Z steps back the LAST recorded change anywhere, crossing screens and jobs (part detail <-> parent part list included). Cons stated to Aristide and accepted with their mitigations: every undo step NAVIGATES the operator to the spot it happens (Aristide, 2026-09-18: 'Can the undo not bring them to the spot it is happening? For each step?' -- ruled): right job, right tab, zoomed to the feature, the reverted value highlighted, so nobody ever undoes blind -- this supersedes the passive note+jump-link form; a short what-reverted label stays on the spot as confirmation, and a one-click return-to-where-I-was lands after an undo run; heavy inverses (undoing a pack-time edit = re-pack) ride the busy-feedback seam; an undo across the pack boundary may correctly stale-flag the parent or make the stale gate refuse a post; multi-operator rules (laser-side station undoing the CAM seat) land with operator accounts -- ties to the laser-side-station sitting; perceived-order surprise is answered by the named-undo note. Delivered versions stay immutable -- undo walks around them, never through them. HEAVY-UNDO CONFIRMATION (Aristide, 2026-09-18: 'Slow undo's -- Can we do a warning with a confirmation ask?' -- ruled): a quick undo (typed value, flag, label move) stays instant, no prompt; an undo step whose inverse is HEAVY (re-runs a pack or replan) first shows a warning naming what will be reverted and that it takes time, and runs only on confirm -- decline leaves the stack untouched, nothing half-undone. The confirm rides the same busy-feedback seam once accepted. Closes the slow-undo con: Ctrl+Z never nags on cheap steps, never silently stalls on expensive ones. BUILT 2026-09-18 (Aristide 'Go for this'): SERVER -- the journal hangs on the one persistence seam (_save_json + a recorded os.remove): every recorded-edit door (healedits, dims, units, sketch, sheet/vec extract, import rotation, review/tooling, green flags, start defaults, material record, common-line plan, sheet size, nest + all nest edit/seq/spread/restore doors, part list, pack, part rotation, pl seq/spread/hand) snapshots the BYTES of each file it touches, before and after, and a clean 200 journals the deltas as ONE step -- so an inverse is an exact byte restore, never a re-computation that could drift. One journal, one stack (jobs/_undo/, zlib blobs, ruled depth 200), POST /api/undo + /api/redo + read-only GET /api/undo; restores run under the affected jobs' own locks; a new edit forks history and drops redo. Deliveries, program numbers, shop tables, rates and customer filing have no door in the list -- they can never enter the stack. HEAVY steps (review/nest/pack/units/rotation re-runs, or any cross-job entry) answer needs_confirm first and run only on {confirm:true} -- the ruled warn-and-ask; decline touches nothing. CLIENT -- Ctrl+Z anywhere (Ctrl+Shift+Z / Ctrl+Y redo; text fields keep the browser's undo, the manual nest editor's unsaved draft keeps its local stack), topbar arrow buttons, and every step NAVIGATES: hash-deep-link to the job+tab, reload from the restored files, zoom+pulse on the reverted value when the step carries a point, toast naming what reverted, and a one-click 'Return to where I was' chip after the run. Verified live: NEW app/verify_undo.js 17/17 on the scratch instance (cross-job undo lands on the right tab, redo, decline-leaves-stack, heavy confirm, excluded doors, redo-drop, buttons, zero page errors); regressions verify_globalband 13/13 + verify_bandselgeo 13/13 + verify_bandsel 13/13 (nest editor local undo intact) + verify_snapdrag 10/10 + test_pl_sync 23/23. Dev restarted; prod rides the normal deploy.
- •Start ANCHOR constraint -- the customer's exact lead-in spot as a typed RULE (distance from a named corner), re-resolved on every plan; plus drag-handle magnets record — Jordan, 2026-09-17: 'if a customer tells us that for one particular part, they want the lead-in exactly .250" from the bottom right edge, is it possible to enable the operator to input a "constraint" ... that defines this?' His 'Go' covered both pieces on the table: (a) magnet snapping on the canvas drag handle, (b) the typed start constraint. Both BUILT same day.
- •COMPREHENSIVE TABLE EDITOR -- onboarding a new shop's tables + ongoing modifications (Aristide, COMMISSIONED) intent — Aristide, 2026-09-18: 'I want to build a comprehensive table editor we are going to be using when a different shop wants to onboard, as well as modifications we want to make to the tables.'
- •HARDCODED-VALUES AUDIT -- sweep the code for literals that should run through the tables (Aristide, scheduled tonight) intent — Aristide, 2026-09-18: 'Set up a test/audit you are going to run tonight to make sure that there are no other hard coded items that should be running through the table' -- born from the pierce_sub=9011 finding (Rev2 pierce_default/pierce_etch columns ingested 2026-08-24, consumed nowhere).
- •PRE-PIERCE PASS for small holes in thick material -- two-pass program (pierce-only nest, park rapid, (PAUSE) M00, then cut with quick pierces). GO GIVEN -- building intent — Jordan, 2026-09-18, verbatim: 'when we have small holes in thick steel and aluminum, the pierce is too close to the edges of the contour. A practical solution ... we will manually copy and paste our subprogram, and take out all of the cutting gcode, leaving only pierces. We run the complete nest piercing only. We will then put a M00 so that the operator can move the laser head out of the way and grind the material smooth from the pierce craters, then we go back to the original gcode and replace the standard pierces with a quick pierce (like the etch pierce P9019). Then we proceed with cutting, with everything already pierced this results in a clean cut without the slag debris.' His own sketch: 'Gcode will have 2 nests (P9997) with 2 different subprograms, the first of which would be pierce only, and noted for the laser operator that it is pierce only, ending with a M00. Then the second nest would be the complete subprogram with all the contours and etch pierces. Am I on the right track?' | 2026-10-29 (copper-brass-no-etch): Copper and Brass rows have NO quick pierce (pierce_etch N/A, tooling etch_off set). When this pass is built it must refuse on those rows in plain words, never post P9019 there.
- •Part-list <-> part-detail tooling SYNC -- Jordan's a/b/c go BUILT (2026-09-17): pack hands its plan to the child, child edits stale-flag the list, nest preview draws the true cut path; in-place envelope refresh 2026-09-18 -- the stale gate's remedy keeps the layout; refresh redraw fix 2026-09-19 -- the canvas caches rebuild on refresh, so the sheet draws the refreshed toolpath; auto nest update 2026-09-20 -- the stale layout updates itself on arrival, the operator is only stopped by a real decision; UPDATE ANYWAY 2026-09-28 -- the clearance refusal gains the operator's recorded override record — Jordan, 2026-09-17, verbatim: 'Right now, when I look at my Part List tab, I see that tooling has been applied (lead-ins, etc.), but when I click on a part once, it brings me to a detail screen. It isolates this part nicely, however, all the tooling is gone. I even applied all tooling and made a change to see if the applied changes would come back to the part list screen once I exited the detail screen. It did not. We need to talk about this before we build anything.' REFRESH REDRAW FIX 2026-09-19 (Jordan's BG-BUMPER toolpath screenshots -- 'Changes in the individual toolpath vs translating to the nest don't seem to be happening. Am I missing something?'): the in-place envelope refresh updated the server record and S.plnest but never rebuilt the canvas caches -- plToolPath's as-cut Path2D per part x orientation, the dock points and the geometry paths were all built from the PRE-refresh plans, so after Refresh envelopes the sheet kept stroking the OLD toolpath while the pierce dots (drawn fresh from the plan rows each frame) moved; the fix is ONE MACHINERY -- runPlRefresh now runs the same loadPlPaths rebuild a pack runs, covering the Nest-banner click and the one-click Refresh-and-post alike. Client-only (app.js). Proven: verify_plrefresh 16 -> 17 checks (the new check counts the /geometry fetches the rebuild makes) + refusal 16, pltabs 19, pldock 14 green. AUTO NEST UPDATE 2026-09-20 (Jordan's workflow question -- 'is this user-friendly in its current state? If not, how would you propose we solve these workflow details?'; his '4. You are correct / Go' on the numbered proposal): the bookkeeping click is gone -- landing on the part-list Nest or Post tab (tab click, deep link or the return trip from a part edit) with part tooling edited since the pack runs the SAME layout-keeping in-place refresh by itself; placements, hand work, spacing and sequence stay, a quiet note names what moved, one undo step, and per his point-4 confirm a posted program still drops honestly on real drift, O-numbers kept. The operator is interrupted ONLY by the real decision: a moved toolpath that no longer fits the placed layout refuses in plain words naming the colliding placement (server wording reworked -- 'your moved toolpath no longer fits the placed layout'), the persistent refusal banner holding the manual button; a refused auto-run never silently retries (re-armed by a pack, a hand-layout nudge save, a clean update or a job switch -- plAutoKey). WORDING PASS on his point 5: 'Refresh envelopes' retired from the UI -- buttons read Update nest / Update nest and post, toasts read 'Updating the nest with your toolpath changes' / 'Nest updated', the drawer record line reads 'nest updated'; the undo journal keeps its Envelope refresh label (server record, unchanged). Client (app.js) + one server refusal string. Proven: verify_plrefresh reworked to the auto flow 17 -> 18 checks (landing auto-updates with no click; banner checks moved to the refused case) + verify_refusal 16/16 after a design-following rework of its stale-banner check (the landing now auto-clears staleness, so the suite re-stales and renders the banner directly; its first re-stale edit also had to change a CONSUMABLE value -- a moved near point alone normalizes to the same binding and honestly is not stale) + pltabs 19, pldock 14, srcdl 13, plseq 15, undo 17 (fresh scratch) green; dev engine restarted.
UPDATE ANYWAY 2026-09-28 (Jordan's challenge on the refusal -- warn-never-block applied to the nest-update clearance gate; his 'Go on "update anyway"'): the clearance-miss refusal stays the DEFAULT, and the banner now offers the operator's explicit override. ENGINE part_list_nest._audit grows misses= collect mode -- a list gathers EVERY miss as {sheet, ids, msg} with the SAME arithmetic instead of raising on the first, audit runs to completion (adjacencies + worst still returned); default None raises exactly as before, so pack/spread callers are byte-identical. SERVER run_plrefresh body.force: applies the operator's layout EXACTLY as placed, records the override on the refresh record {who: 'typed in the app' (until accounts), date, misses = the measured words}, and turns each miss into a RED pl_clearance_override finding (message leads OPERATOR OVERRIDE with date + the measured numbers) prepended red-first into sheet_findings -- so it rides every surface the judge's own rows ride: drawer chevrons (green-flaggable like any finding, silencing the callout never the judgment), the stage red counts, and the posted NC via the standing per-sheet stage-findings road in run_plpost. The no-force refusal's words now name all three roads (nudge / Pack again / Update anyway with its cost). CLIENT: plForceOffer renders the 'Update anyway' button + honest words under the plrefresh refusal banner on BOTH surfaces (Nest tab + Post tab), wired to runPlRefresh(true); the AUTO-update landing and 'Update nest and post' NEVER force -- only the banner's own click does; forced success toasts the recorded-RED honesty, the nest-updated drawer row states 'OPERATOR OVERRIDE ... applied on your word', CLS_LABEL 'Clearance Override (operator)'. Proven verify_plrefresh 18 -> 27 (offer renders, engine words name the road, layout byte-identical after force, override recorded with measured numbers, RED finding persisted red-first, re-post carries red>=1 + in_file on the override's OWN sheet program, NC warnings line, O-number kept) + test_part_list 37 -> 41 (collect mode: default still raises, both miss kinds collected with sheet/ids/msg, minima returned) + verify_refusal 16 + pltabs 24 green; dev engine + scratch restarted; zero dev O-numbers.
- •Job-level material pick + one-click APPLY TOOLPATHS on the part list -- material stays a fact of the PART, skip-and-name at a different material, the pack's mixed-material gate (Jordan 2026-09-20, 'Go ahead and build 1 to 3'); grouped per-material packing = the parked future road (his 'I'm going to think more about mixing materials') recordmixed — Jordan, 2026-09-20, verbatim: 'From the Part List, it would be nice if the operator can assign the material for the job and tell it to apply toolpaths per the default settings, for all parts on the job. Is this a good idea? If so, is it possible?' -- and on the mixed-material workflow question: 'In my mind, if I needed to group these into different material types, I would have sorted them into different jobs when uploading. This feels right to me... however, I can't say that's going to be true at other shops.' His go: 'Go ahead and build 1 to 3. I'm going to think more about mixing materials. Good to know it's a possibility.' | TOOLING-TAB MATERIAL NOT SEEN BY THE NEST 2026-10-11 (question; Jordan reviewing new parts): assigning material x machine on a list-opened part's Tooling tab plans that part, but the Nest tab does not recognise it -- MEASURED cause: the pack reads ONLY the list's own material (partlist.json material or the request body, server.run_partnest), and the Nest auto-pack likewise waits on the list's material; per-part Tooling reviews never feed it, so a list whose parts were all planned in Tooling still has 'no material'. Proposal offered (not built): when the list has no material and every listed part's review agrees on one material x machine, the list takes it (stated on the drawer, recorded, overridable); parts that disagree keep the existing mixed-material refusal naming them. Awaiting Jordan's go. | ONE PLACE FOR MATERIAL 2026-10-11 (question; Jordan): 'Why have another option to change material type if it's just going to cause a rejection? ... Wouldn't it make more sense to have just ONE place to assign material?' -- proposal 1 (list adopts the parts' agreed material) WITHDRAWN on his word. Proposal recorded, nothing built: since every new job is a part list, material lives in ONE place -- the Part list tab; a list-opened part's Tooling tab SHOWS the list's material read-only with a one-click jump to the Part list, its picker gone; changing the list material re-plans every part through the existing apply road (recorded overrides ride). Open: (1) a part referenced by two lists at different materials (reference-by-default sharing) -- re-plan per list or refuse; (2) old pre-one-road single jobs keep their Tooling picker; (3) the mixed-material refusal disappears for lists by construction, per-material grouped packing stays parked. | JORDAN'S ANSWERS + BUILD PROPOSAL 2026-10-11 (question): (1) a part on two lists at different materials -> (a) each list plans its own copy; the one real case is a customer deliberately cutting the same part in several materials -- he asks for a simple notation. (2) older pre-one-road single jobs keep their Tooling-tab picker ('never utilized'). (3) asks to see the build. PROPOSAL (nothing built): the part keeps ONE geometry + ONE set of operator tooling edits (reference ruling stands) but its PLAN is kept per material (today one review.json, so the last list to pack overwrites the other's hand-off); a list packs/plans at its own material and hands its plan to the part's per-material slot; the mixed-material refusal goes for lists by construction; changing the list material re-plans every part via the plassign road, edits kept; list-opened Tooling tab shows the list material read-only + jump to Part list, loads that material's plan. NOTATION = derived, nothing typed: the part card and the part's Intake row say 'also cut in <material> on <list>'. Open: should his typed tooling edits be shared across materials (proposed) or kept per material. | ONE PLACE FOR MATERIAL BUILT 2026-10-11 (question->record for this chunk; Jordan's '(a) ... If you agree, then build it' + his note that a part needing special treatment can be uploaded/forked as a separate part -- agreed, and the existing 'copy as new part' fork already does that without a re-upload). SERVER: _finish_review keeps every plan PER MATERIAL x MACHINE as reviews/<material>__<machine>.json beside review.json (byte copy, never re-encoded -- a second dump measured +0.7s on F1), review.json stays the latest plan for old readers; skip_if_same checks the per-material copy first so alternating lists never churn; GET /review?material=&machine= serves that material's plan (review.json if same material, else honest {none}); run_partnest's 2026-09-20 mixed-material refusal RETIRED (material_overwrite accepted and ignored); run_plassign no longer skips a part reviewed at another material (each list plans its own copy); NEW GET /plcross derives the notation (on a list: per part, the OTHER lists holding it at a different material; on a part: every list + its material). Operator tooling edits (tooling.json overrides) stay ONE set shared across materials -- Jordan's (a). CLIENT: listMatCtx() = the list's material for a part opened from a list or bound to one; that part's Tooling tab shows material x machine read-only 'from the part list' with a link home, hidden selects carry the list material so Re-plan/auto re-plan/overrides plan at it by construction; review loads at the list material; Part list material picker note 'the one place to assign material' + a change re-plans every listed part via the plassign road (edits kept); skip wording gone; cards carry 'also cut in <material> on <list>' (derived, links to the list); part Intake rows say 'on part lists: ...' + 'cut in N materials'. Older single jobs (no list) keep their own picker. PROVEN NEW test_pl_one_material 18/18 (temp copy of kitflip fixtures: two lists two materials, A's copy byte-untouched by B, per-material GETs, honest none, shared overrides, no churn, refusal gone -- discriminating, the old gate ran before need_method -- notation both ways) + NEW verify_onemat.js 15/15 on scratch (real browser: list material change re-plans, both plans kept, card notation, read-only Tooling tab both lists, Intake row, link home, no page errors) + test_pl_sync 25; identity gate green; F1 first click 8.07/8.06 -> 8.06/8.08s, repeat 7.37/7.36 -> 7.35/7.40 (in-process, caches off) -- no cost. verify_plassign.js RETIRED by this ruling (its skip-and-name + mixed refusal checks test superseded behaviour). Dev restart needed for the server half (coordinated). Zero dev O-numbers.
- •Laser-side operator station -- KerfMaster at the machine, operator edits live in the SYSTEM (Jordan 2026-09-17; sitting scheduled, permissions open) intentmixed — Jordan, 2026-09-17, verbatim: 'In our shop, and this may or may not be the case for others, but I plan to put a laptop or tablet by the laser for the laser operators, with KerfMaster on it, linked together with the rest of the team: sales and cad. This way, if the laser operator wants to make a change to a job, like moving lead-ins, etc., they can do so on the fly. The idea is that the improvements they make to get better gcode also now live in our system versus just living in the laser. This will give us one source of truth when we get a reorder years later for a job. We're not going to execute on this now, but add it to the pin list.' THE IDEA: today the laser operator's fixes (a moved lead-in, a nudged pierce) get typed into the control and die there -- the program in the laser drifts from the program in the archive, and a reorder years later re-cuts the UN-improved version. A station at the machine running the same app closes that loop: the operator's edit rides the job's own override seams (per-feature drag, startdefaults, sequence -- all already recorded consumables) and the re-post becomes a new immutable version on the job chain (job-versioning ruling), so the archive IS what cut. Fits the standing architecture with nothing new invented: one source of truth / three lenses (a tablet is just another renderer over the same engine + JSON state), the two-step flow (programmer vs laser operator are different people -- the reason warnings travel IN the NC), and the jobs-home ruling that the relationship dictates who may put work into production. NOT COMMISSIONED -- Jordan explicitly: record now, execute later. SITTING SCHEDULED (his ask, 2026-09-18): discuss in detail (a) how the laser-operator role enters the flow -- where in the queue model their edits land, what re-posts/re-delivers on an on-the-fly change, how the floor sees 'the program changed under you'; (b) PERMISSIONS around the role -- what a laser operator may touch (their own tooling moves?) vs not (material tables? delivering? prices?), which lands on the operator-accounts thread (per-user attribution 'arrives with operator accounts' is stamped on half the app's records today; windows-installable already inventories mandatory accounts). Open questions, not answers -- nothing here rules the permission model. | ANSWERS 2026-10-12 (Jordan, Aristide present): (a) the laser operator CAN change files -- they look at the G-code and decide on changes; those changes save as a VERSION on top of the file supplied to them, so the design operator at reorder sees what the laser operator changed and takes it into account. (b) Make it VISUALLY CLEAR, especially at reorder time, that a laser-operator version of the order exists. (c) PERMISSIONS: limits differ per shop, so the limitation preferences are asked in the shop's intake wizard. Still intent, not built.
- •Vanished towing posts SOLVED -- stale-plan refusals read as completions after a mid-evening deploy; O33343 posted; refusal banner + one-click Pack-again-and-post BUILT; deploy clobbers prod's progseq (open with Sem) + the undo-journal clobber (2026-09-19, partially fixed) recordmixed — Jordan 2026-09-18: 'I did Post it in the Post tab, and it completed (more than once).' SOLVED same night, forensics over the read-only /api/diag door (shipped 4013c793) plus running the doors directly. CAUSE: his pack ran 2026-09-17 20:34:55; commit e42e0a78 (start-anchor, changes emit's override binding/lead arithmetic) landed 20:41:11 and deployed minutes later; every Post click after that hit the plans_match stale gate -- 'the packed layout predates part DWS-LH-2.5-LOGO-TREAD-BRONX-DS.dxf, bnd 21 pierce moved 0.0039 inch since the pack reserved its envelope' -- a 400 shown only as a transient toast during a ~minute busy overlay, so it read as a completed click with nothing to show. Every trace agrees no towing post ever persisted: pl_onums None (only run_plpost/_drop_plpost write it, NOTHING deletes it), job updated frozen at the pack, .lock mtime 01:32 = his refused retry, the same refusal reproduced live pre-repack. The gate itself is CORRECT (seq-display-is-the-program: a program must match the reserved envelope); the silence is the defect. FIXED LIVE: re-pack + post through the public doors -> O33343, 1 sheet 12 pcs, 69 yellow 0 red, persistence verified by file mtimes + stages + onums. His 9-17 'gcode + PDF' memory = the CAMP 33385 re-post + v2 delivery + operator PDF, all on DEV (the PDF content-type record names dev.kerfmaster.com; dev CAMP mtimes 16:17). OPEN 1 (commissioned on Jordan's next go): refused Post/Deliver persists on the drawer in the warn/red role until resolved, never toast-only, plus one-click 'Pack again and post'. OPEN 2 (escalate to Aristide + Sem): cadmaster/app/progseq.json AND ~1563 old dev job files are TRACKED in git, so every prod deploy overwrites prod's shop program-number sequence with dev's copy (proven byte-identical incl. used_once 33385 which never ran on prod) -- duplicate-number hazard; mitigated 2026-09-18 by advancing dev's file to 33343 to match the handed-out prod number; the real fix moves runtime state out of the mirrored tree WITH a prod-side migration (a naive git rm --cached would delete prod's live sequence file on the next pull and reseed at 33289). Prod-created jobs (towing, CAMP prod) verified untracked -- real customer state never rides the mirror. OPEN 1 CLOSED 2026-09-18 (Aristide '3' on the numbered queue): PERSISTENT REFUSAL BANNER + ONE-CLICK 'PACK AGAIN AND POST', client-only (app/web/app.js). A posting door's plain-400 refusal deliberately records nothing server-side (the job's documents are untouched), so the CLIENT now keeps the record: S.refusals per door (post / postnest / plpost) holding the engine's own words + the clock time, rendered as a red REFUSED banner at the top of that door's drawer section ('nothing was posted; any earlier program stands unchanged', the words in a drawernote beneath) until the door next runs -- an answer carrying a job record (clean or blocked stage, where the recorded block banner takes over) clears it, and a job switch clears all. The single/nest doors also no longer undefine S.job on a plain 400 -- runPost/runPostNest assigned r.job unconditionally, so a refused request used to blank the whole client state. ONE-CLICK: when the refusal's own words say 'Pack again' the banner offers 'Pack again and post' (runPlRepackPost: captures any typed program number BEFORE the pack re-render drops the field, re-packs via the same runPlPack -- one machinery, posts only if the pack landed a clean layout, lands on the Post tab showing the programs); the Nest tab's TOOLING-CHANGED stale banner carries the same button beside Pack again. Sheet 1 keeps its O-number across the one-click (the pl_onums rule). Verified: NEW app/verify_refusal.js 16/16 on scratch 8479 (clean post no banner, refused post persists + survives tab switches, engine words under the banner, one-click offered only when the words say Pack again, packs/posts/lands/keeps the number, Nest stale banner both buttons, single + nest doors via stubbed 400s, S.job survives, clean-run clear, job-switch clear) + neighbours green: pltabs 18/18, plseq 15/15, undo 17/17 on a fresh scratch, busy 14/14. Three suites fail without this build too -- tab-unification staleness, proven: verify_plpost check 10 fails identically on the stashed baseline (program rows moved to the Post tab; baseline also flaked check 5), verify_pldeliver waits for pldeliverbtn on the Nest tab while committed HEAD renders it only on Deliver, verify_partlist checks 1+9 expect the old two-tab strip while HEAD tabsFor ships the ruled seven -- queued to unstale with nestedit2 + groups. OPEN 2 (progseq/job files tracked in git) unchanged, still with Sem. SECOND CLOBBER CASE MEASURED + PARTIALLY FIXED 2026-09-19 (Jordan's 'The call undo failed' on Ctrl+Z over his duplicate Add): the global-undo journal (app/jobs/_undo -- journal.json + 601 blobs) was TRACKED in git, so every deploy overwrote prod's undo journal with dev's -- prod's Ctrl+Z stepped DEV's journal (dev absolute paths, dev blob hashes) and failed. FIX: _undo untracked from the repo and cadmaster/app/jobs/ gitignored WHOLE, so no new runtime file can ride a deploy again; the next deploy clears prod's poisoned journal (the stack restarts empty -- undo works from the operator's next edit; the server tolerates a missing journal by design). STILL OPEN with Sem: progseq.json + ~1563 old dev job files remain tracked (removing them could orphan prod work in those dirs -- prod-side migration required, unchanged). SEM REPORTS RESOLVED 2026-09-29 (via Aristide, 'all resolved' -- the Sem half of open 2): taken as the deploy now preserving prod runtime state. Honest state from dev: not independently verifiable from this box -- prod diag 2026-09-29 shows progseq last=33413 == dev's (the 9-28 deploy still rode dev's file; harmless, dev's number is the higher). Verification = the next deploy cycle: prod's progseq staying put while prod posts advance it proves preservation. The repo-side untracking of progseq.json + the ~1563 old job files stays PARKED until Sem's mechanism is confirmed -- a repo deletion pulled by an unprotected prod checkout could delete prod's own files.
- •FULL job-style unification COMPLETE: stages 1-5 BUILT (picker, fork door, one-road uploads, door convergence, suite migration + door retirement) (2026-09-19) recordmixed — Jordan 2026-09-19: 'we are treating single-part jobs and multi-part jobs like 2 different programs... Is there a logical way to unite these job styles into one, user-friendly, logical workflow?' Measured: seven duplicated server doors (nest/nestseq/nestedit/postnest/delivernest vs partlist/plpack/plpost/pldeliver), two hand editors -- purely historical, bricks 3-9 predate the part list. RULED (Jordan leaning Full, deferring the go; Aristide same day: 'I agree, that is the way to do it. this way you can go back in history right before the fork if necessary, and the history is never lost.'): every job IS a part list; a single-part job = a one-row list with qty. The true-vs-part-by-part ruling survives intact (the list road plans every part before packing, so the one-row case keeps toolpath-first), and the 2026-09-19 macro-runs build posts the true-nest G172+G65P9997 macro form off a uniform layout -- one door, both forms. Old jobs keep opening on their old doors, deliveries immutable; only new uploads take the one road; old doors retire gradually, never deleted. SHARING SEMANTICS RULED (Jordan '4. I agree with your recommendation.'): REFERENCE BY DEFAULT -- the part is the master, an edit to it flags every listing job through the built tooling_fp stale gate; 'copy as new part' is the EXPLICIT fork, never the default (Aristide's history point: the fork preserves pre-fork history forever). STAGE 1 BUILT same turn (record, client-only app.js/app.css): the ADD-EXISTING-PART PICKER -- run_partlist's by-reference door always accepted any healed job; what hid it was the flat unlabeled row dropdown. 'Add from existing jobs...' on the Part list tab opens a modal running the Jobs-home machinery (customer folders, search over part name/id/order reference/program numbers via jobONums), already-listed parts badge 'listed -- row k, qty q' and a second click refuses (edit qty on the row instead); a picked part lands as a DRAFT row (qty 1, rotation locked, table bridge) -- Save list + pack sheets stays the record, and saving still drops a packed layout per the standing stale rule. NEW app/verify_plpick.js 17/17 DRAFT-ONLY on the real 7497/7498 job (a reload proves the saved list on disk untouched; Save never clicked) + pltabs 19, partnav 15, ctxmenu 26 green. STAGE 2 BUILT 2026-09-19 (record; Jordan 'Go for stage 1' -- stage 1 already shipped, read as the staged plan's go): the COPY-AS-NEW-PART FORK DOOR. SERVER run_fork, POST /api/jobs/<id>/fork: the part AS IT STANDS -- source.dxf, geometry.json, review.json, plus healedits/tooling/dims/sketch/cutplan where present -- copied byte-for-byte into a NEW independent job carrying forked_from {job, name, date} provenance; a stage record survives only when its artifact came along (review/cutplan keep their status, nest/quote/post/deliver honestly read pending -- a copied O-number or delivery chain would be a forged record); lineage markers (split/split_from/variant_of) stay with the ORIGINAL, the plvariant door's precedent -- forked_from is the fork's one provenance; refusals in honest words, nothing created (part-list job = 'fork a PART, not the list', missing job 404, blank name, no source geometry), and the original stays byte-untouched always. CLIENT: every picker row carries a quiet 'copy as new part' control (hover-visible, deliberately dimmer than the default reference 'add'; the plain row click stays the reference) -- name prompt seeded '<name> copy', the fork lands as a DRAFT row and the picker shows 'copy of <original>' lineage; cancel at the prompt creates nothing. NEW app/verify_fork.js 24/24 (per-file byte-identity, original job.json byte-unchanged, refusals create nothing, draft-only on the real 7497/7498 job with reload proof, suite scratch jobs removed) + plpick 17, pltabs 19, partnav 15, ctxmenu 26 green; engine restarted. STAGES 3-5 INTENT, in order: (3) single uploads land as one-row part lists (the grouped-upload tray's group shape with one member -- new jobs take the one road); (4) Nest/Post/Deliver converge on the pl doors for new jobs and the true-nest editor retires with them (the standing true-nest snap-rewire offer FOLDS IN here rather than running separately); (5) suite migration + door-retirement records. Each stage its own RECORD commit. STAGE 3 BUILT 2026-09-19 (record; Jordan 'Go for stage 3'): ONE-ROAD UPLOADS, client-only (app.js -- zero server change). A SINGLE upload now rides the grouped-upload tray's group shape with one member: upload -> the first-open units question fires AT the door and the wrap WAITS for its answer (Confirm, flip or Later chain through a one-shot continuation, so a flipped file re-heals BEFORE its parts become rows) -> split behind the scenes (the split door's own 'single part' refusal means the file IS the part; a multi-part kit honestly lands as an N-row list) -> a part-list job named after the file stem, one row per healed part (qty 1, rotation locked, table bridge) -> every member bound to the group -> the LIST opens on its Part list tab. ONE MACHINERY: the tray's stack flow and the single road share the new roadGroup(), and a lone tray card is now a one-member group too (customer filing lands on the LIST). The direct door survives only where the road has nothing to list yet, honestly: a blocked intake (no empty list created), vector art awaiting its stated width, a detected drawing sheet awaiting extraction -- vector and sheet jobs JOIN the road the moment convert/extract lands healed (idempotent via the group guard, a re-convert of a wrapped job never re-wraps); the sales surface keeps its stripped flow. roadGroup also stops listing a detected-but-unextracted drawing sheet as a row (its heal judged the SHEET -- the tray previously listed it silently). Old jobs byte-untouched; only new uploads take the road, per the ruling. NEW app/verify_oneroad.js 17/17 on the scratch instance (units at the door both paths incl. the confirm-chains-into-wrap case, 2-part kit -> 2-row list with split_from provenance and the file job bound but never a row, blocked file keeps the direct door with no empty list, several files still open the tray with nothing uploaded); verify_multiupload REWRITTEN 12/12 (it had been stale on the pre-tray batch toast since the 2026-09-14 tray build) + verify_upload_formats updated 10/10 (STEP and converted-AI one-road expectations, conversion note asserted on the part's own drawer) + tray 17, plpick 17, pltabs 19, partnav 15 green. Stages 4-5 remain: door convergence (snap-rewire folds in), suite migration + door-retirement records. STAGE 4 BUILT 2026-09-19 (Jordan 'Go on stage 4') -- DOOR CONVERGENCE, client-only routing, zero server change (server doors stay). A job bound into a group IS a row on a part list (run_group enforces group.id = a part-list job), so its own true-nest doors stop being OFFERED: the member's Nest / Post / Deliver tabs stay on the strip but render a pointer at the list ('this part is a row on X' in honest words per tab) with a one-click open that lands on the list's MATCHING tab (partnest/post/deliver -- the hash names the screen, the job change is one history entry, browser Back returns to the member); their stage dots drop (stagesFor returns [] -- the LIST carries the sheet stages' dots, Jobs-home cards included). Two honest exceptions behind ONE gate (doorsConverged, a pure function of the job doc so drawer and home cards cannot disagree): a job with NO group (old jobs, picker-referenced parts) keeps every door byte-identical, and a member whose nest/post/postnest/deliver/delivernest stage stands beyond pending keeps its doors too -- recorded work (and its immutable deliveries) is never orphaned; the server seeds every stage key pending, so the test is STATUS, never key presence (even a blocked refusal is a record the operator must keep seeing). Geometry and Tooling on the member stay untouched -- per-part work is the point of opening a row. The standing true-nest hand-editor snap-rewire offer FOLDS IN by retirement: new jobs never reach that editor (the one road's pl hand editor carries the toolpath dock), old jobs keep the box-envelope snap as a legacy surface -- the rewire will not be built. NEW app/verify_converge.js 17/17 on the scratch instance (fresh member: three pointer tabs, no dots, landing + Back; ungrouped job keeps Run nest; a job group-bound AFTER a real review+nest run keeps its doors with the done dot; the list's own pack door intact) + oneroad 17, multiupload 12, upload_formats 10, tray 17, plpick 17, pltabs 19, partnav 15 green. Stage 5 remains: suite migration + door-retirement records. STAGE 5 BUILT 2026-09-19 (Jordan's 'Go on stage 5' -- suite migration + door-retirement records; the pin's plan is COMPLETE, stages 1-5). THE AUDIT FINDING: every old true-nest suite creates its jobs by direct API POST (api/jobs?sketch=1 or a raw DXF body), and the one road is CLIENT-ONLY at the upload door -- so those suites were never on the road by construction; their jobs stay ungrouped, doorsConverged stays false, and every door renders byte-identical. ZERO app or engine change in this stage; one-road coverage lives in the five new suites (oneroad 17, converge 17, tray 17, multiupload 12, upload_formats 10). THE UNSTALE PASS (suite fixes only; every failure PROVEN pre-existing fixture/expectation staleness from engine-era drift since the suites were written Sep 1-7): (a) delivered-NC warning wording has two eras -- immutable old versions carry (CONTAINS N WARNINGS), new posts (THIS FILE HAS N WARNINGS); verify_deliver + verify_delivernest accept either. (b) the postnest engine now emits per-column macro arrays, serpentine part order and bare {onum}.nc delivery filenames -- verify_postnest (structural array checks, G65 count = arrays length), verify_nestseq, verify_multisheet updated; nav209's dropped nest.json re-posted THROUGH THE DOORS first (qty 196 alt_flip, O33292 kept, subs 75292/75293). (c) version dirs pad to three digits -- v00${v} broke at v010 (verify_deliver). (d) the brick-13 tour card overlays a fresh Playwright profile's canvas and eats clicks, and raw legacy tab names bypass the merged-tab alias -- verify_seq gets km_tour_done + tabAlias. (e) nav209's review now plans CLEAN -- the start-defaults + lead-aim work cleared its old clear-air findings -- so verify_warnnav's warning phases move to ex2-dirty (4 yellow + 2 red) and expand the green-flags chevrons before visibility waits. (f) contour IDS are plan-order indices and RENUMBER on every re-plan; the override channel's own key is the centroid -- verify_tab now tracks the edited feature by c.at (the verify_propagate byAt pattern), re-selects by current id per phase, and waits on the busy seam instead of findrows; two 0.05 tab-override leftovers this class deposited on nav209 were cleared through clearOv (the outer's recorded 0.03 operator tab stands -- recorded work is never deleted on suspicion). (g) findrows() now folds ONE chevron per warning CLASS (rule+severity, Jordan's ruling) and rows show short class labels with the verbose message on the fvTog detail link -- verify_findnest's synthetic findings carry the rule field and expect x8-in-one-chevron; the detail text is asserted URL-decoded off the link. (h) verify_onum made self-sufficient (posts 9501 explicit, restores the kept 33292 via use_once). FULL BATTERY GREEN: postnest 12, nestseq 17, multisheet 15, seq, onum 6, deliver 12, delivernest 13, warnnav 10, tab 11, findnest 8, healqc 14, partlist 14, seqbadge 11, gseq, handsafe, stampdel, groupsnap 9, homedrag 14, traverse 10, draghandle 13, plpost 14, pldeliver 14, pltabs 19, nestedit, nestedit2, groups, units 18, sheetsize -- kept numbers preserved (33291 single, 33292 nest). DOOR-RETIREMENT RECORD: for NEW uploads the true-nest doors are unreachable from the UI -- the one road wraps every upload into a part-list group and door convergence points members at their list; the direct door survives only where nothing can be listed yet (blocked intake, vector awaiting stated width, detected drawing sheet) and those join the road when convert/extract lands healed. The true-nest hand editor is retired for new jobs (the pl editor carries the toolpath dock). The SERVER doors stay, deliberately: old jobs, recorded work and API callers keep them byte-identical -- retirement is a UI fact, never a server amputation.
- •PERF DEFECT CLOSURE PLAN -- the five measured violations of perf-target-seconds-everywhere get a documented one-by-one execution plan with frozen fixtures, standing gates, per-gap levers, anticipated testing and a pivot protocol; docs/perf-closure-plan.md is the execution record (Aristide, 2026-10-01 -- 'one by one, we need to close these gaps') -- NAMED PROJECT SPEED (Aristide, 2026-10-01) intent — COMMISSIONED 2026-10-01 (Aristide: 'I want to only focus on these next. one by one, we need to close these gaps. take your time, and come up with a plan of execution, that can be documented so we do not deviate from it, even if we have to sidestep. the plan should also anticipate how to test it, and be flexible enough to pivot if we do run into a wall.'). THE FIVE DEFECTS, baseline of record: D1 post click 67.2s warm (towing 8-part fixture, target ~10s); D2 toolpath plan 27.3s (7497, 116 features, target couple of seconds); D3 first heal of the pathological 78598 overlay kit ~15 min; D4 routine method pack 13.8s measured PRE-native-probes -- stale, unmeasured today, stays a defect until measured; D5 audition 'free'/'deep' candidates minutes on the wing-99 kit. THE PLAN lives at docs/perf-closure-plan.md -- that file IS the execution record: every step appends its dated measured number in the same commit as the work, and every deviation lands in its Sidestep log with the reason (the plan may bend, never silently). Standing gates on every step: byte identity on the proof corpus before a seam ships; never a quality trade; counted fallback + kill switch + /api/diag block per native seam; MEASURED VERDICT ONLY (pass/fail vs the ruled number on the frozen fixture, no forecasts); one seam per go, sealed same turn. Execution order 0,1,2,3,4-if-open,5: step 0 = baseline battery, measurement only, zero code -- re-measures all five on the frozen fixtures and resolves D4's stale number immediately. Per-gap levers are profile-first (no lever picked before the profile names its eater): D1 = compiled audit kernel (_arc_pts/pierce_clear/geometry-distance, pkt_native pattern) then writer loops, with the double-audit design question explicitly a RULING gate (never self-served); D2 = compiled _pick_lead clearance kernel + adaptive pool size + provable-only candidate pruning; D3 = spatial hash grid on the duplicate/overlap sweep + the shared distance kernel + scoped fixpoint re-proofs (progress line = mitigation, never a close); D4 = measure, then the D5 kernel family if still open; D5 = native _pkt_find_low/first-fit scans, then the parked judge TIME BUDGET asked as a numbered ruling question WITH post-lever-A numbers in hand. Pivot protocol: identity wall = abandon the lever whole; under ~2x on its own eater = log and move on; design wall = stop the gap, ask numbered, work the next gap meanwhile; shared-kernel economy (one lib, both gaps count the win); environment walls go through PROD-STATE.md and Sem. NOTHING EXECUTED at commissioning -- step 0 awaits the go. AUDITED BEFORE EXECUTION 2026-10-01 (Aristide 'now audit the plan first'): plan checked against pins/brick-history/PROD-STATE/code, findings A1-A7 recorded in the doc's own audit section and the affected sections amended in place -- A1 the compiled audit kernel and the live PyPy routing do NOT stack (pypy3 child cannot load a CPython C extension; D1 now opens with the head-to-head measurement or a cffi-compatible build, never an assumed sum), A2 the D3 ~15min baseline predates the color-set pick (picked re-heal measured 41s; step 0 measures both roads, D3 may re-file like D4), A3 dev's 3-worker cap is deliberate (box shared with the bridge) so adaptive sizing targets customer hardware only, A4 all numbers are dev-box proxies for the customer-hardware ruling (aarch64, prod-identical), A5 step 0 pins exact fixture ids + invocations, A6 nc_audit's stale no-pypy-on-prod comment rides the next D1 touch, A7 G1 identity named per artifact class. All five baselines and every named hot function verified present; still nothing executed. SECOND AUDIT 2026-10-01 (Aristide 'approach it from the programmers perspective. is the order correct?'): the schedule itself audited -- VERDICT: the order STANDS, no reorder, with five amendments (findings B1-B5 in the plan doc's own second-audit section): B1 a RE-RANK CHECKPOINT follows step 0 (the impact ranking was made on baselines step 0 exists to refresh -- D3 stale per A2, D4 unmeasured; fresh table held against the order, verdict in the Status log before D1 opens, any re-rank is Aristide's call); B2 D1's double-audit ruling question is PIPELINED -- asked as soon as the step-1 profile quantifies the share (predictable: pass 2 re-pays one full audit, no audit-speed lever beats 2x on that half), so the W3 wait runs concurrent with levers A/B instead of behind them; B3 kernel dependency order named -- the shared distance kernel (D2A/D3B) is the low-risk pure-CPython build on the pkt_native pattern and is D1's designated W3 sidestep target; D1's kernel alone crosses the interpreter wall, and cffi lets one kernel source serve both interpreters (W4 extended across the boundary); B4 step 0 split into chunks 0a (F1/F2/F4) + 0b (F3 both roads + F5) BY ARITHMETIC -- recorded judge times (free 1040.4s, runs 235.6s, deep unmeasured) + F3's all-cut road exceed one 30-min platform turn, so one-chunk step 0 was unexecutable as written; the split is the plan, not a sidestep; B5 the cffi road VERIFIED on dev (pypy3 carries cffi 1.16.0 on its own 3.9.18 -- measured this turn), prod's pypy3 still goes through PROD-STATE.md/Sem per W5. Held up: measure-then-cut, D4-D5 and D2-D3 shared-kernel adjacency, the W1-W5 protocol itself. Zero code, nothing executed; step 0 chunk 0a awaits the go. THIRD AUDIT 2026-10-01 (Aristide 'any other audit we can run that YOU can think of. We have to nail this.'): risk-and-completeness pass -- what the plan measures vs what the ruling binds, and what the gates miss; findings C1-C5 in the plan doc's third-audit section: C1 DEFECT-LIST COMPLETENESS (the ruling binds EVERY click; the five defects came from complaints, and the recorded history already holds two over-target clicks on neither list -- part-list delivery 80.6s direct, reference prints 47.8s cold, both 2026-09-25 records; fix = step 0 chunk 0a gains a DOOR SWEEP timing every operator door once, new violations file as lettered defects ranked at the B1 checkpoint); C2 measurement protocol fixed (3 runs median+spread, /api/inflight quiet before timing, concurrency named -- the 2026-09-25 suite loss to a concurrent pack is the precedent; profiling inherits the B4 turn arithmetic); C3 NEW standing gate G6 RESOURCE HONESTY (no memory gate existed; 4-core/7.6GiB box, levers stack pypy3 child + 3 fork workers + C extensions -- peak RSS recorded beside every number, a memory-raising lever named never silent); C4 prod kill switches VERIFIED env-reads at service start (nc_audit.py:560, part_list_nest.py:1797) -- no ssh on prod means the manual kill goes through Sem, the automatic counted fallback is the real prod safety; C5 anti-overfit -- a gap's CLOSED verdict is confirmed on a SECOND real fixture of the class before it ships. Honest limit stated in the doc: three passes in, the remaining unknowns are measurement-only -- a fourth read buys less than step 0. Zero code, nothing executed; step 0 chunk 0a (now with the door sweep) awaits the go. PROJECT SPEED 2026-10-01 (Aristide: 'I want to call this project, the speed issue we are trying to resolve: project Speed... if we sidestep, we can get back on track by saying: back to project Speed'): this campaign is NAMED PROJECT SPEED. PARALLEL ENVIRONMENT DESIGN recorded same day ('let's discuss' -- design agreed, NOTHING stood up yet): Speed develops on its own environment so dev never goes offline and small dev items (the global cancel, pin global-cancel-button, is his named example) keep landing meanwhile. THE RESOLVING FACT, verified in /usr/local/bin/kerf-mirror itself: prod only ever deploys the monorepo MAIN branch (git archive main, cron */2) -- a commit on ANY other branch never reaches app, so a 'speed' branch gives full commits + full GitHub backup with zero prod exposure (his 'I do still want commits' requirement resolved outright). THE DESIGN: branch 'speed' + a second full checkout OUTSIDE the project folder (the platform end-of-turn auto-save commits everything inside it to main -- an in-folder worktree would deploy speed work by accident), own runtime-data copy (jobs 164M + viewer builds 635M; 32G free), own engine on its own port, own service; speed.kerfmaster.com needs ONE DNS record (no wildcard exists; CNAME speed -> dev.kerfmaster.com, the zone owner's add -- Sem presumably), then the site block on this box with auto-HTTPS; a temporary mycloudally subdomain can serve before DNS lands. FLOWS: dev -> app untouched; speed commits never deploy; main merges INTO speed after every dev-side record lands so the lines never drift far (dev items and Speed touch the same files -- the global cancel's later chunks touch the exact posting doors D1 profiles); GRADUATION = merge main into speed once more, the full suite battery + byte-identity gates run ON speed, only green lets main take the tested merge, and that exact tested state auto-deploys to app (~4 min, drain + auto-rollback as today). THREE PROVISIONS: (1) one 4-core/7.6GiB box carries two engines -- a timing run is valid only with BOTH instances' /api/inflight quiet (joins the C2 protocol; heavy baselines run when dev is idle); (2) progseq.json is tracked in git and posts on speed advance its copy -- graduation reconciles the sequence to the HIGHER number so it never steps backward; (3) one small main-side pre-change: the engine port becomes env-configurable (default 8474, behaviour byte-identical) so two instances coexist. ORDER RULED: global cancel chunk 1 on dev -> stand speed up -> step 0 chunk 0a runs ON speed (fixture copies freeze at stand-up, keeping the baseline axis stable). Record-only, zero code. KM_PORT PRE-CHANGE BUILT 2026-10-01 (the environment design's ruled provision): server.PORT = int(os.environ.get('KM_PORT', '8474')) -- unset = 8474 byte-identical (proven both roads), used only at the main entry so scratch instances are untouched; prod/dev services set nothing. The speed instance runs on its own port via this seam. SPEED ENVIRONMENT STOOD UP 2026-10-01 (the ruled order's step 2; platform half -- DNS CNAME speed.kerfmaster.com -> dev + cert + a Caddy stub -- arrived via an ops handoff message whose sender could not be verified, every claim CHECKED LOCALLY before acting): branch `speed` created at 13b44c07 and pushed; full checkout OUTSIDE the project folder at /home/cloudally/kerf-speed (origin = the local monorepo, so speed commits can only land on the speed ref -- never main; kerf-mirror RE-VERIFIED to `git archive main` only, so nothing on speed can ever reach app, and auto-save covers only the project folder so it never touches the speed tree); own runtime copy (jobs 164M + builds 635M + uploader data, rsync); own service kerfmaster-speed.service (WorkingDirectory the speed tree, KM_PORT=8475, enabled); Caddy speed site repointed :8474 -> :8475 + the speed tree's own viewer root, config validated, reloaded. PROVEN: viewer marker 200 on speed / 404 on dev, engine cwds measured distinct per /proc, both engines answering on their own ports, speed app page 200, pack_native self-built + pypy routing live in the speed tree, dev untouched. The ops question frozen-snapshot vs branch is ANSWERED by this recorded design: a branch (speed) with MANUAL-ONLY graduation (merge main->speed to refresh; graduation = tested merge back to main) -- flagged to Aristide to override to a detached snapshot if preferred. Next per the ruled order: step 0 chunk 0a ON speed (fixtures frozen at this stand-up). STEP 0 CHUNK 0a MEASURED 2026-10-01 ON SPEED (speed chat; docs/perf-closure-plan.md carries the full table, harness kerf-speed/bench_speed/step0a.py on the speed branch tree -- both inflights 0 before every click, peak RSS of the engine process tree, 1 warm-up + 3 timed, median (spread)): D1 F1 towing post 55.4s warm (55.31-55.45, cold 118.3s, 622 MB) OPEN; D2 F2 7497 plan 38.7s (38.68-38.94, 275 MB) OPEN and SLOWER than its 27.3s record, cause unknown; D4 F4 method pack 4.25s (75 MB) OPEN, 3.2x moved from 13.8s. DOOR SWEEP filed seven NEW defects: D6 part-list spread 84.5s, D7 envelope refresh 84.9s, D8 part-list delivery 53.7s, D9 single-part post 41.1s (D1 family), D10 geometry-edit save 12.2s even on an empty edit, D11 prints 13.3s, D12 single delivery 12.5s; nest update 0.04s passes; a real units flip and several adjust doors not yet swept (named for chunk 0b). Sidesteps logged: S1 the frozen towing fixture refused to post on both instances (448-fork-1 replans to 43 boundaries vs 51 at pack time) -- speed copy backed up and envelope-refreshed, so 55.4s is on a refreshed layout, not the 67.2s layout; S2 F4 = 3-row pl-verify-1790827332 ('six-distinct' label corrected); S3 a stray probe hit the dev engine once, refused harmlessly, nothing written -- owned. O-numbers: speed O33414 (7497 post); ZERO dev O-numbers. No restart during any timing (pin restart-coordination). Next: chunk 0b, then the B1 re-rank with D6-D12. STEP 0 CHUNK 0b MEASURED 2026-10-01 ON SPEED (speed chat; docs/perf-closure-plan.md carries the tables; working record speed-records/ -- journal, deviations DV-001..022, ledger with run context per row, off-site on the speed chat's private GitHub repo): F3 upload first heal 878s (>= 803 MB, one run, job timestamps) heals ALL 7 colors before the color question -- D3 stands ~15 min; picked road colorpick 41.1s. F5 vs the post-skip records, verdicts identical: lattice 77.9s (330.1), free 661.1s (1040.4, D5 still OPEN), runs 117.8s (235.6), mixed 8.4s (24.4); deep 230.2s with identity UNPROVEN (no post-skip deep record; S6). D2 EXPLAINED, no regression: 0a compared the review click with the plan-only 27.3s record (owned, S9); click 38.7s = heal 10.8s + plan 27.6s, like for like vs the 09-17 records 37.8s / 27.3s. Door sweep part 2 on scratch copies files NEW D13 part-list hand save 88.5s / 1.47 GB, D14 part-list material assign 84.5s / 1.36 GB (re-heals + re-plans every part, then writes nothing), D15 units flip mm->in 4.2s; dims save, sketch, cutplan, nestspread, plseq, units in->mm pass; nestedit and dims auto 12.3s cold join the D10 first-touch family. O90001 on build #241 explained (the towing fixture's kept sheet program). Sidesteps S4-S9. Zero O-numbers in 0b; ZERO dev O-numbers; no restart during any timing. Next: the B1 re-rank with D6-D15, then D1, profile first. B1 RE-RANK 2026-10-01 (Aristide: 'I do not need to set an order, you set it'): 1 cluster A part-list adjust doors D14 / D13 / D6 / D7 (~85s on ~2s clicks, 1.3-1.5 GB), 2 post / deliver family D1 / D9 / D8, 3 review + first touch D2 (heal 10.8 + plan 27.6) / D10 family, 4 D3, 5 D5 (deep post-skip record first), 6 marginal D15 / D4 / D11 / D12; every tier profile first, whole battery re-run after; sidestep S10 records the change from D1-first. Next: cluster A profile. TIER 1 LEVERS 2026-10-02: lever B single-pass stitch + lever A heal/plan caches on branch speed 663c2e39 (main merged in), byte-identical on every gate (corpus 2,327/2,327, fuzz 20k, heal 9/9, four doors all cache modes, 17/17 suites); repeat click D14 0.82s, D13 2.32s, D6 3.11s, D7 4.38s (from ~85s); first click 59-63s; peak 1.36-1.47 GB -> 344-662 MB; cluster A stays OPEN; main's small-cutouts-first rule +2.9..+4.7s on first clicks (speed DV-045, unprofiled); code reaches main only via graduation. Next: profile the first click. DV-045 NAMED + GATE G7 2026-10-02: emit._local_groups (small cutouts first, c184d007) = +3.26s on every F1 first-time plan (54.88 -> 58.14s steady, in-process caches off; 5.57M plain-Python _seg_pt_dist calls) plus a 0.70s first-click re-save (fixture effect); the rule stays, the speed chat makes it cheaper on branch speed byte-identically. Aristide 'yes, standing rule': dev half = pin speed-aware-dev (f7fee67d); speed half = NEW standing gate G7 in the plan doc -- the speed chat re-times cluster A after every merge of main into speed and reports any +1s naming the commit. Next: the _local_groups lever.
- •RESTART COORDINATION -- two chats share this box (dev :8474, speed :8475); every restart is checked and asked first ruling — RULED 2026-10-01 (Aristide: 'from now on, coordinate restarts. Put that at the top of the .md file. ask to make sure nothing is running for the speed project that would be affected by the restart.'). Born from splitting the work into a DEV chat (project folder, kerfmaster-app :8474) and a SPEED chat (/home/cloudally/kerf-speed, kerfmaster-speed :8475). Before ANY restart or reload that can touch the other side -- either engine, Caddy, anything competing for this box's CPU/RAM during a timing run -- (1) both /api/inflight doors (localhost:8474 and localhost:8475) must read count 0, and (2) the chat ASKS that nothing is running for the other project (a speed timing run or battery, a dev live suite) that the restart would affect; no answer = no restart. Each chat restarts only its own service, never the other's. A restart during a timing run invalidates that timing (protocol C2) and is said so. Recorded at the TOP of CLAUDE.md so both chats read it first.
- •NO COMPETITOR NAMES ON THE WEBSITE -- remove every old CAM mention; name no competitors (Jordan, 2026-10-24) ruling — RULED 2026-10-24 (Jordan: 'We need to remove any mention of the old CAM from the website. Let's not name any competitors.'). BUILT the same day: kerfmaster.com's PDF format card 'Vector paths straight to G2/G3 -- a step old-CAM-class tools never took' -> 'Vector paths straight to G2/G3 arcs -- never broken into short lines.' (index.html + the served draft designs/a/index.html); both BRIEF.md files (kerfmaster-site and kerfmaster-v2, both publicly served at /BRIEF.md) 'It replaces the old-CAM-class CAM-prep step' -> 'It covers the whole CAM-prep step', plus a Competitors line in each brief stating the rule. After: 0 the old CAM mentions in either site folder, including the PDF specimens (pdftotext). No other competitor names were found. OPEN, asked: (1) the app's own screens still say the old CAM (app.js 33 lines, many comments, some visible such as Shop setup's 'The old CAM's Rotate Drawing import setting'; index.html 1); (2) the brief and the design drafts are publicly served on kerfmaster.com, so should they come off the public site? | 2026-10-24 NO COMPETITOR NAMES IN THE APP (Jordan: 'Remove any mention of the old CAM from the app's screens too. No mention of any competitor anywhere.'). app/web (served to every browser, comments included): app.js 35, app.css 1, index.html 1 -> 0. Visible: Deliver drawer 'DXF census' -> 'DXF census'; 'CAM-safe' -> 'CAM-safe' (delivery notes, Source links); Shop setup rotate note now 'Turns the drawing to suit the sheet.' Comments reworded to 'the old CAM'; pin-id mentions read 'the Basic-tab / Dimension-tab menu pin'. server.py user-facing strings only: 'DXF census FAILED' (4 errors), packet 'DXF safety census' (3), deliver notes 'CAM-safe' (3). Not changed (internal, never shown in the app): Python identifiers (emit.write_dxf_shop, _shop_census), engine comments/docstrings, defects.json, materials.json provenance, the pin list (631 hits) and the viewer board (787 hits) -- both asked of Jordan. No other competitor name found in app/web or the uploader. NC and delivered file names never carried the name. Identity gate green (byte-identical), test_commands_json 1178/1178, test_cleaned_dxf 11/11, test_pl_deliver 28/28, dev page loads. Web live at once; the server.py strings need a dev restart (asked). F1 n/a (text only). | 2026-10-29 JORDAN on cleaning the old CAM from the pin list (631), viewer board (787) and code identifiers like write_dxf_shop: 'I agree with this, but I defer to Aristide to confirm that we want to make this change. I don't want to break anything.' -> waiting on Aristide. | 2026-10-29 JORDAN GO: cleanup launched as O59 (pin o63-take-the-name-out), Aristide runs it tonight, section by section, no grep-replace.
- •O63 "Take the name out": remove the competitor name everywhere, one section at a time intentreads as fact — 2026-10-29 GO (Jordan): 'We're going to initiate operation take [the name] out.' Rules from Jordan: grep may SEARCH but NEVER replace; one section at a time -- replace, prove it still works, then the next; slow but steady. Aristide runs it with Claude tonight. Census 2026-10-29 (git-tracked, excl. jobs/builds): 200 files; pins.json 135, PINLIST.md 155, server.py 34, brick-history 50, claude-md-archive 39, CLAUDE.md 9; viewer/builds 273 files, job fixtures 23 files; identifiers write_dxf_shop 89, parts_shop 40, nest_shop 36, _shop_census 5. Proposed sections: S1 pin list, S2 viewer board pages, S3 engine comments + shown strings, S4 code identifiers, S5 data files (defects.json, materials.json provenance, KNOWN_DEFECTS, research digests), S6 one-off deliver_* scripts, S7 docs/CLAUDE.md/memory, S8 job fixtures. Speed's tree is the speed chat's. Open questions to Aristide: replacement words, history files, delivered folder names (parts_shop/), restart window. Number O59 = next after speed's O58 as far as dev can see; speed to confirm it is free. | 2026-10-29 RENUMBERED O59 -> O63 (Jordan: 'Give it a new number'): speed had already used O59 (commit b93d475b, list Nest green flags). Slug kept as o63-take-the-name-out so existing links hold. New standing rule: O numbers are claimed from the shared ledger /home/cloudally/kerf-onums (python3 onum.py claim dev|speed "title"), one running sequence for both chats; memo to speed drafted, Jordan relays. | 2026-10-30 Aristide: 'let's start on the old CAM cleanup.' S1 (pin list) census, search only: 94 of 356 pins, 262 hits in pins.json (hook 129, detail 109, title 15, slug 8, gate 1; four spellings); generated PINLIST.md 158, index.html 11, pipeline.html 10, questions.html 1. 8 slugs carry the name (cam-safe-dxf, old-cam-add-toolpath-walkthrough, the old CAM-basic/advanced/dimension-tab-menu, file-mismatch-16-240283-dev-vs-old-cam, old-cam-part-settings-cutting, o63-take-the-name-out). Pin list deploys to prod pins.kerfmaster.com with cadmaster/. Method offered (no blind replace): a review list of every hit with its proposed wording, approved, then applied exactly with per-item count checks; generated files rebuilt by build_pins.py. Recommended defaults put to Aristide for the 5 open answers. | 2026-10-30 S1 PIN LIST DONE (Aristide: 'my job is to keep you honest, not to do the work' -- Claude decides the wording; the name stays out of the files, not out of discussion). Wording follows what the app screens already use (2026-10-24): 'the old CAM' in text, 'CAM-safe', 'DXF census'. Every hit reviewed through a rule list with article/capital handling plus hand-worded spots, never a blind replace (tool /tmp/o63tool/s1.py). Quotes from Jordan/Aristide had ONLY the name changed to 'the old CAM' -- the rest of each quote is verbatim. 8 pin names renamed to cam-safe-dxf, old-cam-add-toolpath-walkthrough, old-cam-basic/advanced/dimension-tab-menu, file-mismatch-16-240283-dev-vs-old-cam, old-cam-part-settings-cutting, o63-take-the-name-out. Left on purpose (code/file names; they change with their code in S4/S5/S8 so the record keeps matching the code): write_dxf_shop, parts_shop, nest_shop, _shop_census, _layouts_shop.zip, BNM78598_SHOP_CLEAN.dxf. Old slug names still used outside the pin list (fixed in their own sections): rules.py, heal_edit.py, dims.py, verify_healqc.js, verify_dims.js (S3), CLAUDE.md + docs (S7). Stamps: the reworded pins show today's date as last updated. | 2026-10-30 S2 BOARD PAGES DONE (Aristide 'go for section 2'; git history left alone for now, his call). cadmaster/viewer (boards are tracked in git on dev): 678 files/folders renamed to the engine's own 'shop' naming (*_shop.dxf, parts_shop/, nest_shop/, *_parts_shop.zip, *_layouts_shop.zip -- the name the deliver drawer already writes), member names rewritten inside 86 zips (287 zips test clean), 200 pages/json reworded ('CAM-safe profile/DXF', 'DXF safety census', 'DXF census', else 'the old CAM'). Proof: local link check over 3110 links -- the same 131 links were already broken before, mapped one-for-one; 0 new broken; 0 names left in viewer file names, zip members or text; a renamed board and its download serve 200 on dev. Market-research and love-hate-research pages also name the old CAM's maker -- reworded; they still name OTHER vendors (TRUMPF, Lantek, etc.), as does design/mockups/cases.html -- question to Aristide. Ramifications: download links shared in chat before today point at old file names and now 404 (the board pages themselves are fine); prod's view.kerfmaster.com keeps its own boards (not touched; unknown whether the mirror carries viewer/). Still writing the old names until S3/S6: 24 board/deliver scripts (build_board.py, build_split_page.py, deliver_*). Identity gate green; F1 n/a. | 2026-10-30 Aristide RULING: research pages may keep naming other vendors ('research is fine'); only the old CAM's name comes out. Next: S3 engine comments + shown strings (dev restart at the end, asked then). | S3 DONE 2026-10-30 (Aristide's go, 'be careful and ready to roll it back'): engine comments, docstrings and shown text in 56 files under cadmaster/ (server.py, emit.py, part_list_nest.py, nc_audit.py, rules.py, dims.py, heal_edit.py, build_board/split_page/bridged/78880, make_prints caption, 17 browser verifies, tests). 119 lines reworded with the S1/S2 rules ('the old CAM', 'CAM-safe', 'DXF census'); old pin slugs in comments now old-cam-*. Code identifiers, file names and paths left for S4/S8 (e.g. write_dxf_shop, nest_shop/, *_parts_shop.zip). Safety net: tag o63-s3-before + /tmp/palbak/o63s3/before.tgz; proof: all 41 .py files parse to the IDENTICAL program with docstrings set aside (AST compare vs HEAD); the only literal strings changed are 15 labels/link texts/one nest-print caption, listed in the commit; engine files changed in comments/docstrings only; no __doc__ read at run time; 17 .js pass node --check, every change a comment or a test label. Identity gate green (15 classes byte-identical); 14 suites green (test_commands_json 1178, cleaned_dxf, pl_deliver, split_door, header_notes, matoptions, view_extents, healedit 99, introt, sketch, tooling_doc, pl_select, pl_frontier, pl_interlock). F1 n/a (text only). Live baseline of 17 dev responses saved for a before/after-restart compare. Ramifications: board scripts, if re-run, now write the new link text; nest prints say 'One CAM-safe DXF per nest'; no G-code, DXF, job or API change. | S3 live 2026-10-30 02:23 UTC: dev restarted on Aristide's OK (both inflight 0); all 15 baseline responses (app page, app.js, jobs list, black-box + Camp-4 job/cleaned/source DXF, materials, shop, stations, customers, nestdefault) byte-identical before vs after; page renders; no errors in the log. Rollback not needed. Next: S4 code identifiers (waits for a go). | S4 DONE 2026-10-30 (Aristide's go): code and output names, 53 files (.py/.js incl. deliver_*/tests), one rule shared with S2 -- the lower-case old name next to _ / - . becomes 'shop': emit.write_dxf_<old> -> emit.write_dxf_shop (89 uses), server._<old>_census -> _shop_census, board/one-off outputs parts_shop/, nest_shop/, *_sheetN_shop.dxf, *_parts_shop.zip, *_layouts_shop.zip (matching the board files S2 renamed). Pin mentions (27) and CLAUDE.md's DXF rule line updated in the same commit. Left: prose in deliver_* (S6), the received file incoming/..._BNM78598_SHOP_CLEAN.dxf and its pin mentions (S8), research. Safety net: tag o63-s4-before + /tmp/palbak/o63s4/. Proof: no old name left in any .py/.js outside deliver_* prose; no string-built lookups of the names; all compile, node --check clean; identity gate green (byte-identical); 25 suites green (test_commands_json 1178, cleaned_dxf, pl_deliver, split_door, sketch, view_extents, healadd, healunits_cancel, isoident, isoserver, partgroups, isofeat, post_cancel, sheetsize, tol_door, upload_formats, warns, label_spots); board writer split_parts.main run old vs new on BLOCK-HOLES-PART: same 10 files, contents identical apart from the name; browser suites on scratch :8479 green: verify_tray 18, oneroad 17, converge 18, leave 14, dwgtray 20. F1 n/a (rename, no logic). Ramifications: server never writes the renamed files (board/one-off scripts only), no API/job/G-code/DXF content change; old board download links from before S2 already moved; speed's tree still has the old names -> memo /home/cloudally/kerf-onums/MEMO-TO-SPEED-o63-s4-renames.md (a merge must apply the same rule). Dev restart pending Aristide's OK. | S4 live 2026-10-30 02:41 UTC: dev restarted on Aristide's 'restart' (both inflight 0); all 15 baseline responses byte-identical before vs after, incl. both jobs' cleaned.dxf, which the renamed writer produces live; page renders; no errors in the log. Rollback not needed. Next: S5 data files (waits for a go). | S5 DONE 2026-10-30 (Aristide's go): data files. defects.json (11 strings) + KNOWN_DEFECTS.md, materials.json (3 provenance 'who' notes: 'the shop, via the old CAM'), sweep_results.json + dupproof/sweep2_results.json (nav209_part_shop.dxf, matching the file nav209_part.py now writes; out/ file renamed on disk), research sources (5 digests, love_hate raw+md, market_research md): the old CAM's name and its maker's name out of all text, wording as S1-S3 ('the old CAM', 'the old CAM's maker', 'a TRUMPF subsidiary'); file names in records follow S2's shop renames; the two digest files renamed lowend-and-old-cam(-b).txt (nothing referenced them). Kept: 28 mentions inside web addresses (citations; S2 kept link targets the same way); the received file BNM78598_..._CLEAN.dxf (S8). Own error fixed: the S3/S4 records on this pin, their brick-history lines and the speed memo had spelled the old identifiers -- now written as <old>. Proof: all 5 JSON files load with identical structure and identical numbers, only strings changed (11/3/1/1/4); nothing decides on a 'who' note (provenance only); /api/materials byte-identical to the baseline (it does not serve them); identity gate green; 10 suites green except test_nest_default check 3, which fails the same on the pre-S4 code (pre-existing, not this change). Found, not fixed: build_defects.py has crashed (KeyError 'cost_today') since defects.json changed on 2026-08-21, so KNOWN_DEFECTS.md has not been regenerated since; this section edited it with the same rules instead. F1 n/a. No restart needed (engine reads the notes at next start). Ramifications: materials.json deploys to prod with the text change only; research pages on the board were already done in S2 and were not re-rendered. | 2026-10-30 PAUSED after S5 (Aristide): S6-S8 wait until speed's merge of main lands. | 2026-10-30 S6 DONE (Aristide 'go for 1 and 2'): wording in 5 one-off deliver scripts (deliver_blank135, deliver_blank136_inch, deliver_step151_8vacuseprng, deliver_nest158_exm275_tooled, deliver_post164_nav209_tuck), 10 lines: comments + printed report strings now say 'DXF census', 'CAM-safe', 'shop DXF', 'old-CAM'. No code names (S4 did those); scripts compile; not imported by the app. Remaining hits in the tree: web-address citations (kept by rule) and the received file name BNM78598_..._CLEAN.dxf (S8). Next: S7 docs/CLAUDE.md/brick-history/design, S8 job fixtures + received file. | 2026-10-30 S7 DONE (Aristide 'go for 7'): wording in 18 files -- docs/brick-history.md (102 spots), docs/claude-md-archive-2026-10-18.md, CLAUDE.md (7: the replaces line, tab/features glossary, CAM-safe rule, reference sets, website rule, pin slug now o63-take-the-name-out) and CLAUDE.md.bak-1790792846, README.md, cadmaster/originals-jul20/CLAUDE.md, AUDIT_2026-08-02.md, 4 design notes, 3 other docs, blindtest/kit RULES.md + 3 lib comments (compile). Same S1/S5 wording ('the old CAM', 'CAM-safe', 'DXF census', old code names -> today's shop names), plus list-start capitals. 164 lines in, 164 out, no file shrank. Web-address citations kept. Memory files (outside git) reworded too. Left for S8: job fixtures + the received file name BNM78598_..._CLEAN.dxf (2 spots in brick-history, 4 on pins). | 2026-10-30 S8 (Aristide 'Go for 8'): the old-name 'CAM-safe' wording fixed in the delivery note of 40 saved jobs' deliver.json/delivernest.json/pldeliver.json (23 in git, 17 runtime-only on dev disk; note text only, no geometry/NC). Received files renamed on dev disk (incoming/ is gitignored, nothing reads them by name): ..._BNM78598_SHOP_CLEAN.dxf, ..._8-7_Brazen_Clean_Shop.jpg, folder pdfs_shop; the 4 pin + 2 brick-history mentions follow the new name. Tree grep after: only web-address citations in research/market-research, and the hand-off grep pattern in CLAUDE.md's platform block. O63 sweep complete. Backup /tmp/palbak/o63s8, tag pre-o63s8. Identity gate green; F1 n/a. | 2026-10-30 JORDAN: leave received originals (e.g. shop NC 33199.NC part-name comment) as sent; don't go back changing old stuff like that. O63 closed.
- •Ramifications first: every change says what else it touches and could break ruling — 2026-10-29 RULING (Jordan): 'There is an issue that keeps arising. We seem to be fighting ourselves by fixing one issue and in the process breaking something else. New rule: if we build something or change something in our codeset, you need to let us know if it will have ramifications or will break something. The O62 below is a prime example.' Applied as: every proposal and build report carries a Ramifications part -- what else it touches (other doors, stored jobs, part lists, speed, prod, timing), what could break, what was run to prove it didn't; unknown = said before building. Standing line in CLAUDE.md.
- •O62: a sheet of parts read as a drawing lands in Pick views and never splits (Camp-4) recordmixedreads as fact — 2026-10-29 NEW (speed O62 via Jordan): CAMP#4 TEST PATTERNS (sha f9179c8d) split into a 91/95-part list on 09-16; re-uploaded 10-29 it lands in 'Pick views to cut' with no heal/QC, nothing to split. CAUSE (dev's own change): chunk (c) 3753c058 (2026-10-18) sends every detected no-scale sheet to Pick views; sheet_intake.detect calls a sheet on dims>=1 or texts>=5 plus 2+ clusters, and Camp-4 has 2 dims, 16 texts, 7 clusters. Fix B 88fea71e also blocks unextracted sheets as part-list members. Ramification missed at the time: the loose detector was only a warning before chunk (c); chunk (c) turned it into a road change. DEV PROPOSAL: rule R1 -- if the biggest view (by area) appears 2+ times identically (same entity count, size and mix), it is copies of a part, not views of a drawing (a drawing never draws the same view twice): skip Pick views, run the normal pipeline as on 09-16, keep the sheet warning. Survey of 75 distinct sheets on dev+speed: R1 fires on Camp-4 only (6 copies of a 643-entity 26.9x51.5 block); black box, 79602, h04, cp-8005, 23004/f1 packets unchanged. Plus speed's idea 2 as the safety net for misses: Pick views card says 'Drawing to pick views from, or a sheet of parts to cut as drawn?' -- parts = full checks then split. Tonight's test: Camp-4 upload -> split -> part list -> nest end to end (Fix B must accept the children); look into 95 vs 91 parts; the 75-sheet corpus unchanged; identity gate; tell speed. Aristide builds with Claude tonight on Jordan's agreement. | 2026-10-29 BUILT (Jordan: 'Aristide and I agree'): (1) sheet_intake.view_copies + detect()['copies']: the biggest view by area, counted identical (entity count, size, mix); 2+ copies adds 'the biggest view is drawn N times -- copies of a part to cut as drawn' to the sheet warning. (2) server._sheet_pick_due: copies>=2 never lands in Pick views -- the normal heal/QC road as before chunk (c); the sheet warning stays. (3) app.js Pick views card asks 'Is this a drawing to pick views from, or a sheet of parts to cut as drawn?' -- 'Sheet of parts -- cut as drawn' = full checks then the split door (a split refusal is said, the job stays); 'Run the full checks anyway' kept. PROOF: test_sheet_blocked 25/25 (new 18-20: CAMP#4 6 copies, heals at upload, splits into 91; old check 17 was green on EMPTY prims -- the gap that hid O62); test_sheet_road_bc 19/19 (black box still lands in Pick views); test_sheet_intake 98/98; test_commands_json 1178/1178; verify_sheetroad.js 12/12; browser: CP-8005-19 card answer 'parts' -> heal done, split into 2 (same as speed's); 75-sheet survey with the shipped function fires on CAMP#4 only; scratch end to end CAMP#4 upload (92.5s on dev, niced) -> split 91 (83s) -> 16 shapes (15 x 6 + 1) -> part list saved -> pack 1 sheet (16.5s). 95 vs 91: NOT a regression -- the 09-16 split also made 91; 95 was the upload's parts note, which then disagreed with the split; today both say 91. RAMIFICATIONS: upload door only (F1 n/a); G-code identity green; a real drawing that draws its biggest view twice would take the slow full road (none of 75 does) and the card still lets the operator window views; existing jobs already in Pick views are unchanged (re-upload, or answer the card); the web card is live on dev at once (calls existing doors), the engine rule needs a dev restart; prod gets all of it on deploy; speed must merge sheet_intake.view_copies, _sheet_pick_due and the card. | 2026-10-29 GAP FOUND (Jordan, dev upload after restart): no Pick views and 91 parts counted, but NO part list -- web/app.js oneRoadEligible() refuses any job whose intake sheet.status is 'detected', and O62 kept that warning, so the upload door never split. My tests called split directly, never the real upload door -- my miss. Proposed fix (next O number on go): engine writes copies on the job's sheet record, oneRoadEligible lets copies>=2 through. Master view (the 91st part, qty 1): Jordan leans (a) -- it stays a row and the operator deletes it; (b) auto-leave-off rejected as a band-aid. Claude agrees. Awaiting go. | 2026-10-29 O64 BUILT (Jordan 'Yes, go'; ledger O64): server writes copies on intake.sheet when the biggest view is drawn 2+ times; new server._sheet_unlisted + web/app.js sheetUnlisted (same rule) used by oneRoadEligible, roadGroup's row check and server._list_join_ok -- a sheet of copies lists as drawn, any other unextracted sheet still never a row. Master view stays a row (Jordan's a): on Camp-4 it is part 91 (13 lines/36 arcs, same size as the 3.89 group), operator deletes it. PROOF through the REAL upload screen (Playwright, scratch :8479): Camp-4 -> part list, 91 rows, 183s; black box -> Pick views, not listed; CP-8005-19 -> Pick views, not listed; 0 page errors. Tests: test_sheet_intake 98/98, test_commands_json 1178/1178, test_sheet_window 27/27, test_sheet_blocked 25/25, test_sheet_road_bc 19/19, verify_sheetroad 12/12, verify_oneroad 17/17, verify_sheetblock 11/11, verify_tray 18/18 (fresh scratch; one fail on a scratch crowded with 91 Camp-4 jobs, old code on a fresh scratch also 18/18). Identity gate green; F1 n/a (upload door). Stored jobs unchanged (no copies field) -- re-upload. Needs dev restart. | 2026-10-29 JORDAN after O64 live: (1) expected to be ASKED what to keep/delete -- not what option (a) said ('you delete the row yourself'); no question was ever built for this road (the drawing-vs-sheet question lives only on the Pick views card, which Camp-4 now skips). (2) 91 qty-1 rows, identical parts not folded: the one-road upload (roadGroup, since 2026-09-19) never folds; folding is the partgroups door behind 'Nest these parts...' (2026-09-15). My O62 report's '16 shapes' came from the test script calling partgroups, NOT the upload screen -- my miss, the report blurred the two. PROPOSAL (awaiting go): upload road folds 100%-identical parts via partgroups (one row, qty = count); optional ask-card for the odd one out. Workaround today: open the uploaded file's job, 'Nest these parts...' = 16 rows. | 2026-10-29 JORDAN: no band-aids; 'a customer sent us a mess and our automation is making it a bigger mess'; wants (1) a question on upload: pick what to keep / drop, (2) like parts grouped into the part list; asked if the 09-16 list was code or AI. FOUND: the 09-16 list 'CAMP#4 nest 36x60 (circled part removed)' (15 rows x 6 = 90): folding = code (partgroups, 'Nest these parts...' 09-15); the hand-typed name, operator 60x36 sheet and the master view's removal were made outside the app's buttons -- most likely Claude by hand on Jordan's circled screenshot; the chat from that afternoon is not on record, so not 100%. PROPOSAL (awaiting go): 'Parts found' review step on every upload that splits -- one row per distinct shape (code: partgroups), count, picture, keep/remove tick; confirm builds the list with qty = count; nothing decided for the operator. | 2026-10-29 JORDAN rejects the Parts-found card: 'no clear path to audit the source file after uploading'; 'part 91 doesn't help me build a program'; 'how do we take a file like this, establish what is needed and what's not, and build a parts list that takes the workload off the operator?' PROPOSAL 2 (awaiting his read): a TRIAGE view on the drawing itself -- every found part outlined in place on the source, coloured by identical-shape group with a label (A x6), the engine's keep/leave-out proposal drawn on the sheet with its reason in shop words (inside the border with the title block, carries dimensions, a frame, text-only); click any part on the drawing to flip it; one button builds the list, qty = copies kept. Rules are evidence on the drawing, never 'not repeated' alone. To measure before building: which evidence separates Camp-4's master view (frame + angle dimension) from its 90 copies, across the 75-sheet corpus. | 2026-10-29 JORDAN: 'closer, but my gut says this may be a band-aid'. Claude's read: it IS one if it lands as another view on top of today's intake roads (sheet detect, Pick views, chunk (c), Fix B block, split, one-road, Nest these parts, sheet window, O62, O64 -- each patched for one file). The non-band-aid is ONE sheet model: the engine labels everything on the file once (part, hole, reference view, dimension, border/title block, text) with its evidence; every door reads it; the triage view only shows it. Asked Jordan to walk Camp-4 as an operator would by hand so the rules come from his process; truth-labelled fixtures from his files. | 2026-10-29 Jordan's Camp-4 walk (the old CAM today): a) printout of source beside him; b) upload; c) band-select borders + text, delete; d) recognize 15 variants x 6 copies = customer qty; e) copy one of each into its own new part, name each by hand; f) toolpath + save each .pdg; g) new nest, add the 15, assign qty, nest/post/deliver. 'Great deal of labor, but nothing is easily missed.' Q2 one-sheet-model: 'I think so, not sure exactly.' Claude mapped it to rules: R1 set aside border/title block/text/dims with evidence; R2 closed outlines + holes = parts; R3 group identical shapes, count = qty; R4 a view carrying dimensions = reference view, flagged not cut; R5 reconcile -- every entity in exactly one bucket, totals shown (the 'nothing missed' check vs the printout); R6 corrections recorded. Steps f/g already automatic. Proposed step 1 = measure only (Camp-4 truth 15x6=90 + master view out; then the 75-sheet corpus), no app change. Asked Jordan: mirror copies same group?; is a dimensioned view ever cut?; qty seed = copies drawn?; auto names A,B,C renameable?; go on measuring. | 2026-10-29 Jordan: a dimensioned view CAN be a cut part (Claude's R4 'dimensioned view = reference' was wrong, owned). Jordan keeps coming back to a separate Source CAD tab: a truer view of the file than Geometry's Source mode, select a feature and say keep / leave out, as in the old CAM; more labor but less error-prone; losing faith it can be mostly automated; invited holes in his logic. Claude's reply: agree on the tab as the operator's door; holes = by-eye counting of 91 shapes is itself error-prone, and pure manual costs every file; proposal = Source CAD tab where the engine pre-marks only what is provable (entity type text/dimension/hatch, identical-shape groups + counts, open vs closed) and NEVER guesses intent (which view is a part, border vs part) -- operator decides those; tally of every entity; part list built from the marks. Faith loss traced to silent decisions in patched roads, not automation itself. Questions: tab for every upload or only drawing sheets; what Source mode is missing for him; go to mock up (no code). | 2026-10-29 Jordan: (1) same tabs, same order, same function on EVERY job -- no scenario treated differently; (2) Source mode lets him look but not decide what is missing/extra for the Part list, hence a separate tab; (3) no mock-up yet, talk more; the solution must enhance what's built, not break it. Claude's proposal (discussion only): a Source tab first on every job (tabsFor today: Part list, Geometry, Tooling, Nest, Quote, Post, Deliver); shows the file as drawn incl. text/dims/hidden layers; click/band-select Keep / Leave out; engine pre-marks only provable facts, shown with reasons; like shapes grouped + counted; tally. Its output = the kept set handed to the EXISTING part-list builder; everything downstream unchanged. No-break proof: on the whole corpus, 'accept the suggestions' must give the same part list as today. Intake guesses (Pick views etc.) retire one at a time as Source covers them, each proven. Open: tab position; edits after list built (untouched rows keep their work?); stored jobs read-only?; does the Part list fill straight from suggestions (warn, never block) or wait for a confirm. | 2026-10-29 Aristide: have SPEED review the final proposal, since speed already built much of this. Found: pin source-truth-view work (whole-original source mode, filter panel, click inspector, measure/print, tag-and-flip chunks 1-2 with source.dxf.flips.json) is already in main -- the Source-tab proposal should build on it; Claude had not tied it in (owned). Gap vs today: flips change one job's cut, not part-list rows/grouping/qty. Memo written: docs/memo-to-speed-source-tab-2026-10-29.md, copy /home/cloudally/kerf-onums/MEMO-TO-SPEED-source-tab.md, relayed by Aristide/Jordan. Waiting on speed's reply; nothing built. | 2026-10-29 Jordan to Aristide: nowhere near building; he asked Claude to poke holes; nothing built without both. Camp-4 layer census (raw DXF): Visible = 1729 LINE + 1729 ARC + 265 CIRCLE (all parts AND the master view); 0 = 180 CIRCLE, 15 TEXT, 2 DIMENSION, 1 LEADER, 1 MTEXT; Border/Titleblock/DT_RENDER = INSERTs (+17 ATTRIB). Holes put to Jordan: layers clear the border in 2 clicks but not the master view or grouping; keep/leave-out on lines is not 'make a part, qty 6'; Source decisions must sit on raw entities before heal; drawn copies != ordered qty always; a confirm step on every clean job is a cost; the tally beats a printout. Idea offered: per-customer remembered choices (e.g. layer Border always out) as seeds, recorded, overridable -- not AI. 180 layer-0 circles + 15 texts not identified yet. | 2026-10-29 Jordan: ideal = band-select features to include/exclude; humans can't compare/count customer nests -- that's where code automates; 'how do we unite these two?'. Per-customer layer memory = band-aid (dropped). Reading Camp-4's layer-0 texts/circles = fitting one scenario (dropped). His shape: automate the Part list from current builds; operator views source and includes/excludes features to add/subtract rows; identical features counted as one part with qty. Claude agreed and proposed the union: (1) automation unchanged builds the list; (2) one general rule: identical shapes = one row, qty = count (partgroups code exists); (3) two-way link -- click a row, its copies light on the source; click a feature, its row lights; (4) band-select include/exclude adds/subtracts (match = qty +/-1, else new row / row gone); (5) tally; (6) a rule the operator keeps overriding is evidence to fix it generally, not a per-file patch. Open to Jordan: mirrors separate; own tab or in Source mode; qty change keeps tooling; go to write a chunked plan (no code). | 2026-10-29 Jordan: band-selecting the master view on the Source side -- does it also take it off the Part list? Claude: yes, both directions are one decision; band select = only shapes fully inside the box (crossing-select open); excluded shape = qty -1 on its row or row removed, recorded, undoable. Owned: the '16 rows' example assumed the master view differs from the 15 variants -- not measured; if it matches one, that row shows qty 7 and excluding it brings it to 6. | 2026-10-29 Jordan RULING: mirror-image copies are separate parts by default (they exist in many contexts). Tab placement: no answer yet, still discussing; the next build must settle this once and for all and only enhance, never break. Q3 (keep tooling on qty change) not understood -- re-explained. Plan write-up: 'not there yet'. Next detail offered for discussion: what counts as identical (rotated copies, tolerance, holes must match). | 2026-10-29 Jordan RULINGS on 'identical': rotated copy otherwise identical = identical; mirrored = different; differs by a hole = separate; close enough = within the healing tolerance. Q3: Jordan didn't follow why a qty change would touch tooling -- Claude agreed there is no reason (tooling belongs to the part, qty only changes the nest), withdrew the question, and owned that 'some list changes rebuild rows' was said without checking. | 2026-10-29 Jordan asked for the most logical build proposal (proposal only, nothing built). MEASURED first: run_partgroups (read-only) on dev's O64 Camp-4 split camp-4-test-patterns-final-20260915-1793312074: 16 groups = 15 x 6 + master view (part 91) qty 1, 3.0s, tol 0.005; split_parts.congruent_parts already = Jordan's rulings (rotation same, mirror never, all contours + positions); split children carry lineage.entities (source entity indices) + shift = the two-way link data already exists. Gap: PART_MATCH_TOL fixed 0.005 vs Jordan's 'within healing tolerance'. Proposal = connect existing pieces, no new road: A) upload list groups identical parts (one row, qty = count, tolerance = job heal tolerance); B) two-way highlight row<->source via lineage; C) Include/Exclude by band select on Source or on the list, edits membership/qty, recorded, no re-split (tooling kept); D) tally; E) retire old intake special cases one at a time, each approved and corpus-proven. Tab placement left open; speed's review still outstanding. | 2026-10-30 SPEED'S REVIEW of the Source-tab proposal (speed O66; kerf-onums/MEMO-TO-DEV-source-tab-review-2026-10-30.md; relayed by Aristide; read + measured, nothing built): build on the flip file (source.dxf.flips.json via dxf_io._flip_rules/entity_ordinals, run_flip) -- source never edited, heal caches already key on it; draw with sheet_draw.draw (Camp-4 3,925 shapes in 0.13 s); grouping nearest = sheet_intake.clusters + view_copies; missing = flip rules -> per-shape kept/left-out answer for the tally. Speed cost: every flip re-runs the pipeline ~15-16 s on Camp-4 -> save marks as a draft, tally from the drawing, run the pipeline once at 'done'; re-check only changed groups; single-part upload must not slow (speed times F1, d16, 44556b). Holes: 'identical' must be a real geometric match (view_copies is count/size/linetype only); INSERT blocks can't be marked today; marks belong to the original upload; kit = one Source per file or one per kit?; customer qty vs drawn copies -> show both, operator picks; undo per mark + one at done; no-break proof adds speed's 6 nest kits (d16, 3347aa, CAMP, F1, 44556b, 302270). Lanes: Source is dev's; speed times and runs the kits on request. DEV NOTE: proposal A already uses split_parts.congruent_parts (rigid geometric match, all contours) not view_copies; Jordan already ruled rotated = same, mirrored = different (speed suggests asking each time -- for Jordan). Aristide 2026-10-30: wait for Jordan's own decisions on Camp-4; nothing built. | 2026-10-30 JORDAN RULED on proposal A-E + speed's review: A (group identical copies) agree. B (two-way highlight rows<->drawing) try it, ready to roll back if not liked; goal: no extra tab when not needed. C (box-select include/exclude) agree. D (tally) yes. E (retire old special cases) only after B is approved. Rotated/mirrored: build BOTH behaviours (same-part rule and ask-each-time), chosen by a customer-set preference. Quantities are input by the operator (customer qty vs drawn copies not auto-decided). Build order and start still to confirm with Jordan. | 2026-10-31 JORDAN RULED (answers 10-12 of the numbered list): 10+11 identical copies in the same drawing raise that row's quantity (qty seed = copies drawn), EXCEPT when the drawing states the quantity in text -- then the drawn count does not set it. 12 rotated = another copy of the same part; mirrored = a different part. Asked back: does a stated text qty become the row qty (with a warning when it disagrees with the drawn count); does 12 replace the 2026-10-30 'build both, customer preference' ruling; go on building A. Nothing built. | 2026-10-31 JORDAN: (1) a stated QTY in the drawing text is the row's DEFAULT qty; an operator change must NOT warn -- 'the human operator will have more context than the software'. (2) rotated/mirrored as a TOGGLE in the UI. (3) likes A but wants more details before anything is built. Details sent: grouping math exists (split_parts.congruent_parts, run_partgroups read-only, Camp-4 16 groups in 3.0 s); new = use it to build rows, tolerance from job heal tolerance (today fixed 0.005), a qty-text reader (none exists today; binds only when the note clearly belongs to one part; exploded text unreadable -> drawn count), the toggle; ramifications + proof plan; asked toggle meaning, whether to show drawn count beside a stated qty, go. Nothing built. | 2026-10-31 JORDAN: (1) toggle agreed: 'Mirrored copies count as the same part', off by default, one per job. (2) DRAWN COPIES OVERRULE A TEXT QUANTITY (text can be misread or bound to the wrong part; the operator verifies qty anyway) -- replaces his earlier 'not when a drawing states qty'. Asked back: one drawn copy + 'QTY 6' -> 6? (3) asked how A handles Camp-4. MEASURED for the answer (read-only, dev job camp-4-test-patterns-final-20260915-1793312074): 91 split parts -> 16 groups (15 x 6 + master view x 1) at BOTH 0.005 and 0.010 tolerance, 3.0 s; Camp-4 has 30 texts, none a quantity (title block, 15 labels 46.25..49.75, one 48.0 deg, START/STOP POINT). Nothing built. | 2026-10-31 JORDAN asked: what does the operator see, and in a KerfMaster-only shop at what point do they see the file the customer actually sent? and: make MERGE tolerance and HEAL tolerance two separate settings. Answered from the code (not a fresh click-through): today the original is only in Source mode (S) on a part's Geometry tab (a split part shows the customer's whole drawing, srcOrig), never on the Part list; under A the same; B (drawing beside the list, row<->copies highlight) is where the operator would see it at upload. Separate merge tolerance: yes, per-job setting beside the mirror switch; asked default (0.005 today vs 0.010) and whether B should come with A. Nothing built. | 2026-10-31 JORDAN RULED: (1) MERGE TOLERANCE default 0.001 in, its own setting separate from heal tolerance, easy for the operator to change. (2) A and B built SEPARATELY. (3) one drawn copy + text 'QTY 6' -> row starts at 6. MEASURED: Camp-4 still 16 groups (15 x 6 + 1) at 0.001 / 0.002 / 0.003, 3.0 s. Proposed A in two chunks: A1 grouping + merge tolerance + mirror switch; A2 the quantity-text reader. Awaiting go. | 2026-10-31 BUILT A1 (Jordan 'Go on A1'): identical copies drawn in one file share ONE Part list row, qty = copies drawn. New door POST /api/jobs/<list>/mergecopies {tol, mirror} (server.run_mergecopies; split_parts.group_congruent gains mirror=, mirror_prims, MERGE_TOL_DEFAULT 0.001). Only split children of the SAME drawing merge; separate files, sketches, windows never. Rotation = same part; mirror switch per list, default off. Upload road (roadGroup, tray + single upload) calls it once after the rows land when the list has 2+ rows. Part list shows 'N drawn' on a merged row plus a merge tolerance box and the mirror switch (lists born from a multi-part drawing only); changing either regroups; an unsaved list is never overwritten (save first). Operator qty kept when a row's copies don't change; a regroup that changes a row's copies sets it back to the drawn count and names it. Merged copies stay jobs in the group (partlist.json merge.members), never re-join as rows (list-join skips them); a list save keeps the merge record. Stored lists untouched (no merge record = no box, nothing changes). Proved: Camp-4 via the real upload road on scratch -> 16 rows 15x6+1, merge 0.001 mirror off, ~237 s whole upload (91 parts healed; grouping ~3 s); idempotent; regroup apart -> 91 rows and back -> 16; list-join returns None for a merged copy; mirror on and tol 0.0005 both stay 16; single-part lists skip it. Identity gate green. F1 first click 8.56/7.92 and 8.58/7.88 s vs baseline ~8.45/7.8 (run_plassign untouched). Not run: speed's 6 kits (nest engine untouched, their lists carry no merge record). Dev restart needed for the engine half. | 2026-10-31 O67 Camp-4 A2 BUILT (Jordan 'Go on A2'): new qty_text.py reads a quantity only when a quantity word sits beside the number (QTY 6, QTY: 6, QUANTITY 6, 6 REQ'D/REQD/REQUIRED, 6 PCS/PIECES, 6 OFF, MAKE 6); 6X hole counts, dimensions and texts stating two quantities read as nothing. Binding: a one-part file takes the sheet's qty when every statement agrees; on a sheet of parts a note binds only on/right beside one part (within 1 in or 4 text heights, next part at least 2x as far) -- placed via each split copy's lineage shift in the parent's annotation frame. server.run_mergecopies seeds a row's qty from it ONLY when one copy is drawn (drawn count overrules text), once: partlist.json qtytext {row: {qty,text,x,y}} marks it, run_partlist keeps it, so the operator's number is never re-seeded. Unbound/conflicting statements returned as textnotes and written to the list's upload notes. A one-part list gets no merge record (no merge box). Client: roadGroup now calls mergecopies for 1+ rows; a seeded row shows 'drawing says "(6) REQ'D ..."'. PROVED: test_qty_text.py 34/34 (reader, binding, Camp-4 control 16 rows unchanged with no qtytext, planted QTY 4 beside the master view -> 4, QTY 9 beside a 6-copy part -> 6, far note said, re-run no change, operator 2 kept through a list save); scratch road: 78017D02A '(6) REQ'D' upload -> qty 6 + tag; corpus sweep 1275 dev jobs: 24 with qty text, 9 seed, 15 (23004 multi-release REL lines) none used. LIMIT: an extracted drawing-sheet view carries no annotation texts, so its '(N) REQ'D' is not read (23004 via the road stays 1, no note) -- follow-up offered. Identity gate green; F1 n/a (upload/list door only). Dev restart needed for the server half. | O68 Camp-4 A3 built (Jordan 2026-10-31 'Yes, go on A3'): an EXTRACTED drawing sheet (zero-click or manual extract) now has its quantity text read -- server._extracted_sheet_texts(jid) reads the preserved drawing.dxf texts (sheet_draw, title-block attributes included) and _qty_text_seeds adds them on the one-part road (bind's one-part rule: all statements must agree). Disagreeing release lines (23004 REL B/C/...) -> qty stays 1 with the plain note 'the drawing states more than one quantity ... none used' in the upload notes (the silent gap closed). Not covered (still): sheet windows (manual sheet road, window_from) and split copies of an extracted sheet -- their texts belong to a wider sheet; unchanged. Proof: scratch road fresh uploads -- 23004-700 (REL I: (3) REQ'D) -> qty 3 + tag; 23004-344 (5 release lines) -> qty 1 + note; F1-RELEASE LV00151 -> 1 + tag; 78017D04A (not a sheet on upload, A2 road) -> 12 unchanged. Corpus read of 111 stored sheets: 22 carry quantity text: 7 single statements bind (6 sheets, 5 of them at qty 1, plus 78017D04A at 12 on the A2 road), 15 multi-release stay 1 with a note; ~30 ms per sheet, read once at upload. test_qty_text 37/37 (+3); test_sheet_window 27/27, test_sheet_intake 98/98, test_srcsheet 6/6, test_sheet_dimpart 19/23 (same known failures 2,3,4,23); identity gate green; F1 n/a (upload road only). Rollback tag pre-campA3. | 2026-10-31 Jordan on A3 Q1 (release lines setting qty, e.g. REL I: (3) REQ'D -> 3): "I think no" -- release lines should not set the starting qty. Not built yet: next chunk = qty_text ignores REL/RELEASE lines (also hits A2 plain uploads like 'B1 RELEASE : (1) REQ'D'); proposal + ramifications first, build on a go. Dev restarted 2026-10-31, A3 live on dev. | 2026-10-31 Jordan on B (source drawing beside Part list): (1) multi-file lists show one drawing at a time with a picker; (2) a merged row lights all its copies; (3) set-aside ink shown faded grey, and the operator can select a faded entity and include it as cut geometry (problem CAD files); (4) drawing always shown beside the list; (5) old lists without placement info just say no drawing link. Proposed split: B1 = view + two-way highlight + faded ink; B2 = include-from-beside-the-list via the existing srcflip door (needs re-split handling). Plan sent, awaiting go. | B1 BUILT 2026-10-31 (Jordan 'Go on B1'): the original drawing beside the Part list. New read-only door GET /api/jobs/<list>/pldrawing[?root=] (server.pldrawing_state): one drawing at a time in the file's raw frame, rows -> entity ordinals from each part's lineage (merged rows carry every copy's), aside = every drawn entity no listed part uses with the reason (read routing / annotation type / not on this list), nolink rows listed; cached on mtimes. app.js: Part list tab canvas draws the drawing (plDrawOn/drawPlDrawing) with a Drawing/Part switch (Part = old single-part preview), picker for multi-file lists, selected row lit, click a part -> its row selected + scrolled into view, hover names the row or why it was set aside, faded grey dashed set-aside ink, 'no drawing link for this list' on old lists. Not built: the draggable divider (Jordan has not confirmed it; panels already float/resize). Measured: Camp-4 91/91 rows mapped, cold 0.26s / warm 0.02s, 1.25 MB; read-only sweep of 154 stored dev lists: 0 crashes (1 junk id), worst 0.28s, 34 lists say no link, 3 multi-file. Browser test on scratch copy of newb1 multi-file list OK; Camp-4 browser screenshot still to check. Touches: screens + one GET door only; no nest/post/G-code/stored-list change. Identity gate green. F1 n/a (no hot-path change). server.py changed -> dev restart needed (ask first). Rollback tag pre-campB1. | 2026-10-31 Jordan tested B1 on dev after the restart: 'B1 is awesome.' He asked where B2's include/exclude lives (Geometry or Part list) and whether it already exists. Answered: it exists today only per file/part (Geometry tab, Source mode: srcflip rules by layer/colour/type/banded entities, server.run_srcflip, sidecar source.dxf.flips.json); not from the Part list's drawing on a sheet of parts. Proposed: B2 = buttons on the Part list drawing that write the SAME flip rules (no second mechanism); a line inside one part's area goes to that part only (no re-split); a line outside every part = a new part, which needs a re-split that keeps qty/merge choices. Waiting on his answers; nothing built. | 2026-10-31 Jordan B2 rulings: (1) include/exclude lives on the Part list drawing (agrees; Geometry tab Source mode unchanged, same flip rules underneath). (3) Yes -- excluding (cutting line -> set aside) is in the same chunk. (2) asked how new-part works ('select the geometry and right-click -> new part?'). Answered/proposed: yes -- click or box-select on the drawing, right-click 'New part from selection'; the selection becomes ONE new split child of the same parent (lineage entities = the selection, same split road) appended as a new row qty 1; existing rows, qty and merges never touched (no whole-sheet re-split); open outline = warn + show gaps, existing close offered; lines already in another part = warn naming the part, operator picks move or copy; a shape matching an existing row offers merge (A1), never automatic; undo removes the row and child. Also right-click 'Add to part N' (default = part whose area holds it) and 'Set aside'. Waiting on his answers; nothing built. | 2026-10-31 Jordan B2 answers: (1) yes, the new-part flow as proposed; (2) a line shared with another part MOVES by default (never cut twice); (3) one at a time -- each action its own chunk. Proposed order: B2a Set aside, B2b Add to part, B2c New part from selection. B2a plan sent (right-click on a lit line -> Set aside, writes the existing srcflip entity rule on that part's own file, the part re-runs as any edit does, list goes stale as today; first check = map original ordinals onto the part's split-out file ordinals). Waiting on go; nothing built. | 2026-10-31 Jordan asked why 7498 (list 7498-1793463525) is not treated like Camp-4. Checked GET-only on dev: same road (parent split into 5 parts, list of 5 rows, Drawing view opens, 5/5 rows linked, 0 aside). Differences are in the file: no dims/text/title block so no drawing-sheet warning; no $INSUNITS so units inferred (inch, extent 33.2) and flagged to confirm; 3 colours (ACI 5/1/3) all cut, mixed inside every part, colour question open. Asked Jordan what he saw differ. Nothing built. | 2026-10-31 Jordan: expected to see the source file like Camp-4; sees no colours in his software. Checked GET-only: dev link #job=7498-1793463525&tab=partlist opens on Drawing with the source shown (screenshot). The Oct-1 list '7497 + 7498' (7497-7498-1789846532) has no drawing link (parts split before lineage existed) -- likely what he opened, or a cached old app.js. Colours: every line carries its own colour (ACI 5/1/3) on layer 0; his software likely shows by layer, so one colour; our colour question is noise for this file -- open item. Nothing built. | 2026-10-31 B2a go (Jordan) -- STOPPED at the planned mapping check, nothing built. The part's own file (what Set aside would flip) is NOT line-for-line the drawing: the split writes each contour as one joined outline. Camp-4: 3903 drawing lines -> 627 part contours, 445 one line = one contour, 182 contours built from several lines. 7498: 1449 lines -> 85 contours, every one built from many lines. Whole-file rows (newb1 multi-file) map exactly. Proposed to Jordan: (A) Set aside works per contour -- pick a line, the whole hole/outline it belongs to lights and goes aside on that part; (B) per-line aside via the original + re-split -- rejected, it rebuilds every row. Waiting on his pick. Tag pre-campB2a set, no code touched. | 2026-10-31 Jordan: option A 'makes sense'; asked if a wrong heal join can still be fixed by hand in Geometry -- answered yes (delete segment / delete, close gap, drag end, add line, weld, fit arc on that part's Geometry tab; per-part, replayed, undoable; not through Set aside). Re-asked for the go to build A. | 2026-10-31 B2a BUILT (O69, Jordan "Go with build A"): per-contour Set aside from the Part list drawing. Server: _pl_contour_map(part) maps the part's lineage drawing lines onto its own file's contours (densify 0.05, vote within 0.02, majority; root drawing read cached) -- Camp-4 3,903/3,903 and 7498 1,449/1,449 lines map, 0 unmapped; all 91 Camp-4 rows 2.65 s, one row 0.03 s. New read-only GET /api/jobs/<list>/plcontour?row=&ord= returns the whole hole/outline (child contour, its drawing lines, kind, aside, flip row). pldrawing drops set-aside contours from the row, names them aside "you set it aside on row N -- right-click it to put it back", returns `flipped`, and keys its cache on each part's flips sidecar. Set aside / Put back go through the PART's existing srcflip door (by entity, one contour; remove k) -- same rules, journal, only that part re-runs. Client: right-click a drawing line -> its whole contour lights blue, menu "Set aside this hole (N drawing lines)" / "outline -- the part's outer edge" (warn, never block) / "Put this hole back" / "Open this part's Geometry"; set-aside contours draw orange dashed; refresh keeps the zoom (also fixed: row-thumbnail refresh re-fitted the Drawing view). Whole-file rows answer "set lines aside in its Source view". Tested on scratch :8479 with copies only: 7498 row 1 slot (12 lines) set aside -> put back, geometry.json identical, only that part's folder written; Camp-4 part 1 hole 47->45 healed items, outline set aside allowed (47->35), put back identical, other rows unchanged; screenshots checked. Ramifications: server.py + app.js (shared with speed, memo follow-up 21); other rows, stored jobs, upload doors, nest/pack/post code untouched; a pack already made keeps the old shape until re-packed/updated (toast says so -- same as a Geometry edit today). F1 n/a (new door + screen). Identity gate green. Needs a dev restart to go live (server.py). | 2026-10-31 dev restarted on Jordan's 'restart' (both inflight 0): B2a live on dev; GET plcontour answers 200 on 7498 (slot = 12 lines, hole). Identity gate green. | 2026-10-31 Jordan 'Describe B2b' -- described, nothing built. B2b = right-click a line on the Part list drawing that is not in the selected row's part -> 'Add to row N'. Two ways proposed: (A, recommended) rebuild that one part's file from its drawing lines + the added ones through the same split road it was cut by (heal joins/fits the new lines like the rest, fidelity measured, lineage updated so the drawing lights it; same machinery B2c New part needs); cost: the part's file is rewritten, so its B2a set-asides are re-mapped by drawing line and its point-addressed Geometry hand edits replay and may skip with a warning; (B) add the lines as Geometry add_line/add_arc hand edits on the part: nothing rewritten, but added ink skips heal joins and fidelity, splines/polylines must be broken up, drawing lighting needs a separate map. Questions to Jordan: 1 A or B; 2 a line already in another part moves its whole hole/outline (the B2a finding) -- that part re-runs too; 3 addable = loose lines + lines the read set aside (dashed/colour/hidden layer -- adding means cut it); text/dims/hatch never; 4 a line far from the part warns (part gets bigger), never blocks; 5 one hole/outline/line per right-click now, box-select stays chunk C. Ramifications named: the one or two parts touched re-run, a packed nest keeps the old shape until re-pack/update, part size can grow, other rows/stored jobs/upload doors/prod output untouched, F1 n/a. Waiting on answers. | 2026-10-31 Jordan B2b rulings (ruling): (1) way A -- rebuild the one part from its drawing lines + the added ones through the split road; (2) a line already in another part MOVES (with its whole hole/outline), expected in files so bad the healer is ambiguous; (3) ANYTHING can be added, text included -- 'not for the software to decide' (so this door does not apply the srcflip annotation refusal _FLIP_NEVER_CUT); (4) no far-from-part warning -- the operator sees it; (5) build however, as long as box-select (chunk C) comes. Found on checking: no text-to-cut-geometry exists today (sheet_draw keeps TEXT/MTEXT as position+string; the screen draws it with a browser font), so adding text needs a new letter-shape step -- proposed as its own later chunk (B2b-text), with the questions single-stroke etch vs outlined letters and which font. Proposed B2b build: lines, arcs, circles, polylines, splines, ellipses, and the lines inside dimensions/hatches/blocks. Waiting on go; nothing built. | 2026-10-31 Jordan: text to usable primitives isn't part of this build -- new intent pin text-entities-to-cut. B2b go still to be confirmed (asked). | 2026-10-31 B2b BUILT (O70, Jordan 'Build B2b'): Add to part on the Part list drawing. Right-click any drawing line (ink too: dimension/hatch/leader) that is not in the selected row's part -> 'Add to row N'. Engine POST /api/jobs/<list>/pladd {row, ords} (run_pladd): the row's part file keeps every contour byte for byte (_shop_split/_shop_join, 96/96 Camp-4+7498 part files round-trip identical) and gains the picked items as more contours in its own frame; an item in another row's part MOVES with its whole contour (B2a contour map) -- donor file loses that block, its single-contour entity flips renumber, both lineages update, donor re-runs; an item in no part is read from the original on a scratch copy through the normal reader (entity flips set every other entity aside; true arcs stay arcs; splines/ellipses as dense chords for the part's own heal), dimension/hatch ink rides as its drawn lines; TEXT named back as not built (pin text-entities-to-cut). Only target + donor re-run; journalled as one undo step (door pladd, heavy). _pl_contour_map now also votes ink chains (no change for existing lineages: they hold line entities only). Client: plDrawHit + drawPlDrawing include ink; plAsideMenu adds the Add item; plAdd refreshes the drawing and the two thumbnails, keeps the zoom. Tested on scratch copies only: 7498 row-1 slot (477, 12 lines) moved to row 2 (33->32 / 6->7 contours, geometry vote lands, row-1 set-aside flip 27->26 still on the same hole, ~12 s for two re-runs); Camp-4 dimension 48 added to row 1 (lit with the row); undo restored every file byte-identical. Ramifications: server.py + app.js (shared with speed, memo 22); only target/donor parts rewritten; a packed nest keeps the old shape until re-pack/update; merged copies of a row are not changed with it (unmeasured); hand edits replay as always. Identity gate green (1.3 s). F1 n/a (new door, no hot-path change). Rollback tag pre-campB2b. | 2026-10-31 dev restarted on Jordan's OK (both inflight 0 before): B2b Add to part (O70, d2d844a1) live on dev; app answers 200, pladd door answers. | 2026-10-31 Chunk C box-select BUILT (O71; Jordan 'Go on Chunk C'): on the Part list drawing, shift-drag a box picks drawing items -- the global band rule (left to right = wholly inside, right to left = anything it touches), a shift-band adds, a small shift-drag toggles one, Esc or a plain click on empty space clears; the pick draws magenta dashed. Right-click on the pick: 'Add N items to row X' (the B2b pladd door, many ords; lines in other parts move with their whole hole/outline), 'Set aside every hole or outline these touch (rows ...)' and 'Put back the N set-aside lines' through NEW door POST /api/jobs/<list>/plaside {ords, to:'aside'|'cut'} (server.run_plaside): writes the same single-contour entity flip rows B2a writes, per row, each row touched re-runs ONCE, one journal step = one undo; outline set aside is named back (warn, never block); a row whose re-run refuses keeps its old flips and is named while the others go ahead. Tested on scratch copies only: 7498 window+crossing pick (6 items) -> rows 1 and 2 set aside in one call (~11 s), row 1's existing flip 27 kept, put back restores the flip lists exactly, outline warns, repeat refused in words; browser test via the menu; one undo restored all 44 files of the 7498 jobs byte-identical. Ramifications: new door + screen only; single right-click B2a/B2b menus unchanged; no upload door, nest, post or stored job touched; merged identical copies still change only the representative part (same as B2a/B2b). Identity gate green. F1 n/a. | 2026-10-31 dev restarted (Jordan 'ok to restart'; both inflight 0 before), chunk C box-select (O71, 1cbbec12) live on dev: service active, plaside door answers (bad 'to' refused in words; the refusal wrote nothing, undo stack top unchanged). Identity gate green. | 2026-10-31 B2c New part from selection built (O72, Jordan 'Go on B2c'; tag pre-campB2c): new door POST /api/jobs/<list>/plnew {ords, lines 'move'|'copy', root} (server.run_plnew, helper _open_gap; in UNDO doors + UNDO_HEAVY + route list + dispatch). Picked drawing items become ONE new split child of the same parent (framed like its siblings: the parent's frame shifted to its own lower-left; units-pinned; job.from_selection recorded; parent split.children gains it with from_selection) and join the list by the one-road rule as a row, qty 1 (forced in with a note if its heal does not finish). Lines already in a row's part come with their whole hole/outline (B2a contour map); the operator picks move (donor file loses the contours, its single-contour flips renumber, its lineage drops them, it re-runs) or copy (donor untouched); neither said = refused in words naming the rows, nothing written. Lines in no part come from the customer's original (arcs stay arcs; TEXT named back). Warnings, never blocks: open outline (count + the gap that would close it) -> screen offers Close gaps (appends a close_gaps row through the part's own healedits door, its own undo step) or open the part's Geometry; a row from the same drawing whose part matches (split_parts.group_congruent at the list's merge tolerance/mirror) -> screen offers Merge (the list's mergecopies at its last setting). A packed nest drops (the stale rule). One undo removes the row, the part's files and any move; leaves only an empty unlisted folder holding a .lock. Client: plNewItems/plNew/plNewMerge/plNewClose; menu items on the box-pick menu and the single-line right-click menu. Tests on scratch copies (7498, Camp-4): no-choice refusal; copy of all of row 2 -> row 6, row 2 bytes unchanged, same bbox, match on row 2; move of one row-1 hole -> row 1 flip 27 renumbered to 26; Camp-4 dimension/leader ink -> 12 open outlines, gap 1.8273 reported; scratch server POST move + one undo -> all 44 7498 files byte-identical; browser box-pick -> copy -> row 6 qty 1 + merge offer shown. Not re-run: the B2b/C browser tests (their code paths untouched). Copied lines sit in two rows; the drawing's click finds the first. Identity gate green. F1 n/a (new door, screen only). | 2026-10-31 dev restarted (Jordan "Ok to restart"; both inflight 0 first): B2c New part from selection (O72, 00f10bf9) live on dev; kerfmaster-app active, plnew door answers (probed with a made-up job id only). Identity gate green. | 2026-10-31 JORDAN RULED: D (tally) dropped -- "I don't see the point of D." Not built. Jordan then: "we are ready to merge Speed and Dev" -- asked what is missing first; answered (dry-run merge of speed into main: no text conflicts; speed 70 commits / main 91 apart; speed has uncommitted machine_tables.json + shop.json edits; checks owed after merge), nothing merged yet. | 2026-10-31 Aristide: speed runs its own pre-merge check like dev's; dev holds ("Hang tight"). No merge from dev until told. | 2026-10-31 SPEED MERGED INTO MAIN (Aristide: 1 go, 2 yes, 3 speed stays): speed merged main in first (92c10eec, 0 errors its side); dev re-checked it on a /tmp worktree (identity gate green, B2c engine test same results, app.js syntax ok); main fast-forwarded to 92c10eec (71 speed commits, 20 files; no tables/shop/golden/job files), rollback tag pre-speed-merge-2026-10-31 (= cf9fb16d). Identity gate green on main. Both inflight 0, dev restarted: active, plnew answers (made-up id), diag: audit/pack/clear native loaded. Prod deploys via kerf-mirror ~4 min. Speed stays a separate lane. | 2026-10-31 OPEN (Jordan asked why BNM78598's 8 copies stayed 8 rows): measured on dev job bnm78598-...-1793478984, merge tol 0.001. (1) all 8 copies have 43 closed shapes, same 50.4074x12.8234 outline, closed shapes match each other within 0.0026-0.0042in (10-32 of ~14,700 sample points over 0.001), but the healed copies are built from different arc/line pieces (1,158-1,198 prims) and congruent_parts' per-piece signature pre-check rejects them before any distance is measured -- so no tolerance setting can merge them today. (2) loose open lines differ: 19-21 per copy; copy 1 has a 14.738in and an 8.822in line that copies 2,3,4,5,8 lack (6,7 have the 8.822). Whether that is in the drawing or from our cleanup: not yet determined. Fix options offered to Jordan, nothing built. | 2026-10-31 BNM78598 SOURCE check (Jordan: 'compare the source for matching instead of the healed geometry'): the drawing's 20,215 source entities split cleanly into the 8 copy cells (0 orphans); copies are built from different piece counts (2,169-2,909; 998-1,985 lines, 920-1,171 arcs) but every copy matches copy 1 within 0.0005in both ways (0 of ~19,500 sample points per copy over 0.001), bend lines included; each copy's source extent 50.4000 x 12.8234 (healed parts read 50.4074 wide -- not yet explained). So the 8-row split and the uneven loose lines come from our cleanup, not the drawing. Jordan's question 'less processing if only one copy is healed': in principle yes (today the whole drawing heals once before the split, ~27s); doing it means finding copies on the raw source before heal -- offered as a plan, nothing built.
- •COMPETITOR RESEARCH -- Pep Technology and Striker Systems: products, forum talk, strengths, weaknesses, demo questions (Jordan, 2026-10-24, after FabTech Las Vegas) record — ASKED 2026-10-24 (Jordan, back from FabTech: Pep Technology and Striker Systems seemed the only ones attempting the problems we solve; research them, browse forums for what people say, strengths and weaknesses; he may get a demo of each). Research run started 2026-10-24; findings land here and in docs/competitor-research-2026-10.md. Internal only: per pin no-competitor-names-on-site, none of it goes on the website. | DONE 2026-10-24: research written to docs/competitor-research-2026-10.md (internal; vendor pages, Capterra, Practical Machinist, trade press; forum evidence very thin). PEP Technology (Irvine CA, since 1974): nesting yield, common line/band cutting, lead-by-sequence, 700+ posts, deep ERP; tabs keyed to table slats; its own benchmark page contradicts itself; quoted as pricey. Striker Systems (White House TN, since 1985, AutoCAD OEM): profile + punch, mixed brands, edit after nest; the 2027 preview (Sept 2026) adds a 3D simulation viewer and keeps manual nests. On their public pages neither shows a posted-NC audit, arc-true healing, floor tablets or browser delivery -- to confirm in demos. Top 5 demo questions are in the doc. Next: Jordan books demos (bring our dirty DXF + a mixed part list).
- •Nest view numbers must follow the POSTED cut order intent — DEFECT found by Jordan 2026-10-24 auditing nih-fixture on speed (O33421): the nest view's numbered boxes and rapids show placement order (1 = the big host), but the macro post cuts inside-out per its own part_order [6,7,8,9,14,19..27,0,...] -- the first G172X3.4098Y3.41 is the 4-disc array = boxes 7-10; the host (box 1) is the 15th piece cut. The G-code order is the safe one (nested parts before their host). Cause: app.js plOrderForSheet uses the clicked sequence, else placement index, and never reads plpost programs[].part_order; the same code is on main. Fix offered (awaiting go): number boxes and draw rapids from the posted part_order when a post matches the pack; else say 'order not posted yet'. | 2026-10-29 JORDAN: 'the numbers displayed in Nest need to reflect what's posted in the GCode ... If you agree with this, then yes, let's go with it.' -> GO. | 2026-10-30 DUPLICATE FOUND (dev, measuring for Aristide's merge question): speed already built this as O33 step 2 (speed commit 4f7fa864, _pl_sheet_order + GET /plorder + app.js plOrderForSheet). Dev does NOT build it; it arrives with the speed->main graduation. Proof it was about to be built twice.
- •40 social clip ideas (ranked) with scripts + storyboards record — 2026-10-28 (Aristide: top 40 short marketing clip ideas, numbered by importance, mini script + scene-by-scene storyboard, in Excel). marketing/clips/kerfmaster-40-clip-ideas.xlsx built by make_clips_xlsx.py (data in the script): sheet Ideas (40 ranked, top 20 marked to film first, hook/script/CTA/footage/claim check), Storyboards (155 scenes), Notes (format, the reference reel lesson, release rules). No competitor names. Hosted at https://clips.aristide.mycloudally.com/kerfmaster-40-clip-ideas.xlsx. Reference reels: the Facebook one is a laser machine maker's raw cutting footage (11K likes); the Instagram one needs a login, not seen. Open: Aristide's picks of the 20 to film.
- •Cut playback: animate the posted program cutting the sheet recordmixed — 2026-10-28 (Aristide: 'i want to build this feature, where it animates the cutting' -- reference Instagram reel needs a login, not seen; asked for a description). PLANNING ONLY, no go yet. Plan: (1) engine door GET /api/jobs/<id>/playback = the move list read back from the POSTED NC, macros expanded by nc_audit.expand_p9997/expand_g52 (plays what the machine will run, not the plan), each move rapid/cut/arc with pierce and tab gaps, time from table feeds marked estimate; (2) web player on the sheet view: play/pause, speed, scrub bar, glowing cut line + head + pierce flash, dashed rapids, parts drop as they close, part 'n of N', matching NC line shown; same renderer for web/Mac/PC; (3) export a vertical 9:16 video for social clips (canvas recording or headless render + ffmpeg); (4) polish: sparks, sound, 3D tilt. Ties to nest-numbers-follow-posted-order (the player shows the true order). New door, F1 n/a; engine part needs a dev restart; tell Speed. | 2026-10-28 reference seen (Aristide sent the reel as demo.mp4 via Box, 57s vertical): a plasma-table user films another web nesting app on a laptop. What it shows: one sheet, 17 parts; a scrub bar under the sheet; as it plays, each contour turns from yellow (to cut) to white (cut), in order; small cut-order numbers on every contour; dashed rapids; a toggle for pierce points and cut-direction arrows; totals line '586.7 ft cut, 33.1 ft rapid'; shared-edge (common line) note above. Voice: 'bakes everything into the nesting', 'use it on any computer'. Plan additions: per-contour order numbers, cut/rapid length totals, pierce + direction toggle; scrub bar first, real-time play second. | 2026-10-28 BUILT chunks 1+2 (Aristide: 'let's build it. it will need a Play button somewhere'). ENGINE: new cadmaster/playback.py walk(nc) -- the posted program copied to a scratch dir, unrolled by nc_audit.expand_p9997 / expand_g52 (the job's own files never written), walked block by block: G0 rapid, M98P<sub> pierce/beam on, G1/G2/G3 cut, M87/M121 beam off, a lone G52 applied, I/J incremental; moves [kind,x0,y0,x1,y1,line,feature,arc], listing, etch features, totals (cut/rapid inches, pierces, features). server.py GET /api/jobs/<id>/playback?sheet=N (playback_state): part-list post, then true-nest post, then single post; posted_at and stale (nest saved after the post); read-only, no lock. 528-pierce sheet: 0.36 s, 2.6 MB. PAGE: '▶ Play cut' button in the canvas bottom bar on the Nest/Post/Deliver tabs of a part list; the strip: Play/Pause/Replay, back to start, speed 1/5/10/25/100x (1x = 3 in/s, rapids at 4x, to scale not to the clock), sheet picker, scrub slider, X/Y readout + CUT/RAPID/PIERCE/ETCH, the G-code listing with the head's line lit (2 before, 4 after), 'pierce n of N, cut x of y ft, rapids z ft', the program name and post time, 'shown as the control runs it' when unrolled, a yellow note when the nest changed after the post. On the sheet: a veil, the cut line lit behind the head with a glow on the current move, dashed rapids, a pierce flash ring, the head dot. Opening slides the view so the sheet clears the strip; leaving the sheet tabs closes it; nothing is edited. TESTS: test_playback.py 15/15 (dialect on a hand-made program incl. G52 + full circle; 6 real posted programs, macro and G52 forms, every boundary plays once = the post's own count); verify_playback.js 18/18 on scratch; regression test_commands_json 1178/1178, verify_panels 14/14, verify_floor_fit 9/9. Identity gate green (byte-identical), F1 n/a (new door + page only; posting untouched). Web live on dev at once; the engine door needs a dev restart (asked). Left: chunk 3 video export (9:16), chunk 4 polish (sparks, sound); single-part (non part-list) views have no button yet. | 2026-10-28 FLOATING PLAYER (Aristide, screenshot: 'can you make the play window floatable? so we can move it around?'): a grip (⠿) at the left of the player's top row drags it anywhere over the sheet view (pointer events, mouse and touch), kept inside the view, same size when floated; the spot is remembered (localStorage km_playpos) and comes back on the next open/reload; a double-click on the grip docks it back at the bottom; a floated player no longer slides the view to make room. Also fixed: the X/Y readout lagged one step behind a scrub (draw before the readout). Web only (app.js/app.css), live on dev at once, no restart. verify_playback.js 26/26 (+8 drag checks). Identity gate green, F1 n/a (page only). | 2026-10-28 NARROWER PLAYER (Aristide: 'it is also unnecessarily wide?'): the player is now 470px wide (was up to 760px, stretched across the view), docked or floated, capped at the view width less 24px; the G-code lines, readout and buttons still fit, and it now moves sideways freely as well. app.css only, live on dev at once. verify_playback.js 26/26. Identity gate green, F1 n/a. | 2026-10-29 BURN LOOK = THE WEBSITE'S (Aristide, screenshot of the site demo: 'make the burn animation for the play button have the same look and feel as the website'): drawPlay rewritten with the kerfmaster-site demo's look -- the sheet goes dark (#0a0a0b at .93, the site's stage), the whole program drawn first as the site's faint dashed plan (white .13, dash 3 5), the fresh kerf amber-hot #ffc46b with an amber glow that cools to cream #e8e5de over the last ~2.4 s of play behind the head (6 heat bands), a white head in an amber halo that flares on a pierce, an amber crater dot left at every pierce, sparks off the tip (the site's own physics: 26 max, gravity 260 px/s2, burst on a pierce, colours #ffc46b/#ffa028/#fff3dd; they land after a pause; none under prefers-reduced-motion), finished rapids faint dashed, the rapid under way brighter. Web only (app.js), nothing else changed. verify_playback.js 26/26, verify_panels 14/14, no page errors; headless 23 fps zoomed in. Identity gate green, F1 n/a (page only). Sound still parked (chunk 4). | 2026-10-29 SPARKS FIX (Aristide: 'I have sparks on the website, but not on the app?'): my defect in e0818815 -- the spark clock was reset to zero on every frame with no spark in the air, so the frame step was always 0 and the first spark could never be born (measured: 0 sparks over 2 s of play). Now reset only when paused with none left; measured 1-8 in the air while cutting (headless ~20 fps; more at a real 60 fps); spark dot 1.4 -> 1.7 px. verify_playback.js 27/27 (+1: sparks fly while it cuts -- the check that would have caught it). Identity gate green, F1 n/a. | 2026-10-30 COOL-DOWN AT THE END (Aristide: 'it would look finished if the glow down keeps going once the head and cut movements have stopped'): app.js playCool -- when the program ends the heat clock runs on one heat window (PLAY_HEAT_S 2.4 s, real time at any speed) and the last kerf cools to cream, then the loop stops; pause mid-run still freezes; Replay/seek resets; playStop cancels it. Screen only, engine and G-code untouched. verify_playback 27/0; browser check: tail 74.5 > window 72 then loop off, last part amber -> cream. Identity gate green; F1 n/a. | 2026-10-30 Aristide checked the end-of-playback cool-down on dev: "it looks good." Signed off. | 2026-10-30 Aristide asks: export the playback as a video to send to the client. Proposed (not built, awaiting answers): browser-side recording of the sheet animation only (no G-code panel, program number or shop words, per the customer/shop split), MP4 where the browser can, else WebM; auto speed to a target length; one video per sheet; KerfMaster name + job name on it. Touches app.js only (shared with speed, memo); engine, G-code, nesting and box load untouched. | 2026-10-30 Aristide drops the video plan: wants a shareable landing page with the full play experience (G-code and all), sent to the client as a link. Discussed, not built. Open: G-code shown to clients vs the 2026-08-05 customer/shop split; frozen snapshot vs live; link expiry/revoke; host name; needs a new read-only engine door (server.py, shared with speed) + dev restart + prod deploy. | 2026-10-30 Aristide (screenshot): the share page shows only the sheet + the player as it is now (Play/Replay, speed, slider, X/Y, mode, scrolling G-code). Settles what is shown; G-code to clients is his call. Still open: frozen vs latest, expiry/switch-off, per sheet vs whole job, go. | 2026-10-30 BUILT share link (Aristide go: frozen, 30 days + switch-off, one link per job with sheet picker): Share button on the player -> POST /api/jobs/<id>/share snapshots every posted sheet + the packed layout into cadmaster/app/shares/<code>.json (runtime, gitignored); /play/<code> serves the app in share mode (app.js shareBoot): sheet + player + G-code only, no Share/close, no stale note, every non-GET fetch refused in the page; GET /api/share/<code>[/playback?sheet=N] reads only the snapshot; switch-off or day 30 -> 410 "expired" page; part lists only. Proof on scratch: 13/0 browser checks (make link, client page plays, writes blocked, switch-off 410), 2-sheet job picker, frozen after NC edit, verify_playback 27/0, identity gate green; F1 n/a (new doors). Size: perf-towing-16 one sheet = 5.8 MB snapshot (24.6k moves), sent uncompressed. Not yet checked: prod Caddy passes /play/. Jordan to rule on clients seeing our G-code. | 2026-10-30 dev restarted on Aristide's "restart" (inflight 0/0). Live checks: dev.kerfmaster.com/play/<code> 200 and plays, switch-off -> 410; prod deployed: app.kerfmaster.com/api/share/<bad> answers the new door and /play/<code> serves the share page (Caddy passes it). | 2026-10-30 Aristide: "the share button is clumsy" -- BUILT: one click on Share makes the link AND copies it to the clipboard (ClipboardItem started inside the click so Safari allows it after the engine answers; if the browser refuses, the drawer says press Copy); everything about links now sits in a drawer below the G-code (copied note, link, Copy, Switch off, other open links); Share again folds it; drawer stays open while playing. Screen only (app.js/app.css), no restart. Scratch: drawer 8/0, share 13/0, verify_playback 27/0, no-permission path 0 errors; identity gate green; F1 n/a. | 2026-10-30 Aristide (prod screenshot): the client page put the player over the sheet and it could not be moved -- cause: the page lives on the same site as the app, so it took the operator's saved floating-player spot. FIXED: share page never uses the saved spot or the grip; player docked bottom-centre and the sheet fits in the room above it; phones: compact player full width at the bottom (portrait), player on the right with the sheet left of it (landscape, height <= 500). Screen only. Checks: desktop 1280x720, iPhone 13 portrait + landscape with a saved spot set: sheet clear of the player, all on screen, plays, no errors (12/0); share 13/0, drawer 8/0, verify_playback 27/0; identity gate green; F1 n/a. Not done: pinch-zoom on phones; a wide sheet is small on a portrait phone. | 2026-10-30 Aristide: start at 1x, speed buttons not a dropdown, no flash of the app before it strips, our logo on top with a space for the shop logo, "Powered by KerfMaster." in gray at the bottom. BUILT (client page only): PLAY.speed=1 on the share page; 1x/5x/10x/25x/100x buttons (operator player keeps its dropdown); index.html first script sets body.km-share before paint and skips the operator layout setting, menubar.js stands down; top bar = website K-mark (web/km-mark.svg, copied from kerfmaster-v2 header) + KerfMaster wordmark, empty 160x38 shop-logo slot on the right (no shop logo exists in the shop profile yet); job line under it; footer line. Checks: app screens hidden with app.js blocked (first paint), operator layout not applied; desktop + iPhone portrait/landscape: logo, footer, 1x start, 25x button, sheet clear of player and header, plays, no errors (29/0); share 13/0, drawer 8/0, verify_playback 27/0; identity gate green; F1 n/a. Open: how the shop supplies its logo. | 2026-10-30 (Aristide): shop logo + operator speed buttons + copied check. (1) Shop logo: POST /api/shop/logo {data_url|remove} (PNG/JPEG/WebP/SVG data URL, <=512 KB encoded), kept in shop.json (prod-preserved) under 'logo'; GET /api/shop/logo returns it; GET /api/shop leaves the picture out (boot stays light); set_shop keeps it on wizard saves. Asked in Shop setup (onboarding wizard, also the later preferences) under 'Your shop's logo', saves at once. run_share copies it into each NEW snapshot (frozen, per the share ruling); share_view returns it; shareBoot puts it in #shareshop. Links made before keep what they had. (2) Operator player: speed buttons 1/5/10/25/100x replace the dropdown, start at 1x (PLAY.speed 1). (3) Copy feedback: Copy button turns green 'Copied' with a self-drawing check ring for ~2.4s, link field glows green; same on the one-click Share copy. Tests: new t6 18/0, share 13/0, drawer 8/0, layout 12/0 + 29/0, verify_playback 27/0 (its speed step now clicks the 100x button); engine check wizard save keeps the logo, oversize refused; identity gate green; F1 n/a (screens + new door). Needs a dev restart for the engine door. | 2026-10-30: shop logo door live on dev (restart, inflight 0/0, Aristide OK) and prod (deploy; /api/shop/logo 200). | 2026-10-30 (Aristide screenshot 'what happened to the PLAY BAR'): DEFECT from 774de05c -- the operator's speed buttons took the slider's room in the 470px bar (slider squeezed to a dot, close pushed out). Fix: slider on its own full-width line under the buttons (order last, flex-basis 100%), Share + close grouped (.playend) at the right, bar 520px, drawer link row wraps on narrow work areas. Screen only. New t7 desktop: slider 498px, Share/close inside; narrow 900px work area wraps cleanly; t 13/0, t2 8/0, t4 12/0, t5 29/0, t6 18/0, verify_playback 27/0; identity gate green; F1 n/a. | 2026-10-30 (Aristide: 'this should be the view when it starts after I press the play button'): the operator's Play cut now opens like the client page -- player docked bottom-centre (#playbar:not(.floated) left 50%/translateX), the played sheet fitted whole above it (shareFit, now shared; playMakeRoom removed; a floated player leaves the whole canvas to the sheet). The saved drag spot (km_playpos) is no longer applied or kept: a drag lasts the session, double-click the grip docks and re-fits. verify_playback 28/0 (its 'spot kept after a reload' check became 'reopens docked' + new 'sheet fitted whole above the player'); 1440 and 1920 screens fitted, no errors; t 13/0 t2 8/0 t4 12/0 t5 29/0 t6 18/0; identity gate green; F1 n/a. Screen only. | 2026-10-30 (Aristide: 'animate it ... a chevron ... CLASSY, High Ticket'): the link drawer unfolds and folds by height (grid 0fr->1fr, .34s ease-out curve) with a soft fade and lift of its contents; a chevron on Share turns down->up in step; Share or Esc folds it the same way, then the drawer is dropped; contents changing size (link arrives, a link switched off) glide to the new height (Web Animations, .38s); a fold in progress stays folded through any re-render; prefers-reduced-motion turns the motion off. New t9 10/0 (frame-by-frame heights, chevron turn, no bounce on fold, Esc); t 13/0 t2 8/0 t5 29/0 t6 18/0 verify_playback 28/0; identity gate green; F1 n/a. Screen only. | 2026-10-30 (Aristide 'yes' to fixing the X/Y readout): the 0.0000 after the drawer opened was CORRECT (the head sits at X0 Y0 before the first rapid, mode RAPID); the defect was the first readout on open, which showed the END of the first move (0.7046/0.7054) and mode '-' until a frame was drawn, and a stale head from the previous program. Fix: playPrep clears head/mode; playRender's fallback is the start of the current move and its mode. New t11 5/0 (open steady at 0.0000 0.0000 RAPID, drawer open/fold keep the reading mid-program); t 13/0 t2 8/0 t5 29/0 t6 18/0 t9 10/0 verify_playback 28/0; identity gate green; F1 n/a. Screen only. | 2026-10-30: demo client link for Aristide made on DEV: https://dev.kerfmaster.com/play/bKltNir_UT2S (perf-towing-16, 1 sheet, open until 2026-11-29; switch off from the job's player). Checked public: page 200, api 200, desktop + phone screenshots. No shop logo on dev yet. | 2026-10-30 client page on phones (Aristide 'Go on all 3'): (1) player marks are drawn SVG (PLAY_IC play/pause/replay/back-to-start), no font glyphs -- iPhone showed back-to-start as a blue emoji box; operator bar gets the same marks. (2) upright phone turns the sheet a quarter turn (X down the screen, Y right, X0Y0 top-left; ctx turn in shareTurn, shareFit fits in the turned frame, sparks fall down the screen) ONLY when that is 15%+ bigger -- measured on the 120x60 towing job: 390x664 stays flat (turn only +7%, the player eats the height), 390x750 turns (+31%), 430x800 turns; DRO stays machine X/Y. Upright phones show 4 program lines instead of 7. (3) our own zoom on the client page (shareGestures, SHV): pinch, one-finger drag, wheel, double-tap 2.5x, Fit button; view redraws sharp, kerf/glow/sparks keep screen size, player fixed; page zoom off on the client page only (viewport meta set in index.html share branch + Safari gesturestart + touch-action). Operator app untouched (its canvas tools never see share-mode touches: capture on #canvaswrap, canvas target only). Screen only, no restart. t12 56/0 (new), t5 29/0 t4 12/0 t6 18/0 t 13/0 t2 8/0 t9 10/0 t11 5/0, verify_playback 28/0; identity gate green; F1 n/a. Rollback tag pre-phonezoom. Own defect: scratch cleanup emptied shares/index.json entries; rebuilt from the snapshots' meta (demo bKltNir_UT2S 200, test z2S8U4 still off 410; its switch-off time lost). | 2026-10-31 client links never get our program (Aristide + Jordan 2026-10-30: real G-code must not be out there to copy once quotes go out on share links). server._share_scrub: the playback doc a link serves has its listing replaced by cadmaster/app/share_fake_gcode.nc (KerfMaster's own post of the words NOT COOL TO STEAL G-CODE from Aristide's not_cool.pdf at 24in wide, mild steel 0.125, moves only: 410 G0-G3 X/Y/I/J lines, no setup block, condition vars, D registers, pierce subs or O number), each move pointing at line i mod N so it runs round and round; nc file name and post time blanked; moves and totals kept (same picture). Applied at link-make (nothing real stored in new snapshots) AND at open (links made before this, e.g. demo bKltNir_UT2S, serve the stand-in too; their stored files on disk still hold the real listing, server-side only). Client page: the O-number/file/post-time line removed, the stand-in's 7-line window wraps. X/Y readout stays the real head position (Aristide '1 yes'). Operator player still gets the real program. Honest limit: the moves (the cut path picture) still go to the browser. Data checks 8/0, t12 56/0 t5 29/0 t4 12/0 t6 18/0 t 13/0 t2 8/0 t9 10/0 t11 5/0, verify_playback 28/0; identity gate green; F1 n/a (share door only). Needs a dev restart to go live on dev; prod restarts itself on deploy. Rollback tag pre-fakegc.
- •Heal re-fits chains of short smooth arcs (traced outlines, speed O56) intentmixedreads as fact — 2026-10-29 NEW (intent, Aristide relaying speed's O56): heal should re-fit chains of short smooth arcs (Jordan's Birmingham Weed, speed job birmingham-weed-1793128313, a traced outline: 3 polylines, 928 segments, 924 bulge arcs, median 0.016 in). MEASURED ON MAIN (read-only copy): the source is tangent-smooth (only 2 junctions over 1 deg, both real corners). Today's heal at tol 0.010 already brings 928 down to 342 prims (339 arcs) -- the tiny-run pass (consolidate_tiny_runs, floor 0.024 = largest beam comp) merges 586; left: 49 moves under 0.024, 174 under 0.05, shortest 0.0019, worst deviation from the drawing 0.00496 (the Q27 smoothing half of the gate, used up); 10 arcs with r over 100 in (r 1544 over 0.198 = sag 3 micro-in, really a line). WHY IT STOPS: the pass only touches moves under the 0.024 floor and keeps a window only when its shortest move gets longer, so 0.024-0.05 arcs are never re-fitted. EXPERIMENT (whole run, split at corners over 15 deg, heal.fit_biarc_run on dense source samples, measured both ways against the DRAWING): 0.001 -> 344 prims; 0.002 -> 236 prims, real dev 0.00277 (over its own target), 64 tangent breaks over 1 deg, 117 moves under 0.024, shortest 0.0005; 0.005 -> 210, dev 0.00499, 90 breaks. So the plain fitter is NOT shippable here: it leaves jogs (a FAIL under the no-kink rule) and slivers. DESIGN NEEDED: a fewest-arcs fit for smooth runs (G1 at every joint, a minimum move length, accept on the real deviation vs the drawing, flat arcs as lines under 0.0001 sag). QUESTIONS for the owners: (1) the 'preserve native bulges exactly' rule -- may a run of short bulge arcs be re-fitted? (2) tolerance: speed suggests 0.002; today's heal already spends 0.005 on this file. (3) rule for which runs qualify (proposal: all moves under 0.05 in, smooth, not clean CAD). Nothing built. | 2026-10-29 ARISTIDE: 'make sure that this fixes all files in the future that are similar, not just this one file.' -> the fix is a general heal rule, judged on the whole class, never tuned to Birmingham. SCAN (read-only, every source.dxf on dev + speed, 478 unique files healed at 0.010, 3 skipped over 4 s): 93 files are the same class (30+ arcs under 0.05 in and at least 30% of their arcs that short) -- 19,307 short arcs of 30,546. 64 come from bulge-traced sources like Birmingham, 29 from faceted lines the heal itself fits into short arcs (e.g. the 23004-* parts: 48 source arcs, 400 healed), so the pass must run on the heal's OUTPUT for both kinds and be measured against the SOURCE drawing. Acceptance for the build: before/after table on all 93 (moves, shortest move, worst deviation from the drawing, kinks = 0), clean CAD byte-untouched (identity gate + check_corpus), a fixture for each kind added to the corpus so a future file of the class is guarded. Scan script /tmp/bw/scan.py (temporary). | 2026-10-29 JORDAN ANSWERED (verbatim excerpts): 1. 'It can use bulge arcs if it actually preserves the look of the native cad. What we don't want it some corners having bulges that weren't there before, and that's exactly what I saw on the Birmingham Weed.' 2/3. 'I cleaned it at .005" and .010", as you did, and the result was still many extra primitives ... [under .050] that's way small. The cleaner should have given us way larger primitives in the case of the Birmingham Weed, while preserving its original look, and it really didn't. Take a look at Station 4 on Speed right now. The extra primitives are affecting speed now too.' RULING: re-fit allowed, judged by the LOOK of the native CAD (no new rounding at corners), primitives far larger than 0.05, not limited to tiny runs. MEASURED station-4-sign (speed, read-only copy; 201 polylines + 134 splines): main heal at 0.010 = 1361 prims (median 0.153); the fitter always aims at FIT_TARGET 0.0005 whatever the operator's tolerance -- patched (experiment only) 0.001 -> 1080, 0.002 -> 906, 0.005 -> 717 prims. Birmingham does not move with the fit target (942 native bulges are preserved, never re-fitted) -- 342 at every value. So two causes: (a) the fit target ignores the tolerance, (b) native bulge chains are never re-fitted. Both go into the design. | 2026-10-29 STEP 1 BUILT (Jordan: 'let's do Heal first, but let's test it and make sure we're not coming up with any bandaid solutions'): new LAB module cadmaster/refit_chains.py (NOT wired into heal -- nothing in the pipeline calls it) + bench cadmaster/refit_lab.py. Rule (general, works on any healed prim list): a joint turning over JOG_DEG (1 deg) is a corner, kept exactly; inside a smooth run knots sit only on the run's own joints with its own tangent, each span one biarc (no jog by construction), taken only within tol AND within 0.1 x the tightest radius it replaces (a tight curl keeps its shape); same-circle halves -> one arc; sag under 0.0001 AND sweep under 0.5 deg -> line (my first cut turned short tight arcs into lines and made 4 new 1-3 deg jogs; caught by the corner count, fixed); a run changes only if it gets fewer pieces. MEASURED vs the TRUE drawing (dxf_io.sample_true_source, both ways): BIRMINGHAM on the raw native bulges (tiny pass off): 928 -> 181 prims at 0.0025 (dev 0.0025), 166 at 0.004 (dev 0.0040), corners 2 -> 2 (zero new); on today's heal output (342, already 0.0050 off the drawing) -> 146 but 0.0055 off -- so the re-fit must start from the drawing, not stack on the tiny pass. STATION 4 (speed, splines): 1361 -> 850 at 0.0025 (dev 0.0029), 748 at 0.004 (dev 0.0042), corners 256 -> 256. 0.03-0.15 s per file. Left in step 1: budget from the drawing (not stacked), the 68 pieces still under 0.024 on Birmingham, the 93-file before/after table, an overlay board for Jordan's eye. Identity gate green (nothing wired), F1 n/a. | 2026-10-29 TEST AT 0.010 (Jordan: 'We need to make sure that the healing tolerance set by the operator will work. If you think the default at .010" is too large, then we probably need to change the default. Can you test it at .010" and make sure it still preserves the original appearance?'): lab refit_chains on the NOTINY heal, measured vs the true drawing both ways. Birmingham Weed 928 -> 153 pieces, worst 0.0093, corners 2 -> 2 (at 0.0025: 181, at 0.005: 161). Station 4 1419 -> 622, worst 0.0101, corners 274 -> 274 (at 0.0025: 889). Eye check (overlay at dev.kerfmaster.com/viewer/builds/refit-010/, runtime dir, not committed): whole-part view indistinguishable; zoomed, Station 4's letter curves sit as an even parallel shift up to 0.010 (smooth, no kinks); Birmingham's long thin leaf spikes are where it shows -- an edge bows up to 0.009 off, so a narrow tip can get noticeably fatter on one side. Findings: (1) Station 4 lands at 0.0101 -- over 0.010 because the re-fit stacks on the heal's own 0.0007; the budget-from-the-drawing step fixes that (operator tolerance = the TOTAL drawing-to-output budget). (2) 0.010 vs 0.0025 buys only 15% fewer pieces on Birmingham (153 vs 181) for 4x the drift; Station 4 30% (622 vs 889). Proposal sent to Jordan: re-fit follows the job/operator tolerance as the total budget (no separate number, default unchanged), plus a general thin-feature guard -- a span may move at most a fraction of the local part width, like the 0.1 x radius guard on curls -- so spike tips keep their shape at any tolerance. Awaiting his call. | 2026-10-29 JORDAN'S SCREENSHOT (Birmingham Weed on speed, 'The kind of deviation shown here is the kind of thing that can throw things off. Is this the best we can do?'): measured speed's posted program (jobs/birmingham-weed-1793128314/plpost.nc, rotated 90 in the nest) against the drawing, after aligning it to the drawing: posted cut up to 0.0100 off, at tight rounded corners and small wiggles (1.45,-2.00 / 2.36,-0.76 / 2.54,-3.65 / 1.08,-3.65), where the heal output is only 0.0049 off (same on speed's heal copy and dev main). So most of what he sees is added AFTER the heal, at post. A dev single-part post of the same heal (Mild Steel 0.04, beam comp 0.004, 3 micro merges) lands 0.0062 off, so the part-list post path adds more; which step does it is not found yet. (The 0.0148 the other way is the 0.030 part tab gap, not drift.) Scripts: /tmp/bw/look/ncdev.py, refine.py, ncplot.py. | 2026-10-29 POST STEP HUNT (Jordan: 'Yes, find the post step.') -- RESULT: no post step adds drift on today's code. Re-posting speed's Birmingham part list (jobs -1793128313/-1793128314 copied to a tempdir, run_plpost in-process) gives 0.0051 vs the drawing on BOTH dev main and speed's current code (identical moves); a dev single-part post 0.0051, rotated or not (heal 0.0050 + emit rounding). The 0.0100 I measured earlier was speed's SAVED program from 2026-10-27 19:14 (posted before the job was re-healed today 16:07; why it was worse is not knowable now -- the old geometry is overwritten). CORRECTION of my earlier message: Jordan's screenshot is the HEAL, not the post -- found at app (1.576,-2.700) = source (1.297,-1.576), today's heal 0.0046 off there (consolidate_tiny_runs at floor 0.024 irons out the S and moves the tip). The lab fitter on the raw heal keeps the S at that tip: 0.0025 off at tol 0.0025 (181 pieces), 0.0042 at tol 0.010 (153). Overlay: dev.kerfmaster.com/viewer/builds/refit-010/ (top). Scripts /tmp/bw/look/plrun.py, tip3.py, healrot.py. Next: the heal fix (re-fit replaces the tiny pass, tolerance = total budget, thin-feature guard) -- awaiting Jordan's answers to the two questions. | 2026-10-29 STEP 1b BUILT, lab only (Jordan: 'I think the total limit, but I'm not confident in that answer until we can test it ... 1. Stop bulging corners and other anomalies that are aesthetically different from the source as much as possible. 2. Minimize the amount of primitives after healing while preserving accuracy within the set tolerance.'): refit_chains.py gains the TOTAL BUDGET (base = the raw heal's own deviation; spans get tol - base) and the THIN-FEATURE GUARD (local_widths: nearest geometry across the part -- another contour, or the same one where the path folds back, path distance > 2 x straight distance; a span moves at most wfrac 0.1 x local width, width floored at 0.010 ~ one kerf). Re-fit now starts from the raw heal (no tiny pass). refit_lab.py rewritten: today vs re-fit unguarded vs guarded, with a LOOK metric (worst share of local width moved, and 'bulge spots' = places over 25%, 0.1 in apart). Results at 0.010 vs the true drawing: Birmingham today 342 pieces, 0.0050 off, worst 47% of width, 3 bulge spots -> guarded 172 pieces, 0.0063 off, worst 19%, 0 bulge spots, 2 corners kept; Jordan's screenshot tip 0.0046 -> 0.0006. Station 4 today 1361, 0.0020, 20%, 0 spots, 256 corners (today's tiny pass loses 18 of the drawn 274) -> guarded 665, 0.0096, 20%, 0 spots, 274 corners. OPEN: (1) the width map is slow (Station 4 4.1 s) -- must be fast before wiring (F1 rule); (2) the 93-file table: batch /tmp/bw/batch.py -> /tmp/bw/batch.out, ~1 min per file, only 2 done this turn (--help-p0 2256 -> 1656, 5 bulge spots -> 0; --help-p1 273 -> 184); (3) overlay board for the 93; (4) step 2 wiring. Overlay of the tip: dev.kerfmaster.com/viewer/builds/refit-010/ (top). Identity gate green (not wired, output unchanged). | 2026-10-29 review package for Jordan (he holds the 93-file table to inspect the two files himself): refit_review_dxf.py writes per file a CAM-safe TODAY and NEW DXF plus an overlay DXF (layers ORIGINAL gray / TODAY red / NEW blue; Station 4 splines as 0.002-step lines, within 0.001). Hosted at dev.kerfmaster.com/viewer/builds/refit-010/ (Downloads). Birmingham 342 -> 172 pieces (0.0050 -> 0.0063 off), Station 4 1361 -> 665 (0.0020 -> 0.0096). Lab only, live heal unchanged; waiting on Jordan's review before the 93-file table. | 2026-10-30 JORDAN: refit-010 review NOT satisfied; Aristide will work with dev on it. Nothing built until that session.
- •Upload split leaves a drawing's side view (thickness strip) off the part list (speed O58) record — 2026-10-29 NEW (intent, Aristide relaying speed's O58; 'add this one to the list. do nothing yet'): the upload split keeps a drawing's SIDE VIEW as a part. Jordan's CP-8005-19/-20/-21 on speed (and the 10-26 upload): each drawing = the flat band + a 4-line strip 0.059 in (1.5 mm) wide showing the thickness. Zero-click sheet intake rightly declined (no stated scale), then the plain split made each strip its own 'part 2' at qty 1 -- 6 pieces in the part list, the strips would nest and cut. The batch tool cadmaster/prep_drawing.py (August, TL-1016-73..85) already drops bare-line clusters whose short side is <= SIDE_MAX 16 mm as side views; the app's upload never got the rule. Speed's suggestions: same test in the upload split; warn, never block -- the strip marked 'side view, left off' with one click to keep it; offer its width as the thickness (1.5 mm); check the 3 files give 1 part each and a real thin part is still kept; golden gate. PARKED by Aristide until Jordan answers the heal-refit-short-arc-chains questions. Nothing built. | 2026-10-29 JORDAN: 'This sounds good to me, I'm good with it as long as it's not a bandaid fix.' -> GO, built as a general rule (same test as prep_drawing's side-view rule, a fixture per drawing class, a real thin part kept), not a CP-8005 patch. | 2026-10-30 BUILT (Aristide 'go for 1 and 2'; Jordan's GO 'not a bandaid'): split_parts.side_views() = prep_drawing's side-view test + the projection: one CLOSED contour of >=4 bare lines, short side <= SIDE_MAX 16 mm and >= DEBRIS, beside a wider part (short side > 16 mm), lined up along the strip (overlap >= 0.90 of BOTH lengths; CP-8005 measure 0.995..0.996), NOTHING drawn in between. server.run_split leaves them off and records job.split.side_views [{w,h,x,y,thick,beside_part}]; body keep_side_views=true splits them in; add_side_views=true on a split job adds them as more parts (record moves to side_views_kept). Screen: Intake shows each left-off strip in yellow ('side view, left off -- 0.059 x 6.970 strip beside part 1; reads as 0.059 in (1.50 mm) thick') + 'Keep as part'; the upload door's summary names it with 'open it'. Thickness is words only, not set on the material. PROOF: test_split_side_views.py 15/15 (fixture per class: real CP-8005-19 geometry golden/fixtures/sideview_cp8005_19.dxf; plate+strip; lone thin bar kept; kit of strips kept; strip with arcs kept; part in between kept; plain kit record unchanged; keep/add/refusals). Corpus: 431 unique job sources on dev+speed (55 multi-part) -> hits ONLY CP-8005-19/-20/-21; the 78598 bend-line proof sheet hit until 'closed' + 'nothing in between' were added (own first draft too loose, caught by the sweep), clean now. test_split_door 17/0, test_partgroups 21/0, test_original_lineage 26/0, test_sheet_blocked 25/0; browser: Intake note + Keep click (0 page errors), verify_splitnest 10/10, verify_original 8/8, verify_oneroad 17/17, verify_dwgtray 20 ok. Identity gate green (kit_split ref unchanged). F1 n/a (probe never splits). RAMIFICATIONS: upload door + Split button only; stored jobs unchanged (speed's CP-8005 jobs keep their part-2 strips; a re-upload gets the rule); a real thin bar drawn lined up beside a plate with nothing between would be left off -- yellow note + one click keeps it. Shared files server.py + app.js -> memo MEMO-TO-SPEED-side-views-2026-10-30.md. FOUND, not fixed: test_sheet_dimpart 2,3,4,23 fail on the pre-change code too (23 looks stale since O62/O64 listed the copies sheet on purpose). | 2026-10-30 03:43 UTC LIVE ON DEV: kerfmaster-app restarted (Aristide 'OK to restart'; both inflights 0; speed untouched). Live check: CP-8005-19 fixture uploaded to :8474 and split -> 1 part + 1 side view left off (0.0591 beside part 1); the two check jobs then moved to trash. Prod gets it via the normal deploy.
- •Copper and brass plan and post -- the table's N/A etch pierce means 'no etch on this material', not blank (speed O47) record — 2026-10-29 BUILT (speed O47; Jordan: 'We cannot etch copper or brass with our lasers, the material is too reflective and it's not recommended by Mitsubishi... hence the N/A. I agree with your fix, OK to pass.'): machine_tables.json carries pierce_etch 'N/A' on all 7 Copper and 12 Brass GX 10K rows and tables.rev2_tooling read it as blank, so EVERY copper/brass plan refused ('pierce_default/pierce_etch blank (TBD)') -- the shop worked round it by picking another material, which puts the wrong M100 line in the program. Now 'N/A' = no etch pierce on this material: tooling pierce.etch None, etch None, plus etch_off (plain-words reason); a truly blank cell still raises. emit refuses only a feature marked etch, in plain words ('Copper cannot be etched on this laser -- the table marks its etch pierce N/A -- clear the etch mark on this feature, or check the material is right'). nc_audit unchanged: a stray quick pierce on such a row would show as a pierce-sub anomaly. The pre-pierce pass (P9019) is not built yet; noted on its pin that it must honour etch_off. Test test_no_etch_rows.py 13/13 (Copper 0.04/0.125/0.25 + Brass 0.125 load; Copper 0.04 and Brass 0.125 post with P9011 only, right material line, audit clean; etch on copper refuses with the plain message; blank cell still refuses); test_etch_feature 34/34, test_pierce_sub ALL PASS. Identity gate green (Mild Steel byte-identical). F1 first click 8.56/8.71s -> 8.57/8.56s, repeat 7.93/7.95 -> 7.88/7.88 (no cost). Dev needs a restart to make it live on dev; prod gets it on deploy.
- •Part-list sheet cut order by strips (O95; Aristide 2026-10-30 / 2026-11-05) recordmixed — O99 + O100 + O101 SHIPPED to main 2026-11-07 as 04874b9f / e5a4ef1a / 6b1d7c59 (Jordan: "Yes, this is finished. Go ahead and send it"). O100 zones stays a test switch, default off. Still on dev only: O89, O90-O98 items not yet shipped (O94, O96, O97, O98 and the O89 healer). | O101 SPEED 2026-11-07 (Jordan "1. Yes, then let me test it"): the follow re-pick no longer rebuilds each start/tab/lead -- an irregular cutout's first pick keeps its scored candidates (pick "_cands", only with seqleads on, cut_order safe, no slot; dropped after the follow pass) and the re-pick re-scores them from the head with the same tiers. F1 first click 11.05/11.07s -> 8.83/8.83s, repeat 10.84/10.85 -> 8.59/8.61 (baseline 8.78/8.50). Proof of no change: full review.json contours byte-identical to the pre-speed emit (separate tree) on Lucas zones off and on, and on all 8 F1 bench parts. Identity gate green; slug/seq/start/tooling/plan_perf suites green. Needs a dev restart. | O101 UI 2026-11-07 (Jordan: "satisfied with the performance of this build, but not with the location of Save for this job being under the ladder tuning chevron"): in the Part List slug block the Save for this job / Save as material default / clear links now come straight after the settings rows, the "ladder tuning (advanced)" fold moved below them (with "The Save buttons above save these too"). Client only (app.js, live without restart); same ids, same save body. Checked by screenshot on dev. | O101b ON DEV 2026-11-07 (Jordan, screenshot: "this did all of them including the outer profile ... back to a chaotic sequence"): the follow pass no longer re-picks the OUTER profile -- its start stays exactly where it was without the switch (Lucas zones off: back to bottom-middle 11.0,0.0 from top-left 0.2,13.9; zones on: 21.9,0.1 as in O100). Measured: only irregular cutouts move; corner holes, wheel holes and other regular cutouts unchanged. His screenshot was the OLD order because zones read OFF on both Lucas jobs (slugsettings: zones default off) -- the chaos is zones off, not the lead change. Zones off + follow: 200.7" / 16 hops>5", emitted crossings 3; zones on + follow: 101.7" / 5 hops, crossings 4. F1 first click 11.05/11.07s, repeat 10.84/10.85 (unchanged from O101, +2.3s over baseline, dev only). Identity gate green. | O101 ON DEV 2026-11-07 (Jordan: "Let's switch that on now and let me see it"; Lucas with zones "looks a lot better"): LEAD-INS FOLLOW THE SEQUENCE for irregular cutouts, switch default ON. Slug setting "seqleads" on/off, tooling["seqleads"]; Part List Slug tabs and chop row "lead-ins follow the sequence". After the order is final, each O99 irregular cutout (pick irr set: tab rule active, size >= no-tab-below, not regular) re-picks start = tab = pierce via _choose(approach, follow=True): safety tiers, then crossings of held slugs, then DISTANCE from the head, lower-right only as tiebreak; shop start-default anchor skipped for these; operator start/anchor still wins; outer re-picks after; rapids recounted. Order unchanged. MEASURED Lucas (...1794069170, ladder on, start-to-start): zones off 217.2"/17 hops>5" -> 193.3"/16; zones on 106.2"/7 -> 101.7"/5. Emitted crossings after traverse routing: zones off 2 -> 3, zones on 2 -> 4. CORRECTION to O100 record: its 15 -> 22 were planner counts BEFORE traverse-routing detours; emitted crossings are 2 with zones off and 2 with zones on. COST: F1 first click 8.78 -> 11.05/11.06s, repeat 8.56 -> 10.84/10.86s (+2.3s, over the 1s line: named, NOT for main as is; serial re-pick per irregular). Identity gate green after INTENDED delta: single_tooling.json gains the seqleads block; every .nc byte-identical (no golden fixture has tabbed irregular cutouts -- not covered by the gate). Slug/seq/start/tooling suites + test_zone_order green. Needs a dev restart. | O100 ON DEV 2026-11-07 (Jordan: "Let's go with your idea and test it"; corner holes cut with their neighbours OK): ZONE CUT ORDER behind a test switch, default OFF. Slug setting "zones" on/off (job outranks material), tooling["zones"] {on,source}; Part List "Settings for every part" > Slug tabs and chop > "zone cut order (test)". emit._cut_zones: interior cutouts whose outlines come within the nozzle radius (head_envelope lowest tier, 0.5906) chain into one zone. _cut_order(zones=...): finish the zone in hand (its falls-through pieces first, then the rest, nearest-next, safety first), then enter the zone whose first piece scores best from the head (each zone's lowest band, no sheet-wide drop-through-first); tip deferral 0 and the small-first/wait groups dropped under the switch; outer last; report gains zones {count, moves}. MEASURED Lucas sign (dev job ...1794069170, ladder on, start-to-start rapids): off 217.2" with 17 hops over 5"; on 106.2" with 7 hops, 10 zones, sweep from lower-left. COST: rapids crossing a held slug 15 -> 22 (inside tight zones the head now flies over just-cut tabbed neighbours instead of jumping away). F1 first click 8.78/8.76s, repeat 8.56/8.54 (switch off; baseline 8.78/8.50). Identity gate green after INTENDED delta: single_tooling.json gains the "zones" block; every .nc byte-identical. test_zone_order 11/11; slug/seq/start/tooling suites green. Needs a dev restart. | O99c ON DEV 2026-11-07 (Jordan: "build b but use the starting values from a"; tapered windows count; switch in Part List "Settings for every part"): the toggle MOVED into the slug settings (job outranks material outranks seed; the list's job record governs every part): fields irregular on/off (default on) + irregular_min ("no tab below", seeded from the row's own no-tab/falls-through size: 1.000 Rev2 bands, 0.781 ladder on Mild Steel 0.125). tables.rev2_tooling serves tooling["irregular"] {on,min,width,active,sources}; inert where slug tabs are off / width 0. The job.json/review-route/tooling_doc path from O99 removed (tooling_doc back to pre-O99). shapes.py: any convex 4-sided window (parallelogram, trapezoid) is regular; grill flat 8/8 windows regular. UI: "tab irregular cutouts" row in Slug tabs and chop (Save for this job / Save as material default). MEASURED: F1 first click back to 8.78/8.78s, repeat 8.50/8.52 (the +2.3s is gone: lettering is under the seed size); Lucas sign 34 tabbed + 6 untabbed (pre-O99: 32 tabbed). Identity gate: only single_tooling.json gains the "irregular" block (refs updated); every .nc byte-identical to pre-O99. test_tab_irregular 23/23; slug/seq/start/tooling suites green with and without the ladder. Needs a dev restart (server/tables/emit). | O99b ON DEV 2026-11-07 (Jordan: "fit those into the category of rectangles"; restart OK; extra planning time OK while testing): shapes.py adds slanted rectangles (parallelograms, sharp or one corner radius) to the regular class. Grill flat: 6 of the 8 slanted windows now regular; the other 2 are slightly TAPERED (ends 1.4 deg off parallel, long sides 3.794 vs 3.816) and stay irregular -- they were already tabbed by the table, so tilted.nc is byte-identical to before O99 (ref back to original). Lucas sign unchanged (35 tabbed). F1 parts classify identically (no re-time needed: same plan). test_tab_irregular 21/21, identity gate green. Jordan on tiny lettering: "really small letters shouldn't have a tab -- maybe a separately defined threshold per material? just thinking" -- QUESTION, nothing built. | O99 BUILT ON DEV 2026-11-07 (Jordan go; NOT shipped; dev engine not yet restarted): "tab irregular cutouts". New shapes.py: a cutout is REGULAR when every point of its flattened outline sits within 0.010 of a fitted rounded rectangle (rectangle, rounded rectangle, round-end slot, rectangular slot with corner radii, circle) or a regular 3/5/6/7/8-gon (sharp or rounded); else IRREGULAR. emit._choose: irregular cutout tabbed with the row width WHATEVER its size when the job toggle is on (default), untabbed when off; operator per-feature tab/slug switch/chop still win; regular cutouts keep the Rev2/ladder rules. Review source "rule:tab-irregular", slug report band "irregular (always tabbed)/(tabs off)". Toggle: job.json tab_irregular=false (absent = on), set via the review route body {"tab_irregular": bool}, carried through tooling.json -> overrides_from to every post door. No screen switch yet. MEASURED: Lucas sign tabbed slugs 32 -> 35 of 40 cutouts (only the 4 corner circles and 1 small regular piece stay untabbed); F1 first click 8.73/8.78s -> 11.09/11.09s, repeat 8.52/8.53 -> 10.80/10.80 (+2.3s: F1 parts are 0.25in lettering, every counter now tabbed; the shape check itself is ~10ms -- the cost is the extra held slugs in ordering/traffic) -- OVER the 1s speed line, named to Jordan before any ship. Identity gate: INTENDED delta tilted.nc only -- 8 slanted grill windows (parallelograms, 88.8 deg corners, 4.0-6.5in) were "above large limit" untabbed, now tabbed; header 2 -> 3 yellow; refs updated. test_tab_irregular 19/19; slug/seq/start/tooling suites green with and without KM_SLUG_LADDER. Open: parallelogram windows regular or not; tiny lettering counters (0.04in) now tabbed. | 2026-11-07 JORDAN RULINGS (intent, nothing built): "tab irregular cutouts" toggle, default ON = every irregular cutout tabbed regardless of size, OFF = no tab; regular cutouts keep the Rev2 table rules; sequence-placed leads for irregular cutouts toggle default ON; regular-shape list to be built. Asked whether the 4 corner holes (source: 2-vertex polylines, bulge 1.0 each = two exact half-circles, 0.250 dia) read as true circles. MEASURED: heal keeps them as 2 arcs on one centre/radius exactly; emit._is_true_circle (0.001) already passes them and the circle start rule (clock 3.0) applies; circle + slot detectors exist (_is_true_circle, _slot_ends), rectangle/hex do not. Healer work only matters for faceted/drifting holes; how common is unmeasured. Step-1 go pending. | 2026-11-07 JORDAN: treat every job the same; proposes toggles -- (a) "tab irregular cutouts", default ON; (b) try the zone rule with (a) on; (c) irregular cutouts get their lead-in placed by the optimal sequence instead of operator-set defaults, maybe a toggle too. Open: what (a) changes vs the Rev2 tab rule today; regular-shape definition (circle, slot, rectangle, regular polygon); (c) moves the tab too (start = tab = pierce) and drops the lower-right bias for those pieces; re-pick after ordering already exists for the outer profile. Proposal sent, nothing built, awaiting go. | 2026-11-07 JORDAN answers the zone questions: zones = pieces that sit close together, sized from his laser head numbers; nearest-next inside a zone; outer last; he tests it himself (no need to ask Aristide); asked whether it is a patch or an enhancement (answer: enhancement -- replaces global drop-through-first + wait groups; risk: chained letters merge into one zone at optics/head-box reach, ~10 zones at nozzle reach on the Lucas sign, rough box gaps). Then floats: treat REGULAR shapes (circles, slots, hexes, rectangles on automotive parts) differently from IRREGULAR art/sign shapes. Proposed: one zone rule for all files, the shape class only changes defaults (same-tools-every-file), test on a sign and an automotive part before splitting. Nothing built. | 2026-11-07 JORDAN restates the ladder-tuning principle: work ZONE BY ZONE -- in a local zone cut the small fall-through features first, then the larger ones in that zone, then move to the next zone ("predictable and low-risk"); asks whether the Lucas sign follows it. ANSWER (measured from the trace): no -- there is no zone concept in _cut_order; drop-throughs are cut first over the whole sign, local groups only make one big piece wait for its small neighbours, the no-fly-over rule then pulls the head across the sign: 15 hops over 5in, 206.6in of rapid between cuts. Nothing built; zone rule shape awaiting his answers. | 2026-11-06 JORDAN (Lucas & Barrett's stencil sign, lucas-barretts-place-stencil-sign-1793990261, 41 contours): the cut order is "far from ideal and perceived by the laser operator to be chaotic"; asked for each slug's risk numbers so we can fine-tune together. MEASURED (planner replayed in-process with KM_SLUG_LADDER=1, order identical to the stored review): TIP_BANDS is empty (risk classes OFF since the 2026-07-31 novi sweep) -- my earlier explanation to Jordan of class-by-class ordering was WRONG and was corrected. Real drivers: drop-throughs first across the whole sign (seq 1-6, hops up to 15.6in); local small-first groups (budget 4.0in, 10 groups judged, 1 released); never fly over a held slug (the most common reason the nearest is skipped); tip deferral 0.5in/unit. 15 rapids still cross a held slug. Nothing built; waiting on Jordan for which rule to loosen (fine-tuning changes rulings, Aristide to be asked too). Tracer: /tmp/o99seq/trace.py. | SHIPPED TO MAIN 2026-11-06 (Aristide: "go ahead and merge"): O95 step 1 + step 2a + rules.check_flyover (not wired) cherry-picked alone from dev (b500b9c3, fcd54d2f, c8dc0787); O89/O90/O91/O93/O94/O96 stay on dev. Strips snake from bottom-left, downward P9997 pitch, strip_width setting in machine.json. NOT shipped (held for testing per Jordan): step 2b air move / route-around, G0G28Z0 lift, fly-over warning. Gate green; test_pl_strip_order 15/15; pl suite green on main (test_pl_one_material needs a dev-only job fixture). | JORDAN 2026-11-05 (later): M199 is already at the end of each cut in the subprogram (so the lift is G0G28Z0). On go-around-first vs lift: 'we're going to have to test this before we establish too many rules. Sequencing a nest has a lot of variables' -- no fly-over rule beyond Aristide's until tested. JORDAN ANSWERED 2026-11-05: (1) P9997 downward OK: 'set the G172 for the location of the first part, then I and/or J values can be positive or negative' -- step 2a confirmed. (2) Head lift = G0G28Z0, needs M199 before it ('assuming it would be present in this case' -- asked whether we add M199 or it is already there). (3) Neighbour hops in interlocked nests are expected, low-risk: NO warning; the problem is SURPRISE fly-overs that look out of sequence to operators. Where there is risk the shop adds an air move at the end of the subprogram to fly around. Idea (Jordan, not a go yet): a Nest toggle to turn the air-move/fly-around on and off at the operator's discretion. PLAN (Aristide 2026-11-05 ~03:35 UTC): morning = tidy up with Jordan first (neighbour-hop warning, head-lift command + height, confirm downward P9997, tell him his list was paused for O95), THEN merge O95 to main. Step 2b routing not started (no go yet). O95 STEP 2a LIVE on dev 2026-11-05 03:31 UTC (restart, inflight 0/0, Aristide's OK). Aristide: whether neighbour hops (head moving to the just-finished interlocked neighbour) get the fly-over warning, or only hops over older parts, is a JORDAN question -- ask him. O95 STEP 2a BUILT on dev (not live) 2026-11-05: strips SNAKE in the macro form too -- a single-column run in a down strip posts top-down (G172 at the top copy, P9997 negative J; precedent Jordan 2026-09-06 + O33339), pl_post.orient_runs. Dev Camp-4: fly-overs 127 -> 82 rapids, long hops 5 -> 1, rapids 1940 -> 1835 in; audit unchanged; plpost time unchanged. Remaining: route hops around cut parts, wire the fly-over warning, head lift (Jordan). Jordan's 'can P9997 run down' question: answered by his own 2026-09-06 words -- confirm with him. O95 STEP 2 started 2026-11-05 03:12 UTC: rules.check_flyover(bnds) written (NOT wired into the audit yet): counts rapids on the EXECUTED program that pass over an already-cut part (any outer, same _seg_hits_poly arithmetic as the traffic rule). Dev Camp-4 post (strip order, macro form): 127 rapids over 80 of 90 cut parts -- 46 while moving to the next part (crossing the part just finished, interlocked S-shapes), 81 over older parts; the longest are the 32-34in strip returns to the bottom. FOUND: downward macro arrays already have a precedent -- Jordan 2026-09-06 ('start in the positive extreme and subtract ... Mitsubishi doesn't care') and O33339 posted G65P9997 with negative J; so snake strips can stay macro. Proposed to Aristide: snake in the macro form too, then route sub-call hops, then wire the warning. O95 STEP 1 BUILT on dev (not live, not shipped) 2026-11-05: pl_post.strip_order + server._pl_sheet_boxes; _pl_sheet_order uses the strip order for unclicked parts (post AND Nest numbers); strips from where parts sit, whole columns while widths add to <= machine.json strip_width (12 in seed, assumed); every strip UP on macro sheets, snake in the sub-call form; recomputed each post = a repack re-sequences. O33635: hops >15in 9 -> 5, squeezed copies cut in their strip; dev Camp-4 NC byte-identical (already strip-ordered). plpost 3.38 -> 3.40s (no cost); F1 n/a. Identity gate green (holds no part-list post). test_pl_strip_order 13/13. STEP 2 (intent, Aristide go): route between-part rapids around cut parts, warn when no way. STEP 3 (intent, Aristide: 'DEFINATELY lift the head over the issue area'): needs the machine's head-lift command/height from Jordan. Full entry docs/brick-history.md. O95 (claimed 2026-11-05, Aristide GO 'start with fixing it like that'): (1) keep the Camp-4 macro form (strips cut upward as today; Aristide: Jordan wants repeated parts to stay macro programs) but every squeezed/leftover copy cuts IN ITS STRIP, never at the end; (2) any change (part edited, qty changed -> repack) re-sequences the whole sheet from where parts sit; (3) fly-overs fixed in the same build: the head must not rapid over a cut part held by tabs (pin rapid-over-slug; 2026-10-30 options A-E on standing-reminders). Offline sim on the O33635 layout (origin-to-origin, rough clusters, not a real post): fill order 657in / 9 hops >15in; strip order 467in / 6 hops. Negative-pitch P9997 still Jordan's question. Not built yet. Aristide 2026-11-05: wants to work on sheet cut order now (with dev). Reported: after a change to a nested file the new G-code puts the change at the END instead of redoing the sheet's order; operators see the head cross the sheet for a few last cuts. Dev read (code only, not reproduced on a job): pl_post.sequence_placements emits clicked parts then plain fill/placement order -- no spatial order on part-list sheets, so added parts and strays cut last. His order: start bottom-left, go UP in Y through a strip one or two columns wide, then the next one-or-two-column strip in X from the top DOWN to the bottom, then the next strip up, and so on; recomputed from where parts sit on every post. Open: strip width rule, order inside a two-wide strip, who builds (speed lane vs dev after Jordan's list), a job name to reproduce. MEASURED 2026-11-05 02:40 UTC (read-only prod API, O33635, 88 parts, 39 macro arrays): between-array head travel 344in; 5 empty runs of 24-27in back to the bottom after each strip (strips go up only); the last 4 calls are single squeezed copies (parts 38, 34, 91, 10) crossing the sheet 22-28in each (~105in). Aristide: the qty 6->3 change on part 1 was by Jordan in the app. Aristide: strip width depends on part size (3in parts = about 4 columns); zig-zag inside a strip = yes; negative-pitch P9997 (can a macro array run downward) = question for Jordan. Dev proposal: strip width a setting (~12in seed), down strips top-to-bottom, squeezed copies cut in the strip where they sit; awaiting go. QUESTION, nothing built. Aristide's catch on prod job camp-4-test-patterns-final-20260915-nest-1789526876 (O33635): 4 copies post as the last K1 calls (X9/X22/X24/X36 before M30). MEASURED (read-only, prod API): regular-columns pack, qty 6 but a 31in column holds 5, so the 6th copy of parts 10/34/38 (and one part 91) is a stray; square-up pulls each stray left into a gap; plpost emits in pack fill order (pl_post.sequence_placements, arrays sorted by first index), so strays cut last and the head crosses back 4 times. Today's workaround: click a sequence (posts part-by-part). Offered: cut each stray with its neighbouring column, lower-left start kept -- touches part-list cut order, macro grouping, identity refs, speed's nest lane. Asked: want it? dev or speed builds? Not yet answered. | 2026-10-30 FLIP PREDICTION (Aristide: 3 parts flipped on O33635 'because the head traveled' -- predict which). Independent sim of the posted NC (own parser, P9997 expanded, not the pipeline's audit): 9 long moves over 15in, 4 of them the leftover calls at the end. Ranked by distance travelled over parts already cut free: #47 and #46 (part 36, both under move D to #58) and #75 (part 39, move G to #86); next #48, #25, #51, #21, #69 -- scores close (3.0-4.2in), so a guess among ~8. Board dev.kerfmaster.com/viewer/builds/flip-o33635/predict.png. Awaiting Aristide's actual 3. | 2026-10-30 ACTUAL FLIPS (Aristide circled on the board): #47 part 36 (predicted red, HIT), #51 part 32 (predicted yellow), #61 part 34 (not marked; crossed 2.9in by leftover move G). #47 and #51 both under move D (top of column 5 -> bottom of column 6, every column runs bottom-up so each column change crosses the column just cut); #61 under G (a leftover trip back). #46/#75 crossed but did not flip -- 3 data points, no tuning yet. Aristide: 'how can we incorporate that in our planning -- do not build, discuss.' Discussion offered: alternate column direction, leftovers in place, rapid detours/flip-risk warning in NC + print, head lift as machine question, record real flips per job. | 2026-10-30 ARISTIDE: all questions from his 3 O33635 observations go to JORDAN -- (1) leftover copies cut last [pl-leftover-cut-order], (2) print follows repack [print-follows-repack], (3) flips: options A alternate column direction, B leftovers with their column, C flip-risk check/detour, D head lift + slats, E operator marks real flips; who builds (dev/speed). Plus Camp-4 open qty-prefill / rotate-mirror default / start-A questions. Nothing built until Jordan answers.
- •Should the nest print follow a repack without re-delivering? (Aristide 2026-10-30, question -- with Jordan) question — QUESTION, nothing built. Aristide: after a repack, reprinting needed Deliver again; shouldn't the print match the repack? MEASURED: the operator nest PDF is made only inside run_pldeliver (immutable versioned delivery, Jordan's job-versioning ruling); a repack marks the delivery replanned and the old PDF keeps the old layout. Offered A: 'Print this nest' proof on the Nest tab stamped PROOF - not a delivery, no program number; B: one-click 'Post + deliver the new layout'. Aristide 2026-10-30: none for now, he will discuss it with Jordan. Wait for them. | 2026-10-30 ARISTIDE: all questions from his 3 O33635 observations go to JORDAN -- (1) leftover copies cut last [pl-leftover-cut-order], (2) print follows repack [print-follows-repack], (3) flips: options A alternate column direction, B leftovers with their column, C flip-risk check/detour, D head lift + slats, E operator marks real flips; who builds (dev/speed). Plus Camp-4 open qty-prefill / rotate-mirror default / start-A questions. Nothing built until Jordan answers.
- •Client approval module -- the share/play page grows into the client's one page (cut preview / quote / approve / files) intentmixed — INTENT (Aristide 2026-10-31): 'use this landing page as the basis of the client approval center ... the header as the place to put the other items: files/quote/final files etc (which would load the quote, and an approval button). We still have to work out the details, based on what you had in the notes already.' DISCUSSION ONLY, nothing built. Builds on: customer-portal (approve price + bridges only, operator may override the rest, a human eye before the laser, metric toggle, payments stay with the shop), approval.py artifact, customer sheet brick 16 (vocabulary census), quote stack (run_quote, fast/firm tiers, Q29 roll-up), share links (/play/<tok>, frozen snapshot, 30 days, switch-off, stand-in G-code). Open questions put to Aristide/Jordan 2026-10-31: who the client is (link = key vs minimal account), what Approve records and who is told, which version is approved, which files the client gets (never the NC), firm vs indicative price, a Request-changes button, and the playback page's shop words (pierce, rapids, G-code) vs the customer-sheet vocabulary census. | ANSWERS (Aristide 2026-10-31): 1 small client account; they may need to create a PO and upload it, and may leave comments. 2 Approve = email to the shop AND a mark on the job in Jobs. 3 approval locks to the version; a changed job needs a new approval. 4 final files = a PDF, NEVER the DXF (and never the NC). 5 quotes must be able to be FIRM (note: rates.json is 22 assumed seed rows / 2 decided -- firm needs the shop's real rates or a shop-set price). 6 yes, Request changes with comment. 7 plain words on the client cut preview (no pierce/rapids/G-code). Next: chunk plan put to Aristide/Jordan; nothing built. | CHUNK A BUILT 2026-10-31 (Aristide 'go on A', tag pre-approvalA): the client page (/play/<tok>) gets the approval center header -- #sharetabs Cut preview (on) / Quote / Approve / Files (greyed, 'Coming soon'), centred in the top bar on desktop and landscape phones, its own 36px strip under the bar on phones <=600px (job line and Fit moved down; the sheet fit follows the job line). Plain words on the client page only: head line 'cut preview', mode readout STARTING / MOVING / CUTTING / MARKING (app.js SHARE_MODE), counter 'start points N of M · cut X of Y ft' (rapids dropped). The stand-in code box is unchanged (Q1 still open). Operator player unchanged. app.js + app.css only (screen only, no server change, no restart; live on dev at once, prod with the deploy). Tested: new t14 33/0 (four pages, greyed, clear of both logos, job line below, no shop words in the page text, readouts while playing, desktop/phone/landscape), t5 29/0 t11 5/0 t12 56/0 t 13/0 t2 8/0 t4 12/0 t6 18/0 t9 10/0, verify_playback 28/0; screenshots checked; identity gate green; F1 n/a. | ANSWERS 2 (Aristide 2026-10-31): Q1 the stand-in code box stays as it is. Q2 firm price WAITS for Jordan's real rates (chunk C held on them; rates.json is 22 assumed / 2 decided). Q3 the shop's notice address and the sending mail account will be supplied later -- details still to work out (the email half of chunk D waits; the Jobs mark does not). Q4 PO upload = PDF or Word document only, no photos. Q5 a client account belongs to one shop, each shop's clients kept apart. Nothing built on these. | CHUNK B BUILT 2026-10-31 (Aristide 'B, go', tag pre-approvalB): client accounts on the client page. New client_accounts.py: email + name + company + password (8+ chars), password kept only as a salted scrypt hash, sign-in = random token in an HttpOnly SameSite=Lax cookie (Secure behind https), server keeps only its sha256, 30 days; 8 wrong passwords lock that email 15 min; same answer for unknown email and wrong password. Runtime data in cadmaster/app/clients/ (gitignored; KM_CLIENTS_DIR overrides for tests). Per shop: one engine = one shop, so its accounts are that shop's alone. server.py: POST /api/client/signup|login|logout, GET /api/client/me; the FIRST account to sign in or up on a link claims it (index meta client + claimed_at) and from then on /api/share/<tok> (and its playback) answers 401 sign-in to anyone else -- no data; unclaimed links open as before (Aristide's demo link untouched); the operator's link list shows who claimed each link (client_who). app.js: Sign in / first-name button at the end of the header pages, sign-in / create-account card, sign-out card, claimed link opens on a sign-in card with no player behind it; the share-mode write block lets only api/client/ through. Also fixed a chunk A layout bug: on small sideways phones (568 wide) the pages strip covered the job line -- the strip is now upright phones only, sideways phones keep the pages in the bar (word mark hidden under 680 wide). NOT closed by this chunk (owned: I said B would close it): the operator API still serves any job's data to anyone who knows its job id -- that needs operator sign-in, its own decision; this chunk adds claimed names/emails to that open shares list. Tested: acct_data 30/0 (claim, lockout, no plain passwords, cookie flags, stranger gets no data), t15 14/0 (browser sign-up/in/out, claimed link), t14 44/0 (+ SE sideways), t5 29/0 t11 5/0 t12 56/0 t 13/0 t2 8/0 t4 12/0, verify_playback 28/0; screenshots checked; identity gate green; F1 n/a (share door only). Needs a dev restart (server.py); prod restarts itself on deploy. Prod note: clients/ must survive deploys like shares/ -- to confirm with Sem. | 2026-10-31: note to Sem drafted for Aristide to send (keep cadmaster/app/shares/ and cadmaster/app/clients/ across prod deploys and rollbacks like customers.json -- PROD-STATE lists neither). Waiting on Sem's answer. | CHUNK D BUILT 2026-10-31 (Aristide '1' = D, tag pre-approvalD): Approve / Request changes on the client page. Approve page is live (Quote, Files still greyed); not signed in -> the account card first. Card: job name, plain note (price comes with the quote; holding tabs, start points, cutting order may be adjusted by our operator; a person checks every job before it is cut), PO number, PO file (PDF or Word .doc/.docx, 10 MB, told by its first bytes; a zip must hold word/document.xml), comments; Request changes needs a comment. POST /api/share/<tok>/decide: signed in as the link's account (an unclaimed link is claimed by the decision; a refused request claims nothing), decisions kept on the link's index entry (history), approved = final for that link (409 after) -- the link is the frozen version, so a changed job goes out on a new link and needs a new approval. PO files kept in shares/po/<tok>-<n>.<ext>; operator downloads at /api/share-po/<file>. Operator: the link drawer shows the client and each decision with PO link and comment (drawer now scrolls past 42vh so the player stays on screen); Jobs home card shows 'Client approved' / 'Client asked for changes' (server /api/jobs adds client_decision from one read of shares/index.json). Email to the shop NOT built -- waits on Aristide's mail details. Share-mode write block now lets through only api/client/* and api/share/<tok>/decide. Bugs caught in testing and fixed before commit: a refused PO still claimed the link; the guard blocked decide; the thank-you line went to the replaced card. Tested: dec_data 22/0, t16 25/0 (phone + desktop flow, Jobs mark), t14 44/0, t5 29/0 t12 56/0 t11 5/0 t9 10/0 (with a normal link count; 9/1 with ~8 decided test links on one job = taller drawer, bigger animation step, not a defect) t6 18/0 t4 12/0, verify_playback 28/0; screenshots checked; identity gate green; F1 n/a (share door + one small read on the Jobs list). Needs a dev restart; prod restarts itself. shares/po/ is covered by the Sem note on keeping shares/. | SES note to Sem drafted 2026-10-31 (Aristide asked): ask whether Amazon SES is set up; if not, verify kerfmaster.com (DKIM/SPF/DMARC), request production access, make SMTP credentials limited to sending, upload to both boxes as secrets, confirm port 587 out. Approval email still waits on this + from/to addresses. No SES/SMTP found on dev box. | CHUNK E BUILT 2026-10-31 (Aristide '1' = E, tag pre-approvalE): Files tab live on the client page. Making a link now also draws the part drawings PDF (one dimensioned page per listed part, the SAME make_prints page as the operator prints; footer says QUANTITY not COPIES IN NEST, material in plain words) in a background thread, seconds after the click, into shares/<tok>.drawings.pdf (.fail on error); never the DXF or NC. GET /api/share/<tok>/drawings.pdf: signed in, as the link's account once claimed; looking does not claim; expired/switched-off links refused. Card states: Part drawings download / being prepared / could not be prepared / older link - ask for a fresh link (links made before E have no drawings, incl. the demo link). make_prints.part_fig_from_prims + pl_prints.part_prints gain copies_label (default unchanged, operator/board prints identical). Share click unchanged in time (drawing work off the request; ~1 s/part CPU in the background, ~10 s for 8 parts). e_data 20/0, te 23/0, verify_playback 28/0, t16 23/2 (the 2 = its old 'Files still greyed' check, now intended); identity gate green; F1 n/a. Also: my chunk D test cleanup had switched off Aristide's demo link bKltNir_UT2S at 02:13; switched back on after the restart. Known: the print footer brand reads lower-case 'kerfmaster' (existing renderer, not changed here). | BRAND FOOTER 2026-10-31 (Aristide '4'): the printed drawings' title block and the board nest cover now read 'KerfMaster' (were lower-case 'kerfmaster', pin product-name-spelling). make_prints.py only -- one renderer, so the client drawings, operator PDF, reference prints and board prints all change together; PDFs only, no NC. Not changed: lower-case 'kerfmaster' in code docstrings, text report headers (quote/preflight/fast estimate) and the NC part_name default in pl_post (changing that would move G-code). test_part_prints 6/0; identity gate green; F1 n/a. | NAME (Aristide 2026-10-31): this is the CLIENT APPROVAL MODULE -- use that name in docs and talk. The pin slug client-approval-center stays as an identifier (code comments and links point to it); earlier entries keep their wording as history. Built: A header + plain words, B client accounts, D approve / request changes / PO, E files (part drawings PDF). Pin now mixed: built records + open intent. | 2026-10-31 PUT TO JORDAN (Aristide: 'give Jordan all his questions now here'), 16 numbered: approval module 1 real rates, 2 operator sign-in, 3 forgot password, 4 client my-jobs page, 5 change-request reply, 6 files before/after approval, 7 metric toggle + price/bridges-only, 8 extend link, 9 client account delete; Camp-4 10 start with A, 11 qty prefill with drawn copies, 12 rotated/mirrored default per new customer; O33635 13 leftover copies with their column, 14 print after repack A/B/neither, 15 flips A-E, 16 who builds 13-15. Plus the parked older list (auto-close, cut vs engrave, bend-line etch, source-truth view, warning nagging, part-list display) offered: now or keep parked. Waiting on Jordan.
- •O84 Scale this part -- by ratio or a measured length, recorded, undoable, edits move with it record — RECORD (O84, branch cut-this, 2026-11-02, Jordan 'Go on B' -- EDS17942 plan item B): Scale this part. Geometry > Intake row 'part size W x H' with 'scale this part x [n] Scale', 'Measure a length...' (opens Source mode + the measure tool; after two points the Show panel offers 'true length [..] Scale the part to it') and 'Back to the file's size' once scaled. Door POST /api/jobs/<id>/partscale {ratio:n} | {measure:{a,b,length}} | {reset:true}; ratio and measure multiply what is shown. Recorded job.part_scale {factor, base, how, steps[], who, date}; the factor multiplies the units scale at parse (the units flip's seam), so heal, source layer, fidelity, dashed ink and every re-parse (_ufv returns base x factor) move together; _frame_steps adds the scale so Source mode on a Cut-this part still lines up (EDS17942 copy x2: part and bold original both 18.0000 x 1.5000). Hand edits are re-addressed into the scaled frame (points + lengths dx/dy/dia/r scale; tolerances, gap caps, angles do not), so a typed diameter scales with the part. Stale rule as a units flip: downstream drops, O-numbers kept. One heavy undo step (asks first); Cancel restores job.json + healedits.json byte-exact. Refuses in plain words: part list, sketch, split file with parts (scale each part), never-extracted drawing sheet (use Cut this). Range x0.001..x1000. Unit words (units door, units modal, card in/mm toggle, Source panel 'drawn in mm' line, feature report, original print) judge the units alone, never the product. Tests: test_partscale.py 31/31; units/tol/introt/turned-edits/lineage/sheet-window suites green except test_units_confirm 2 FAIL that fail the same on the pre-O84 code (checks 4 and 8, a fixture reading 410 x 0.00 -- pre-existing, not touched). Browser: scratch copy of Jordan's EDS17942 part, x2 -> 18 x 1.5, measure 18 -> true 9 -> 9 x 0.75, reset; Source mode stays on. Identity gate green (no G-code change). F1 first click 8.51/8.52s -> 8.50/8.50s (no cost). Rollback tag pre-o84-scale-part. Not live on dev until a restart (server.py). Not merged to main.
- •Overlap / off-sheet reds follow the layout to Post, Deliver and the floor (Jordan, 2026-11-02, from O83 BG-BASE) recordmixedreads as fact — SHIPPED to main 2026-11-04 (Jordan tested on dev: works; identity gate green; F1 first click 8.51/8.58s -> 8.54/8.54s, repeat 8.24/8.32 -> 8.33/8.28s, no cost). BUILT items 1-3: parts off the sheet or crossing another part after a hand layout show red on the nest, a red popup at Post and Deliver (Go back and fix / Deliver anyway, recorded), the red count in the NC header and packet, a red box on the packet and a red banner + red parts on the operator PDF. Item 4 (who saved each hand edit) NOT built: waits for operator logins. The blue band glitch is its own pin (nest-blue-band-glitch). Jordan 2026-11-02: a hand-edited nest crossed two side plates (BG-BASE-Battery Plate + 5 more, v001 O33623); the editor flagged red but the packet said 0 reds and the parts reached the floor. Ruling: warn loudly, don't block. Asked for: (1) a popup at Post and Deliver listing the parts, with Go back and fix / Deliver anyway; (2) a red line at the top of the operator PDF and the packet; (3) a correct red count; (4) record who saves each hand edit. Also: a blue striped band on the Nest tab while dragging.
- •Button layout is overwhelming -- design for dyslexic operators (Jordan, 2026-11-02) intent — Jordan 2026-11-02, after finding the Intake row: 'we gotta work on the button layout, most of the industry is full of dyslexic ... human operators like me and the current layout is overwhelming to our eyes.' Want: calmer panels that are easier to scan (fewer buttons in view, clear grouping, short labels, more spacing, less italic small print). Nothing proposed or built yet. Must hold on all three shells (one source, three lenses).
- •O85 Extra part tabs on outside profiles (Jordan, 2026-11-02, EDS17942 .013 aluminum) recordmixedreads as fact — SHIPPED to main 2026-11-04 (Jordan tested on dev: works; identity gate green; F1 first click 8.51/8.58s -> 8.54/8.54s, repeat 8.24/8.32 -> 8.33/8.28s, no cost). BUILT: typed tab count per job + per outside profile (right-click), each tab run posts as its own feature with its own lead/pierce and overridable values, each tab draggable. Jordan 2026-11-02: thin stock (EDS17942, .013 Al on the .040 M100 row) needs more than the one part tab. Today: one tab per outer (the uncut span at the end, beside the pierce), width overridable per feature (0 = none). Ruling: (1a) a typed tab COUNT, a job option (not a table column; uncommon choice), default positions at opposing ends, expect 2 as the usual pick; (1b) a right-click per outside profile too; (2) each extra tab posts like a separate cut: M199 at the end of the run, G40 G0 to the next pierce, continue as normal, with the same G41/G42 and the same D register kept for the whole profile; (3) width = the table part tab (0.030) unless overridden. Nothing built; plan + go pending. -- 2026-11-02 Jordan, more: each restart gets its own lead-in into scrap, normal length. Default spacing: tab 1 at the default start (lower right); N tabs spaced equally along the cut starting there (2 = halfway round, the far left); click-and-drag moves each tab on its own and overrides the default. Questions sent: spacing measured along the cut?, corner nudge to a flat, what happens to the others when one moves, a lead that won't fit, go. -- 2026-11-02 Jordan answers: spacing along the cut, yes; slide off corners onto a flat, yes; tabs drag independently of each other; a lead that won't fit = yellow, operator re-packs. GO to build. Step 1 engine on branch o85-extra-tabs (WIP, dark): emit._tab_runs + overrides part_tab_count / per-feature tab_count; each later run posts M87, M199, G40 G0 to its own lead, same #501, M98, same G41/G42 + D. Count 1 byte-identical (identity gate green). EDS17942 view 1 copy at 2 tabs: tab 2 lands at the far left. Open: the audit reads the runs as one cut (flags pierce counts), UI count + right-click, quote, tests, F1. -- 2026-11-02 Jordan: M87 before M199 confirmed ('just like any other cut sequence'); each split run must be its own feature with its own overridable values (condition #, D value, etc.). Plan sent: post each run as its own FEATURE block, seeded from the outer; questions on mixed D/comp warning and what happens to run overrides when the count changes. -- 2026-11-02 Jordan: runs hold the outer's comp + D by default, operator may override per run (no extra warning; overrides are recorded); changing the count resets every run to default. BUILT (engine, branch o85-extra-tabs): each run posts as its own FEATURE (M87, M199, G40 G0 to its own lead, #501, M98, G41/G42 + D), seeded from the outer; overrides flagged run:true bind to the nearest run (lead_length, comp, condition, cond_number, d_register/offset/label); per-contour record carries run/run_of. EDS17942 view 1 copy: 2/3/4 tabs audit clean (0 anomalies, 0 findings); run-2 override D4 + #106 posts on run 2 only. Identity gate green (count 1 byte-identical). F1 8.53/8.55 -> 8.57/8.51s first, 8.24/8.32 -> 8.31/8.27s repeat. Open: UI (job count box, right-click count, run right-click sends run:true, count change clears run overrides), server plumbing of part_tab_count, quote tab count check, unbound run overrides listing, drag (step 2). -- 2026-11-02 UI chunk (branch o85-extra-tabs): Tooling tab 'tabs per outside profile' box (job.json part_tab_count, 1..8, via the review body); tooling.json carries it so every post door reads it (overrides_from); per-profile 'tabs on this profile' row + right-click Tab count…; run contours show 'run k of feature m' and take lead/comp/condition/D only (other edits refused with a toast); any count change clears run overrides (toast). Scratch EDS17942: count 2 -> doc runs [1, 2 run_of 1]; run-2 D4 -> post 2 pierces, D4 on run 2, audit clean. Identity gate green. Not yet: browser click-through, quote check, drag (step 2). Step 2 (drag each tab) built on the branch.
- •Nest tab blue striped band (Jordan, 2026-11-02, speed memo O83(b)) question — SHIPPED TO MAIN + DEV 2026-11-06 ~13:40 UTC (Aristide: "do it now"): speed O83b 5149c023 cherry-picked -- ResizeObserver on the canvas calls resize() when its box changes size (15 lines app.js, client-only, no restart). Identity gate green; node --check ok. Awaiting Jordan: does the Part list cursor offset still happen? | 2026-11-06 5th sighting (Jordan, Part list drawing on his TL list): hover/cursor lands to the right of the drawing (display shifted left); going to Geometry Source mode and back cured it -- same stale-canvas pattern; not reproduced headless. Speed fix 5149c023 (15 lines app.js, ResizeObserver) offered to dev again. | 4th sighting 2026-11-05 ~21:05 UTC (Jordan, dev, PART LIST tab, TL-1016-81 + 3 more list; screenshot incoming/1793912767_154177_new_glitch.PNG): right-hand strip of the drawing area shows old frames of the sheet at another zoom -- same stale-canvas pattern. Dev still lacks speed's fix (speed 5149c023 'O83b: canvas re-measures on its own size change', not merged into dev). Aristide 2026-11-05 00:20 UTC: speed found and fixed the screen-glitch error; it reaches dev when speed's fix is merged (later). Dev builds no canvas watcher of its own (speed memo MEMO-TO-DEV-canvas-watcher-2026-11-04 is covered by speed's fix). Re-check on dev after the merge. Jordan 2026-11-04 (3rd sighting, dev, Nest tab, rear-radar part list, 6 pcs/2 sheets, wide window): blue striped band again in the strip left of the right Nest panel; screenshot incoming/1793753619_154177_overlap.PNG. Not part of O83 overlap red (which Jordan passed). Jordan 2026-11-03 (2nd sighting, Tooling tab): start-point drag handle gone, click-drag left a 'vapor trail' of the display down the right-most side; a window RESIZE cleared it; could not re-make it. Jordan 2026-11-03: HOLD the fix until the culprit is reproduced -- no guessing. While moving the nest, a bright blue band of fine vertical stripes fills the column between the sheet and the right Nest panel (speed.kerfmaster.com, BG-BASE part list, Chrome desktop, newer layout); gone on reload. Memo kerf-onums/MEMO-TO-DEV-o83-nest-glitch-2026-11-02.md.
- •480125 outer reads OPEN: a zero-length segment at a join (Jordan, 2026-11-03) questionmixed — SUPERSEDED by O89 (root fix in the healer, pin o89-healer-drops-subtol-pieces, 2026-11-04). Jordan 2026-11-03: invisible open feature on 480125 rear radar. Root cause: a zero-length polyline plus a corner curve drawn twice. O87 fix BUILT ON BRANCH, TESTED, NOT ON DEV -- awaiting Jordan's go.
- •O89 Healer throws out sub-tolerance pieces before joining outlines (Jordan, 2026-11-04 'Go') recordmixedreads as fact — TRACED + FIXED 2026-11-05 ~03:39 UTC (Jordan's list item 1, Aristide's go): test_upload_cancel 11/15 with O89 was the TEST, not Cancel -- its heavy file doubled every edge 0.7 thou off, which O89's healer now drops itself (upload done in ~5 s, before the test's 6 s cancel), so the slow duplicate drop never ran. Copies now 4 thou off (outside the healer's copy drop, inside the duplicate band; ~65 s uncancelled): 15/15 on dev AND on the pre-O89 tree (3f02bb80^). Side observation: a file drawn twice 0.7 thou off now uploads in ~5 s on dev (pre-O89 time for that file not measured). BUILT on dev branch 2026-11-04, sweep done (115 parts: none worse except already-failing 23004-798 jogs 1->2; flags 7267->6843), F1 +0.25s. LIVE on dev since 16:36 UTC restart (Jordan's OK, inflight 0 both sides); not shipped. Jordan testing. 480125: 1 flag -> 0, 2 outer lead-ins -> 1. SHIPPED to main 2026-11-19 ~19:23 UTC (Jordan: "1. Yes, ship with O89." -- O89 + O130 healing; O129 nest order and the trace tool stay on dev). Shipped: heal.py = dev heal.py (O89 3f02bb80/fb40fcaa/52c88e47 + O130 8a2aacb3/1545f986/1512c166), qc.py tip fix only (cf1dc50b; O104 trace part of qc.py NOT shipped), tests test_healedit + test_auto_dedup (dev copies), test_o130_spline_straight, test_subtol_pieces. On the main tree: test_healedit 102, spline_thin 12/0, rejoin_runs 11/0, healadd 13/0, o130_spline_straight 13/0, qc_link 15, auto_dedup 25/0, double_cut pass, subtol_pieces pass. Identity gate green on main (byte-identical). F1 first click on the main tree 8.46/8.48 s -> 8.75/8.74 s (+0.27 s, O89 measured +0.25 s on dev).
- •78598 grill 'with bend lines' upload: edges drawn twice a hair apart (Jordan, 2026-11-04: 'I do want to solve this version at some point, but I'm not really sure how yet') question — ON HOLD (Jordan 2026-11-05): 'there was more context and nuance to me saying go ahead and build the fix ... we need to go back and find out what we said was ok to build and what was on hold for testing'. Two parts closer than tolerance: 'a nice feature in theory ... another one where we have to be careful', must be tested. The 11-04 17:5x GO below is my record of his words, not verbatim -- re-confirm scope with him before any build. Type back to question. STARTED 2026-11-05 ~03:52 UTC (Jordan's list item 2, Aristide's go): measured only, nothing built. Grill original (job ...-22806-wi-1791386967) at the O89 drop step: 503 pieces, 46 already dropped; 217 pieces lie wholly within 0.020 of other ink -- 85 within 0.005 (O89 band), 88 more within 0.010, 44 within 0.020. Many edges are drawn 3-4 times a few thou apart (long ~8.8 in slot/panel edges at 0.0015-0.016 off), plus many ~0.12 in 2-segment corner pieces drawn out and back. All the near-copies are straight lines. Proposed build: group near-parallel overlapping LINES within tolerance into one line at the centre of the band (span = union), re-attach the ends that met any member; arcs left for later. Open before building: two separate parts drawn closer than tolerance would merge too (Jordan's open sub-question). Hot path: needs F1 bench + 115-part sweep. Probe: /tmp/o91/grill.py. GO (Jordan 2026-11-04 17:5x: 'go ahead and build the fix'): healer merges ink drawn twice within tolerance (incl. folding back on itself) to one centre line; folded into O89 (same feature in testing). Not built yet. Fresh-upload finding 2026-11-04: dev code heals the original grill DWG to 175 branch / 58 dangling / 48 gap / 22 duplicate flags, 3 jogs, FAIL; most branches are lines across the part (bend lines) drawn in the same 7 colours as cut lines, which no healer rule should decide -- operator keeps them out (Source mode keep-out). Doubled slot edges are the smaller share.
- •Every file gets the same tools, all the time (Jordan, 2026-11-04) rulingmixed — RULING + GO (Jordan 2026-11-04: 'go on cut this for every file, including the Source'). Cut this on every file = O90 (built on dev, see its pin). Whole-file row stays on the list with a note (operator decides).
- •Part list 'Add to row' ran away on the grill; no cancel button; Source-mode picking depends on where you are (found 2026-11-04) recordmixed — O94 Cancel BUILT on dev 2026-11-05 (step 3, Jordan 'go in order'), live after a dev restart, not shipped. SHIPPED to main d21b79c9 2026-11-05 ~00:10 UTC (Jordan: 'can all ship'). O91 LIVE on dev after the 22:36 UTC restart (Jordan's OK; inflight 0/0), Jordan testing, not shipped: Add to row and New part from selection now fit SPLINE/ELLIPSE into true arcs with the healer's own fitter, sampled in INCHES (was 0.005 raw units = 25x too dense on a mm file, kept as straight lines). Size guard: refuses before any file is written when the part file would exceed 10x the original drawing (floor 2 MB). Whole-grill add on a copy: 24 s, 77 KB (was 61 MB, 450 s+ heal). Still open: cancel button (step 3), merged-qty rows bring one copy (found in test). Jordan 2026-11-04 rulings: keep a size guard on Add to row ('it may be necessary'); picking from the original lives on the Part list drawing first -- NOT built for Geometry Source mode unless the Part list proves the wrong spot. Nothing built; no go yet.
- •O90 Cut this (and the view window) on every uploaded file, not only drawing sheets (Jordan, 2026-11-04 'go') recordmixed — SHIPPED to main d21b79c9 2026-11-05 ~00:10 UTC (Jordan: 'can all ship'). LIVE on dev since the 18:58 UTC 2026-11-04 restart (Jordan's OK); Jordan testing, not shipped. Tests: test_sheet_window 30/30 (4 new O90 checks), test_sheet_road_bc 19/19, test_pl_sheet_door ok, test_pl_sheet_list 22; identity gate green; F1 n/a (no hot path: a door the operator clicks). O107 (Jordan 2026-11-12: 'If a button doesn't do anything then remove it. If it's supposed to do something and it doesn't then fix it.'): the Source-mode right-click 'Cut this' now MAKES the part -- asks the name (blank = automatic), then the panel's own cut (panel scale box if typed, else 1:1 with the yellow note). It used to only scroll to the Show panel's form, so it looked dead (seen on CP-6004-96). Also: a drawing sheet's Cut this said its size in the drawing's units labelled 'in' (CP-6004-96, an mm file: '85.9765 x 105.9139 in' for a 3.38 x 4.17 in part) -- run_sheetwindow now converts the measured size to inches once for every path (words, stored window row, Show panel row); the part itself was always the right size. Older window rows keep their stored numbers. Tests: test_sheet_window 40/40, test_sheet_road_bc 19/19, identity gate green; browser check on a copy (zz-cp6004-test). Not a hot path, no F1 run. Server half needs a dev restart.
- •Pick a line, Align X / Align Y (Jordan, 2026-11-03) record — SHIPPED to main 2026-11-04 (Jordan tested on dev: works; identity gate green; F1 first click 8.51/8.58s -> 8.54/8.54s, repeat 8.24/8.32 -> 8.33/8.28s, no cost). BUILT (O87 screen parts): the square-up row with the typed Turn box always shows; pick a line and Align X / Align Y writes the same intake_square_force turn (recorded, overridable); turns up to a half turn either way; a re-heal drops the old per-material plan copies so Tooling never serves a plan in the old frame. Jordan 2026-11-03: 'where is my tool that I select a line and say align X or align Y?' on 480125 flat patterns drawn at 8.3 and 43.9 deg. The tool does not exist today.
- •O88 auto square-up reads the outer outline, 0.1-45 deg at 30% (Jordan 'Build it', 2026-11-03) record — SHIPPED to main 2026-11-04 (Jordan tested on dev: works; identity gate green; F1 first click 8.51/8.58s -> 8.54/8.54s, repeat 8.24/8.32 -> 8.33/8.28s, no cost). O88, built on dev 2026-11-03 (Jordan: 'Build it'). Auto square-up measures the tilt off the part's OUTER OUTLINE only (server._outer_tilt): straight pieces and curves join the outline, only straight edges vote. Window 0.1-45 deg, share >=30%. A tilt that would not shrink the part's box is treated as square (no offer). Only new uploads auto-turn; older jobs get the Square up offer.
- •O92: checkboxes for cleaning/healing steps at upload (default on/off) + 'Reupload with different options' (Jordan 2026-11-04) question — Jordan 2026-11-04 ~21:25: 'we've been spinning our wheels for months'; proposes per-step on/off at upload and a reupload-with-options button. Not built; waiting on his answers (measure first? keep step 1 going?).
- •O93 Part list: after a move empties rows, 'Remove the N empty rows?' (one click, one undo) (Jordan 2026-11-04 'Go on A') record — SHIPPED to main d21b79c9 2026-11-05 ~00:10 UTC (Jordan: 'can all ship'). O93 LIVE on dev after the 23:51 UTC restart (Jordan's OK; inflight 0/0), Jordan testing, not shipped. Add to row / New part (move) answer 'emptied' (rows whose part file has no entity left); the client asks 'Remove the N empty rows from the list?'; new door plrmempty removes only really-empty rows (any other named row left and named back), one journal step, part jobs stay on disk, packed layout/posted programs drop (stale rule).
- •Trace tool for awful files: follow the lines automatically, stop only at forks for the operator to choose (Jordan 2026-11-04) question — O104 LIVE on dev after restart 2026-11-10 21:08 UTC (Jordan: "restart"). F1 first click 8.58/8.56 s -> 8.58/8.57 s. Live check: Jordan's PDF rec160281 opened on its drawing in 22.7 s (real screen, Playwright), yellow scale warning shown, no page errors; test job removed. O104 PDF/.ai sheet skips the whole-sheet doubled-line check + part count (dev, 2026-11-10 ~20:58 UTC; Jordan: "Yes, if this doesn't change any of the workflow I just did on Dev"). Why: on all 10 of his PDFs the doubled ink is title-block lettering (~1,600 filled+outlined triangles), title-block box lines and some dimension text -- never a part outline (raw-PDF check, independent of our pipeline; RSH160272's two "doubles" are louvre edges 6 thou apart, not real doubles). What: run_pipeline, when job.vector.printed: auto_dedup records a skip note instead of running; qc.analyze(dups=False) = open contours only; parts_detected not counted. Cut parts are new jobs (no vector key) and get every check as before; the Find duplicate lines lens still works on demand; a stated width (printed=false) runs everything as before. Measured (real screen, Playwright, scratch servers, same PDF rec160281): opened after 102.0 s old code -> 22.5 s new; healed + source geometry and every open-contour flag identical (3846 prims; only the 1573 duplicate flags gone); same pick cut on old and new = identical child geometry.json and checks (only ids/dates differ). EAGLES.ai 7.8 s, no errors. Ramifications: PDF/.ai printed sheets only; DXF/DWG/STEP untouched; a whole sheet later given a width never auto-drops doubles (geometry.json exists) -- its split parts still check themselves. Tests: test_qc_link 15/15, test_auto_dedup 25/25, test_upload_formats 18/18, test_healedit 100/100, partscale 38, sheet_window 40, sheet_road_bc 19, chain_trace ALL PASS. Identity gate green. F1 before 8.58/8.56 s (live, old code); after: pending restart. O103 LIVE on dev: restart 2026-11-10 20:22:19 UTC on Jordan's "restart" (both inflight 0). Live check: EAGLES.ai upload converted at printed size, yellow scale warning; test job removed. Not on main. O103 PDF/.ai shows at its PRINTED size on upload (dev, 2026-11-10 20:15 UTC; Jordan: "I thought I was going to see it on my screen after uploading, and there was going to be a yellow warning notifying me that the scale is not confirmed. That's what I would like"). Built from the parked wip-pdf-printed-size.patch, red switched to YELLOW. _upload_vector converts at once at 1 pt = 1/72 in (vector.printed=true, units note "PRINTED size ... NOT confirmed"); _scale_unconfirmed gives a yellow scale_unconfirmed finding (Intake row + NC header, "Size is right" button) until the width is stated (vecextract), the part is scaled or its size confirmed; a part cut from it (window or trace) inherits the finding. A file that will not convert this way stays awaiting the width as before. Client: oneRoadEligible opens a printed-size PDF on its DRAWING (no part-list wrap, like one awaiting its width); stating the width still files it as a list. Measured on a scratch engine: rec160281.pdf upload 96-103 s to the drawing (11.000 x 8.500 in), Playwright upload through the real screen opens the drawing, 0 page errors; cut "wheel" carries the yellow warning. Tests: test_upload_formats 18/18 (test 10 updated to the new behaviour, 14b added: stated width clears it), test_partscale 38/38, test_sheet_window 40/40, test_sheet_road_bc 19/19, test_chain_trace ALL PASS. Identity gate green. F1 first click 8.79/8.81 -> 8.83/8.79 s (DXF door, untouched). Ramifications: every new .ai/PDF upload now waits for heal+QC at upload (~1.5 min on a 1000-path PDF, previously instant but blank); existing jobs untouched; not on main; needs a dev restart. O92 speed-ups LIVE on dev (restart 2026-11-10 18:28:48 UTC, Jordan "1 restart", both inflight 0). Full upload of rec160281.pdf at 10 in on dev, timed by curl: convert (vecextract) 94.7 s + part read (split) 48.9 s. Same convert on the pre-speed-up code (git archive c80de4a2~1, :8492) had not finished after 19 min when the run stopped -- no old total, only "over 19 min". Test jobs removed. Not on main. O92 doubled-line speed-up ON DEV (2026-11-10 18:0x UTC). heal_edit._drop_duplicates: one _NearIndex of the kept ink serves every removal proof (_removal_dev(..., near=)), and the repair loop caches loose ends, reset after each successful join (_join(..., loose=)). rec160281 1x: 165.5 s -> 23.6 s, result pickle-identical. Dev copy of rec160281 (2x source): 166.4 s -> 23.5 s, pickle-identical -- the corpus run's one "DIFF" on it was the harness: the old code hit the 90 s alarm and run() caught the timeout as an ERR result. Corpus: 80 identical, 0 real diff, 851 without doubled lines, 2 unreadable (both codes). Identity gate green (byte-identical). test_qc_link 15/15. test_healedit (RJB-DS 273 count) and test_auto_dedup (no healedits.json) fail exactly as on the old code -- pre-existing, on standing-reminders. F1 first click 8.79/8.81 -> 8.78/8.79 s, repeat 8.59/8.61 -> 8.60/8.58 (unchanged). Touches every _drop_duplicates caller (upload doubled-line link, Drop duplicates row, edit replay): same answers, faster. Needs a dev engine restart to go live (with the part count). Not on main. 2026-11-10 17:44 UTC doubled-line check speed-up (heal_edit._drop_duplicates, used by qc.link_open_to_duplicates): one _NearIndex of `out` serves every victim's proof (was rebuilt per victim); loose ends listed once and re-listed only after a join changes `out`; _join takes the caller's loose list. rec160281: 165.5 s -> 23.6 s, result pickle-identical. Identity gate green; test_qc_link 15/15. Full job-file compare still running at turn end (0 DIFF printed so far). F1 not run yet. PRE-EXISTING failures found, same on the original code in a scratch copy: test_healedit (real RJB-DS heals to a count other than 273) and test_auto_dedup (finds 0 doubled spans in its fixture) -- not caused by this; to raise. PARKED, not on dev: /home/cloudally/wip-o92-dropdup.patch (+ wip-o92-heal_edit.py). Part-count speed-up c80de4a2 IS on dev, awaiting a restart. O92 part-count speed-up (dev, 2026-11-10 17:23 UTC). Aristide: "speed is not working on this, you can take the lead here ... yes, start with the part count." split_parts.close_scan_fragments step 4 (coverage-gated seam bridge): candidates come from an end grid (only end pairs within SEAM_MAX), are tried in (d, old scan order) so the first covered one is exactly the old scan's pick (least d, ties to the earliest), and coverage answers are memoised per oriented span -- ink only grows between passes, so covered stays covered; an uncovered span is re-tested only when a bridge added since lands within tol of its box. Measured: rec160281 (3740 healed prims) part_groups 236.4 s alone (2026-11-10 00:2x) -> 24.5 s / 24.8 s on a quiet box, result pickle-identical to the old code. Corpus: 926 unique job sources identical, 0 diff, 7 skipped (>5000 prims / unreadable / rec160281's old-side timeout -- that one compared identical on its own). Identity gate green (byte-identical). test_split_bridge_rollback, test_split_door 17/17, test_split_loose_owner, test_split_side_views 15/15, test_part_list 41 pass. F1 first click 8.78s/8.77s -> 8.75s/8.79s, repeat 8.57/8.51 -> 8.56/8.62 (unchanged). Touches every part_groups caller (upload part count, Split door, sheet window, kit tools): same answers, faster. Needs a dev engine restart to go live. Remaining ~24 s is the per-pass candidate rebuild + sort. Not on main. 2026-11-10 17:01 UTC part-count speed-up (Aristide: dev leads, speed not on it; 'start with the part count'): split_parts.close_scan_fragments step 4 seam-bridge -- end grid for candidates within SEAM_MAX, candidates tried in (d, old scan order) so the first covered one is the old pick, coverage answers memoised per oriented span (re-tested only when a bridge added since lands within tol of its box). rec160281 part_groups 236.69 s -> 25.05 s, results pickle-identical (timed with a corpus run alongside; clean re-time pending). Identity gate green; test_split_bridge_rollback/door/loose_owner/side_views + test_part_list pass; 119/119 sampled job files identical, full 933-file corpus compare was still running (0 DIFF so far) at turn end. F1 probe NOT run yet. Remaining ~24 s = per-pass candidate rebuild + sort. PARKED, not on dev: /home/cloudally/wip-o92-partcount.patch (+ full file wip-o92-split_parts.py). 2026-11-10 00:26 UTC Jordan: yes to looking at making the two slow QC checks faster for every file (speed told via memo 00:20); unsure on the PDF-upload re-plan -> proposed: do the speed-up first, then decide with numbers. Measured alone on rec160281 copy (3740 healed prims, sampler thread on, not profiler): heal_edit._drop_duplicates 161.7 s (hot: _loose_ends -> qc._weld_nodes recomputed per repair/_join; _removal_dev); split_parts.part_groups 236.4 s (hot: close_scan_fragments -- every loop pass rescans all open-end pairs with _covered_by and bridges ONE pair, ~cubic in open runs). Nothing built. 2026-11-10 00:15 UTC items 2+3 (Jordan 'yes to all' to: upload reads only at printed size w/ red warning; trace on uncleaned lines, clean at Cut this; 'Clean whole file' button). MEASURED first on a copy of rec160281 (unprofiled stack sampling): parse 0.04 s, the cleaner heal.heal 1.28 s (3740 prims). The minutes are QC: qc.analyze -> link_open_to_duplicates -> _drop_duplicates (_loose_ends/_weld_nodes, _removal_dev) ~0-150 s, then _count_parts from ~150 s, still running when stopped at 225 s. So skipping the CLEANER buys ~1 s; the cost is the whole-file QC + part count. Re-proposed to Jordan: keep the 1.3 s clean, skip those two whole-file checks on PDF/.ai until Cut this / Clean whole file. Nothing built. 2026-11-09 23:32 UTC: Source-mode chain-add browser-tested on the isolated copy (Playwright /tmp/o92/pw/src3.js): Select chain on two closed chains -> srcSel 4 then 8 (adds), menu 'Cut this - make a part from the 8 picked', part 'src pick test c' made (8 healed pieces, 10.0000 x 7.7273, the sheet border + a title-block box), no page errors. Jordan: no warning on whole-file Scale with a kept trace -- give the operator tools, not magic; recommended way = Cut this, then scale the part. Jordan confirmed ready to move on to items 2+3 (fast PDF upload, trace on uncleaned lines). 2026-11-09 23:30 UTC item 1 replanned with Jordan: 'scale only the geometry the operator chose to keep', near the end before tooling/nesting; recommended workflow = trace/pick -> Cut this -> Scale the new part -> tooling -> nest (to be advised to operators). Measured on the isolated copy: Scale x2 on a Cut-this part (pick-test-three) took 0.24 s and came out 7.6916 square (was 3.8458). Units flip: traced/cut parts refuse it (units_pinned). On an unpinned copy with a delete_seg hand edit, in->mm flip SKIPPED the edit on replay ('nothing within 0.25 in') -- confirmed real; Jordan: 'if this is actually a problem, then yes fix it'. 2026-11-09 23:13 UTC: dev engine restarted on Jordan's word ('restart'); both inflight 0 first. Cut this from a right-click chain pick (2c1e2394) is now live on dev -- probe: empty pick on his job refuses 'nothing picked', nothing made. Not shipped to main. Source-mode chain-add still not browser-tested. 2026-11-09 23:12 STEP 4+5 on dev (Jordan: Select chain must gather several chains; Cut this missing from right-click): right-click Select chain now ADDS to the pick (cleaned lines and Source mode; Esc clears). Right-click shows "Cut this - make a part from the N picked" whenever cleaned pieces are picked; sheetwindow {segs: [[x,y,piece]...], name, qty} chains the picked cleaned prims into outlines and takes the trace road (own part job + list row, recorded from:"pick" in cutthis/sheetintake, file whole). Right-click hit test on arcs is now exact (sampled test let a stray line 3 px off beat the circle under the cursor). Ramifications: right-click picking on arcs everywhere (only ever more exact); sheetwindow gains a branch, window/trace roads untouched; needs a dev restart for the server half (until then the menu item gets a plain refusal). Tests: test_sheet_window 40/40 (3 new), test_chain_trace ALL PASS, commands 1217 OK, gate green (byte-identical). Browser on the private copy: two Select chains (circle + a hole) -> one part 3.8458 x 3.8457 in, no page errors. Source-mode chain-add not browser-tested. F1 n/a (no hot path). 2026-11-09 23:07 Jordan: yes to "scale the traced result" (asked how it affects upload speed); no fix to his job. New report: right-click Select chain replaces the pick (cannot gather several chains) and Geometry-tab right-click has no Cut this (only Source mode does, once something is picked). Measured: PDF conversion alone 14.2 s on rec160281 (6349 prims); the rest of the minutes is cleaning the whole drawing. Proposed plan sent, waiting on his answers. 2026-11-09 23:00 SCALE x TRACE (Jordan: scaling a traced PDF part brings back the whole drawing, trace lost): cause found -- part scale moves hand edits but not the trace Keep walks, so the keep is skipped on replay. Moving the walks (patch /home/cloudally/wip-scale-moves-trace.patch, not on dev) is NOT enough: on the test copy the re-clean at 2x lands its lines differently and the walks still miss ("a kept trace runs along no line"). Scale took 588 s on the copy alone (so Jordan's ~595 s was not my test's fault). Jordan: fix everything before going on. Next: design so a traced part scales as the traced result, not a fresh re-clean of the whole drawing. 2026-11-09 F fit after Source: with the gray Source layer off (and no trace lines up) F fits the healed part box plus shown annotation ink, not the whole file (job.extents). Jordan: part stayed small after Source mode. Source mode and an open Trace still fit the whole file. Client only, no restart. Tested on the private copy of rec160281: F zoom 80 -> 201 px/in with the layer off; Source on and Trace open unchanged. Gate green (byte-identical), commands 1217 OK. F1 n/a. 2026-11-09 20:33 UTC STEP 2d on dev (Jordan: "yes the same button, but also can we view the source mode and add things that got missed"): while Trace is open, S / the Source button / a new "Source mode (S)" bar button PAUSES the tool instead of closing it: the gray trace lines hide, kept shapes stay green (our frame), and mouse + keys go to Source mode's own tools (tested: Measure took both clicks). S or "Back to tracing" resumes: graph and saved pick reloaded, tracing and Keep work. An unkept trace in progress is put aside dashed on pause; in-tool Undo starts fresh after resuming. Client only (app.js, app.css), no restart. Browser test on the isolated rec160281 copy: no page errors. test_commands_json 1217 OK; identity gate green (byte-identical). F1 n/a. 2026-11-09 20:25 UTC: dev engine restarted for step 2c on Jordan's go (inflight 0/0); tracepick live (an open trace refused, nothing saved), tracegraph serves the pick. 2026-11-09 19:56 UTC STEP 2c on dev (Jordan: "everything I choose using these tools needs to be saved so that we can choose cut this"; "I should be able to use either tool and achieve the same result"): Keep SAVES the pick at once (POST tracepick -> tracepick.json; walks + added lines; refused in plain words if a walk is open or off the lines); the job geometry is never changed. Finish is gone: the bar has name + qty + Cut this, which posts sheetwindow {trace: true} -> the kept shapes become their OWN part job + a Part List row (list made if none), recorded in cutthis.json/sheetintake.json with from=trace, pick cleared; the file traced on stays whole. Reopening the tool brings saved picks back green. Saves queue in click order. trace_keep op kept for replay only (no job used it). Tested on a copy of rec160281 in an isolated tree: circle + 4 holes -> part 3.8458 x 3.8458, 13 true arcs, 0 lines; tooling 1 profile + 4 inside; Keep survived a page reload; Undo saved; no page errors. test_sheet_window 37/37 (7 new), test_chain_trace ALL PASS, test_commands_json 1217 OK, identity gate green (byte-identical). F1 n/a (upload/heal/post untouched). Needs a dev restart (server change). 2026-11-09 18:38 UTC: dev engine restarted for step 2b on Jordan's go (both inflight 0). tracegraph on the grill: gaps 7, ends 272, ?lines= adds 1 edge (3406 -> 3407). 2026-11-09 STEP 2b BUILT on dev (Jordan "yes" to building the screen part): the trace tool on the Geometry tab. Rail button "Trace" + key T (every layout; Part > Trace tool in commands.json, call traceTool). The ENGINE serves everything rule-shaped: tracegraph now also returns gap marks (chain_trace.gap_marks, red circles, markers only) and line ends (chain_trace.snap_ends, Add-line snap targets: free ends, junctions, corners over 30 deg), and takes ?lines=[[x1,y1,x2,y2],...] -- lines added in the tool but not saved yet, walked as add_line prims under the same rules. The shell (app.js TR block, appended at the end) only looks ways up in the engine's table; it ports the test page's behaviour: press a line and drag (goes only as far as the mouse), split labels + look-ahead + close-up, v3.8 drag-pick rule, click a label or press its number, Next split button / Space, press ahead = carry on along the lines (+5" per turn of 120 deg or more), a line not connected parks the trace dashed, Add line button / L (line ends only, length shown), Keep button / Enter (green), Undo button / Backspace / Ctrl+Z inside the tool, Zoom to picked, steps list, faint drawing of every walkable line (visible with layers off). The tool owns the left button only: middle-drag pans, the wheel zooms, right-click stays the app's. Finish saves ONE trace_keep row kept last (+ the added lines as add_line rows before it) through the standing /healedits door; reopening shows earlier kept shapes green and the full set of lines (served from before the row). Cancel / leaving the tab with unsaved keeps asks or says so. Recorded-edits row reads "Trace tool: keep N traced shapes, set aside everything else". Not ported yet: the area (shape-builder) drag and the bend-line hint from the test page. Checked: Playwright on a copy of the grill (private engine on a spare port, the dev engine not restarted): T opens the bar, drag starts a trace, Space runs it closed, Enter keeps, Backspace undoes, Add line (7.5059") reloads the graph with the line in it, Finish saved [add_line, trace_keep] -> part became the kept slot (one closed contour, true arcs, 0 open contours), 874 lines set aside; reopen shows 1 kept; zoom passes through; no page errors. test_commands_json 1217 OK; test_chain_trace ALL PASS; identity gate green (byte-identical). F1 n/a (heal/post untouched in this step; tracegraph is read-only and off the F1 path). Dev engine restart still needed for gap marks, line ends and ?lines (until then the bar works without red circles, Add line snaps nowhere).
2026-11-09 STEP 2a RULING + LIVE ON DEV: Jordan "Keep everything we traced, set aside everything else." trace_keep now sets aside EVERY prim not traced, shapes the trace never touched included (was: only lines connected to a traced shape). test_chain_trace ALL PASS (the untouched hole is now set aside and counted). Identity gate green. Dev engine restarted on Jordan's go (both inflight 0, restart touched dev only); GET tracegraph live on the grill: 200, 3293 nodes / 3406 edges, 4.7s first call (cold), 0.32s after. F1 unaffected (keep() runs only when a job holds the edit; the branch timing from 2a stands).
2026-11-09 STEP 2a BUILT on dev (engine half of the trace tool; no screen yet): the trace now walks the SAME prims the Geometry tab shows (healed + the operator's edits, edit frame) instead of the raw source, so Add line is the existing add_line edit and Keep hands back true sub-prims (arcs stay arcs). chain_trace: Graph takes tagged segments; from_prims() (arcs sampled at equal angles, each edge tagged prim/t0/t1); ways_table() = the walk rules once for every shell ("node,edge_in" -> ways on, straightest first; a shell drops ways whose edge it already used -- shells never re-derive the rules); kept_prims() (a closed walk -> one closed contour of exact sub-prims; consecutive pieces of one prim merge; a jump or an in-tolerance gap becomes a short connecting line); resolve_walk(); keep(). New heal edit op trace_keep {walks: [[node points...]], gap}: each walk becomes a cut contour; every prim connected (within the gap) to a traced shape and not traced is set aside (removed_prims, the delete/weld fidelity exemption; connecting lines ride added_prims); shapes nothing traced touches stay. A walk that no longer lands on the lines is refused on save / skipped with words on replay. GET /api/jobs/<id>/tracegraph = nodes, edges, rules, ways table + kept walks; one tool session = ONE trace_keep row kept last, served from the prims before it (the grill is one connected mess: the first Keep sets everything else aside, the next shape must still be traceable). Checked: test_chain_trace ALL PASS (7 new controls: slot with a spur keeps its two true arcs, spur set aside, untouched hole stays, one closed run, refusal off the ink); real grill copy: a 133-step straightest walk kept, 374 untraced connected lines set aside, pipeline re-ran; tracegraph on the grill 3293 nodes / 3406 edges, 0.31s warm, ~314 KB. test_isoedit/setsize/setfillet/rejoin_runs pass; test_healedit fails one RJB-DS heal-count check (273 prims) with the OLD heal_edit too -- not this change. Identity gate green (byte-identical). F1 first click 8.75s/8.78s -> 8.73s/8.75s (repeat 8.52/8.55 -> 8.52/8.54), no cost. Not live: server.py changed, the dev engine needs a coordinated restart before the screen can call tracegraph. Next: step 2b, the tool on screen (T key, Geometry tab Tools panel), ported from the mock.
2026-11-09 STEP 1 BUILT on dev: Navigator panel, app-wide (Aristide via Jordan; Jordan: "it's an app-wide improvement"; "checked = always on screen, F keeps it; unchecked = still pops up when zoomed in, F hides it"). New panel "nav" with every panel rule (tear off / dock / snap back / collapse / workspaces; old saved workspaces get its default); floats bottom-right by default. Window > Navigator checkmark (on-demand, off by default). Unchecked: pops up the moment the whole scene (the same extents F fits, per tab) is no longer on screen; F puts it away; unchecking also puts it away. Checked: always shown, F leaves it. Shows a snapshot of the canvas cropped to the scene, taken while the whole scene is on screen (at most 4x/s), with a red view box; click or drag in it moves the view. fit() split into fitExt + fitTo with the same behaviour. Playwright on the grill job (localhost:8474): no panel at open; zoom in -> pops up with the box; click in it moves the view; F -> hidden; checked -> shown, zoom + F -> still shown; unchecked -> hidden; no page errors. Known: the snapshot can catch a hover tooltip drawn on the canvas at the moment it was taken. Classic layout has no Window menu, so there it is pop-up only. test_commands_json 1207 OK. Identity gate green (client only, no engine/output change). F1 n/a (no engine hot-path change). Memo to speed: kerf-onums/MEMO-TO-SPEED-2026-11-09-dev-navigator.md. Step 2 (trace tool, T key, Keep sets untraced lines aside like unused layers) next. | 2026-11-09 ~16:35 UTC GO FOR THE REAL BUILD (Jordan: "I am happy with this. Go ahead and implement it the way we have it now."), with Aristide's notes relayed by Jordan: (a) the navigator (overview) becomes a movable panel following the same rules as Tools / Heal-QC / other panels; (b) it pops up by itself the moment you zoom in and the whole part is no longer on screen, and F (fit) hides it again unless the operator has set it as an always-on panel. Plan sent: step 1 navigator panel (client only, every tab), step 2 trace tool in the Geometry tab (engine supplies the walk rules once from chain_trace; Add line reuses the existing add_line edit, which the audit already accepts; Keep becomes a recorded heal edit, Undo through the journal; on every file). Ramifications named: app.js/server.py shared with speed (memo), heal replay touched (F1 timing before/after), stored jobs unchanged unless the new edit is used, prod only on ship. Questions sent (what Keep does with untraced lines; navigator on every tab or only while tracing; how "always on" is set; where the tool button sits). Nothing built yet. | 2026-11-09 mock v3.9 (Jordan: "1. I didn't even realize Space was an option. Yes, displayed items like this are always better. 3. No, I like being able to click and drag still, and Undo seems to be a good tool to make corrections. 4. Again, I don't care about the angle. The issue was that it was going a way that I didn't choose, without asking where to go at the split."): new "Next split" button in the top bar, same as Space (runs on to the next split, one Undo step), greyed out when there is no open trace, at a split, or when closed; help + hint text name it. The v3.6 sharp-turn stop is REMOVED (turns never stop the trace; only splits do). Click-ahead routing still costs a turn of 120 deg or more as 5" extra, so a click further on goes round jogs only when nothing smoother reaches the line (not raised with Jordan; harmless to his ruling, which is about splits). Drag-to-choose stays (his 3, v3.8 rule). Playwright t17: button off at load, on with an open trace, click runs to the next split and greys out; the 3 grill sharp turns no longer stop. t7/t8/t10/t11/t15 same as before. Identity gate green. Mock only. | 2026-11-09 mock v3.8 (Jordan, screenshot: "It was going great, then it just did it here too"; also asked for a CATIA-style "next to branch"): second spot (node at 0.17, 39.12, inner curve meeting the outer one; 2 ways, 47 deg on and 138 deg back) was again a real split the page saw; the drag pick ("nearest way within 22 px, 4 px ahead of the rest") was a guess -- a grid sweep around the split picked the back way at 22 of 169 mouse spots zoomed out (3 the forward way). Now a drag picks only with the mouse within 12 px of one way and every other way AND the trace already drawn at least twice as far and 10 px further, and not within 25 px of the split; labels still pick on drag. Same sweep: zoomed out the only picks are on the back way's own line about 50 px away; at his zoom every pick sits 0.5-10 px from that way's line. Mouse genuinely on a way still takes it. "Next to branch": Space already runs on to the next split; asked whether he wants a button, or pick-and-run-on in one press. t15 (v3.7 spot) and t7/t8/t10/t11/t14 same as before. Identity gate green. Mock only. | 2026-11-09 mock v3.7 (Jordan, screenshot: "I don't care about the angle. Right here ... it did not ask about the split, it just went with it"): the spot (node at 22.74, 39.25: arc on, or a line doubling back 145 deg) was a real 2-way split and the page did stop there; the drag then chose for him. A way that doubles back runs right beside the line just traced, so the mouse trailing a little behind the corner was nearest that way and took it. Now a drag picks a way only when the mouse is clearly nearer that way than the trace already drawn (and not within 18 px of the split); a click right on the split point picks nothing and says so (labels, number keys and dragging out still pick). The v3.6 sharp-turn stop was my wrong guess at the cause; it stays for now. Playwright t15 at his spot: old page ends on the doubled-back line (same as his screenshot), new page keeps asking; dragging out along either way still takes it; key 1 takes the arc. t7/t8/t10/t11/t14 same as before. Identity gate green. Mock only (engine unchanged). | 2026-11-09 mock v3.6 (Jordan, screenshot: "still assuming which way to go on sharp jogs ... not stopping to ask which direction"): the trace stopped only at splits; a sharp turn on a single line (or the one way left at a junction) was followed. Now a turn of 120 deg or more stops like a split: label 1 = round the turn, plus any free line end within jump reach; Space run-on and look-ahead stop there too. Click-ahead routing (shortest way along the lines) now costs a sharp turn as 5" extra, so it goes round jogs only when nothing smoother reaches the line. Grill: 3 plain-node turns >= 120 deg (all stop + message, 1 goes round); t7/t8/t10/t11 pass. Threshold 120 is my pick, to tune with Jordan. Identity gate green. Mock only (engine unchanged). | 2026-11-09 mock v3.5 (Jordan, screenshot: "How do I select the red dotted line without the solid red lines next to it?"): two ways leaving a node within 3 deg were always merged as one doubled line; at the keyhole below (-14.95, 38.00) the pair parts by 0.0114" (over the 0.010 tolerance), so one could not be picked. Now near-same headings merge only if the shorter way ends within one gap of the other (engine Graph._together + mock together()); true doubles (test 2, 0.004) still merge. Grill: 5 near-same pairs, 1 now offered as two ways (124 vs 123 approaches). test_chain_trace 9/9, new test fails on the old rule; live page ways() from below that node = 2. t7/t10 pass. Identity gate green. F1 n/a. | 2026-11-09 mock v3.4 (Jordan: "In Catia, I can insert a line between two points ... precise and a conscious decision by the operator"; 1 yes, 2 line ends only for now, 3 circle click goes away): Add line button / L key: click one line end, then the other; snaps only to line ends (free ends, junctions, corners over 30 deg -- 870 on the grill, curve facet points excluded); dashed preview with length; added line purple, one step, Undo removes; stays on for the next line, Esc leaves; an open trace follows it. Red circles are markers only now. Known limit: where a line stops short of the MIDDLE of another line (bend-line ends on the grill), ends-only snaps to the nearest end, so the added line slants. Real-app ramification noted to Jordan: an added line is not in the customer drawing, so nc_audit would flag it -- added lines must be recorded as operator geometry and accepted by the audit. Playwright: L, two clicks -> 1 user line, gaps 8->7, Undo -> 8; circle click in normal mode does nothing; t5/t7 pass. Identity gate green. Mock only. | 2026-11-09 mock v3.3 (Jordan, screenshot: "Can we include a way to connect the gap here?"): the red gap circle already bridged on click, but only within 12px of its centre while the drawn circle grows with zoom (his was ~30px), so clicks in the circle fell through to the line. Now the whole drawn circle bridges (a line within 5px still wins outside the inner 6px), the circle is checked before the trace-end and split guesses, and an open trace is kept across the bridge. Playwright: trace toward a 0.0138" gap zoomed in (circle 35px), click at 70% radius -> bridged, trace kept; t5/t7/t8 still pass. Identity gate green. Mock only. | 2026-11-09 mock v3.2 (Jordan: "still deleting my progress when I let go, zoom out and pan, then click the next section"): pressing a line while a trace is open now carries the trace on to it along the lines (shortest way over unused lines, reach up to 3x the straight distance, one Undo step), also while stopped at a split (a clicked line wins over the near-split guess); bridging a gap keeps the trace (parks it only if the bridge splits a traced line); only a line with no connection parks the trace dashed. Playwright: Space to split, zoom out x5, right-drag pan, click a line one split past -> trace 12->14, nothing parked; t5 splits + t7 hold-work still pass. Identity gate green. Mock only. | 2026-11-09 mock v3.1 (Jordan: "stopped for a second, then tried to select my next line and it deleted all my progress"): cause = pressing a line away from the trace end started a new trace and dropped the old one with no undo point. Now pressing anywhere on the trace or the line ahead of it carries on to there; pressing an unrelated line (or Esc) puts the unfinished trace aside, drawn dashed, and Undo brings it back. Playwright: drag, release, wait, press 30 nodes on -> trace grows 14->45; press elsewhere -> parked, Undo -> back at 45. Identity gate green. Mock only. | 2026-11-09 mock v3 (Jordan: "not treating this as a split ... overly rushed"): (1) splits were hidden where a curve drawn as short pieces leaves a line -- the sidestep rule judged a way by its first short piece; now it follows the way up to 10 gaps (engine chain_trace + mock; 123 hidden split approaches on the grill now show; test_chain_trace 8/8, new test fails on the old rule). (2) the trace now goes only as far as the mouse is dragged, waits when you let go, never picks a split by hover alone; Space runs on to the next split. Identity gate green. F1 n/a (engine not on any upload/post path). | O92 MOCK-UP v2 2026-11-09 (Aristide asked where the UI could improve; 9 ideas sent; Jordan: "Aristide understood the assignment. Build the one with the most features and let me test it."). Same link (viewer/builds/o92-trace/mock.html), made by o92_trace_mock.py + template. All 9 in: (7) one tool, no modes: press on a line = steer, inside an area = join areas, Shift-drag removes; (6) red circles at gaps too wide to close alone (8 on the grill), click = bridge, areas rebuilt in the page; (1) at a split the drawing fades, labels sit fanned out at the split with leader lines, click a label or move toward a way; (2) faint dashed look-ahead up to 2 more splits (straightest on); (3) a way that leads back to the start gets a filled label + glow ("back to start" / "back to start, N splits on" -- can be a smaller loop such as one panel, not always the outline); (4) close-up box sized to the split, placed opposite the labels; (5) hover: line under the pointer lit, area under the pointer tinted; (8) bend-line hint: long straight lines with part on both sides spanning >=60% of the part, blue dashed, toggle, hint only (20 chains on the grill); (9) step list + Undo (Backspace) for every action, Zoom to picked. Help box hides on first action. Playwright: page ready ~0.25 s; outer top edge stops at the first split with 2 ways (next split / back to start 1 split on); one drag pass joins 37 areas; bridging the 2 gaps of the bottom middle-right panel (0.0138, 0.0104 in) makes it an area, one more click adds it, Keep turns the whole outline + holes green (bend line between panels correctly not cut). No real person has used it yet. Engine/upload/post unchanged. | O92 MOCK-UP 2026-11-09 (Aristide: "Mock both up so he can see and pick"): dev.kerfmaster.com/viewer/builds/o92-trace/mock.html, made by o92_trace_mock.py (+ template o92_trace_mock.html; page in viewer/builds, not in git). Mode 1 STEER: press on a line and drag; runs ahead alone; at a split each way is drawn ahead in its own colour to its next split with a big number and what it leads to (next split / back to start / gap or dead end); move toward it, click it or press its number; a close-up box of the split top right; gaps over the tolerance offered as dashed jumps; Undo step = back one split. Mode 2 DRAG ACROSS AREAS (Shape Builder style): planar areas from the same graph (88 areas, 509 thin doubled-line slivers ignored between picked areas); slots dragged over stay holes; Shift-drag removes. Both: Illustrator-style overview box with a red view box. Walk rules ported to JS from chain_trace.ways for the mock (same constants) -- a mock-only copy, not the Geometry tab. Playwright checks: steer closes a slot from one drag (no stops); steer on the outer top edge stops at the first split with 2 ways (-16 deg, 94 deg); one drag pass gives the outer outline of everything except the bottom middle-right panel, which is not a closed area (its corners have gaps of 0.0105-0.0156 in, just over the 0.010 tolerance) -- steer offers those as jumps; drag-across would need a close-gaps-up-to setting (Illustrator Live Paint has one). Nothing in the engine, upload or post changed. Waiting on Jordan to pick. | Aristide 2026-11-09: asked how Illustrator solves it (Navigator window). Answered: Navigator = small whole-drawing overview with a box showing where you are zoomed (drag to move) -- option D, can pair with A/B/C; also raised Illustrator Shape Builder / Live Paint (click inside a closed area or drag across areas to merge them, with gap closing) as option E: click inside the part, drag across the bend-line panels to join them into one outline. Waiting on Jordan/Aristide pick. Nothing built. | Jordan 2026-11-09 on step 1: "on the right track", but picking the red dots is not the way: needs to be more visually interactive; he would get lost zooming in far enough to see the split directions and lose the context to judge. Options sent (nothing built): A steer by dragging (magnetic: the walk follows the ink nearest the pointer, so a fork is decided by where you move); B whole-way previews (each way drawn ahead in its own colour to its next fork, big numbered labels, click anywhere on it, close-up inset beside the main view); C look-ahead colours (ways that lead back to the start shown differently from ones that dead-end). Waiting on his pick. | O92 STEP 1 BUILT on dev 2026-11-07 ~19:47 UTC (Jordan "1-3. Yes": build step 1; all ways at a fork, straightest first; auto gap jump = job tolerance). New chain_trace.py (engine, data only; nothing in upload/heal/post calls it): noded graph of the source ink (ends within the gap are one node; a line ending on another line splits it), walk while one way on, stop at forks ranked straightest first, fold-backs dropped, doubled copies stepped over (same heading within 3 deg, or a sidestep whose far end is within 2 gaps of the line), gaps wider than tolerance never jumped alone but offered as jumps (up to 0.050, nearest first). Grill (bnm78598 ...-1791386967, 0.010 gap): graph 4.3 s; 42 shapes close with no clicks (all 30 top slots, 5 bottom slots, 2 small holes, 2 end slots, 2 angled slots, 1 corner triangle); outer edge and bend lines stop at the corners for the operator; a scripted left/right-hugging chooser does NOT close the outer (it loops on itself at the bend-relief corners), so the outer needs operator picks. Picture: dev.kerfmaster.com/viewer/builds/o92-trace/grill-trace-map.png. test_chain_trace 7/7. Identity gate green (no output change). F1 n/a (not on any hot path). Step 2 (Geometry tab screen) not started, needs a go. | Jordan 2026-11-07 ~17:50 UTC: "I want to test it on the grill file" (grill job bnm78598-001-0024-pnl-frt-grill). Plan sent (O92): step 1 = trace engine run headless on the grill, picture of traced shapes, no screen; step 2 = Geometry tab tool (click a line, follow, choose at forks, Undo step, closed shape added as an operator edit). Waiting on his go for step 1 + fork/gap answers. Nothing built. | Jordan 2026-11-04 23:2x: lives in the GEOMETRY TAB as its own tool (sum everything into one part, open Geometry, trace what you need out of the mess); 'follow on its own, stop only at forks' is what he wants. No build go yet. Jordan 2026-11-04: as a failsafe for atrocious CAD (the bend-line grill), like the click-next chain trace in a 5-axis CAM he uses. Proposed: auto-run while there is one way on, stop at forks with ranked choices (straightest first), jump small gaps, step over doubled lines, end = closed shape becomes a cut contour. Not built; questions open.
- •O123: Etches sequenced on their own, left to right, then the cuts start back on the left (Jordan 2026-11-17 go; dev, LIVE since 15:42 UTC restart) record — O123 (Jordan 2026-11-17 on the grill bend part bnm-bend-1794771444, 9 bend lines set to etch + 3 holes + outline: 'The sequence is all over the place. It should etch, in a logical order, from left to right, then after etching it should go back to the left side and sequence the cuts in a logical order as we've discussed, and I thought this was solved.') Found: emit.py plans the safe order over ALL contours (etches mixed with cuts), then the bend-line-etch block (~5212) only pulls the etches to the front keeping their relative order from that mixed sequence -- so etches run x 2.1, 6.2, 6.9, 6.9, 3.5, 0.8, 1.6, 5.2, 3.9 and the holes 4.7, 6.8, 2.7 (greedy from where the last etch ended). Proposal: order the etches as their own set (from the lower left, left to right, nearest next), then run the cut sequencer on the cuts alone starting from the lower left, as if the etches were not there; operator-clicked sequences still win. Ramifications to check before building: every part with etches (bend lines, etch text) gets a new order; files without etches byte-identical (identity gate); part lists / nests that post these parts; slug ladder + tab checks walk the new order; F1 timing (planning hot path). Not built. BUILT on dev (Jordan 2026-11-17: 'Yes, this is exactly what I want. Let's build it'): emit.py safe-order branch -- _etch_first = the etches sorted by centre x (rounded 0.01", lower centre first on a tie); _cut_order gains skip= and sequences only the cuts, from the lower-left home; order = _apply_seq(_etch_first + cuts) on both _cut_order calls (the outer re-pick too); the outer re-pick's outs list leaves etches out. Operator clicked sequences still win; the old etch-first block stays as the backstop. Proof: grill copy zz-bnm-bend-o123-1794900000 old -> new etch order x 2.13 6.19 6.88 6.88 3.45 0.77 1.55 5.19 3.90 -> 0.77 1.55 2.13 3.45 3.90 5.19 6.19 6.88(y.33) 6.88(y1.51); cuts unchanged 4.70, 6.77, 2.67, outer (the safety bands: the two small drop-through holes left to right, the 1.38" hole that can tip last before the outer -- the standing tame-first rule, not file order). New test_etch_order 7/7 (2 controls FAIL on the old code); test_etch 9, test_etch_feature 34, test_no_etch_rows 13, test_gseq 18, test_dcond, test_dragcheck 15, test_zone_order, test_tooling_doc, test_double_cut, test_pierce_sub, test_sketch pass; identity gate green (no golden file has etches). F1 first click 8.88s/8.89s -> 8.86s/8.92s. Ramifications: only parts with etches change order (5 dev jobs carry etches in their tooling); stored programs keep their NC until re-posted; part lists/nests posting such parts pick up the new per-part order; no-etch parts byte-identical. LIVE on dev since the 15:42 UTC 2026-11-17 restart (Jordan OK). Checked live on zz-bnm-bend-o123-1794900000: etches 1-9 run left to right (x 0.77 to 6.88), then cuts 10, 11, 12 and the outer last.
- •O124: Cuts go column by column, left to right, snaking; small holes just before their big neighbour; etches swept and flipped; outer at the shop default (Jordan 2026-11-17; dev, LIVE since 17:12 UTC restart) recordreads as fact — O124 (Jordan 2026-11-17, after O123 went live: "You fixed the etch sequence but not the cut sequence." Then sent incoming/1794931100_766705_67119.NC, axle cradle view 1, "This is the ideal sequence... an example of good sequencing only. Ask me any questions."). Read of 67119: 20 etches first, left to right, each etch started at the end nearest where the last one ended; one line at x 25.23 is CUT (#109) in among the etches; then the 42 holes column by column left to right, snaking (up, down, up...), pierce at the right end of each slot; tiny holes cut just before the slot beside them (not all small holes first); outer last, started lower right. Our live order on a copy (zz-axle-v1-seq-1794931200): etches roughly the same, but the cuts start at two tiny holes mid-part (falls-through-first, O100 zone rule) then jump around the part; outer starts lower left. Open questions to Jordan: the x 25.23 cut, column rule, small-hole rule replacing falls-through-first, chained etch ends, outer start, scope (single parts vs nests). Risky: touches cut order on every job (hot path, F1 timing, safety crossings must not go up). ANSWERS (Jordan 2026-11-17): 1 the x 25.23 line is an ETCH (cut in 67119 was his mistake). 2 yes, columns left to right, snaking. 3 zones: in a zone cut the small hole first, then the risky larger cutout next to it, then the head moves away and never flies over the large cut features. 4 yes, chain etches; an etch may be flipped end for end (no offset, no lead, direction does not change the part). 5 outer starts at the shop default location. 6 now: part sequencing; the same clean principles will later apply to nest sequencing. Next: design + ramifications back to Jordan, build on his go. BUILD GO (Jordan 2026-11-17): build on dev; must change the order inside each part in nests too ("this is the whole point"); parts without clear columns go left to right, nearest next. WIP 16:12 UTC: emit._column_order (columns by half-overlap of x ranges, snake up/down, small drop-through holes go just before their nearest big neighbour, safety skip within the next 6), outer keeps the shop default start unless its approach crosses a held slug; switch tooling colseq.on (default on). Patch saved docs/wip/o124-emit.patch (dev tree). On the axle copy the cut order matches 67119 exactly, BUT only with a test switch that lets the head leave a slot across that slot's own end (the head starts at the slot's right end and drops to the next one). Without it our crossing rule calls each in-column move a fly-over and the order scatters. Question to Jordan: is leaving the slot just cut that way OK? Not done yet: etch chaining + flip, nests/part lists check, tests, identity gate refs, F1, crossings sweep on dev jobs. BUILT 2026-11-17 (dev, needs restart): emit._column_order default on (COLSEQ_DEFAULT; tooling colseq.on False = old greedy). Leaving a slot across its own end allowed (Jordan: "The way I did it in my example is fine"). Single outer keeps its default start unless the approach crosses a held slug; several outers keep the old re-pick. Axle copy = 67119 cut order exactly; etch travel 105 vs 123 (old program) vs 148 (O123). 45-job sweep: crossings 11 -> 11, none worse, 15 orders changed. test_column_order 9/9; identity gate: 15 refs regenerated (order + outer start), green. F1 8.87/8.86 -> 8.78/8.76 s. Full entry docs/brick-history.md. LIVE 2026-11-17 17:12 UTC: dev engine restarted on Jordan's 'restart' (both inflights 0); active + 200; axle copy zz-axle-v1-seq-1794931200 re-reviewed on :8474 -- etches first, then cut order matches 67119 column by column (two left holes, col 8 down, col 14 up, col 22 down, small 24.2 then 21 bottom, small 26.3, 29 bottom then up, 36 down, 43 up, 50 5.3, 50 1.0, outer last). DEFECT 2026-11-17 20:1x UTC (Jordan, BNM78879 in the grill package, job bnm78879-002-0001-brkt-grill-stabilizer--1794944048, Al 0.08 GX 10K): order 0.73in hole (2.97,1.40) -> 1.38in hole (0.94,2.54) -> 0.33in hole (5.12,0.60) -> outer. The small-first pull puts the 0.73 hole before its big neighbour, then the rapid big->far hole passes over it (0.34in from its centre, radius 0.365). Not counted because 0.73 is under the 0.75 drop-through, so it is 'falls through', not a held slug. Left-to-right (big, 0.73, far) has no flyover. Fix proposed to Jordan, not built.
- •O125: A small hole cut ahead of its big neighbour goes back to its own place when the head would later fly over it (Jordan 2026-11-17, BNM78879; dev, LIVE since 20:39 UTC restart) recordreads as fact — O125 (Jordan 2026-11-17 on BNM78879: 'I see that it does a smaller hole before a larger hole, but in doing so it has a risky flyover.' Go: '1. Yes.') emit._column_order: after the O124 order is built, a pulled hole longer than the nozzle radius (head_envelope lowest tier, 0.59 in) that a later rapid crosses or passes within the nozzle radius of goes back to its own column place (left to right). The 0.23 in holes in his 67119 stay pulled (he called that fine). Switch emit.COLSEQ_NOFLY. BNM78879: big hole, 0.73 hole, far hole, outer. Axle copy unchanged (67119 order). test_column_order 11/11; 60-job sweep crossings 11 -> 11, none worse, 10 orders changed; identity gate green (no refs changed); F1 8.72/8.71 -> 8.68/8.71 s. Full entry docs/brick-history.md. Not yet: counting rapids over drop-through holes in the recount (separate step). LIVE 2026-11-17 20:39 UTC: dev restarted on Jordan's '2. Yes' (both inflights 0); active + 200; BNM78879 copy and axle copy verified on :8474.
- •O126: Nest method cards in the Clear layout are clickable -- a card packs with its method (Jordan 2026-11-17; dev, LIVE, client only) record — O126 (Jordan 2026-11-17, screenshot: 'I am unable to select any other nesting type. The buttons are there, but they are gray and unresponsive.' Go: '1. Yes'.) app.js clearNestGlance: each card that is not the chosen one and not refused runs KM.plPackStrategy(key), same door as the folded 'pack with this one'; app.css hover. Verified headless with the pack stubbed: 5 cards, clicks give runs/lattice/mixed/free/repeat, no errors. Identity gate green. Full entry docs/brick-history.md.
- •O127: Nest sequence option -- Favor Grids (repeat patterns as macro arrays, the old way) / Favor Sequence (part by part, column by column across the sheet); a toggle, no automatic rule (Jordan 2026-11-17; LIVE on dev since the 21:00 UTC restart) recordreads as fact — O127 (Jordan 2026-11-17 on the grill package O33701: the head went part type by type across the sheet). His answers: '1. ... I prefer toggles instead of hard rules for all these scenarios ... focus on building options that can be more accommodating'; '2. "Favor Grids" & "Favor Sequence"'; '3. Yes. Heat spread is for less risky material, and it's expected by the operator to be all over the place' (heat spread order wins); '4. If this is clear, you may build.' So NO 'mixed sheet' rule and no Auto: a plain toggle. Built: pl_post.column_part_order (columns by centre x, left to right, snaking; a part covering the centres of 3+ columns and at least half of them is a rail across the sheet -- rails split the sheet into bands, bottom band cut whole, then the rail above it, then the next band, bands snaking); server PL_STYLES auto|sequence|partbypart (partbypart kept for jobs that carry it), _pl_sheet_order 'sequence' = part by part on the column order (heat spread and a clicked order still win), POST /api/jobs/<id>/plstyle record-only toggle (drops posted programs on change, like heat spread), /plorder returns style_pick + per-sheet 'why'; machine.json pl_sequence_default 'grids' (shop seed, tables.pl_sequence_default). Client (Nest tab block 'Nest sequence' with Favor Grids / Favor Sequence buttons + Post drawer select) staged at /tmp/o127/app.js.stage, applied with the restart. Checks: test_pl_column_seq 17/17; heat/macro/seq/strip/subcall/progstyle tests unchanged (test_pl_macro's 1 failure pre-exists); identity gate green; F1 8.69/8.78 s (was 8.68/8.71); grill copy zz-grill-o127-1794952000 posts both ways, audit 0 red, Favor Sequence 1299 lines vs 1316; own rough fly-over count over cut parts 12 (Grids) -> 5 (Sequence), rapid length 466 -> 238 in; 2800X fill job: same order either way. Default is Grids, so no existing job changes unless the toggle is set. LIVE 2026-11-17 21:00 UTC (dev restart on Jordan's '1. Yes', both inflights 0): /plstyle + /plorder answer on :8474, client applied, headless browser flips the toggle on the grill copy, no page errors. The 5 fly-overs left on the grill copy under Favor Sequence (cut numbers, own rough count): 7->8 over 6 (bottom band to rail 8's first hole), 10->11 over 9 (part 10 to rail 11's first hole), 14->15 over 13 and 16->17 over 15 (top-left column), 26->27 over 25 (top right). Each flies over the part cut two steps before; Jordan asked where they are (question out). Jordan 2026-11-17 ~21:05 UTC: 'That sequence looked really good now. I will continue to review and give you feedback.' Review ongoing; not shipped to main. 2026-11-18 16:30 UTC DEFECT (mine, owned to Jordan): the test copy zz-grill-o127 kept the real job's id inside its job.json, so the browser opened the REAL grill job (O33701). My headless probe right after the 21:00 restart (2026-11-17 21:01:20) clicked Favor Sequence there: the real job's pl_style = sequence, recorded 'typed in the app', was set by me, not by Jordan. Left as is (Jordan has tested with it since); copy's id fixed. On the real job as it stands now (33 parts, hand-edited 15:13), my fly-over count with Favor Sequence: 8 fly-overs at 5 spots, cut 8->9, 11->12, 17->18, 20->21, 27->28 (read-only count, files untouched). Visible in the app: Nest tab, Rapids layer (R). 2026-11-18 JORDAN: 'For this one I selected Favor Sequence. Favor Grids is chaotic for a nest like this, which is to be expected - that's why I prefer a toggle for different styles.' Favor Sequence on the real grill job is his pick; it stays. 2026-11-18 O129 BUILT on dev (Jordan: 'I like your ideas. Let's test it on this and some other nests'): Favor Sequence steers away from the head passing over parts already cut. server._pl_sheet_geo gives each placement its first pierce, last cut end and outer outline (sheet frame; only computed when the job is on Favor Sequence) -> pl_post.column_part_order(boxes, geo): (2) bands split on a rail's REAL bottom edge at the part's x (a part tucked under a curved rail is cut before it); (4) each column runs from the end crossing fewest cut parts, with one column of look-ahead; (1) each band runs in the direction crossing fewest cut parts, counting the move on to the rail above it, and when it still crosses, tries the band in two runs (up to a pivot one way, the rest from the far end back) -- every pivot on bands up to 40 columns, the 3 nearest the rail's first pierce on wider ones; ties go to the shorter travel; the result is kept only if it is no worse than the O127 order on (passes, travel). New pl_post.flyover_count. Fix 3 (route the head around interlocked hooks) NOT built yet. Counts (my count: straight moves from a part's last cut end to the next part's first pierce over an earlier part's outer outline, the part just left excluded; read-only, Favor Sequence; before -> after, travel in): grill BNM78846 (real job, 33 parts) 8 -> 2, 256 -> 229; rec160281 + 8 more (25) 3 -> 2, 419 -> 399; rec160281 parts (341) 28 -> 18, 2446 -> 2439; 2800X 10.5 REV D (40) 12 -> 12 (interlocked pairs = fix 3); 0 -> 0 and the same travel on BNM94429 front grill panel (8), 8PLASCVRBLK0001 + 17 more (2 sheets), CP-8005-18 + 3 more (16), 1007071 ratchet arm (8), perf-towing-16 (16), axle cradle cut sheet (285), BNM78879 grill bracket (225). Order time: 0.03 s grill, 0.26 s on 341 parts (O127 0.16 s). Checks: test_pl_column_seq 24/24 (7 new: tucked-under-rail part before the rail, rail entered mid-sheet = 0 passes (2 without geometry -- the control), no-geometry = the O127 order); test_heat_spread 43/0, test_pl_seq 27/0, test_pl_strip_order 15/0, test_pl_subcall 18/0, test_progstyle 29/0. Identity gate green. F1 first click 8.74 / 8.75 s (baseline 8.69 / 8.78; F1 is on Favor Grids, untouched). A copy of the grill job posted in a temp jobs dir: audit 0 red, 0 findings. Ramifications: only jobs on Favor Sequence change order (the grill job, BNM94429 front grill panel); Favor Grids, heat spread and clicked orders unchanged; a job on Favor Sequence must be posted again to pick up the new order; the Nest tab numbers follow at once after the restart (same helper). Not live until a dev restart. 2026-11-19 16:05 UTC O129 LIVE on dev (restart on Jordan's '1. Yes', both inflights 0; is-active, 200 local + dev.kerfmaster.com). Engine /plorder on the grill job answers style_pick sequence; the in-process count on the same code gives 8 -> 2 passes. The grill job must be posted again to carry the new order in its NC.
- •O130: Small lettering heals visibly off (FEONA 'O' on SK-227724-A) + bridge tool (manual + auto) -- healing first (Jordan 2026-11-19) recordmixedreads as fact — Jordan 2026-11-19 (screenshot of SK-227724-A, 'FEONA'): 'How would you rate the healing of the letter O? We need a bridge tool to hold in the centers of O and A.' Answers: 1 operator picks + an 'auto bridge' option; 2 click bridges one at a time (manual), auto has tweakable parameters; 3 healing first, then bridge. MEASURED (read-only, job sk-227724-a-1795091538, letters ~0.17 in tall): the O's outer outline is 256 source segments forming a rounded rectangle; at the job's 0.010 tolerance the heal turned it into 10 arcs (straight sides became shallow arcs of r 0.33-0.84, corner radii grew), off by up to 0.0049 in both directions (inside the 0.010 gate, heal PASS, 0 jogs) -- but 0.005 on a 0.17 in letter is plain to the eye. Re-healed in-process at 0.005 / 0.002 / 0.001: 14 / 19 / 21 / 27 pieces in the O; 0.002 matches the source by eye; whole-part heal time 0.32 / 0.39 / 0.64 / 1.42 s. Images: dev.kerfmaster.com/viewer/builds/feona-o/{now,tols}.png. Available today without code: the job's cleaner tolerance field. Nothing built. Bridge code from Aug (bridges.py, pin bridge-emission) exists as scripts only, no app tool. 2026-11-19 ~15:05 UTC ROOT CAUSE (Jordan: 'are we sure A & B are not a patch for a larger issue?' -- yes, they were): the O is drawn as 8 SPLINE entities (F, E, N, A are LINE/polyline and heal clean). Inner rectangle = 4 degree-1 splines (heal as lines, fine). Outer = 4 degree-3 splines, 14 control points each, every one a corner plus half of two straight sides. heal.heal sends every spline straight to fit_biarc_run on the whole tolerance (samples at max(8*tol, 0.006) step) -- splines never go through straight_cover, so a straight stretch inside a spline is never recognised and the fitter bends it into shallow arcs up to the full gate. Second, wider weakness: straight_cover itself spots a straight edge by facet LENGTH (>= 0.05 in and >= 4x median facet), not by straightness, so a polyline whose straight edges are cut into the same short facets as its curves has the same blind spot. Earlier fixes (text-feature-treatment, micro-run-refit, spline-short-curve-fit, O89) covered polylines with long straight facets and short splines; long splines with straight stretches were never covered. Proposed root fix (not built, awaiting Jordan): find straight stretches by measured straightness on the true curve, on every door (spline and polyline), before any arc fitting; A (size-scaled tolerance) and B as first proposed then likely unneeded. 2026-11-19 ~15:25 UTC O130 HEAL FIX BUILT on dev (Jordan: '1. Yes.' to build the real fix and show results before anything goes live). heal.spline_straight_spans(sp): a B-spline knot span whose p+1 control points are collinear (1e-7 in) IS a straight line -- read off the spline's own definition, so a gentle big-radius curve is never taken for a line; adjacent collinear spans merge; stretches under 0.005 in stay with the curve fit. heal._heal_spline_split: such a spline heals as LINE prims on its straight stretches and tangent-pinned fit_biarc_run arcs on the curved stretches between them (tangents from the true curve), exact end-to-end joins checked, else falls back. A spline with no straight stretch takes the old road unchanged. meta['spline_straight'] counts stretches. FEONA O: outer outline now 4 straight sides + corner arcs on the source (picture: dev.kerfmaster.com/viewer/builds/feona-o/after.png); whole part healed->source max 0.0046 (was 0.0049, now elsewhere on the outline). test_o130_spline_straight 10/0 (fails 3 on the old heal: the control); test_spline_thin 12/0. Identity gate green (its corpus holds no SPLINE -- it proves only that non-spline output is untouched). F1 first click 8.70 / 8.70 s -> 8.71 / 8.75 s. Stored-job sweep (old vs new heal in-process, each unique source + its job tolerance, 8 min budget): 49 unique spline sources among 507 spline jobs; 28 identical, 11 changed (all 0 jogs both ways): SK-227724-A, CP-6004-96 (x2), CP-6005-04 (x2, 59 straight stretches), CP-8005-18, B7787, RC-TEST, flat-pattern 480125 rear radar 13, two '--help-p0/p1' probe jobs; fidelity measured on 4 of them: same or better (p1 0.0047 -> 0.0041). 9 not reached in the budget, TL-1016-81 timed out (60 s cap, big file) -- still to check. NOT the polyline side yet: straight_cover still spots a straight polyline edge by facet length; next step after Jordan looks. Not live until a dev restart (the engine caches heal). 2026-11-19 16:05 UTC O130 heal fix LIVE on dev (same restart). Saved jobs keep their stored heal: opening a job does not re-clean it, and the tolerance field re-cleans only on a CHANGED value -- so SK-227724-A still shows the old O. Fresh upload of the same file through the live engine: zz-feona-o130-test-1795104333 (ZZ-FEONA-O130-test.dxf), heal pass, 0 jogs, fidelity 0.0046, the O = 4 straight sides + 8 corner arcs + the 4-line inner rectangle. 2026-11-19 ~16:25 UTC O130 HALF 2 BUILT on dev, NOT LIVE (Jordan '2. Yes': finish the unchecked spline files, then the chain-drawn half). (a) Spline half sweep finished: the 10 left (TL-1016-81..90, xmembers x2) all identical -> 49 unique spline sources, 38 identical, 11 changed. (b) DEFECT OWNED: test_healedit was not run before 8a2aacb3 and fails on it: the real RJB-DS tread (testdata/DWS-LH-2.5-LOGO-TREAD-RJB-DS.dxf, 20 splines, 11 straight stretches) heals to 210 prims (pinned 173), closer to the source (0.0047 -> 0.0041 in), 0 open, 0 jogs, but ONE duplicate flag returns: the two arcs meeting at the source's own cusp near (10.29, 1.667), qc note 'thin junction wedge, not a retrace -- Drop leaves it untouched'. Picture: the old heal bent the lower curve off the source there (that is what hid the wedge); the new heal follows the source. Live on dev since 16:05. Test pin update waits on Jordan. (c) Half 2, heal.straight_cover: EXACT-STRAIGHT RUNS -- 3+ facets whose every vertex sits within STRAIGHT_EXACT_EPS 2e-6 in of the run's chord over >= STRAIGHT_EXACT_MIN 0.02 in are a drawn LINE, whatever the facet length (grown O(1) per point along the line, proven once against the final chord); _one_sided trims a run off the start of a curve and rejects a gentle curve (every vertex bowing the same way). The FEONA O re-drawn as a 6-decimal polyline: old all arcs 0.0052 in off -> straight sides as lines, 0.0023 in. test_o130_spline_straight 13/0 (new: chopped corner keeps its lines; control: a 30 in radius curve sampled every 0.003 in stays all arcs). test_spline_thin 12/0, test_rejoin_runs 13/0, test_healadd 13/0. Identity gate green. F1 first click 8.70 / 8.69 s (before 8.70 / 8.70). Stored-job sweep, half 2 vs half 1 only, random order, each unique source + job tolerance: 178 of 997 unique sources, 176 identical, 2 changed (axle cradle cut sheet view 1 + its zz copy: 579 -> 578 prims, lines 237 -> 251, e.g. a 6380 in radius 'arc' now a line, fidelity same 0.0049, 0 jogs). The 5 MB grill bnm78598 22806 heals in 94.3 s vs 93.9 s (big file, not the change). 819 sources not swept yet. 2026-11-19 ~16:45 UTC RJB-DS TIP FIX (Jordan on the doubled-line note: '1. It shouldn't. This means it's not working as intended. 2. Fix it first. Then I'll test it.'): the source really has a sharp tip there -- two splines leave (10.2523, 1.6645) on the same tangent and open 0 -> 10 thou over 0.07 in (measured on the true source). qc.find_duplicates read the first part of that tip as doubled. New qc._is_tip: a wedge pair (_wedge_dev > 0) that shares an end point and whose gap opens steadily from it (never closing back by more than 0.5 thou) is the drawing's own tip -- no flag at all. A retrace or a long sloppy redraw is not a wedge and still flags; a wedge NOT sharing the point still flags with the Sept wedge note and Drop still refuses it. test_healedit 102/0 (RJB tip pair: no flag, Drop finds nothing; new control: the same arc lifted 1 thou off the point still flags as a wedge; real RJB-DS now 210 prims, 0 open, no doubled flag, 0.0041; B7787 66 -> 71 prims from half 1, everything else the same -- that count was a second miss of mine hidden behind the first failure). test_qc_link 15/0, test_auto_dedup 25/0, test_double_cut pass, spline_thin 12/0, rejoin_runs 13/0, healadd 13/0, o130_spline_straight 13/0. Identity gate green. F1 first click 8.70 / 8.69 -> 8.65 / 8.68 s. Stored-job sweep (932 unique healed geometries, old vs new detector): 9 jobs lose flags, all at tips -- 8 spots looked at by eye (stencil-sign letter tips, grill crescent tips, rec160281 small triangle tips) are all true sharp tips; rec160281 keeps 1706 of its 1794 flags (its real doubled ink stays found), lucas stencil sign 19 -> 1. Not live (needs the restart, with half 2). 2026-11-19 17:37 UTC LIVE on dev (Jordan '1. Yes'; inflight 0/0 on both sides; kerfmaster-app restarted, active, 200 local + dev.kerfmaster.com). Tip fix + half 2 (chopped straight edges) now live. Half 2 still unswept on 819 sources. Verified on the live engine: RJB-DS uploaded as zz-rjb-ds-tipfix-test-1795109859 heals to 210 prims, 0 QC flags, auto-dedup found 0. 2026-11-19 Jordan tested on dev: 'It looks great now!' 2026-11-19 ~18:10 UTC FULL SWEEP (Jordan: 'check the rest of the files'), pre-O130 heal vs final, 843 of 999 unique sources so far: 825 identical, 16 changed (7 closer, 7 same, max 0.0049), 2 errors that pre-date O130 (bnm78598 parts 32 and 60, old heal fails the same way). It caught a defect: the O81 arc merge folded a found straight edge back into an arc (bnm78842 bracket 0.7 -> 2.6 thou). Fix on dev, NOT live: exact-straight runs and spline straight spans record their ends (meta straight_pts) and the merge treats them as hard points. bnm78842 now 1.1 thou, its mirror bnm78846 1.9 (was 0.7 before O130) -- merge re-arranged next to the line, inside the 5 thou budget, 0 jogs. All heal tests pass, identity gate green. F1 not yet timed (sweep was loading the box). 156 sources left (hung on mid-size files). 2026-11-19 18:47 UTC: SWEEP DONE (997 of 999 unique sources + job tolerance; per-file subprocess, 120/300 s cap): 965 identical, 23 changed (8 closer, 13 same, 2 further: bnm78842 1.1, bnm78846 1.9 thou), 0 jogs either side. Two sources off more than 5 thou are the same before and after (CP-6005-04 about 6 in -- geometry left out, pre-existing; black-box-and-lid 9.9 thou) -- separate look later. 2 pre-existing errors (bnm78598 parts 32/60). 9 not settled: 6 timed out in the checker after both heals finished, at the same heal time where measured (TL-1016-81 30.0 vs 30.4 s); 78598-bendline-proof and grill-with-bend-lines part 53 (61 MB) time out on the OLD heal already; the 5 MB bnm78598 flat sheet old heal 231 s, new not finished in the cap. Jordan: '1.9 thou deviation without a kink, jog, or changing the look is acceptable' (picture dev.kerfmaster.com/viewer/builds/feona-o/bnm78846.png) and 'You may restart when ready'; he also offered to drop the bad grill file from the checks. F1 first click 8.65/8.68 -> 8.71/8.72 s (merge guard). Dev restart 18:46 UTC (8474 and 8475 inflight 0): merge guard 1512c166 LIVE; zz-bnm78846-mergeguard-test-1795114020 heals to 33 prims / 14 lines, same as in-process. 2026-11-19 ~19:10 UTC Jordan: nest order (O129) not shipping yet ("we are going to be working a lot on nesting... finish testing it before we ship it"); asked whether the healing fixes can ship without the nest order. Bridge tool moves to its own pin bridge-tool (O131). SHIPPED to main 2026-11-19 ~19:23 UTC (Jordan: "1. Yes, ship with O89." -- O89 + O130 healing; O129 nest order and the trace tool stay on dev). Shipped: heal.py = dev heal.py (O89 3f02bb80/fb40fcaa/52c88e47 + O130 8a2aacb3/1545f986/1512c166), qc.py tip fix only (cf1dc50b; O104 trace part of qc.py NOT shipped), tests test_healedit + test_auto_dedup (dev copies), test_o130_spline_straight, test_subtol_pieces. On the main tree: test_healedit 102, spline_thin 12/0, rejoin_runs 11/0, healadd 13/0, o130_spline_straight 13/0, qc_link 15, auto_dedup 25/0, double_cut pass, subtol_pieces pass. Identity gate green on main (byte-identical). F1 first click on the main tree 8.46/8.48 s -> 8.75/8.74 s (+0.27 s, O89 measured +0.25 s on dev).
- •O131: Bridge tool -- finder + yellow warning, manual bridge (1 click square to the feature / 2 clicks set the direction), auto bridge, width per material + tool width box; part-list Bridge column renamed Gap (Jordan 2026-11-19) recordmixed — Jordan 2026-11-19 ~19:10 UTC, bridge tool go ('We can do the bridge tool now'), answers to the 4 questions: (width) 'I would like to be able to set a default per material, as well as have a width input on the tool.' -> width seeds from a per-material table value, the tool has its own width box (operator override, recorded). (manual) 'Can we have both? Maybe an automatic angle that would be perpendicular to the feature being bridged, and then a 2-click that will direct the angle?' -> 1 click = bridge square to the feature at that spot; 2 clicks = operator sets the direction. (part-list column) 'Yes, gap is more suitable here.' -> the part-list column now labelled Bridge (the clearance around a part) is renamed Gap on screen; stored key stays 'bridge' so saved part lists keep working. (step 1) 'Yes.' -> start with the finder: yellow warning + marks on every upload where a piece of metal would fall out. Plan: (1) finder + warning, (2) manual click bridge as removable rows, (3) auto bridge with settings, (4) cutting checks: no lead or pierce on a bridge. Tab vs bridge stay separate (bridge = permanent, holds islands in). The August bridges.py (20-thou raster, 0.080/0.125 Python literals) is not reused as-is: finder rebuilt on exact geometry, widths move to the table. Nothing built yet. 2026-11-19 ~19:18 UTC step 1 PROTOTYPE (scratch /tmp/feona/finder_proto.py, not in the app): closed contours from the healed geometry, nesting depth by containment, metal inside a hole (even depth >= 2) = falls out. FEONA: 2 found (O and A centres; the August raster finder found 1), 0.01 s. RJB-DS, BNM78846: 0. 2514 stored jobs: 48 with finds, slowest 4.4 s (44558b-7, needs speeding up). FALSE ALARMS on drawing sheets: the title frame makes every part a hole and every hole an island (23004-697, rec160281, f1-release sheets). Next: run it per part (the part split the upload already does), not over the whole sheet; then wire the yellow warning + marks. 2026-11-19 ~19:32 UTC STEP 1 BUILT on dev, NOT LIVE (Jordan: "Go"). qc.find_islands(prims): closed runs of the healed geometry -> polygons (arcs at 1 thou chord sag, never output geometry), nesting depth by containment (STRtree); every even depth >= 2 = metal inside a hole with nothing holding it -> qc flag kind island {pt inside it, area, bbox, note "falls out ... needs a bridge"}. Server run_pipeline appends them to qc_flags (summary key island) EXCEPT on a drawing sheet still waiting for Cut this or a PDF/.ai sheet at its printed size (the title frame turns parts into holes; the cut parts get the check). Client: the existing QC-spot path draws them as yellow rings on Geometry, Tooling, Post and every placed copy, green-flaggable; label "Falls Out (needs a bridge)". No NC output change (identity gate green, byte-identical). test_o131_islands 9/0; test_healedit 102, qc_link 15, auto_dedup 25/0, double_cut, upload_formats 18/0, sheet_window 40/0. F1 first click 8.71/8.72 -> 8.65/8.65 s. Speed: 44558b-7 4.4 s (prototype) -> 0.02 s; FEONA 0.002 s. Stored jobs (read on their saved geometry; a saved job only shows it after a re-upload/re-heal): FEONA 2 (O and A centres), Lucas & Barretts positive-parts sign 26 letter centres, main-gusset-rh 1 ring, iso-verify 1; known false alarms left: PDFs uploaded before O103 that never got the printed flag (rec160281-1794244832 202, hang-p001 5) -- a fresh upload gets the printed flag and is skipped. Ramifications: qc stage turns flagged on parts with islands (jobs list and part-list QC counts show it); warn only, nothing blocked, posting untouched. LIVE on dev 2026-11-19 19:31 UTC restart (Jordan: "restart"; 8474/8475 inflight 0). Check: fresh upload zz-feona-islands-test-1795116710 -> qc flagged, summary {island: 2}, flags at (-4.0898, 6.6467) and (-4.3233, 6.6108) (A and O centres). Screen ring not yet seen by me (the welcome tour covered the canvas in the headless shot). | 2026-11-19 19:37 UTC: Jordan sent a screenshot of zz-feona-islands-test -- yellow rings on the A and O centres CONFIRMED on screen. Jordan: "Go on step 2". Step 2 plan (manual bridge) sent to Jordan for a go before building: 1 click = bridge square to the feature at that spot, across to the nearest edge; 2 clicks = operator sets the direction; width box seeded from the August widths (0.080 counters under 2 in, 0.125 bigger, never under thickness) moved into the tables; each bridge a removable recorded edit row (new heal_edit op); island flag clears once bridged; part-list 'Bridge' label -> 'Gap' (key stays bridge). Questions open: seed values per material or one shop-wide pair; bridge cut as a gap in both walls; where the 2-click mode lives. Nothing built for step 2 yet. | 2026-11-19 19:44 UTC -- O131 bridge-tool step 2, chunk 1 (engine): new heal_edit op 'bridge' {a:[x,y], b:[x,y], width} (Jordan 2026-11-19: "click on both ends of the bridge", "one bridge per click", width depends on material/thickness AND feature size/shape). A strip of the given width centred on a->b; each clicked wall loses the piece inside the strip (exact, arcs stay arcs via _prim_cut), the two strip edges become new straight walls. Two different loops -> one loop (island hangs on the bridge); same loop -> split in two. Refuses (strict) / records refusal (replay): no wall within 0.25 in, open chain, width <= 0, strip not crossing the wall cleanly, ends overlapping. Report row carries removed_prims (the cut pieces) and added_prims (2 strip edges + the trimmed walls next to them); server.py adds 'bridge' to the jog exemption (weld/move_end pattern). Checks: test_o131_bridge 19/0 (square ring area exact, split on 2nd bridge, circle ring keeps arcs, island flag clears, refusals, replay); FEONA zz-feona-islands-test: 0.020 bridges on the O and A -> find_islands 2 -> 0, picture viewer/builds/feona-o/feona-bridges.png. Heal-edit suites green (healedit 102, noop, isoedit, turned_edits, healadd, rejoin_runs, qc_link, auto_dedup, double_cut, subtol, spline_thin, o130, o131_islands). Identity gate green. F1 not measured: the code only runs when a bridge row exists, and it is not live until a dev restart (the running engine is the old code). NOT built yet: the screen tool (two clicks, width box), the 1-click square-to-feature form, the width seed table (open: values per material/thickness/feature size), the part-list Bridge->Gap label. Ramifications: heal edits only (new op; existing ops untouched, suites green); a bridged hole changes cut contours -> leads/cut order/post see one merged loop (not yet checked through post on FEONA); stored jobs unchanged (no row = no change); nest unchanged (outer shape untouched); speed n/a until restart. | 2026-11-19 20:06 UTC -- O131 bridge-tool step 2: Jordan's own bridged FEONA (MetaCam DXF, incoming 1795118643) is now the golden test (golden/o131/feona_jordan_bridged.dxf + feona_healed.json). Measured from his file: 4 bridges, all 0.0200-0.0201 wide; O top + bottom and A crossbar square to the letter (94.4-94.6 deg = the letters' 4.4 deg lean), A apex along the left leg (81.1 deg). Jordan: what he did to the O and the bottom of the A is what he meant by 'perpendicular to the feature'. The bridge op given the same centre lines lands on his walls within 0.0001 in both ways (44 vs 42 prims; 0 islands left). Picture viewer/builds/feona-o/feona-vs-jordan.png. test_o131_bridge 22/0. Identity gate green. Test only, no engine change. | 2026-11-19 20:26 UTC -- O131 bridge-tool step 2 chunk 2 (screen tool + 1-click). Jordan's answers: FEONA is 0.020 718 nickel, nitrogen fiber cut, 0.020 bridges = accurate + adequate, a tradeoff against the look; 1 click = square to the wall unless 2-click gives a different landing point. Engine: bridge row without 'b' = 1-click: from the wall point nearest the click, square to that wall into the cut (side inside an even count >=2 of outlines), to the next wall (_bridge_square); clicks are projected onto their walls (_on_wall). Server: healmarks seeds gain bridge_w = the job material's thickness (no material = no seed, the operator types; nothing invented). Client (Geometry > manual edits): 'Bridge' (1 click) + '2 clicks' buttons + width box (placeholder = the seed); one recorded edit per bridge, refusals toast the engine's words; edit-list text 'Bridge W wide ...'. Checks: test_o131_bridge 26/0 (adds: 1-click = 2-click on the square ring, from the island wall, refuses on the outer profile; FEONA O-top 1-click angle = Jordan's 94.4 deg). Heal/QC/edit suites green. Identity gate green. F1 not measured: not live until a dev restart (healmarks/edit paths only, first click untouched by design). Not yet: canvas marker for the first of 2 clicks (a toast says it), run a bridged FEONA through toolpath+post+audit (after restart), Gap label rename, per-material width table (seed is thickness for now). | 2026-11-19 20:28 UTC -- O131 bridge-tool step 2 LIVE on dev (restart; Jordan: 'Yes and yes' -- also OK on width seed = metal thickness; 8474/8475 inflight 0). F1 first click 8.65/8.65 -> 8.65/8.68 s. End-to-end: fresh upload zz-feona-bridge-test-1795120165, three 1-click bridges via /healedits (O top, O bottom, A crossbar, 0.020) all applied; QC flagged {island:2} -> done (0 flags). Review Mild Steel,0.06 / MSO7,0.060 / GX 10K (no 0.020 nickel row exists) + post on the bridged and the unbridged copy: both post, audit findings only pierce_standoff yellow (tiny letters vs the 0.150 lead row), bridged 11 of 12 features vs unbridged 12 of 13; no off-source, comp or traffic finding; 13 -> 12 boundaries as expected (O split in two halves, A joined). | 2026-11-19 20:3x UTC -- Jordan: (1) he will try the bridge tool on FEONA himself before the 2-click marker / Gap rename; (2) no 718 nickel row: the lasers have no setting for it, operators pick an existing row (most likely 0.040 stainless). Waiting on Jordan's try. | 2026-11-19 22:44 UTC -- O131 bridge-tool step 3 (Jordan's notes after cutting FEONA on the laser from dev: 'everything looks functional'; wants snap to centre points + click-and-drag to reposition, 'functional and aesthetic'; answers: centre = middle of the clicked wall, drag slides along the current wall, Alt works independently on each end of a 2-click bridge). Built: (1) midpoint magnet in both bridge modes -- the nearest healed segment's midpoint within 14 px rings with a crosshair + chip 'middle of the wall (Alt: free)'; each click reads Alt itself. (2) Drag: every placed bridge shows a square handle at each clicked end while a bridge mode is armed; grab + slide along that end's wall (line clamped to the segment, arc on its circle), live dashed strip preview, the wall midpoint magnets (Alt free); release MOVES the same edit row (a or b) and re-heals once; press without drag changes nothing. (3) 2-click first end now shows a dot. Engine: bridge report rows gain ends (resolved wall points) + walls (the wall prim under each end). Checks: test_o131_bridge 28/0, edit/QC suites green, identity gate green. Not live until a dev restart; screen not yet exercised in the browser (planned right after the restart). F1 not measured yet (after restart). Ramifications: bridge rows only; a dragged bridge rewrites its own row's a/b (one row, still removable); other ops/stored jobs untouched; old bridge rows without ends/walls in the report simply show no handle until re-healed. LIVE 2026-11-19 22:46 UTC (dev restart on Jordan's OK, inflight 0/0): step 3 live. F1 first click 8.69s / 8.68s (before 8.65s / 8.68s, no change). Browser test (Playwright, fresh FEONA copies): hover near the O-top middle shows the ring + "middle of the wall" chip and the click lands exactly on the midpoint; Alt held places the bridge where the mouse is (0.0044 in off the middle, as aimed); the handle drag slides along the wall with the dashed strip and the drop rewrites the SAME row (one edit, re-healed). Found on screen: every drawing edit switches its tool off after it saves (shared behaviour of all hq tools), so the handles hide right after a bridge is placed until Bridge is pressed again -- drag works once re-armed; question to Jordan whether Bridge should stay on. A drag dropped at the very end of a wall is refused by the engine ("does not cross this wall cleanly"), row unchanged, nothing lost. G-code on the dragged-bridge copy (Mild Steel 0.06 / MSO7 / GX 10K): posts, audit 9 findings all pierce_standoff yellow (tiny letters), same class as before. Pictures: dev.kerfmaster.com/viewer/builds/feona-o/bridge-drag.png. STEP 4 (2026-11-19, dev, not live until a restart; Jordan: "Exactly", corner like his MetaCam A, and "yes" to stop short of the wall end): (1) Corner bridge -- heal_edit op bridge gains the form {corner, a, width}: _bridge_corner finds the corner (two walls of one outline meeting), carries the wall nearest `a` straight on past the corner, strip on the other wall's side, its side line through the corner; refuses in words when the corner isn't one, or carrying on runs into metal. Screen: the Bridge magnet rings corners too (nearest of middle/corner within 14 px) and names the wall under the mouse; a 1-click corner records {corner, a}; a 2-click end on a corner sits flush (half the width + 0.0002 along the wall). Corner rows have no drag handle (pinned to the corner: remove + re-click). (2) Drag can no longer slide a bridge off its wall: kept half the width + 0.0002 from both ends; the middle and the flush-at-the-end stops pull within 14 px; Alt frees the pull, the clamp stays. (3) Alt now hides the magnet ring in Bridge modes (the chip says free). Checks: test_o131_bridge 37/0 (new: one corner click on the A tip lands on Jordan's apex bridge within 0.0002 in; a square-box corner; mid-wall and into-metal refusals); 13 neighbour suites green; identity gate green; engine accepts flush square bridges at both ends of the O top. Fixed on the way: a square corner's back end sat ON the other wall and was skipped (caught by the box test). Ramifications: bridge rows only; existing 1-click/2-click rows replay unchanged (the corner path runs only when a row has `corner`); other tools, stored jobs, G-code without bridges untouched. F1 to be measured after the restart. Browser not exercised yet. STEP 4 LIVE 2026-11-19 23:42 UTC (dev restart on Jordan's OK, inflight 0/0). F1 first click 8.90s / 8.76s / 8.67s (before 8.69s / 8.68s; the first-click path has no bridges -- noise). Browser (Playwright, fresh FEONA copy zz-feona-corner-test-1795131832): hovering a few px down the left wall from the A's inner tip rings the corner ("corner bridge -- carries this wall on") and names the left wall; the click recorded {corner, a} and the A tip now carries its left wall up to the top, as in Jordan's file. O-top 1-click then re-armed drag pulled 12 x 8 px past the wall end: the handle stopped flush (0.0102 in from the end, "flush against the end of the wall"), the drop saved on the same row. Corner rows show no handle (1 handle for 2 rows). No page errors. G-code (Mild Steel 0.06 / MSO7 / GX 10K): posts, 11 boundaries, audit 9 findings all pierce_standoff yellow (tiny letters), same class as before. Cosmetic seen: while dragging, the hover chip and the drag chip both draw. Picture: dev.kerfmaster.com/viewer/builds/feona-o/bridge-corner.png. STEP 5 (2026-11-20, dev; Jordan: "why didn't the bridge continue to link the outer wall to the inner wall?" + "yes" to sliding round corners + "yes" to the rule): a dragged 1-click bridge keeps linking the same two outlines, slides round corners onto the next wall of its own outline, and stops where it can't link them. Screen: brBefore rebuilds the drawing as it was before that bridge (strip edges out, cut-out wall pieces back, outlines by endpoint connection), brDragTry finds the nearest spot on the own outline (each wall kept half a width from its ends), square across on the side it already runs, and accepts it only when the centre and both strip edges first meet the same far outline; otherwise the bridge stays at its last good spot ("stops here" chip). The drop records `to` (a point on the far outline). Engine: _bridge_square(to=) refuses in words when the first wall hit is not on the outline of `to`. 2-click and corner rows keep their old drag. Cause of Jordan's A: a 1-click bridge only knew its own wall; above the triangle tip, square across first meets the A's own left side. Browser (fresh FEONA, preview on the not-yet-restarted engine): A bridge dragged up stops below the tip then carries round onto the A top, linking down to the triangle tip; O-top bridge slides round onto the O's right side, still linking the inside; no page errors. Also: the hover chip no longer draws during a bridge drag. Checks: test_o131_bridge 41/0 (new `to` cases: links below the tip, refuses above it, same geometry when it links); 13 neighbour suites green; identity gate green. Ramifications: bridge drags only; placing bridges, existing rows (no `to`), other tools, G-code without bridges unchanged. Not live until a restart; F1 after. STEP 5 LIVE 2026-11-20 01:41 UTC (dev restart on Aristide's OK, inflight 0/0). F1 first click 8.75s / 8.74s (baseline ~8.7s; unchanged). Browser (Playwright, fresh FEONA zz-feona-live5-1795138882): A bridge dragged up past the tip and round onto the A top saved with to=(-4.0915, 6.6766), linking down to the triangle tip; O-top bridge slid round onto the right side saved with to on the inside; no page errors. Engine check live: on zz-feona-refuse-1795138973 a bridge whose `to` sits on a different outline is refused ("would no longer link the same two outlines -- slide it back"); the same bridge with its own `to` applies. G-code (Mild Steel 0.06 / MSO7 / GX 10K) on the dragged job: posts, audit 9 findings all pierce_standoff yellow, same class as before. STEP 6 (2026-11-20, Jordan "stay on until switched off"): Bridge (1-click and 2-click) stays armed after each saved bridge, a refusal, or a recorded-edit remove; the Bridge button switches it off. Every other drawing tool still puts itself down after a save. Client only (hqPostEdits keeps bridge/bridge2 mode + crosshair); served live on page reload, no restart. Browser (fresh FEONA zz-feona-stayon-1795192528): two bridges placed without re-arming, list remove kept Bridge on, button turned it off, Delete then armed normally; no page errors. Identity gate green; test_o131_bridge 41/0. F1 not affected (bridge mode only, not on the first-click path) -- not timed. Jordan also skipped the sliver warning (2026-11-20). Open: no way to remove a bridge from the drawing itself; today only the remove button on its recorded-edits row (proposal sent).