Skip to content

#291 PF-25: simplify discharges a conditional lemma from a named hypothesis of the statement - #303

Draft
humuhumu33 wants to merge 48 commits into
release/v0.5from
claude/issue-291-simplify-hypotheses
Draft

humuhumu33 wants to merge 48 commits into
release/v0.5from
claude/issue-291-simplify-hypotheses

Conversation

@humuhumu33

@humuhumu33 humuhumu33 commented Oct 23, 2026 •

Copy link
Copy Markdown
Contributor

Fixes #291 on the 0.5.0 line. simplify can now discharge a conditional lemma's condition from a hypothesis of the theorem's statement, so a theorem of the form P x → (f x = 0 ↔ Q x) is proved from a lemma that holds under P x. This is the statement UOR-Foundation/mcp#24 could not write.

The form (SPEC §17.12, PF-25)

The row added to the §17.12 table of language-1.2 constructs:

| simplify hypotheses | lexlean/semantic-module/2 | {"kind":"simplify","definitions":[...],"hypotheses":[h...]} (hypotheses omitted when empty): names for the leading premises of the goal, in order. It lowers to intro h1 … hn and then simp only [h1, …, hn, d1, …]: the hypotheses lead the rule set, which is still exactly the names the source states. Lean discharges the condition of a conditional rule by simplifying it with the same set, so a prior theorem whose rewrite holds under a condition (P x → f x = v) rewrites where a named hypothesis discharges that condition. Linking requires the goal to be the theorem's statement (the proof itself or a branch of cases or induction), at most as many names as it has leading implications, and names that are fresh and distinct, so none of them is among the definitions. A theorem whose hypotheses do not discharge a rule's condition is rejected by Lean (LLV7002). |

The hypothesis is bound by the statement's →, the way nested_induction binds its induction hypotheses in #278. No tactic, option or lemma comes from anywhere but the source, and no raw Lean enters.

In the notation:

theorem{
  name: three_byte_complete_zero_iff,
  parameters: [b1 : Nat, b2 : Nat, b3 : Nat],
  statement: (((leadE1ToEC b1) = true) -> (((scanThree b1 b2 b3) = 0) <-> (((inRange 128 b2 191) = true) /\ ((inRange 128 b3 191) = true)))),
  proof: simplify{definitions: [lead_e1_ec_step, three_byte_zero_iff], hypotheses: [lead]},
  axioms: [Classical.choice, Quot.sound, propext]
}

This lowers to:

  intro lead
  simp only [lead, lead_e1_ec_step, three_byte_zero_iff]

Register (R3)

The case (conformance_pf_25)

The case builds a module in the shape of MCP#24's three-byte row for lead bytes E1..EC (Table 3-7):

  • lead_e1_ec_step is conditional on the lead byte's class.
  • three_byte_zero_iff holds for all bounds.
  • three_byte_complete_zero_iff composes the two, as above.
Copy Result
The module Lean verifies it with exact policies: the step lemma [Quot.sound, propext], the zero test and the composed statement [Classical.choice, Quot.sound, propext]
The premise of the ED class (leadED b1 = true), which does not imply the lemma's condition LLV7002, `simp` made no progress
A policy without Classical.choice LLV7005
Hypotheses in a constructor branch, more names than premises, a parameter's name, a hypothesis also named among the definitions, the form under language 1.1 LLT4001 at linking, before any build output

The case also checks the generated Lean: intro lead, then simp only [lead, …].

Plants (VERIFICATION.md)

Each plant was one edit in a separate worktree, restored with git checkout. Each turns conformance_pf_25 red.

  1. The hypotheses dropped from the simp set, with the intro kept. lexlean verify reports LLV7002, `simp` made no progress: no other rule discharges the condition.
  2. The ED variant made true. The case fails because the copy now verifies.
  3. The forged policy made the observed one. The case fails because no LLV7005 comes.

Identity

The language-1.2 compiler-semantics ID moves, from 5262e5b4… to 583ff8e2…. The reasons:

Commit f48de99 substitutes the ID and lets the writers regenerate their records: check-golden, check-calculus, check-production-export, check-fixtures, then verify-examples without uor-atlas. All 15 non-Atlas examples, compiler, stdlib and bootstrap verified under the new compiler, so every committed proof still verifies.

State of the base. #296 landed on release/v0.5 at 80bf4ba after this head was pushed, and it moves the same ID (to 9fdf4d30…). This PR therefore conflicts on every lock and expected record, and the ID it computes (583ff8e2…) is stale. #295 and #300 move the ID as well. The merge with #296 and one more run of the writers are needed once, on top of whichever identity PR lands last, so I have not repeated them for each landing. Say which order you want, or merge this one last.

