t27b ledger: cap 24 over 22 non-pass, and 5 pass specs without a row #8215

Refs #6063

Master's docs/reports/t27b_expectations.json at 3d2ea88 has two problems:

• It stores max_not_pass 24 over 22 non-passing rows. port(gen_lockfree_stack, tool-registry): the caller owns the storage, so neither reads a dead frame (Closes #7736) #8047 moved two rows blocked -> pass, and its cap line had to equal master's 24 to merge without a conflict.
• Five specs that landed today have no row, and each is t27b pass in its own PR's t27b-native-ratchet run:
  • specs/compiler/theory/warmup.t27 and warmup_t27b.t27 (theory(sieve): C6 warmup measured, C7 speed and quality published (Closes #7596) #8182, run 7a337da);
  • specs/port/trinity/fpga/openxc7-synth/DSP48E1_mock.t27 (Port gHashTag/trinity:fpga/openxc7-synth/DSP48E1_mock.v (Verilog, 1 module) to specs/port/trinity/fpga/openxc7-synth/DSP #7970, run 52f3e15);
  • specs/port/trinity/fpga/rtl/fpga_test_reporter.t27 (Port gHashTag/trinity:fpga/rtl/fpga_test_reporter.v (Verilog, 1 module) to specs/port/trinity/fpga/rtl/fpga_test_reporte #7926, run 06770a6);
  • specs/tri/t27b/verdict_key.t27 (t27b: key reference verdicts by the generated code, not the t27c binary (Closes #8176) #8208, run 0fda91b).

#8173 (Closes #8170) covers the other unlisted rows. It cannot carry these five plus the cap: its cap line and two of the rows would conflict with master.

Boundary

• Edits only docs/reports/t27b_expectations.json (5 rows added, cap line) and adds one docs/now/ entry.
• Data only; no code.
• Lands after t27b ledger: bless lab run a97cb9e55, 14 unlisted pass rows, cap 26 -> 25 (Closes #8170) #8173. The other order would make t27b ledger: bless lab run a97cb9e55, 14 unlisted pass rows, cap 26 -> 25 (Closes #8170) #8173's cap line conflict.

User Scenarios

• A t27b lab run on master after this lands shows no UNLISTED for the five specs.
• The cap test sees cap == reality.

Requirements

• max_not_pass equals the count of rows that are neither pass nor pass_vacuous.
• Rows sorted, unique, every path on the tree.

Success Criteria

• On master after t27b ledger: bless lab run a97cb9e55, 14 unlisted pass rows, cap 26 -> 25 (Closes #8170) #8173 and this PR: 1229 rows, unique, sorted, none missing, not_pass 22 = max_not_pass 22.
• tri t27b ratchet against the first lab run at or after the merge shows no UNLISTED for these five paths and no OVER CAP.

Requirements

FR-001: The max_not_pass value in docs/reports/t27b_expectations.json MUST equal the count of rows whose status is neither pass nor pass_vacuous.

FR-002: Five new rows MUST be added to docs/reports/t27b_expectations.json for the specs: specs/compiler/theory/warmup.t27, specs/compiler/theory/warmup_t27b.t27, specs/port/trinity/fpga/openxc7-synth/DSP48E1_mock.t27, specs/port/trinity/fpga/rtl/fpga_test_reporter.t27, and specs/tri/t27b/verdict_key.t27, each with status pass.

FR-003: All rows in docs/reports/t27b_expectations.json MUST be sorted lexicographically by path and unique.

FR-004: Every spec path present in the repository tree that is tracked by t27b MUST have a row in docs/reports/t27b_expectations.json.

FR-005: One new entry MUST be added under docs/now/ documenting this change.