master Corpus Ratchet: 5 unexpected failures from 2026-10-10 merges (ingest.t27 apostrophe, a/b_c, optimizer, orchestrator_bench) #8562

Master's Corpus Ratchet lists 5 UNEXPECTED FAILURES, all introduced on 2026-10-10 by other merges. The types-classification failure in the same job is mine and is fixed by #8561.

Acceptance criteria

• t27c suite --corpus-only --ratchet on master reports UNEXPECTED FAILURES: 0.
• specs/memory/graph/ingest.t27 parses with 0 recovery events, and no assert in it is wrong on purpose.
• Each fix lands with its own owner's spec change, not a ledger bless that hides it.

Boundary

specs/a/b_c.t27
specs/a_b/c.t27
specs/compiler/optimizer.t27
specs/memory/graph/ingest.t27
specs/port/trinity/src/tri/orchestrator_bench.t27

User Scenarios

• Given the Corpus Ratchet on master reports 5 unexpected failures from 2026-10-10 merges, when t27c suite --corpus-only --ratchet runs, then it reports UNEXPECTED FAILURES: 0.
• Given specs/memory/graph/ingest.t27 contains a ; comment with an apostrophe on line 414 that the parser treats as an unterminated char literal, when the spec is parsed, then it completes with 0 recovery events and no deliberately failing assert remains.
• Given each of the five failing specs has a distinct root cause introduced by a different merge, when the fixes land, then each fix is applied by its owning spec change (not a ledger bless).

Requirements

• FR-001: specs/a/b_c.t27 and specs/a_b/c.t27 MUST parse without discarding characters in the new test blocks introduced by specs: one distinct real test for a/b_c and a_b_c, replacing the #8488 twins (Closes #8508) #8496.
• FR-002: specs/compiler/optimizer.t27 MUST parse without discarding characters and MUST compile successfully (addressing Census the optimizer: 4 of 7 passes have no precondition, and dead_store_elim deletes calls #8502 and regression: compiler/optimizer.t27 and port/tools/gft_deep_demo.t27 stopped compiling on 2026-10-10 #8552).
• FR-003: specs/memory/graph/ingest.t27 MUST parse with 0 recovery events; the apostrophe in the line-414 comment MUST not open a char literal, and any deliberately wrong assert MUST be corrected.
• FR-004: specs/port/trinity/src/tri/orchestrator_bench.t27 MUST pass the gen-verilog phase.
• FR-005: Each fix MUST be committed as its own spec change by the responsible owner; no fix MAY be hidden by a ledger bless.

Success Criteria

• t27c suite --corpus-only --ratchet exits with exit 0 and prints UNEXPECTED FAILURES: 0.
• t27c parse specs/memory/graph/ingest.t27 exits with exit 0 and reports recovery events: 0.
• specs/memory/graph/ingest.t27 contains 0 asserts that are intentionally incorrect (verified by inspection).
• Each of the five boundary files is modified in a separate commit by its owning author (5 commits total, verified by git log --oneline).