chore(release): prepare 0.0.6

[DavidBabinec]

What changed

• Bumped the package version to 0.0.6.
• Added the 0.0.6 changelog entry for the work merged after v0.0.5.
• Updated deployment docs to pin examples to ghcr.io/corebunch/instatic:0.0.6.

Why

This prepares the next tagged release after the latest merged PR batch.

Impact

Users following the deployment docs will pin the new 0.0.6 image once the release tag is published. The release workflow will publish the image and bundle when v0.0.6 is pushed.

Verification

• bun install
• bun run build
• bun test (5730 pass, 0 fail)
• bun run lint
• git diff --check

[DavidBabinec]

Final CMS release smoke for 0.0.6 passed on chore/release-0.0.6 at 55a47b0bca07603e20d7d3a64d0380f596d43d16.

Command:

bun run test:e2e -- tests/e2e/auth.setup.ts tests/e2e/core-owner-lifecycle.e2e.ts --project=setup --project=e2e --trace on

Result: 2 passed, 0 failed.

Covered scenarios: SETUP-001, AUTH-001, EDIT-001, SAVE-001, PUB-001, PUB-002, PUB-003, plus publish step-up coverage from CAP-003.

Disposable local data used by the Playwright E2E stack:

• sqlite:./.tmp/e2e-agent.db
• ./.tmp/e2e-uploads

Trace artifacts are local to the release worktree under .tmp/playwright-results/ and .tmp/playwright-report/.