chore(release): publish chart 0.2.0 to the Pages Helm repo

[ianp94]

The v0.2.0 release workflow succeeded except its final step: the pages job's direct commit to main was rejected by the new protect-main ruleset (the GitHub Actions app has no bypass entry). This PR is the exact output of that job's steps, run manually: basquin-operator-0.2.0.tgz packaged with --version 0.2.0 --app-version 0.2.0 plus the merged index.yaml.

Before the next release: add the GitHub Actions app as a bypass actor on the protect-main ruleset (Settings → Rules → protect-main → Bypass list → add "GitHub Actions"), or the pages job will fail again.

🤖 Generated with Claude Code

https://claude.ai/code/session_01LXSdVrJQy6DvELDbtptG5p

[ianp94]

@claude please review this PR: a mechanical chart-publish commit (basquin-operator-0.2.0.tgz + regenerated index.yaml) replicating the release pages job that the branch ruleset blocked. Verify the index.yaml 0.2.0 entry is well-formed (digest/urls/version/appVersion) and the 0.1.0 entry is preserved.

[claude]

Claude finished @ianp94's task in 1m 33s —— View job

---

Reviewing PR #47

• Gather context (PR diff, changed files)
• Verify index.yaml 0.2.0 entry is well-formed (digest/urls/version/appVersion)
• Verify 0.1.0 entry preserved
• Verify digest matches actual tarball contents
• Post review

Verdict: ✅ Looks correct — mechanical, matches the described release output

index.yaml 0.2.0 entry (docs/charts/index.yaml:3-25):

• digest: 568409bf...3894605e — recomputed sha256sum docs/charts/basquin-operator-0.2.0.tgz locally and it matches exactly.
• urls: [https://ianp94.github.io/basquin/charts/basquin-operator-0.2.0.tgz] — correct path/filename for the Pages Helm repo layout, consistent with the 0.1.0 entry's URL pattern.
• version: 0.2.0, appVersion: 0.2.0 — as expected, matches the PR description's --version 0.2.0 --app-version 0.2.0 packaging flags.
• name, description, keywords, home, sources, type: application all match deploy/helm/basquin-operator/Chart.yaml verbatim.

0.1.0 entry preserved (docs/charts/index.yaml:26-47): byte-for-byte unchanged from before this PR — digest (8f28c0c4...4ecc38) also verified against the existing basquin-operator-0.1.0.tgz and matches.

One pre-existing (not introduced by this PR) point worth flagging for awareness: deploy/helm/basquin-operator/Chart.yaml still has version: 0.1.0 in the repo, while the published index now has a 0.2.0 chart entry. That's expected given the release job overrides the packaged version via --version 0.2.0 on the CLI, but it does mean the source-of-truth Chart.yaml is out of sync with what's published — worth a follow-up to bump Chart.yaml's version field to 0.2.0 so a future plain helm package (without explicit --version) doesn't regress to 0.1.0. Not a blocker for this PR since it's just replaying the existing release job's output.

Also note: docs/charts/basquin-operator-0.2.0.tgz is a binary tarball being committed directly to the repo (consistent with how 0.1.0.tgz is already tracked here, so this follows existing convention for this Pages Helm repo).

No issues that would block merging — this PR does exactly what it says: replicates the blocked pages job's output by hand. Once merged, don't forget the follow-up mentioned in the PR body (add GitHub Actions as a bypass actor on protect-main) so future releases don't need this manual workaround.