release 0.3.0

[mvoutov]

What

Why

Closes #

How I tested

• npm test passes
• Tested against a real repo:
• --dry-run output looks correct (if applicable)

Checklist

• Changes are focused on a single feature or fix
• Tests added or updated for any logic changes
• No new dependencies added (or justified in the PR description)

Summary by CodeRabbit

• New Features

  • Added import graph persistence with automatic code-map skill generation for improved context delivery
  • Introduced domain retry functionality to recover from initialization failures without full regeneration

• Bug Fixes

  • Resolved Windows CLI spawning and process termination issues
  • Improved timeout handling and error messaging across platforms
  • Enhanced graph context warnings and data validation

[coderabbitai]

Caution

Review failed

Pull request was closed or merged during review

Walkthrough

Release version bump to 0.3.0 with changelog documentation. The CHANGELOG documents new features for import graph persistence, code-map generation, and cross-platform bug fixes, while package.json updates the version field accordingly.

Changes

Cohort / File(s)	Summary
Version & Release package.json	Version bumped from 0.2.2 to 0.3.0.
Release Documentation CHANGELOG.md	Added 0.3.0 release section documenting graph persistence features (aspens doc graph, artifact generation), code-map skill auto-generation, doc init --domains retry functionality, and cross-platform fixes (Windows CLI spawning, timeout handling, graph context warnings, test compatibility).

Estimated code review effort

🎯 1 (Trivial) | ⏱️ ~2 minutes

Possibly related PRs

• install aspens + fix claude generation #11: Both PRs involve doc-generation flow updates and retry logic for base skill/CLAUDE.md generation, with overlapping scope in parseFileOutput behavior.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 warning)

Check name	Status	Explanation	Resolution
Description check	⚠️ Warning	The PR description is entirely empty—all template sections lack actual content, providing no details about what changes were made, why, or how testing was performed.	Fill in the 'What' section summarizing the release contents, 'Why' with context/issues, test results, and checklist status. Reference the CHANGELOG.md additions for specifics.

✅ Passed checks (2 passed)

Check name	Status	Explanation
Title check	✅ Passed	The title 'release 0.3.0' directly matches the changeset, which updates version numbers in package.json and documents the 0.3.0 release in CHANGELOG.md.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch new-release

---

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