This PR updates the Images Binding interface to adopt a chainable handle pattern for per-image operations, bringing it more in line with the upcoming Stream Binding.

CRUD support was originally added in #5912 but has yet to be made generally available - at present it is gated to my developer account. This is technically a breaking change to the interface, but is safe as no external users will be impacted.

Changes

Previously, per-image operations were flat methods on the hosted namespace:

await env.IMAGES.hosted.details(id);
await env.IMAGES.hosted.update(id, { requireSignedURLs: true });
await env.IMAGES.hosted.delete(id);
const stream = await env.IMAGES.hosted.image(id); // raw bytes

These operations now go via an intermediate handle, returned synchronously from hosted.image(id):

const handle = env.IMAGES.hosted.image(id);
await handle.details();
await handle.update({ requireSignedURLs: true });
await handle.delete();
const stream = await handle.bytes(); // renamed from image()

Note that upload() and list() are unchanged.

Reviewer considerations

• The breaking change to image() — which previously returned a Promise and now returns a synchronous handle — is the most significant thing to be aware of. Given the gating situation this should be fine, but worth a look.
• The rename from image() to bytes() on the handle is deliberate, to avoid confusion now that image() is the handle factory.
• The corresponding upstream service change is here

Testing

Unit tests. Will verify E2E against gated developer account before releasing more widely