t27b: rows for the 6 specs that landed after #8289 without one #8322

Part of the t27b overnight improvement loop. queen/keyed, queen/simulation, queen/telemetry, automation/tri-wallet-chains, verified/bitstream_reuse, tri/t27b/source_text have no row in docs/reports/t27b_expectations.json, so t27b-native-ratchet is red again (UNLISTED). Add rows measured by a lab or native run, as #8289 did.

User Scenarios

• Given the t27b_expectations.json file lacks rows for six specs that landed after t27b ledger: rows for 9 specs merged without one (Closes #8287) #8289, when the measurement script is run for those specs, then the JSON is updated with their measured rows and the t27b-native-ratchet check passes.

Requirements

FR-001: The docs/reports/t27b_expectations.json MUST contain a row for each of the six specs: queen/keyed, queen/simulation, queen/telemetry, automation/tri-wallet-chains, verified/bitstream_reuse, tri/t27b/source_text.
FR-002: The rows MUST be measured by a lab or native run using scripts/tri_loop/t27b.py and MUST match the format of existing rows.
FR-003: After adding rows, the t27b-native-ratchet check MUST pass (exit 0).

Success Criteria

• Running python scripts/tri_loop/t27b.py --validate docs/reports/t27b_expectations.json exits with exit 0.
• The file docs/reports/t27b_expectations.json contains exactly 6 new entries for the specified specs.
• The command t27b-native-ratchet exits with exit 0.

Boundary

• docs/reports/t27b_expectations.json
• scripts/tri_loop/t27b.py