#523 render repeated and value-identical schemas in markdown output
Fixes #523
MarkdownRender kept a global handledSchemas set (from the 2022 stack-overflow fix) keyed by Schema.equals/hashCode, which are value-based: any second reference to the same component — and any value-identical subtree — was treated as already rendered and silently dropped from the report, so enum changes and nested properties vanished from the .md output.
The set is replaced with an identity-based set of schemas on the current recursion path (added on entry, removed on exit): true recursive definitions still terminate, while repeated references now render in full under every occurrence. Both issue samples now render complete output; 4 new fixture-based regressions (all fail on master). Full reactor mvn test green (272 core tests).
Summary by cubic
Fixes #523: repeated and value-identical schemas were silently dropped from markdown output. MarkdownRender kept a global set of handled schemas keyed by Schema.equals/hashCode, which are value-based, so any second reference to the same component — or any value-identical subtree — was treated as already rendered and its enum changes and nested properties vanished from the report.
Replaced the global set with an identity-based set of schemas on the current recursion path (added on entry, removed on exit), so true recursive definitions still terminate while repeated references now render in full under every occurrence.
- Adds 4 fixture-based regression tests that all fail on
master; full reactor test suite passes (272 core tests).