Skip to content

fix(dupe-bodies): token_floor and token_floor_scenes use pbr_sphere's clamp01 instead of copying it (Refs #10451) - #10468

Closed
gHashTag wants to merge 1 commit into
masterfrom
claude/clamp01-share
Closed

gHashTag wants to merge 1 commit into
masterfrom
claude/clamp01-share

Conversation

@gHashTag

Copy link
Copy Markdown
Owner

7552b89 (#10452) left three byte-identical clamp01 bodies, in
specs/t27f/pbr_sphere.t27, token_floor.t27 and token_floor_scenes.t27. No
ledger holds that group, so the Duplicate Body Ratchet has been red on
master since 7552b89, and every open PR shows the red.

pbr_sphere's clamp01 becomes pub. token_floor and token_floor_scenes
now say use t27f::pbr_sphere::clamp01; and drop their copies, the way
token_floor already uses pbr_sphere's shade. Neither module imported
anything that imports them back, so no cycle. The ledger is not touched.

On the Railway lab at 982894c:

  • dupe_scan: ok, 684 bodies in 196 groups, none new and none grown.
  • t27c check: ok for all four t27f token_floor specs.
  • t27c test-report: pbr_sphere 13, token_floor_scenes 11, token_floor 34
    and token_floor_mux 14 tests pass, 0 vacuous.
  • Seals of pbr_sphere, token_floor_scenes and token_floor were re-saved
    through t27c seal --save. All four pass seal --verify
    (token_floor_mux needed no change).

🤖 Generated with Claude Code

… clamp01 instead of copying it (Refs #10451)

7552b89 (#10452) left three byte-identical `clamp01` bodies, in
specs/t27f/pbr_sphere.t27, token_floor.t27 and token_floor_scenes.t27. No
ledger holds that group, so the Duplicate Body Ratchet has been red on
master since 7552b89, and every open PR shows the red.

pbr_sphere's `clamp01` becomes `pub`. token_floor and token_floor_scenes
now say `use t27f::pbr_sphere::clamp01;` and drop their copies, the way
token_floor already uses pbr_sphere's `shade`. Neither module imported
anything that imports them back, so no cycle. The ledger is not touched.

On the Railway lab at 982894c:
- dupe_scan: ok, 684 bodies in 196 groups, none new and none grown.
- `t27c check`: ok for all four t27f token_floor specs.
- `t27c test-report`: pbr_sphere 13, token_floor_scenes 11, token_floor 34
  and token_floor_mux 14 tests pass, 0 vacuous.
- Seals of pbr_sphere, token_floor_scenes and token_floor were re-saved
  through `t27c seal --save`. All four pass `seal --verify`
  (token_floor_mux needed no change).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-18 13:21:43 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 50
PRs with All Checks Green 0
READY 0
FAILING 50
PENDING 0
NO CHECKS YET 0

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=fad12492937a != manifest seal=87e5cbd3ad94.
    The committed NMSE numbers were certified against an older compiler.rs.
    Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).

@gHashTag

Copy link
Copy Markdown
Owner Author

Superseded by #10471, which makes the same clamp01 dedupe (token_floor and token_floor_scenes use pbr_sphere's clamp01) and also adds the t27b ledger rows. Both PRs rewrite token_floor_scenes.t27 and the same three seals, so only one can land cleanly.

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