[htnabe]

Summary

• Prepare v0.0.6 with Bun as the repository package manager.

Changes

• Replace package-lock.json with bun.lock and pin Bun 1.4.4.
• Use Bun in package scripts, GitHub Actions, Dependabot, the dev container, Git hooks, and VS Code tasks.
• Preserve Node.js 26 compatibility, Vitest, disabled install scripts, and the seven-day release-age policy.
• Retain npm for OIDC/provenance publishing and release package checks.
• Update developer and bilingual user documentation; bump the package version to 0.0.6.

Validation

• bun install --frozen-lockfile — passed, including a clean isolated install.
• bun run lint — passed.
• bun run test — passed (105 tests).
• bun run coverage — passed (105 tests).
• bun run test:runtime — passed (build and plain Node.js 26 ESM import).
• bun run tsc --noEmit — passed.
• npm pack --dry-run — passed (7 expected package files).
• bun run prettier --check package.json AGENTS.md README.md docs/develop/publishing.md docs/guidance/guidance.en.md docs/guidance/guidance.ja.md .github/instructions/legacy-maintenance.instructions.md .github/workflows/test.yaml .github/workflows/publish.yaml .github/dependabot.yml .devcontainer/devcontainer.json .vscode/tasks.json lefthook.yaml — passed.
• git diff --check — passed.
• Confirmed migrated dependency versions and integrity hashes match the previous npm lockfile and frozen installation rejects incompatible manifest changes.

Risks

• Contributors and CI now need the pinned Bun version; Node.js 26 remains required.
• Merge into dev first, then merge dev into main to trigger Publish Release. Create v0.0.6's tag and GitHub Release only after npm publication succeeds.

Checklist

• Conventional commit(s) with gitemoji used
• Commit granularity is meaningful
• Tests and lint were run as appropriate
• Documentation updated if needed

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!