Skip to content

docs(r1-briefs): working-state refresh — testgen/surface/selfhosting post-2026-04-24 merge wave - #738

Merged
briansrls merged 21 commits into
mainfrom
session/zesty-bear-812
Apr 24, 2026
Merged

briansrls merged 21 commits into
mainfrom
session/zesty-bear-812

Conversation

@briansrls

Copy link
Copy Markdown
Contributor

Opened from session-dashboard for session zesty-bear-812.

briansrls and others added 18 commits April 24, 2026 00:42
…edger row (post-#693 escalation)

Director-authored amendment following the 2026-04-24 escalation from PR
#693 (sub-child sharp-bear-829 under Surface Manager).

Two edits:

1. New "Class 5 Gap 3 — port-carried field values in data bodies"
   row in the 2026-04-21 post-merge-debt section. The substrate gap was
   documented in src/v3/DOWNSTREAM_REQUIREMENTS.md:239 but had no ROADMAP
   ledger row for cross-lane visibility. PR #693's execution surfaced it
   as the blocker on sub_charclass_in_std_unicode phase-2.

2. Retract the "ready-to-dispatch (no substrate capability gap)" claim
   on the Character-level row, annotate phase-1 landed via PR #693
   (CharClass vocabulary + Rust-mirror structural scanner path), and
   point phase-2 at the new Class 5 Gap 3 row.

Codifies the audit pattern: "this consumption gap has no substrate
capability gap" claims must be verified by attempting the retype before
the claim lands.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
…-1 status edits + char_in_class interpreter-parity sibling row from main
…-5.4 review)

Row title still said 'consumption gap, not substrate gap' while the
body block retracted that claim and cited Class 5 Gap 3 as a substrate
dependency for phase-2. Title now matches body: mixed classification,
consumption for steps 1+3, substrate for step 2.
…lass phase-2 blocker classification (per gpt-5.4 audit)

gpt-5.4's review on 706 @ 71f46af caught that the row's "remaining
gap" description was wrong: field-level shapes (nested records, list
literals, declaration refs, Var refs, sum-variant literals) are
supported today via FieldValue variants + lower_structural_field_value
(dag.rs:328-353, lower.rs:2616+). The actual remaining gap is the
top-level ValueBody boundary (non-scalar, non-record top-level bodies).

The authority I cited — DOWNSTREAM_REQUIREMENTS.md:239 — is itself
stale: it describes the pre-PR-B-unwind shape where FieldValue was
LiteralBits-only. PR-B's unwind extended FieldValue to carry
Reference / Record / List / Variant, moving the gap to ValueBody.

Two fixes:

1. Rewrite the Class 5 Gap 3 row to describe the actual ValueBody
   boundary, point at code paths (dag.rs, lower.rs) as live authority,
   flag DOWNSTREAM entry as itself stale, and soften phase-2 CharClass
   blocker classification to "provisional pending reproduction."

2. Update the Character-level row's phase-2 block to name that the
   specific shape of the CharClass failure needs concrete reproduction
   from the escalating sub-child before the blocker is finalized.

Recursive audit-pattern instance: the row I wrote to codify "verify
live state before claiming substrate gap" itself failed to verify live
state. Both incidents (2026-04-23 original row + 2026-04-24 my
retraction row) are now cited in the audit-pattern sub-note as
examples of the same discipline.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@briansrls

Copy link
Copy Markdown
Contributor Author

PM review — docs-only working-state refresh across three manager briefs.

Verified

Cross-manager signals (why this clears brief-PR-cadence)

Suggestions (non-blocking)

1. Surface brief — update Cross-manager notifications queued section. The current text reads:

(none yet — coordinate with Self-hosting when T-Sub first gate lands; coordinate with Testgen when T-Emit emit_omni_demo_fixtures_green predicate shape needs defining)

First T-Sub gate (sub_match_over_user_sum) has now landed per #702. Either retire that clause or flip it to an active "notify Self-hosting: first T-Sub gate landed (#702)" entry so the section doesn't advertise a conditional that has already fired.

2. PR title. Repo convention for working-state-refresh PRs (see #700, #720, #723) uses descriptive docs(<brief>): working-state refresh — ... form. Consider retitling before marking ready for review so the squash-merge commit lands with a searchable subject.

No invariant violations; ready to mark for review once (1) is addressed or consciously deferred.

@briansrls briansrls changed the title gunbc Director docs(r1-briefs): working-state refresh — testgen/surface/selfhosting post-2026-04-24 merge wave Apr 24, 2026
@briansrls
briansrls marked this pull request as ready for review April 24, 2026 16:40
@briansrls

Copy link
Copy Markdown
Contributor Author

Review metadata

  • Provider / model: claude / claude-opus-4-7
  • Commit: 4e606603 · Trigger: schedule
  • Thinking: 9.7s wall

Docs-only change updating status trackers in three brief files. No code, no substrate.

Verdict: APPROVE — diff is docs-only (status/decision-log updates across three r1-*-manager briefs). No invariant, modeling, coding, or testing rule applies to working-state bookkeeping. Dates, PR refs, and checkbox transitions look internally consistent.

@briansrls

Copy link
Copy Markdown
Contributor Author

Review metadata

  • Provider / model: codex / codex-default
  • Commit: 4e606603 · Trigger: schedule
  • Thinking: 140s wall

Verdict: APPROVE — docs-only refresh, and the changed lines keep closed vs pending work clearly separated. No concrete violations of the pinned invariants, modeling discipline, coding, or testing guidance observed in this diff.

@briansrls
briansrls merged commit 34126f0 into main Apr 24, 2026
8 checks passed
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