ID

R411

Status

Backlog

Bucket

architecture

Priority

2

Theme

diagnostics

Created

2026-07-01

Updated

2026-08-06

Wire-coercion cast guard for @condition and @externalField (R261 Slice 2)

Problem

R261 Slice 1 landed the wire-coercion cast guard for the three @service sites (A: input-bean scalar field, B: @service scalar arg, E: input-bean enum field) plus the shared classify-time predicate (WireCoercionResolver), the WireCoercionError sealed family, and the enum-constant parity home (EnumMappingResolver.checkEnumConstants). This item is R261’s deferred Slice 2: the same defect on the two non-@service arg-classification sites the Slice 1 spec named but left out:

  • C ; @condition nested input field. ConditionResolver.rewrapForNested builds a 2-arg NestedInputField whose leaf is Direct; ArgCallEmitter then emits (Long) _m.get("filmId") for a nested ID/enum. The @condition argument path in ServiceCatalog.reflectTableMethod (the slot-types-aware overload) also still uses ServiceCatalog.legacyArgExtraction (no wire-coercion check) ; Slice 1 deliberately scoped the reject to the @service caller only.

  • D ; @externalField / accessor arg. FetcherEmitter emits a (ReflectedParamType) env.getArgument(...) cast to the reflected backing-method parameter type.

Why deferred from R261

Slice 1 rode R256’s landed typed-rejection channel (Done). Sites C/D consume the same Slice 1 predicate unchanged. At carve-out time their channel was expected to be the dimensional-model umbrella’s ConditionCall / ExternalFieldCall carrier siblings; that umbrella has since been retired (see roadmap/audits/2026-08-06-r222-lineage.md) and those carriers will never be built, because the fact-base architecture captures @condition / @externalField content as decoded relations instead. The dependency is therefore dropped: sites C/D ride the same typed-rejection channel Slice 1 used, at whatever classification site holds them when this item is picked up. Per the R261 Sequencing section’s reviewer recommendation, C/D were carved here so R261 could close on the @service slice alone.

Constraint

This item must consume the Slice 1 predicate (WireCoercionResolver.checkScalar) and the WireCoercionError.Assignability / EnumConstantDivergence arms with no re-derivation ; the "one predicate, one home" rule. It only threads the predicate through R222’s channel for the legacyArgExtraction path (retire that shim) and the @externalField accessor-arg site, and adds pipeline-tier tests mirroring WireCoercionCastGuardPipelineTest for the two new sites.