Markdown parser fails with CRLF line endings on Windows

[Pleko-script]

Bug Description

The markdown parsers in src/lib/product-loader.ts fail to parse files with CRLF line endings (Windows-style), causing product overview and roadmap content not to display on the homepage.

Environment

• OS: Windows (MINGW64_NT)
• Files affected: product/product-overview.md, product/product-roadmap.md

Steps to Reproduce

1. Create product/product-overview.md and product/product-roadmap.md on Windows
2. Run /product-vision and /product-roadmap commands
3. Start dev server with npm run dev
4. Visit homepage - sees "No roadmap defined yet" despite files existing

Root Cause

The regex patterns in parseProductOverview() and parseProductRoadmap() use \n for line matching, but Windows files have \r\n (CRLF) line endings. This causes the regex to fail to match section headers and content.

Fix

Normalize line endings before parsing:

// In parseProductOverview() and parseProductRoadmap()
export function parseProductRoadmap(md: string): ProductRoadmap | null {
  if (!md || !md.trim()) return null

  try {
    // Normalize line endings (CRLF to LF) for consistent parsing
    const normalizedMd = md.replace(/\r\n/g, '\n')
    const sections: Section[] = []

    // Match sections with pattern ### N. Title
    const sectionMatches = [...normalizedMd.matchAll(/### (\d+)\.\s*(.+)\n+([\s\S]*?)(?=\n### |\n## |\n#[^#]|$)/g)]
    // ... rest of function

Impact

Windows users cannot see their product overview or roadmap until manually converting line endings or applying the fix above.

Suggested Solution

Add line ending normalization at the start of both parseProductOverview() and parseProductRoadmap() functions in src/lib/product-loader.ts.