Skip to content

gen: regenerate igla/own_model_board.json so spec-guards is green on master (Closes #10367) - #10369

Closed
gHashTag wants to merge 1 commit into
masterfrom
claude/own-model-board-json-regen
Closed

gen: regenerate igla/own_model_board.json so spec-guards is green on master (Closes #10367)#10369
gHashTag wants to merge 1 commit into
masterfrom
claude/own-model-board-json-regen

Conversation

@gHashTag

@gHashTag gHashTag commented Oct 18, 2026

Copy link
Copy Markdown
Owner

Closes #10367.

gen/json/igla/own_model_board.json is regenerated from specs/igla/own_model_board.t27. #10275 changed the spec without it, so spec-guards has been red on master and on every PR based on it (including #10362).

What changes

  • One generated file, one line. Nothing hand-edited.
  • Board event message: "1 published, 17 verified, 8 drafts, 1 gaps; 61%" becomes "3 published, 22 verified, 1 drafts, 1 gaps; 61%".
  • Seven cells change status: indices 6 and 7 (cells 7 and 8, live) go to published; indices 15, 16, 17, 24 and 26 (cells 16, 17, 18, 25, 27) go to verified. Cell 26 (DDR3 head read) stays a draft.

Are the claims intended?

Yes. This is the tally #10275 states ("3 published, 22 verified, 1 draft, 1 gap; 61%"). #10275 carried no-auto-merge, was approved by the reviewer bee (review 5561941493, the id REVIEW_ID names) and merged on the bee's approval. The Railway cron (#10324) reposts the board from master's JSON, so after this lands the board publishes that tally, which is what #10275 set out to do.

Verified

  • The file is the t27c JSON generator output from the Railway lab at 483eb32. sha256 f53ac5c74a16c5b68cf6a5d580bc17cdfd16903b162f5f28c1d5a0663ccf65ac, equal to the file CI generates.
  • specs/igla/ and master after 483eb32 do not touch this spec, so the output is still current at the head of master (88bfb2b).

🤖 Generated with Claude Code

@gHashTag @claude
gen: regenerate igla/own_model_board.json from its spec (Closes #10367)
5e6ba44 
#10275 changed specs/igla/own_model_board.t27 without regenerating
gen/json/igla/own_model_board.json, so spec-guards is red on master and on
every PR based on it. The file is the t27c JSON generator output from the
Railway lab at 483eb32; its sha256 (f53ac5c7...) equals what CI generates.
The board event moves from 1 published / 17 verified / 8 drafts to
3 published / 22 verified / 1 draft, the tally #10275 states and the reviewer
bee approved (review 5561941493).

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

github-actions Bot commented Oct 18, 2026

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-18 09:45:52 UTC

Summary

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

These columns do not partition: 0 + 48 + 0 + 0 = 48, and there are 50 open PRs. A PR is being counted twice or not at all.

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
gHashTag enabled auto-merge (squash) October 18, 2026 09:46
@gHashTag

gHashTag commented Oct 18, 2026

Copy link
Copy Markdown
Owner Author

Duplicate of #10368: its file is byte-identical (sha256 f53ac5c74a16c5b68cf6a5d580bc17cdfd16903b162f5f28c1d5a0663ccf65ac). Closing this one so there is a single PR. #10368 links #10366, which the issue-shape gate had closed (missing numbered Requirements); I edited #10366 so it passes.

@gHashTag gHashTag closed this Oct 18, 2026
auto-merge was automatically disabled October 18, 2026 09:46

Pull request was closed

@gHashTag gHashTag mentioned this pull request Oct 18, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

None yet

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

gen: regenerate igla/own_model_board.json so spec-guards is green on master

1 participant

@gHashTag