feat: scaffold + local-dev KV namespace bindings for edge projects (v0.10.1) [BDOK-685]

[DuncanAForbes]

Small CLI DX improvement (BDOK-685). Was uncommitted WIP in the working tree; re-checked and shipped separately from the 0.10.0 app-identity work.

What

• bagdock init scaffolds kv: { OPERATOR_CONFIG } for edge projects (the per-installation lifecycle/config state store edge adapters/comms already expect — the comms env-types template references OPERATOR_CONFIG; the deploy handler provisions KV from config.kv).
• bagdock dev emits [[kv_namespaces]] in the generated wrangler.toml for any declared kv, with a deterministic local-dev-<binding> id/preview_id so local Miniflare persists KV between runs.

Safe / re-checked

• Guarded by config.kv — no effect on projects without KV (all app-type projects unchanged).
• Uses the existing KvDeclaration type + the deploy handler's lowercase-binding convention; valid TOML ordering (array-of-tables after top-level scalars, before [vars]).
• Verified: tsc clean, 28 tests pass, init edge scaffolds the KV block, dev generates a valid wrangler.toml with the [[kv_namespaces]] table.

Bumps 0.10.0 → 0.10.1. Publishes on merge (push-to-main).

Linear

Closes BDOK-685

[coderabbitai]

Warning

Review limit reached

@DuncanAForbes, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 30 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: 356c7587-fd2c-4768-a7c2-c501e78b726f

📥 Commits

Reviewing files that changed from the base of the PR and between d8b1e83 and f148049.

📒 Files selected for processing (4)

• CHANGELOG.md
• package.json
• src/dev.ts
• src/init.ts

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/BDOK-678-kv-scaffold

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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