Classify all 80 conflicted type names, and gate the classification

[gHashTag]

Refs #2774

tri types dup reports which names have two definitions. It cannot say what kind of conflict each is, and the two kinds want opposite repairs. All 80 were opened and judged:

Verdict	Count
DRIFT — one concept that grew a second definition	46
DISTINCT — two concepts that collided on a name	34

docs/TYPE_CONFLICTS.md is the summary; docs/reports/type_conflicts_classified.json holds the per-name reading that decided each verdict.

One row is fixable today with no cross-module decision. AdamWConfig has both definitions in ONE file (specs/ml/optimizer/adamw.t27 lines 28 and 483), six of seven fields identical, and the file's own comment says the second was appended.

The document is gated, in both directions

A written reading of a tree stops being true without anything failing. tri types classified re-takes it:

classified but no longer conflicting  -> STALE     (a repair landed)
conflicting but not classified        -> UNJUDGED  (nobody has read it)

Only UNJUDGED feels like a failure. Passing over STALE is how a document becomes decoration. Both are red. Wired into corpus-ratchet.yml.

Proven red both ways before landing, then restored:

1) drop a row  -> UNJUDGED  Color: conflicting, but nothing has read it
2) plant a row -> STALE     ZZZNotAType: classified, but no longer conflicting
3) restore     -> exit=0, OK

It earned itself on the first execution. HealthStatus — the eightieth name — appeared when #2802 taught the field reader that pub name: T is a field. The classification run predated that change and never saw it.

Recorded rather than hidden

Four verdicts (Agent, AgentStatus, Color, HealthStatus) are reported CONFLICTED by the tool only because it cannot parse the variants : , enum idiom on one side — it compares an empty field list against a full one. Those four were decided by reading the source; the tool's agreement is a coincidence, not corroboration. docs/TYPE_CONFLICTS.md says so in its own section.

ci-gates 205-207.

[github-actions]

📓 NotebookLM Notebook linked to this PR

• Notebook ID: b83263109fb055dc
• URL: https://notebooklm.google.com/notebook/b83263109fb055dc

This notebook contains session context, decisions, and artifacts for this work.

[github-actions]

PR Dashboard

Generated at: 2026-08-29 11:42:53 UTC

• Classify all 80 conflicted type names, and gate the classification #2806 Classify all 80 conflicted type names, and gate the classification | Created: 2026-08-29 | Updated: 2026-08-29 | 17 failing / 24 total
• tri orphaned: inputs named in code that are not in the tree #2805 tri orphaned: inputs named in code that are not in the tree | Created: 2026-08-29 | Updated: 2026-08-29 | 8 failing / 31 total
• Land the formal verification harness on master (it has never run) #2727 Land the formal verification harness on master (it has never run) | Created: 2026-08-27 | Updated: 2026-08-27 | 5 failing / 24 total
• chore(deps)(deps): bump thiserror from 2.0.18 to 2.0.20 #2693 chore(deps)(deps): bump thiserror from 2.0.18 to 2.0.20 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• chore(deps)(deps): bump hyper from 1.10.1 to 1.11.0 #2692 chore(deps)(deps): bump hyper from 1.10.1 to 1.11.0 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 33 total
• chore(deps)(deps): bump base64 from 0.22.1 to 0.23.1 #2691 chore(deps)(deps): bump base64 from 0.22.1 to 0.23.1 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• chore(deps)(deps): bump serde from 1.0.228 to 1.0.229 #2690 chore(deps)(deps): bump serde from 1.0.228 to 1.0.229 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• chore(deps)(deps): bump uuid from 1.23.2 to 1.25.0 #2689 chore(deps)(deps): bump uuid from 1.23.2 to 1.25.0 | Created: 2026-08-24 | Updated: 2026-08-28 | 3 failing / 34 total
• Unbreak FPGA CI and correct two unbacked hardware claims #2081 Unbreak FPGA CI and correct two unbacked hardware claims | Created: 2026-08-11 | Updated: 2026-08-20 | 5 failing / 27 total

Summary

Status	Count
Total Open PRs	9
PRs with Failing Checks	7
PRs with All Checks Green	2
READY	0
FAILING	7
PENDING	0

Seal Status

• ⚠️ STALE -- sha256(compiler.rs)=d25ac0cc159e != manifest seal=87e5cbd3ad94.
  The committed NMSE numbers were certified against an older compiler.rs.
  Run scripts/reseal-check.sh locally for the two-step reseal command (advisory; not a merge gate).