Skip to content

chore(maps): scheduled regen - #814

Merged
bryanmaclee merged 1 commit into
mainfrom
maps/regen-33614345277
Sep 2, 2026
Merged

chore(maps): scheduled regen#814
bryanmaclee merged 1 commit into
mainfrom
maps/regen-33614345277

Conversation

@bryanmaclee

Copy link
Copy Markdown
Owner

Automated maps + @generated regen (cloud-maps beachhead). gate runs on this PR; auto-merges on green. No branch-protection bypass.

@bryanmaclee
bryanmaclee enabled auto-merge (squash) September 2, 2026 09:29
@bryanmaclee
bryanmaclee merged commit 0b5392d into main Sep 2, 2026
2 of 3 checks passed
bryanmaclee added a commit that referenced this pull request Sep 2, 2026
…to zero, and a locus that was disjoint from its answer (#816)

GAPS. g-value-form-sugar-in-bound-position-emits-null -> RESOLVED via #815 (908a631),
PA-verified on MERGED main rather than on the branch. Two corrections to that entry as
filed, both from execution:

  (a) Its `locus=searched:` named emit-html.ts, emit-each.ts and emit-control-flow.ts.
      The responsible site was in NONE of the three — it is emit-logic.ts, a FOURTH file,
      reached via the const-decl/let-decl dispatch through `node.ifExpr`. The searched-set
      was not merely incomplete, it was DISJOINT from the answer. Routed to the nav-maps
      per base §5: a locus error that recurs across dispatches is a map gap wearing a
      brief's clothes.
  (b) Its claim "the explicit-`lift` twin is the control and is correct" holds for the
      LOCAL binding only. For a derived cell BOTH forms fail — so anyone building against
      that sentence works from a false control.

TWO NEW ENTRIES, same root as the one #815 closed, which is why #815 is correctly scoped
as one position of a class and not the class:

  - g-bare-expr-in-if-arm-rebinds-tilde-context-corrupting-the-result-var (HIGH,
    PA-reproduced on merged main, SURVIVES #815). Hits the CANONICAL
    `'{' statement* lift-stmt statement* '}'` production. The corpus misses it on a
    technicality — phase2-if-as-expr-intermediate-014.scrml uses a `let`-decl, which does
    not rebind; only a bare EXPRESSION does. RULING OWED.
  - g-nested-if-as-expression-arm-body-binds-null-silently (MED, RELAYED-VERIFIED-BY-
    REVIEWER and labelled as such — not PA-re-executed). Filed as a fail-SILENT direction
    defect, NOT as a missing feature: §17.6.1 makes the shape unspecified, so supporting
    it is a widening and is bryan's.

REVIEW FLOOR: 1 OWED -> 0. Markers for #812, #813, #814, #815. Code-bearing carve-out
rate holds at 2/163 (1%); the 59% all-PR figure is the volume statistic the S319 note
says not to read as a health signal.

REVIEWER-VS-DEV, ADJUDICATED BY EXECUTION. The S239 pass claimed #815 removes a
ReferenceError/implicit-global class. It does for a SUGAR else arm and does NOT for an
explicit-`lift` else arm — and the explicit-`lift` form is the one §17.6.1's canonical
grammar documents. Recorded in the new HIGH rather than accepted as filed.

DRIVE-BY, in a file already open: g-each-value-form-if-markup-fn-call-branch-stringifies
carried `status=resolved` on its marker (with a bite-proven prov= from S392-peter) while
its HEADING still read `open`. A heading-based sweep saw an open entry the field-based
probe saw closed. Heading corrected; no status change. This is the exact divergence base
§2 warns about — and it cuts against the overlay's own "match on the heading, not on
marker adjacency", since S385 measured headings as the LOSSY side.

Counts move HIGH 77 (-1 resolved, +1 new) and MED 200->201, which is the proof the new
entries are machine-visible rather than prose-only.
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.

1 participant