Add PRD organizing all GitHub issues into milestones and phases#57
Conversation
Research confirmed swift-markdown supports programmatic construction (Heading/Paragraph/CodeBlock/etc. initializers + MarkupFormatter), so the earlier "parse-only" assertion was incorrect. eneko/MarkdownGenerator is 5 years stale (v1.1.0, Jan 2021) and has a single consumer in Tagscriber/KannaMarkdownGenerator.swift — swapping it out during the Kanna→SwiftSoup rewrite costs nothing extra and removes one dependency.
|
Caution Review failedThe pull request is closed. ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (3)
📝 WalkthroughWalkthroughThis change consolidates project documentation and updates development tooling configuration. The old migration plan document is removed and replaced with a comprehensive product requirements document that organizes work into phases, while VS Code launch configurations are updated to use target-based debugging instead of hardcoded executable paths. Changes
Estimated code review effort🎯 2 (Simple) | ⏱️ ~10 minutes Poem
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Co-Authored-By: Claude Sonnet 4.6 noreply@anthropic.com
Perform an AI-assisted review on
Summary by CodeRabbit
Documentation
Chores