docs: clarify Bun requirement for source development

[CooperSheroy]

Summary

• Clarify that source development requires a local bun CLI on PATH
• Distinguish contributor commands from the published npm package's bundled Bun runtime
• Add the note to the root contributor entry point, README development section, and hosted contributing docs source

Validation

• git diff --check
• Not run: Bun-based project commands, because this cron host currently has node/npm but no bun binary on PATH.

Summary by CodeRabbit

• Documentation
  • Clarified that source development requires the Bun CLI to be installed and available on the system PATH.
  • Explained the distinction between the locally installed Bun used for development commands and the bundled runtime included with the published package.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: 4e577f55-d8d8-47c5-a08c-9b130c3b5043

📥 Commits

Reviewing files that changed from the base of the PR and between 6f4cd1d and 86e963c.

📒 Files selected for processing (3)

• CONTRIBUTING.md
• README.md
• docs-site/src/content/docs/contributing.md

---

📝 Walkthrough

Walkthrough

Development documentation now states that contributors need the bun CLI on their PATH, while published ocx commands use the package’s bundled Bun runtime.

Changes

Contributor Bun prerequisites

Layer / File(s)	Summary
Document local Bun requirements CONTRIBUTING.md, README.md, docs-site/src/content/docs/contributing.md	Adds consistent guidance that source-development commands use a locally installed bun CLI, distinct from the runtime bundled with the published npm package.

Estimated code review effort: 1 (Trivial) | ~3 minutes

Suggested reviewers: ingwannu, lidge-jun

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title accurately summarizes the documentation-only change clarifying the local Bun requirement for source development.
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

_{Comment @coderabbitai help to get the list of available commands.}

[lidge-jun]

Integrated into dev as 803807a4 with your authorship preserved via Co-authored-by. Closing this PR since the change is now on the integration branch.

Your three paragraphs went in unchanged — the wording correctly separates contributor commands from the npm package's bundled runtime, and it doesn't contradict the end-user install section further up in README.md. Thank you for catching a gap that trips up first-time contributors.

I added one regression test on top, tests/docs-bun-source-requirement.test.ts. My first attempt matched scattered fragments per file, and an independent review caught that this would keep passing after someone deleted the explanatory sentence, as long as the words survived elsewhere in the file — a test that can't fail for the reason it exists. It also would have broken on a harmless paragraph rewrap. The version that landed locates the paragraph, normalizes its whitespace, and compares the complete paragraph.

Verification, in order: fails with your doc patch reverted, passes with it applied, still passes after rewrapping the paragraph across different line breaks, and fails again when the substantive sentence is removed. Full gates on the integration commit: bun run typecheck clean, privacy:scan clean, and the full suite at 4324 passing across three batches.

---

_{Integrated as part of a maintainer PABCD pass. Plan unit: devlog/_plan/260726_pr_close_rework/010_wp1_docs_bun_requirement_437.md.}