Run locally (WSL, Linux x86-64, Lean 4.32.1)

Not verified locally

  • uor-atlas. It was not verified here, because it is CI-only evidence. It is a language-1.0 project, whose ID does not move, and no file of it changed, so its records stand.
  • The rest of just vv. That includes the full bdd suite, which is CI's.

🤖 Generated with Claude Code

humuhumu33 and others added 7 commits October 23, 2026 11:47
…f_25 (#291, R3 skeleton)

The language-1.2 simplify proof form may name the leading premises of its
goal, introduce them, and add them to its closed simp only set, so that a
prior theorem whose rewrite holds under a condition rewrites where a named
hypothesis discharges the condition.

The case builds a module in the shape of UOR-Foundation/mcp#24's UTF-8
lead-byte classes (Table 3-7, E1..EC): a step lemma conditional on the
lead byte's class, the zero test of the row's conditional, and the
composed statement. It fails on this commit: the schema has no
`hypotheses` member.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
`simplify` gains `hypotheses`, names for the leading premises of the goal.
It lowers to `intro h1 … hn` and then `simp only [h1, …, hn, d1, …]`, so a
prior theorem whose rewrite holds under a condition rewrites where a named
hypothesis discharges that condition. The rule set is still exactly what
the source names.

Linking (LLT4001) refuses hypotheses where the goal is not the theorem's
statement (only the proof itself and branches of cases and induction
carry it), more names than the goal's leading implications, a name already
in scope or repeated (a hypothesis cannot also be named among the
definitions), and the form under language 1.1. A theorem whose hypotheses
do not discharge a rule's condition is rejected by Lean (LLV7002).

The semantic-module and snapshot schemas gain the optional member, and
semantic_ir moves 15 -> 16 and proof_lowering 3 -> 4: the language-1.2
compiler-semantics ID moves. The records are regenerated in the next commit.

SPEC §17.12 gains the row of the form (through `cargo xtask spec`).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…fy-hypotheses

# Conflicts:
#	CHANGELOG.md
The lead-byte module verifies with its exact policy; the ED variant is
rejected by Lean (LLV7002, `simp` made no progress); the forged policy is
refused (LLV7005); the hypotheses dropped from the simp set, the ED variant
made true, and the forged policy made the observed one each turn
conformance_pf_25 red.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…generated by the writers

The semantic-module and snapshot schemas gain `simplify.hypotheses`, and
semantic_ir and proof_lowering move to 16 and 4, so the language-1.2 ID
moves from 5262e5b4... to 583ff8e2.... The ID was substituted, then
check-golden, check-calculus, check-production-export, check-fixtures and
verify-examples (without uor-atlas) rewrote their records; every example,
compiler, stdlib and bootstrap verified under the new compiler.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…otheses

# Conflicts:
#	CHANGELOG.md
#	VERIFICATION.md
The merge of #288 kept its count of 445 in the generated total; the
register has 446 rows. Regenerated by validate-model --write.

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
…otheses

# Conflicts:
#	README.md
#	SPEC.md
#	VERIFICATION.md
#	spec/lexlean.lock

afflom commented Oct 25, 2026

Copy link
Copy Markdown
Member

Maintainer review of 551b0f985 (read from the diff against its merge-base 34cfc1282, nothing built). Accepted in shape; it lands on release/v0.5 after #300, once it is re-merged and regenerated. Nothing in PF-25 itself needs a design change.

What checked out. R3 order (78a732a95 holds the row, the scenario and conformance_pf_25 at conformance.rs:798; the implementation follows in 186f0284f); the statement is byte-equal at ids.toml:962, proofs.feature:170 and the §31 row, and both spec rows are made in spec/src/Chapter17.lex.tex:883 and IdsPF.lex.tex:191-197 with SPEC.md as their projection. The schema stays closed (hypotheses: array of names, minItems 1, uniqueItems, additionalProperties: false kept in both v2 schemas; the 1.1 schema untouched). Linking is the §17.12 rule as written: check_proof carries the goal (Some(statement) from check_theorem, through cases/induction, None through constructor), check_simplify_hypotheses (semantic.rs:8503-8534) requires 1.2, counts the leading implications, refuses excess, repeated and in-scope names, and the hypotheses join proof_binders, so binder hygiene refuses one spelled like a declaration or a built-in. The lowering (backend/semantic.rs:1219-1241) emits intro only when there are names and the rule set is exactly the source's names, hypotheses first. Every refusal is under a registered code (LLT4001, LLV7002, LLV7005; no new code, so ERRORS.md rightly unchanged). Three plants with red lines at VERIFICATION.md:17006-17062. No deferral marker.

Identity. Keep both bumps (semantic_ir 15→16, proof_lowering 3→4): the IR gains a member and the generated script gains a line form, which is what the two version (§21.2). Languages 1.0 and 1.1 do not move (their semantics files and every 1.0/1.1 lock are untouched). The branch's 583ff8e2… is superseded by the merged tree's digest in any case.

Before it can land (blocking, as you anticipated):

  1. The branch is unmergeable: #263 PF-24: runtime bounds a law proof cites (split_exact, UTF-8 decode, UInt32 checked_add) #296 (PF-24) moved the same 1.2 ID, so 2,547 paths conflict (every regenerated record and lock, plus CONFORMANCE.md, README.md, SPEC.md, VERIFICATION.md, model/ids.toml, proofs.feature, IdsPF.lex.tex, spec/lexlean.lock, cases/proofs.rs, conformance.rs). Merge release/v0.5 (after [0.5.0] #279: a fallible loop's ends are in its function's tail (RB-21) #300 lands, so you do it once), resolve the PF-24/PF-25 appends, set the count to the merged register at README, SPEC §31 total and the CHANGELOG sentence, then rerun the writers on the merged tree (check-golden, check-calculus, check-production-export, check-fixtures, verify-examples --write, without the Atlas).
  2. The PR body still says 446; state the merged count and the final 1.2 ID.

Nits, in the same push: the stray blank line after the "Register 445." CHANGELOG entry; proofs.rs:1 doc range (PF-01..PF-25) once PF-24 is in; conformance_pf_25 exercises the in-scope name but not a repeated name nor one spelled like a declaration, one refused copy of each would plant the two branches the schema and hygiene carry; and settle "hypotheses": []: the schema says minItems 1 while check_simplify_hypotheses is skipped on an empty list, so either the schema validation already refuses it before serde (then say so) or the check runs on the empty list too.

Order on the 0.5.0 line: #300 (one push owed, then merge), then this one, then #295. Say the head here when it is up.


Generated by Claude Code

afflom commented Oct 26, 2026

Copy link
Copy Markdown
Member

release/v0.5 now carries the 0.4.0 line (#322 merged at 61b4638cd; register 472; #279's loop-end row is RB-22 and #126 stage 2's rows are SL-06 to SL-08, the release/v0.4 rows keeping their numbers). Merge origin/release/v0.5 into this branch and recount; it then proceeds in the v0.5 order. The second forward merge (H5, H6, the release-workflow fixes) follows #304's landing.


Generated by Claude Code

afflom commented Oct 27, 2026

Copy link
Copy Markdown
Member

release/v0.5 moved: the second forward merge (#327) is merged at 1046646ed, bringing release/v0.4 at a1b925dc6 (the v0.4.0 tag, H5 #298, H6 #304, the release-workflow fixes #320/#321/#323) onto this line. Language 1.2 identity dcdf8a721708f0a9c5e57303f78eef5f5e37c58b7a11a04272d8670f618a699f (1.1 and 1.0 unchanged); register 474 (RB-21 and SP-30 join; RB-16, RB-17, RB-19, RB-20, SP-29, BS-05, BS-06, BS-09 restated). Before the next push here, merge origin/release/v0.5 by merge commit and recount; locks and records are regenerated at the landing, not in the draft.


Generated by Claude Code

afflom commented Nov 3, 2026

Copy link
Copy Markdown
Member

Queue refresh at unchanged head 551b0f9: this work is still needed; PF-25 is absent from current release/v0.5 (2849449). #296 and #300 have landed, so they no longer block the source refresh. #295 remains separate.

The earlier empty-array question is now resolved by inspection: parsing does not run the JSON Schema validator first. Simplify.hypotheses defaults to an empty Vec, check_proof invokes check_simplify_hypotheses only for a nonempty list, and ignored_member permits the serialized-away empty array. Therefore the implementation accepts hypotheses: [], while both published v2 schemas require minItems: 1. Please align the authored-input/schema contract and add a focused regression, along with the previously requested repeated-name and declaration-name refusals, before regenerating identities. This does not call for another validation framework.

Keep this existing draft and refresh it by merging current v0.5, preserving the normative spec/src changes. Coordinate the final writer wave with #405/#396 instead of regenerating another stale baseline. Record the actual final ID/count and complete gate on that head; #291 stays open until the implementation lands. No current-head CI evidence was found in this refresh.

afflom commented Nov 3, 2026

Copy link
Copy Markdown
Member

Maintainer coordination at unchanged head 551b0f985: I am preparing only the narrow source-input correction for explicit JSON hypotheses: [] and the previously requested repeated-name/declaration-name PF-25 refusal copies, in an isolated checkout for review. The existing nonempty-array schema contract, omitted hypotheses and ordinary authoring forms will be preserved. No changes to this contributor branch or independent identity regeneration are being made; #291 remains open pending integration and final acceptance evidence.

afflom commented Nov 3, 2026

Copy link
Copy Markdown
Member

The narrow source follow-up is now durable for this PR's coordinated refresh: commit cd0c6b7a9, on maintainer branch fix/pf25-source-contract. It is a direct child of this PR's unchanged 551b0f985 head; remote tree 7be7dca81f81384f748c5c640a7cb3287ebcf958 matches the independently reviewed local tree. No new PR was opened, and the contributor branch was not moved.

The field-specific deserializer enforces the existing nonempty supplied-array contract: explicit hypotheses: [] is refused, while omitted/default and nonempty forms retain their behavior. PF-25 gains the requested repeated-name and declaration-name refusal copies; the repeated-name copy has two leading premises so it reaches the duplicate check. No schemas, identity inputs, lowering, workflows or generated records change.

Focused evidence: the new source-contract test first failed because an explicit empty array was accepted. The final test passes through the actual notation and semantic-module parsers, including language-1.2/v2 omitted, nonempty and empty cases and legacy v1 omission. Direct CLI checks accept the original and omitted-hypotheses lead-byte copies and reject repeated, declaration-name and empty copies with their expected LLT4001 messages. CLI build, lexlean/repo-conformance all-target/all-feature Clippy with warnings denied, formatting and whitespace checks pass. Full PF-25/Lean verification, regeneration and full acceptance are not claimed here.

Please incorporate this single reviewed commit into the existing branch during its coordinated source refresh, then merge the current v0.5 line, reconcile the register/counts and identity inputs, run the official writers once on the agreed integration tree, and collect final full-gate evidence here. This existing PR remains the sole issue-closing PR for #291; the maintainer branch is prepared review work, not a competing implementation. Its feature-branch push matches none of the CI/honesty/reproducibility push filters, and no Actions runs were created for the published commit at the verification check.

Alexander Flom and others added 6 commits November 3, 2026 21:49
Source-only implementation for #434, preserving shared Decimal parse
evidence, exact policies and frozen older-language files.

Runtime/compiler identities and official products remain deliberately stale
until the coordinated v0.5 wave. This known-incomplete source commit skips
CI; final changed-head full acceptance and CI are mandatory before merge.
No post-fix policy, output or certificate pass is claimed.
The target's value semantics clones a record to read one field, and Rust
copies an in-place record whole on every clone and move. For a program
whose states are large records this dominates run time (84% memcpy in the
uorc search engine) and gives functions frames large enough to overflow
the default stack. rust-std now boxes every field whose type is a datatype
with a field-carrying constructor, reusing the existing box/unbox
rendering and its certificate; rust-core is unchanged.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3Nk2H9geAZ2GKFCNvM
A shared box realizes `indirection` like a cyclic one, so the rendering
check accepts the box a non-recursive record field now lowers to.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3Nk2H9geAZ2GKFCNvM
update bytes at byte is the byte string with the byte at `at` replaced, or
none past its end. rust-std renders it as Bytes::update (update_bytes,
Item.updateBytes, Machine.bytesUpdate, family 40), writing in place when the
buffer is unique and copying, counted, when it is shared; the Lean runtime
uses ByteArray.set!. RustStd states refines_update_bytes, certificate A
gains prim_update_bytes, the preservation library's RustCorr, RustLemmas,
and Primitives gain the cases of the new constructors (kernel-checked), and
the bootstrap twins, conformance encoders and the RB-20 differential follow.
The compiler-semantics ID moves; the records bound to it are regenerated
(uor-atlas verification records excepted).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3Nk2H9geAZ2GKFCNvM
claude and others added 22 commits November 14, 2026 22:11
The three negative fixtures whose request pins rust-core now pin its
descriptor digest under the moved renderer, so each reaches the refusal it
records rather than LLC0203.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
Decimal formatting's runtime and certificate sources move the language-1.2
compiler-semantics ID to 6558e37caeeccfcdd86a54c31db6143364f4c8ae4a0c409c4d07dfaec5c11df2.
Every tracked lock whose only change is that ID is relocked with the built
compiler (267); LANGUAGE_1_2_SEMANTICS_ID takes the recomputed ID.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
release/v0.5 numbers the decimal machines 40..43, so the byte update is
machine family 44 (item family 50 is unchanged): ast.rs, the certificate-B
names, the bootstrap printer and validator, RustSyntax/RustSemantics (both
the source and the committed Lean), and the conformance counts follow. The
std crate, its refinement theorems and RuntimeStd gain update_bytes beside
the decimal functions; every theorem unfolds the same definitions. Portable
gains LexLeanRuntime.update over release/v0.5's slice. Generated outputs are
release/v0.5's, rewritten by the landing regeneration.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
The ToString operands of Portable, Fixed and RustLemmas were written under the
node labels they replaced, but each new constant is a node of its own, so the
labels after it named the wrong nodes (LLP2001: "this statement defines node
3602, not node 3600"). The edited statements are unchanged; `lexlean fmt`
numbers the nodes again from symbolic labels. All 19 runtime and preservation
modules are canonical.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
Portable and RustLemmas carry both changes: #437's ToString operands for
formatting and this branch's LexLeanRuntime.update and its cases, numbered
again by `lexlean fmt`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
The head is #303's with its reviewed follow-up cd0c6b7 (fix/pf25-source-contract).
PF-25 and PF-26 are claimed on release/v0.4 (#507), so simplify hypotheses
are registered as PF-28. The schemas and the semantic IR keep both lines'
proof forms; semantic_ir and proof_lowering move to 17 and 5. Generated
outputs are release/v0.5's, rewritten by the landing regeneration.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
The landing regeneration writes every generated output again; the ones this
branch committed were made on its old base. rust_renderer records the merged
renderer sources.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
The SPEC.md text of this branch is written into its chapter module, at the
machine family release/v0.5 leaves free.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
The canonical graphs move the ID to 8c54fe7b15d5ddf9ff9848559747031aaf161e3793ffa932e46c63e6df475972;
written by `just relock-identity`.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
Update joins the primitives nat_bitwise_function maps to None (the match v0.5 added), the
merge marker left between refines theorems in RustStd is removed, and rust_runtime_std is
written by `cargo xtask semantics-records --write` (#545).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
check_simplify_hypotheses gets its Ok tail back, the nested-induction member branches
v0.5 added pass no goal (a member's motive is not the statement), and the inert
Simplify arm of proof_binders is dropped for the one that visits the hypotheses.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
The write recipes of SPEC.md §9.2, run by regenerate.yml (https://github.com/UOR-Foundation/lexlean/actions/runs/43649832487),
rewrote 5502 paths.

The counts writer reported:

    BS-05 SEEDED_REFUSED_VALIDATE: 273 -> 275 (crates/conformance/src/cases/bootstrap/rust_validate.rs)
    BS-05: §31 row: nothing
    BS-05: the §31 row does not state 273 (-> 275)
    BS-05: register: nothing
    BS-05: scenario: nothing

    VERIFICATION.md rows for the landing (counts | before | after):
    | `BS-05` SEEDED_REFUSED_VALIDATE | 273 | 275 |

    wrote /home/runner/work/lexlean/lexlean/CONFORMANCE.md and /home/runner/work/lexlean/lexlean/ERRORS.md

    written, with SPEC.md and the model projected again; next: the parts without LEXLEAN_COUNTS
…olation

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
…-core

The byte update moves the ID to cddcb1b0bef5b765fcabe89be5e25ef0ec8a3b736049f058c782adb3df03be6f and the
rust-core descriptor to 4bf56bf9 (the renderer record moves).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
The semantics records take #443's renderer and std runtime with this change's
semantic_ir 17; README counts both landings (523).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
The simplify hypotheses move the ID to a29ba62ccdf8f7200ddc7bcffd4a54d61bf1dd12f1e00a1ff866e51ffac848b6.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
The isolated decimal formatting no longer reaches Classical.choice or Quot.sound,
so the exact policy of the production-coverage root follows (LLV7005 on regeneration).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
afflom pushed a commit that referenced this pull request Nov 15, 2026
The two schema members merge structurally; README counts the four landings (525).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
github-actions Bot and others added 5 commits November 15, 2026 02:13
Its lock came from #441 under that change's ID and was skipped by the relock (LLC0102 in fixtures-write).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
…ge-1.2 ID

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
…ge-1.2 ID

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX
afflom pushed a commit that referenced this pull request Nov 15, 2026
Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_013Asa3M8ULnzEQwLLngyBBX

This branch has not been deployed

No deployments
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.

3 participants