Skip to content

type conflicts: 21 new conflicted names read and classified (16 DISTINCT, 5 DRIFT) (Closes #11663) - #11665

Merged
gHashTag merged 1 commit into
masterfrom
ledger/type-conflicts-classify-21-Gaia-MacBook-Air
Oct 22, 2026
Merged

gHashTag merged 1 commit into
masterfrom
ledger/type-conflicts-classify-21-Gaia-MacBook-Air

Conversation

@gHashTag

Copy link
Copy Markdown
Collaborator

Closes #11663. The bless in #11664 absorbed 21 new conflicted names into docs/reports/type_conflicts.json, but the CI check 'Every conflicted type name has a written verdict' then reported 21 UNJUDGED names: classification lags. This reads each new conflict's two definitions (both sites opened, field lists compared) and writes the verdicts:

  • 5 DRIFT: uart_bridge v1/v2 same-design drift (RxState, TxState, LedState -- same field names, widths flattened in v2), the two bogatyr lineage records (BogatyrResult: verdict+checks vs verdict+errors+metrics, both citing the original's common.BogatyrResult), and the gft JTAG scan-chain payload family (JtagData: 3 literally shared field names).
  • 16 DISTINCT: unrelated subsystems that met on a noun (ternary AddResult vs GF16 AddResult, http-ring vs server ChatResponse, binary-argv Cli x2, STARTUPE2 ClockConfig wire vs frequency plan, bscan bridge CoreRegs vs flash master, EchoState machine vs pending bit, fuzz-case Module vs synth Module entry, two PortParse outcomes, Segments interval vs text chunk, per-program TestStatus, TrainConfig/TrainResult of different trainers, generic Tree(T) vs a drawing summary, ValidationContext switches vs parser supplies, ValidationError bare vs parameter tuple).

verdicts in type_conflicts_classified.json: DRIFT 65, DISTINCT 63 (=128). tri types classified cross-check passes: no UNJUDGED, no STALE.

…NCT, 5 DRIFT) (Closes #11663)

Every conflicted name in the tree now has a written verdict; tri types classified reports 128 judged, no stale rows, no unjudged. DRIFT rows are the uart_bridge v1/v2 family (LedState, RxState, TxState), the two bogatyr lineages (BogatyrResult), and the gft JTAG payload family (JtagData).
@gHashTag
gHashTag enabled auto-merge (squash) October 22, 2026 17:01
This was referenced Oct 22, 2026
@github-actions

Copy link
Copy Markdown
Contributor

PR Dashboard

Generated at: 2026-10-22 19:16:50 UTC

Summary

Status Count
Total Open PRs 50
PRs with Failing Checks 36
PRs with All Checks Green 14
READY 0
FAILING 36
PENDING 0
NO CHECKS YET 5

These columns do not partition: 0 + 36 + 0 + 5 = 41, and there are 50 open PRs. A PR is being counted twice or not at all.

Seal Status

  • ⚠️ STALE -- sha256(compiler.rs)=5aec047d42ec != 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).

@gHashTag
gHashTag merged commit c593ff5 into master Oct 22, 2026
21 of 23 checks passed
@gHashTag
gHashTag deleted the ledger/type-conflicts-classify-21-Gaia-MacBook-Air branch October 26, 2026 03:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

master red: tri types ratchet shows 21 NEW conflicted type names since #10390; every lane land fails at the types gate

2 participants