@owlmeans/image-resource 0.1.18-rc.0 → 0.1.18-rc.10

package/agent-meta/manifest.json

@@ -1,8 +1,8 @@
 {
   "schemaVersion": 2,
   "package": "@owlmeans/image-resource",
-  "version": "0.1.18-rc.0",
-  "generatedAt": "2026-08-16T22:20:50.507Z",
+  "version": "0.1.18-rc.10",
+  "generatedAt": "2026-09-01T16:28:56.990Z",
   "canonicalRepo": "https://github.com/owlmeans/common",
   "entries": [
     {

package/agent-meta/skills/image-resource/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: image-resource
-description: How to use @owlmeans/image-resource — image-handling Resource extending @owlmeans/storage-resource with image-specific metadata (dimensions, MIME). Auto-invoked when handling image uploads.
+description: How to use @owlmeans/image-resource — the image-shaped names and AJV schemas over the shared stored-file types from @owlmeans/storage-common. Auto-invoked when typing image records or validating an image upload.
 user-invocable: false
 ---
 <!-- AUTO-GENERATED — do not edit. Regenerate via sync-agent-meta. -->
@@ -8,24 +8,41 @@ user-invocable: false
 # @owlmeans/image-resource
 
 **Layer:** Infra
-**Install:** `"@owlmeans/image-resource": "^0.1.18-rc.0"` in `dependencies`
+**Install:** `"@owlmeans/image-resource": "^0.1.18-rc.10"` in `dependencies` (peer `ajv`)
+
+Types and schemas only — no resource is registered here. An image *is* a stored file
+([[storage-common]]); this package gives that file image-shaped names so a signature says what it
+carries, and re-emits the schemas so an image endpoint validates against its own.
 
 ## Key Exports
 
 | Export | Description |
 |--------|-------------|
-| `Image` types | Image metadata shape (dimensions, MIME, dominant color) |
-| `ImageModel` | Image-specific helpers (resize hints, derived sizes) |
+| `ImageMeta`, `StoredImage`, `ImageData` | The image spellings of `StoredFileMeta`, `StoredFile` and `StoredFileWithData` |
+| `ImageMetaSchema`, `StoredImageSchema`, `ImageDataSchema` | The matching AJV schemas |
 
 ## Usage
 
-Use in conjunction with `makeStorageResource` to type uploads as images:
+Type the record that *describes* the image, and keep it in a database resource — that is what
+answers criteria, sorting and paging. The bytes go to a bucket through
+[[storage-resource]]'s upload-only `create`.
 
 ```typescript
-import type { Image } from '@owlmeans/image-resource'
-const images = ctx.getResource<StorageResource<Image>>('uploads')
+import type { StoredImage } from '@owlmeans/image-resource'
+
+const images = ctx.resource<Resource<StoredImage>>('images')
+await images.list({ entityId, mimeType: { $startsWith: 'image/' } }, { sort: ['name'], size: 20 })
 ```
 
+`instances` carries the renditions — original, thumbnail, converted format — each with its own
+`url` and `size`. Pick the one a screen needs from that map; never rebuild a url by string surgery.
+
 ## Depends On
 
 - `@owlmeans/storage-resource`, `@owlmeans/storage-common`
+- peer `ajv`
+
+## Related
+
+- [[storage-common]] — the stored-file types and schemas these specialize
+- [[storage-resource]] — the bucket upload · [[resource]] — the record store behind it

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@owlmeans/image-resource",
   "type": "module",
-  "version": "0.1.18-rc.0",
+  "version": "0.1.18-rc.10",
   "license": "MIT",
   "scripts": {
     "build": "tsc -b",
@@ -24,7 +24,7 @@
     "ajv": "*"
   },
   "dependencies": {
-    "@owlmeans/storage-resource": "^0.1.18-rc.0"
+    "@owlmeans/storage-resource": "^0.1.18-rc.10"
   },
   "devDependencies": {
     "@owlmeans/dep-config": "workspace:*",