Commit 26d16af
proto(#262): Phase-3 measurement — slot model = value path for all predicates
Measured the first Phase-3 question (is the assignment-driven slot model
viable as the single model?) by extending slot coverage to name-based
(global) bindings and running the suite flag-on.
Result: 45 failures, ALL of the form "got 0 expected 1" — full-window
predicates returning false because the slot window is exactly 1 short. Not
a sampling-regime divergence: the slot model matches the value path for
every predicate. The sole gap is a 1-count FIRST-ASSIGNMENT lag on name
bindings — the binding is created by the upcoming SET_NAME and does not
exist at OBSERVE_ASSIGN time, so the slot starts at the 2nd assignment.
(Function-locals are unaffected: their slots are pre-allocated by the
compiler, so they observe from assignment 1 — Phase 2 already green.)
So the assignment-driven slot model is sound; Phase 3 needs first-assignment
coverage for name bindings (observe-at-SET, or slot-promote interrogated
module vars), then report on the single model, then delete the value path.
Exploratory name-based shadow reverted to keep Phase 2 flag-on green; the
finding is recorded in the OBSERVE_ASSIGN comment.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>1 parent f049fe0 commit 26d16af
1 file changed
Lines changed: 8 additions & 3 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
3664 | 3664 | | |
3665 | 3665 | | |
3666 | 3666 | | |
3667 | | - | |
3668 | | - | |
3669 | | - | |
| 3667 | + | |
| 3668 | + | |
| 3669 | + | |
| 3670 | + | |
| 3671 | + | |
| 3672 | + | |
| 3673 | + | |
| 3674 | + | |
3670 | 3675 | | |
3671 | 3676 | | |
3672 | 3677 | | |
| |||
0 commit comments