chore(main): release 0.1.0

[semantic-release-pusher]

🤖 I have created a release beepboop

0.1.0 (2026-08-28)

Features

• add bootstrap script with optional DDD layering (64c8d1e)
• add CLI entry point with lazy app build and __complete fast path (4ca714a)
• add package skeleton with example hello command (eff22f2)
• ban relative imports and drop a dead bootstrap exclusion (76e3d70)
• build with uv_build instead of hatchling (f39c7b3)
• build with uv_build instead of hatchling (7d0556d)

Bug Fixes

• deploy docs on workflow_dispatch, not only push (f4c2f5e)
• deploy docs on workflow_dispatch, not only push (7435517)
• drop npm cooldown to 1 day to unbreak pnpm resolution (8cec60d)
• drop npm cooldown to 1 day to unbreak pnpm resolution (c114ba6)
• escape sed replacements, validate PACKAGE_NAME, fix description leak (8925b7e)
• pin the far edge of bootstrap's ci.yaml job cut (5fb7718)
• seed an empty CHANGELOG.md so the first release is well-formed (9c291ab)
• seed an empty CHANGELOG.md so the first release is well-formed (d9db146)
• strip template-only content from generated projects (caee764)

---

This PR was generated with Release Please. See documentation.

[yo61-lastlight]

This release PR bumps the package and manifest versions and generates the 0.1.0 changelog. The version updates are consistent, but the generated changelog leaves a stray duplicate heading in the published release notes.

[yo61-lastlight]

[Important] Remove the duplicate changelog heading

The generated 0.1.0 changelog will be published with a second top-level Changelog section after the release notes. That leaves the release artifact malformed for every reader of the package changelog, so this stray heading should be removed before cutting 0.1.0.

[yo61-lastlight]

Prior finding still open — CHANGELOG.md still ends the generated 0.1.0 notes with a second ## Changelog heading. The release version bumps are consistent, but the changelog artifact remains malformed until that stray heading is removed.

[yo61-lastlight]

[Important] Remove the duplicate changelog heading

The current release notes still add a second top-level Changelog section after the 0.1.0 entries, so the published changelog for this release remains malformed for every package reader. Remove this stray heading before cutting 0.1.0.

[yo61-lastlight]

Prior findings: fixed — CHANGELOG.md no longer ends the generated 0.1.0 notes with a second ## Changelog heading. This release PR now consistently bumps the manifest, pyproject, and lockfile versions to 0.1.0 and leaves the generated changelog well-formed.

[semantic-release-pusher]

🤖 Created releases:

• v0.1.0

🌻