docs: rebuild skill flow diagram with the drawio skill

[phj6688]

Overwrites docs/linear-issue-craft-flow.drawio with a render-verified draw.io flowchart produced through the drawio skill (author topology, ELK auto-layout, structural validation, render, then look at the pixels).

What changed

• Light theme, drawio-native palette with a legend (Start/File, Decision, Archetype, Draft/Gate, Headless path, Stop). The previous version was a dark Amber poster; the drawio skill is light-background only by design.
• Focused on the core flow: classify the archetype (q1..q4 decisions to epic / story / hardening / task, or decompose) -> "Archetype chosen" -> Draft -> Gate 1 -> interactive (Gate 2, Gate 3, show + approve) or headless (save-hook) -> File. The downstream-pipeline and golden-rules panels from the old poster are dropped to keep the diagram inside the skill's single-page quality gates.
• Aggregator node added so the four archetypes converge cleanly instead of edges spearing through sibling boxes.

Verification

• validate.py --stage post-layout: no blocking gates (warnings only: aspect and two edge-clips, both reviewed).
• Rendered via the pinned headless drawio image and inspected: all node and edge labels legible; legend swatches match fills; decision logic matches SKILL.md.
• Residuals (documented): tall aspect (inherent to a ~13-step flow) and two convergence edges that clip the Story box's left edge without touching its label.

README and CHANGELOG updated to describe the new diagram. Docs-only; CI (skill/manifest validation, ruff, tests) is unaffected.

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 42 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: cb35f927-84b0-4fd3-9a70-5db41131517c

📥 Commits

Reviewing files that changed from the base of the PR and between 544b596 and 35fd26f.

📒 Files selected for processing (3)

• CHANGELOG.md
• README.md
• docs/linear-issue-craft-flow.drawio

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/drawio-skill-rework

---

_{Comment @coderabbitai help to get the list of available commands.}