fix: M:N derivation classified inherited relationships against the visiting entity, not the declaring one - #373

Merged

dmealing merged 13 commits into

mainfrom

followup/m2m-selfjoin-declaring-entity

Sep 14, 2026

Commits on Sep 14, 2026

fix(metadata-ts): M:N derivation must use the DECLARING entity, not the visiting one

dmealing
and
claude
committed
923e252
fix(metadata-java): M:N derivation must use the DECLARING entity, not the visiting one

dmealing
and
claude
committed
94fb8a9
fix(metadata-ts): accept BOTH the declaring base and the navigating entity as the M:N subject

dmealing
and
claude
committed
1062191
fix(metadata-java): accept BOTH the declaring base and the navigating entity as the M:N subject

dmealing
and
claude
committed
8f7f55b
fix(metadata-python): M:N derivation must use the relationship's subject, not the visiting entity

dmealing
and
claude
committed
7c09e0b
fix(csharp): M:N derivation — and M2MNavigation.IsSelfJoin — must see the declaring entity

dmealing
and
claude
committed
75f2415
test(codegen-kotlin): pin that Kotlin reaches the fixed M:N derivation

dmealing
and
claude
committed
aa31ec4
test: pin the ADR-0041 bare-name divergence the subject widening enlarges

dmealing
and
claude
committed
a25dbef
docs: record the inherited-M:N junction-FK contract and the fix

dmealing
and
claude
committed
de477a5
fix: compare the M:N subject by resolved entity identity, matching the Java port

dmealing
and
claude
committed
c6f0cee
fix: match the hetero TARGET junction reference by identity too, and align IsSelfJoin

dmealing
and
claude
committed
f72b4c5
refactor(python): delegate the reference head-parse; correct four stale doc claims

dmealing
and
claude
committed
06daf4f
Merge remote-tracking branch 'origin/main' into followup/m2m-selfjoin-declaring-entity
dmealing
committed
eaff41d

Navigation Menu

Uh oh!

fix: M:N derivation classified inherited relationships against the visiting entity, not the declaring one - #373

fix: M:N derivation classified inherited relationships against the visiting entity, not the declaring one#373
dmealing merged 13 commits into
mainfrom
followup/m2m-selfjoin-declaring-entity

Commits on Sep 14, 2026

fix(metadata-ts): M:N derivation must use the DECLARING entity, not the visiting one

fix(metadata-java): M:N derivation must use the DECLARING entity, not the visiting one

fix(metadata-ts): accept BOTH the declaring base and the navigating entity as the M:N subject

fix(metadata-java): accept BOTH the declaring base and the navigating entity as the M:N subject

fix(metadata-python): M:N derivation must use the relationship's subject, not the visiting entity

fix(csharp): M:N derivation — and M2MNavigation.IsSelfJoin — must see the declaring entity

test(codegen-kotlin): pin that Kotlin reaches the fixed M:N derivation

test: pin the ADR-0041 bare-name divergence the subject widening enlarges

docs: record the inherited-M:N junction-FK contract and the fix

fix: compare the M:N subject by resolved entity identity, matching the Java port

fix: match the hetero TARGET junction reference by identity too, and align IsSelfJoin

refactor(python): delegate the reference head-parse; correct four stale doc claims

Merge remote-tracking branch 'origin/main' into followup/m2m-selfjoin-declaring-entity