[WIP] Prepare and validate v0.2.0 npm release with CI verification

[Copilot]

Thanks for assigning this issue to me. I'm starting to work on it and will keep this PR's description up to date as I form a plan and make progress.

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Prepare and validate v0.2.0 npm release (version bump + CI verification)</issue_title>
<issue_description>#### Goal

Prepare a clean v0.2.0 release of PromptKit suitable for automated npm publishing, ensuring version correctness, CI success, and release hygiene.

This issue is intended for a GitHub SWE agent with repository access.

---

Context

• v0.2.0 has been tagged / released conceptually.
• The npm package.json (or equivalent npm manifest) still references the previous version.
• Automated npm publishing is enabled via GitHub Actions and should be the source of truth.
• We do not want manual publishing or version reuse.

---

Tasks

1. Version hygiene

   • Locate the npm manifest used for publishing (e.g. package.json).
   • Update the version to 0.2.0 (or the next appropriate patch version if 0.2.0 is already consumed).
   • Ensure there are no other stale version references (docs are fine to lag; manifests are not).

2. Commit and traceability

   • Commit the version bump as a standalone, minimal commit.
   • Use a neutral commit message, e.g.:
     chore: bump npm version for v0.2.0 release

3. Release alignment

   • Verify that the git tag / GitHub Release version matches the npm version.
   • If mismatched, update tags/releases as needed to maintain consistency.

4. CI / automation verification

   • Ensure the existing GitHub Actions workflow triggers correctly.
   • Confirm that the workflow:
     • authenticates correctly to npm
     • publishes the expected package name
     • publishes the expected version
   • Do not introduce new publishing mechanisms unless required to fix a break.

5. Validation

   • Confirm that the published npm package:
     • has the correct version
     • is publicly accessible (if scoped, ensure access: public)
     • contains the expected files (no empty or malformed tarball)

---

Non‑Goals

• No changes to PromptKit semantics, templates, or documentation.
• No refactoring of CI beyond what is required to unblock publishing.
• No manual npm publish outside of CI.

---

Definition of Done

• ✅ npm registry shows the correct PromptKit version.
• ✅ GitHub Actions publishing job passes cleanly.
• ✅ Versioning is consistent across:
  • npm manifest
  • git tags
  • GitHub Release metadata
• ✅ No reuse of an already‑published npm version.

</issue_description>

Comments on the Issue (you are @copilot in this section)

• Fixes Prepare and validate v0.2.0 npm release (version bump + CI verification) #53

---

📱 Kick off Copilot coding agent tasks wherever you are with GitHub Mobile, available on iOS and Android.