master red: Corpus Ratchet -- four type names gained a second definition when #10370 made specs parse #10389

The required check "Corpus Ratchet" (step tri types ratchet) fails on master at eb425e6: ledger 108 name(s), observed 111. Four type names gained a second definition and one ledger name is resolved.

Goal

Make tri types ratchet CLEAN again by removing the cause, not by blessing it. The four names are new conflicts because #10370 (b2fbb75, "verdict-blocked specs compile and seal") made specs parse that did not parse before, so their structs became visible to tri types dup for the first time:

• Context: specs/port/browseros/trios/agent-server/apps/server/src/api/utils/security.t27 vs specs/queen/lotus.t27
• MatchResult: specs/server/router.t27 vs specs/tri/search/pattern.t27
• UnsubscribeResult: specs/bus/schema.t27 vs specs/bus/pubsub.t27
• ProofTrace: specs/ar/coa_planning.t27, specs/ar/datalog_engine.t27 vs specs/ar/proof_trace.t27

HttpStatus now has exactly one definition (specs/server/http.t27), so its ledger line and its row in the classified table are stale.

Boundary

• the five specs named above, renamed on the side that seals: verdict-blocked specs compile and seal; 11 refused specs fixed, 30 blocked ones listed (Refs #8314) #10370 touched
• .trinity/seals/*.json of those specs, written by t27c only
• docs/reports/type_conflicts.json, docs/reports/type_conflicts_classified.json, docs/TYPE_CONFLICTS.md (HttpStatus removal only)

User Scenarios

• Given master after this change, when tri types ratchet runs, then it prints RATCHET: CLEAN with the ledger and the observation equal.
• Given master after this change, when tri types classified runs, then every conflicted name has a verdict and no verdict is stale.
• Given a renamed spec, when t27c test-report runs on it, then every test passes as before and its seal is current.

Requirements

• FR-001: Each of the four names MUST end with one definition per name; the renamed type keeps its fields and behaviour.
• FR-002: The ledger MUST NOT gain a name; only the resolved HttpStatus is removed (a legitimate bless).
• FR-003: Only .t27 files, seals and data/doc tables change; no hand-written foreign code.

Success Criteria

• tri types ratchet is CLEAN and tri types classified is OK.
• t27c test-report passes for the five renamed specs and t27c seal-audit names none of them.
• Corpus Ratchet is green on the pull request.