fix(cli): support CRLF and UTF-8 BOM in markdown frontmatter

.dockerignore

@@ -0,0 +1,10 @@
+# Dependencies (npm ci installs fresh inside the container)
+node_modules
+**/node_modules
+
+# Build artifacts (rebuilt from scratch inside the container)
+dist
+**/dist
+
+# Version control
+.git

.github/workflows/release-sdk.yml

@@ -348,15 +348,32 @@ jobs:
             CLI_SOURCE_DESC="CLI built from source (same branch/ref as SDK)"
           fi
 
-          # Create release notes with CLI version info
-          NOTES="## Bundled CLI Version\n\nThis SDK release bundles CLI version: \`${CLI_VERSION}\`\n\nSource: ${CLI_SOURCE_DESC}\n\n---\n\n"
-
+          # Create release notes file
+          NOTES_FILE=$(mktemp)
+          {
+            echo "## Bundled CLI Version"
+            echo ""
+            echo "This SDK release bundles CLI version: ${CLI_VERSION}"
+            echo ""
+            echo "Source: ${CLI_SOURCE_DESC}"
+            echo ""
+            echo "---"
+            echo ""
+          } > "${NOTES_FILE}"
+
+          # Get previous release notes if available
+          PREVIOUS_NOTES=$(gh release view "sdk-typescript-${PREVIOUS_RELEASE_TAG}" --json body -q '.body' 2>/dev/null || echo 'See commit history for changes.')
+          printf '%s\n' "${PREVIOUS_NOTES}" >> "${NOTES_FILE}"
+
+          # Create GitHub release
           gh release create "sdk-typescript-${RELEASE_TAG}" \
             --target "${TARGET}" \
             --title "SDK TypeScript Release ${RELEASE_TAG}" \
-            --notes-start-tag "sdk-typescript-${PREVIOUS_RELEASE_TAG}" \
-            --notes "${NOTES}$(gh release view "sdk-typescript-${PREVIOUS_RELEASE_TAG}" --json body -q '.body' 2>/dev/null || echo 'See commit history for changes.')" \
-            "${PRERELEASE_FLAG}"
+            --notes-file "${NOTES_FILE}" \
+            ${PRERELEASE_FLAG}
+
+          # Cleanup
+          rm -f "${NOTES_FILE}"
 
       - name: 'Create PR to merge release branch into main'
         if: |-

.github/workflows/release.yml

@@ -206,13 +206,22 @@ jobs:
           RELEASE_BRANCH: '${{ steps.release_branch.outputs.BRANCH_NAME }}'
           RELEASE_TAG: '${{ steps.version.outputs.RELEASE_TAG }}'
           PREVIOUS_RELEASE_TAG: '${{ steps.version.outputs.PREVIOUS_RELEASE_TAG }}'
+          IS_NIGHTLY: '${{ steps.vars.outputs.is_nightly }}'
+          IS_PREVIEW: '${{ steps.vars.outputs.is_preview }}'
         run: |-
+          # Set prerelease flag for nightly and preview releases
+          PRERELEASE_FLAG=""
+          if [[ "${IS_NIGHTLY}" == "true" || "${IS_PREVIEW}" == "true" ]]; then
+            PRERELEASE_FLAG="--prerelease"
+          fi
+
           gh release create "${RELEASE_TAG}" \
             dist/cli.js \
             --target "$RELEASE_BRANCH" \
             --title "Release ${RELEASE_TAG}" \
             --notes-start-tag "$PREVIOUS_RELEASE_TAG" \
-            --generate-notes
+            --generate-notes \
+            ${PRERELEASE_FLAG}
 
       - name: 'Create Issue on Failure'
         if: |-

.gitignore

