-
markdown_renderer_baseline_failures.json
docs/plans/markdown_renderer/markdown_renderer_baseline_failures.json Plans Plans and history
-
markdown_renderer_debug_log.md
docs/plans/markdown_renderer/markdown_renderer_debug_log.md Plans Plans and history
-
markdown_renderer_dynamic_browser_evidence.json
docs/plans/markdown_renderer/markdown_renderer_dynamic_browser_evidence.json Plans Plans and history
-
markdown_renderer_release_evidence.json
docs/plans/markdown_renderer/markdown_renderer_release_evidence.json Plans Plans and history
-
markdown_renderer_static_browser_evidence.json
docs/plans/markdown_renderer/markdown_renderer_static_browser_evidence.json Plans Plans and history
-
markdown_renderer_step1_solution_assessment.md
Should we make another Step 1 for improving the Markdown renderer?
docs/plans/markdown_renderer/markdown_renderer_step1_solution_assessment.md Plans Plans and history
-
markdown_renderer_step2_feature_description.md
Existing documentation is reachable, but the renderer loses tables, list structure and section links.
docs/plans/markdown_renderer/markdown_renderer_step2_feature_description.md Plans Plans and history
-
markdown_renderer_step3_development_plan.md
Each stage targets at most one hour of authored work, excluding mechanical dependency files; split before implementation if larger.
docs/plans/markdown_renderer/markdown_renderer_step3_development_plan.md Plans Plans and history
-
markdown_renderer_step4_implementation_summary.md
All five approved stages delivered and verified in the local target environment.
docs/plans/markdown_renderer/markdown_renderer_step4_implementation_summary.md Plans Plans and history