Lane A Root-A emit-seam grounding (the E0107-unmasked dominant pole): faithful-list/FreeMonoid CONSUMPTION through host Vec receivers — emitted count/first/skip/iteration render as bare Vec methods on Rc-of-Vec and fail method-resolution (16 errors in std_realization_schedule.rs: 13 E0599 + 3 E0308,

[gunbai-bot]

Lane A Root-A emit-seam grounding

faithful-list/FreeMonoid CONSUMPTION through host Vec receivers. Emitted count/first/skip/iteration rendered as bare host-Vec methods on Rc<Vec<...>> and failed method-resolution — the 13 E0599 + 3 E0308 in std_realization_schedule.rs.

Root (in INFER, not the emitter — §6 root-cause-to-the-language-layer)

A transparent type-alias receiver (type Schedule = List<List<Runnable>>) is resolved so its structural .name carries the container carrier (List) while its ident_span still points at the source spelling (Schedule). Pervasive type machinery reads the kind via authored_name_at (which returns the source spelling, not .name), so algebra-method dispatch, element typing, and ReceiverSelf result reconstruction all miss the kernel-algebra profile (keyed by List/Set/Map) and fall through to a bare host-Vec method.

Fix

• reground_alias_carrier_identity (04_types.dag) re-grounds ident_span onto the structural .name so authored_name_at agrees with .name (pure ident-normalization, no peel; mirrors structural_carrier_template_name).
• resolve_method_receiver_type (04_lookup.dag) composes the one existing peel authority resolve_scrutinee_type_node (the match-scrutinee resolver, seen-set bounded) with re-grounding, double-gated so structs/services/already-grounded/container-spelled receivers short-circuit — it returns the peeled type only when peeling reveals a declared-container-alias carrier the spelling hid.
• Call site: 04_infer.dag ExprMethodCall receiver. Authority in src/v1/04_{types,lookup,infer}.dag; seed mirrors in v1_compiler_infer_{types,lookup}.rs + v1_compiler_infer.rs.

Verified by execution

• Baseline (origin/main) emits 16 bare .count()/.skip()/bare-.first() calls on Schedule receivers → 0 with this change (all faithful host-Vec: .len() as i64, .first().cloned(), .iter().cloned().skip(n).collect()).
• Blast radius A/B: byte-diff of the full base-vs-fix --emit-fresh output = exactly one file differs (std_realization_schedule.rs). Zero corpus-wide dispatch regression.
• Termination oracle: full-corpus regen_stage0 --emit-fresh TERMINATES (197s local; 503s independent cold confirm), 108 modules. EMIT_EXIT=1 is the pre-existing std_serialization.rs self-compile mismatch (identical on baseline), not this change.
• cargo fmt --check + clippy -p v1-compiler clean; both realization_schedule witnesses pass.

The remaining errors in that file (Measure<Time> E0573, inner List E0107) are separate upstream poles (other lanes), byte-identical in the baseline.

Deeper root (tracked, not gold-plated here)

alias-carries-name-not-carrier is the same class the measure-tower and brand-peel hit. The general fix is canonical-identity-on-the-resolved-node (the wall-after-grounding being tracked); this PR grounds it surgically at the method-receiver seam only.

🤖 Generated with Claude Code