fix(buckets): read camelCased enable-snapshots flag in create

[designcode]

What

buckets create --enable-snapshots never enabled snapshots — it created the bucket but silently left snapshots off. (mk --enable-snapshots was unaffected.)

Root cause

Commander passes flags to handlers as camelCase keys, so --enable-snapshots arrives as enableSnapshots. buckets/create.ts looked up only ['enable-snapshots', 's', 'S'] — missing the camelCase key — so the value was always undefined and enableSnapshot: enableSnapshots === true was always false. mk.ts already reads the camelCase key, which is why it worked there.

Fix

Add 'enableSnapshots' to the getOption lookup, matching mk.ts and the sibling enableDirectoryListing/sourceSnapshot reads.

Test

The existing "create with all flags" integration test passed --enable-snapshots but only asserted exit code, so it never caught this. Added a regression test that creates a bucket with --enable-snapshots and verifies snapshots are actually enabled via buckets get. Verified passing against the live backend.

🤖 Generated with Claude Code

---

Note

Low Risk
Small option-parsing fix in bucket create plus a new integration test; behavior change is limited to honoring an existing flag correctly.

Overview
Fixes buckets create --enable-snapshots so it actually turns snapshots on instead of succeeding with snapshots still disabled.

Commander exposes that flag to handlers as enableSnapshots, but buckets/create.ts only looked up kebab-case and short aliases, so the value was always missing and enableSnapshot was sent as false. The change adds enableSnapshots to the getOption list, consistent with other create flags and with mk.

Adds a CLI integration test that creates a bucket with --enable-snapshots and asserts buckets get shows snapshots enabled, since the prior “all flags” test only checked exit code.

^{Reviewed by Cursor Bugbot for commit f46ab4c. Bugbot is set up for automated code reviews on this repo. Configure here.}