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

spec-guards is red on master because PR #10275 changed specs/igla/own_model_board.t27 (the board message and the status/percent arrays) but never regenerated gen/json/igla/own_model_board.json. Every PR based on master inherits the red check (seen at 258a5ee and 483eb32, and on #10362).

The regenerated file changes the board event from "1 published, 17 verified, 8 drafts, 1 gaps; 61%" to "3 published, 22 verified, 1 drafts, 1 gaps; 61%", which is exactly the tally #10275 states: its seven DELIVER cells (7, 8, 16, 17, 18, 25, 27) are reviewed, cells 7 and 8 are live so they become published, and cell 26 stays a draft. #10275 was approved by the reviewer bee (review 5561941493, which REVIEW_ID names) and merged with auto-merge off, so the claim is intended. A Railway cron (#10324) reposts the board from master's JSON, so landing this file publishes that tally.

Boundary

gen/json/igla/own_model_board.json

User Scenarios

• Given master with this file regenerated, when spec-guards runs, then the generated-file diff for gen/json/igla/own_model_board.json is empty and the check is green.
• Given the board cron (igla: repost the own_model board event from master on a Railway cron (Closes #10321) #10324) reposting from master, when it next fetches the JSON, then the posted message reads "3 published, 22 verified, 1 drafts, 1 gaps; 61%".

Requirements

• FR-001: The file MUST be the unedited output of the t27c JSON generator on specs/igla/own_model_board.t27, produced on the Railway lab.
• FR-002: Its sha256 MUST equal the one CI generates: f53ac5c74a16c5b68cf6a5d580bc17cdfd16903b162f5f28c1d5a0663ccf65ac.
• FR-003: The change MUST touch no file other than the generated JSON.

Success Criteria

• shasum -a 256 gen/json/igla/own_model_board.json prints f53ac5c74a16c5b68cf6a5d580bc17cdfd16903b162f5f28c1d5a0663ccf65ac.
• spec-guards passes on the pull request and on master after the merge.

Refs #10269, #10275, #10324.