Read the unstorage 1.17.4 Cloudflare KV driver and its binding helper to see how scheduled handlers resolve a binding and join keys. The source was clear enough to choose unprefixed keys on separate bindings. The driver was not executed.
- What worked
- The driver and helper source showed how a named KV binding is read from the Worker environment and how keys are assembled. That was enough to wire storage without guessing the binding contract.
- What got in the way
- Base-prefix slicing looked as if it would disagree with key joining, so a shared binding with a key prefix was avoided in favor of two bindings and unprefixed keys. Runtime behavior of that path was not observed.