Skip to content

Walkthrough rule 2: catch shifted and derived vars items - #357

Merged
Kyu-seok merged 2 commits into
masterfrom
walkthrough-vars-shift-derived
Nov 18, 2026
Merged

Kyu-seok merged 2 commits into
masterfrom
walkthrough-vars-shift-derived

Conversation

@Kyu-seok

Copy link
Copy Markdown
Owner

Summary

Closes #300. varsRepeatingTheData (#273's second rule) now also catches a vars item that repeats the data off by one frame or in a derived form.

 repeats(item in a run)
   values drawn on the data, same frame        # place, pointer, span start/end/length, label, whole list
+  derived, same frame                          # pointer or span start/end ±1, span's to - from, list in another order
+  if none of those: a drawn value a frame late or a frame early (every pair of frames drawing both, two or more)

Message names the form, e.g. pointer "right" of array "xs", plus 1, a value in map "counts", a frame late. why still excuses an item from every form, and a why repeating nothing still fails.

add-walkthrough step 3 lists what the test can't catch, each with its reason: a part of a drawn list in vars, and a value with a position kept only in vars.

No derived form was dropped: none raised a false alarm. No tracer was regenerated: all 22 Walkthroughs pass unchanged.

Evidence

  • Before: the new breakage cases on varsFixture() fail as not caught:
    item a frame late, item a frame early, item a pointer plus 1, item a pointer minus 1, item a span's exclusive length, item a list in another order → []
  • After: all caught with the form named. Quiet: a parameter, a why kept by a new form, an item matching in one pair of frames. Breaking the two-pair threshold made that last case fail as it should.
    noVarsItemRepeatsAValueDrawnOnTheData passes on every Walkthrough; com.codebite.problem 365/365, full backend suite green.

Merge Danger

Door: two-way

Test and skill text only; no production code.

Blast Radius: tests

A future Walkthrough whose vars item follows the data off by one now fails noVarsItemRepeatsAValueDrawnOnTheData until its tracer draws it or gives it a why.

🤖 Generated with Claude Code

Kyu-seok and others added 2 commits November 18, 2026 23:26
A vars item now also fails when it follows a drawn value plus or
minus 1, a span's exclusive length or a list in another order, or,
following none, a drawn value a frame early or late (#300). Partial
lists and positioned values kept only in vars become review items in
add-walkthrough step 3. All 22 Walkthroughs pass unchanged.

Closes #300

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@Kyu-seok
Kyu-seok merged commit 26c7f7f into master Nov 18, 2026
5 checks passed
@Kyu-seok
Kyu-seok deleted the walkthrough-vars-shift-derived branch November 18, 2026 14:52
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Walkthrough rule 2: cases the vars check misses

1 participant