Skip to content

docs(skills): roadmap — snapClip bed-flat volume pin resolved #1108

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
andymai merged 1 commit into from
Jul 17, 2026
+18 −4
Merged

docs(skills): roadmap — snapClip bed-flat volume pin resolved #1108

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 18 additions & 4 deletions .claude/skills/roadmap/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -256,8 +256,15 @@ snapClip family — THREE roots CLOSED 2026-07-16 (#1080, #1082, #1085); deepene
cache — captured operands are fallback-poisoned, never replay them directly),
the by-edge-id acceptance gate is BLIND to position-duplicate leaks (poison
propagates silently — evaluate a position-quantized gate), and the bed-flat
clip volume 46.701 vs 46.6±0.05 pin (genuine deviation, the reference kernel
passes — per-op dual-kernel volume diff).
clip volume 46.701 vs 46.6±0.05 pin — RESOLVED, NOT a brepkit defect: the
per-stage dual-kernel diff localized the whole delta to the relief cut, whose
cutter (buildSingleCellSocket) brepkit represents as EXACT ANALYTIC (native
census F=34 {plane:18,cylinder:8,cone:8}, zero NURBS — the #1045
loft-recognition) while the reference keeps a NURBS loft that bulges ~0.062mm³
and over-removes 0.146mm³ from the clip corners. brepkit's 46.701 is the MORE
Comment on lines +262 to +264
accurate value; the pin is calibrated to the reference's loft approximation
(the "snapshot pins are kernel-specific" class). Resolution is tool-side pin
recalibration, not a brepkit change.

Fit-offset groove-mouth sliver family — CLOSED (2026-07-16, PR #1078, fixture
`crates/io/tests/fitoffset_groove_mouth_inmem.rs`): each groove cutter's mouth
Comment on lines 256 to 270

@greptile-apps greptile-apps Bot Jul 17, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Resolved item left in open-work REMAINING list

The bed-flat clip volume pin is now marked RESOLVED, but it is still embedded in the REMAINING after the deepened-opening union... sub-section of the snapClip family block. An autonomous session using this file as its work-selection oracle will read this section, see a REMAINING list with three entries, and may still treat the volume pin as actionable — especially because the heading says "deepened-notch remains" and the list structure implies all three bullets are open. The resolved entry should be removed from the REMAINING list (or the list suffix should explicitly exclude it) so the open-work set is unambiguous. The same issue applies to the second mirrored copy of this block at line ~577.

Fix in Claude Code

Comment on lines 258 to 270

@greptile-apps greptile-apps Bot Jul 17, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Entry violates the document's own one-line rule

The file's maintenance contract (line 15) reads: "Keep every entry to ONE line with a pointer (a test path, a git-history PR number, a memory-free source file) that carries the detail. Never duplicate the detailed truth here; point at the repro." The new text is ~5 sentences of inline prose. If the resolution detail is worth preserving, a pointer such as RESOLVED — see PR #1108 dual-kernel diff would satisfy the rule; the full breakdown belongs in the PR or a linked note, not inline. The same applies to the mirrored copy near line 585.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

Fix in Claude Code

Expand Down Expand Up @@ -570,8 +577,15 @@ snapClip family — THREE roots CLOSED 2026-07-16 (#1080, #1082, #1085); deepene
cache — captured operands are fallback-poisoned, never replay them directly),
the by-edge-id acceptance gate is BLIND to position-duplicate leaks (poison
propagates silently — evaluate a position-quantized gate), and the bed-flat
clip volume 46.701 vs 46.6±0.05 pin (genuine deviation, the reference kernel
passes — per-op dual-kernel volume diff).
clip volume 46.701 vs 46.6±0.05 pin — RESOLVED, NOT a brepkit defect: the
per-stage dual-kernel diff localized the whole delta to the relief cut, whose
cutter (buildSingleCellSocket) brepkit represents as EXACT ANALYTIC (native
census F=34 {plane:18,cylinder:8,cone:8}, zero NURBS — the #1045
loft-recognition) while the reference keeps a NURBS loft that bulges ~0.062mm³
and over-removes 0.146mm³ from the clip corners. brepkit's 46.701 is the MORE
Comment on lines +583 to +585
accurate value; the pin is calibrated to the reference's loft approximation
(the "snapshot pins are kernel-specific" class). Resolution is tool-side pin
recalibration, not a brepkit change.

Fit-offset groove-mouth sliver family — CLOSED (2026-07-16, PR #1078, fixture
`crates/io/tests/fitoffset_groove_mouth_inmem.rs`): each groove cutter's mouth
Expand Down
Loading