@@ -47,11 +47,15 @@ packages/*/coverage/
 # Generated files
 packages/cli/src/generated/
 packages/core/src/generated/
+packages/web-templates/src/generated/
 .integration-tests/
 packages/vscode-ide-companion/*.vsix
 
 # Qwen Code Configs
+
 .qwen/
+!.qwen/commands/
+!.qwen/skills/
 logs/
 # GHA credentials
 gha-creds-*.json
@@ -70,6 +74,8 @@ __pycache__/
 integration-tests/concurrent-runner/output/
 integration-tests/concurrent-runner/task-*
 
+integration-tests/terminal-capture/scenarios/screenshots/
+
 # storybook
 *storybook.log
 storybook-static

.prettierignore

@@ -18,3 +18,4 @@ eslint.config.js
 gha-creds-*.json
 junit.xml
 Thumbs.db
+packages/cli/src/services/insight/templates/insightTemplate.ts

.qwen/skills/pr-review/SKILL.md

@@ -0,0 +1,104 @@
+---
+name: pr-review
+description: Reviews pull requests with code analysis and terminal smoke testing. Applies when examining code changes, running CLI tests, or when 'PR review', 'code review', 'terminal screenshot', 'visual test' is mentioned.
+---
+
+# PR Review — Code Review + Terminal Smoke Testing
+
+## Workflow
+
+### 1. Fetch PR Information
+
+```bash
+# List open PRs
+gh pr list
+
+# View PR details
+gh pr view <number>
+
+# Get diff
+gh pr diff <number>
+```
+
+### 2. Code Review
+
+Analyze changes across the following dimensions:
+
+- **Correctness** — Is the logic correct? Are edge cases handled?
+- **Code Style** — Does it follow existing code style and conventions?
+- **Performance** — Are there any performance concerns?
+- **Test Coverage** — Are there corresponding tests for the changes?
+- **Security** — Does it introduce any security risks?
+
+Output format:
+
+- 🔴 **Critical** — Must fix
+- 🟡 **Suggestion** — Suggested improvement
+- 🟢 **Nice to have** — Optional optimization
+
+### 3. Terminal Smoke Testing (Run for Every PR)
+
+**Run terminal-capture for every PR review**, not just UI changes. Reasons:
+
+- **Smoke Test** — Verify the CLI starts correctly and responds to user input, ensuring the PR didn't break anything
+- **Visual Verification** — If there are UI changes, screenshots provide the most intuitive review evidence
+- **Documentation** — Attach screenshots to the PR comments so reviewers can see the results without building locally
+
+```bash
+# Checkout branch & build
+gh pr checkout <number>
+npm run build
+```
+
+#### Scenario Selection Strategy
+
+Choose appropriate scenarios based on the PR's scope of changes:
+
+| PR Type                               | Recommended Scenarios                                        | Description                       |
+| ------------------------------------- | ------------------------------------------------------------ | --------------------------------- |
+| **Any PR** (default)                  | smoke test: send `hi`, verify startup & response             | Minimal-cost smoke validation     |
+| Slash command changes                 | Corresponding command scenarios (`/about`, `/context`, etc.) | Verify command output correctness |
+| Ink component / layout changes        | Multiple scenarios + full-flow long screenshot               | Verify visual effects             |
+| Large refactors / dependency upgrades | Run `scenarios/all.ts` fully                                 | Full regression                   |
+
+#### Running Screenshots
+
+```bash
+# Write scenario config to integration-tests/terminal-capture/scenarios/
+# See terminal-capture skill for FlowStep API reference
+
+# Single scenario
+npx tsx integration-tests/terminal-capture/run.ts integration-tests/terminal-capture/scenarios/<scenario>.ts
+
+
+# Check output in screenshots/ directory
+```
+
+#### Minimal Smoke Test Example
+
+No need to write a new scenario file — just use the existing `about.ts`. It sends "hi" then runs `/about`, covering startup + input + command response:
+
+```bash
+npx tsx integration-tests/terminal-capture/run.ts integration-tests/terminal-capture/scenarios/about.ts
+```
+
+### 4. Upload Screenshots to PR
+
+Use Playwright MCP browser to upload screenshots to the PR comments (images hosted at `github.com/user-attachments/assets/`, zero side effects):
+
+1. Open the PR page with Playwright: `https://github.com/<repo>/pull/<number>`
+2. Click the comment text box and enter a comment title (e.g., `## 📷 Terminal Smoke Test Screenshots`)
+3. Click the "Paste, drop, or click to add files" button to trigger the file picker
+4. Upload screenshot PNG files via `browser_file_upload` (can upload multiple one by one)
+5. Wait for GitHub to process (about 2-3 seconds) — image links auto-insert into the comment box
+6. Click the "Comment" button to submit
+
+> **Prerequisite**: Playwright MCP needs `--user-data-dir` configured to persist GitHub login session. First time use requires manually logging into GitHub in the Playwright browser.
+
+### 5. Submit Review
+
+Submit code review comments via `gh pr review`:
+
+```bash
+gh pr review <number> --comment --body "review content"
+```