Merged result in parse_item not passed back to parse_object_fields

[koxudaxi]

Related: #2990, #2993

When $ref is combined with schema-affecting keywords (e.g., const) and the merge correctly occurs in parse_item, the merged result is not passed back to parse_object_fields. This causes it to generate the pre-merged type instead of the merged type.

This was noted by @juliusliu02 in #2993 (comment) as a separate aspect of the original issue #2990.

#2993 addresses part 1 (preventing unnecessary merges for non-schema-affecting extras), but this issue tracks part 2 (ensuring merged results propagate correctly when merging is intended).

[coderabbitai]

🔗 Related PRs

#2838 - Fix allOf multi-ref to preserve inheritance with property overrides [merged]
#2853 - Fix reuse-model generating type aliases instead of class inheritance [merged]
#2861 - fix: handle type definitions from grand(grand...) parent schemas [merged]
#2962 - Fix allOf array property merging to preserve child $ref [merged]
#2985 - Address review feedback for recursive/dynamic ref support [merged]

---

📝 Issue Planner

_{Check the box below or use the @coderabbitai plan command to generate an implementation plan and prompts that you can use with your favorite coding assistant.}

• Create Plan

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!

[github-actions]

🎉 Released in 0.54.0

The fix/feature from PR #2997 has been included in this release. See the release notes for details.

Thank you for your contribution!