chore: archive v2.2 User Experience Polish milestone
All checks were successful
CI / ci (push) Successful in 1m15s
CI / e2e (push) Has been skipped
CI / deploy (push) Has been skipped

Phases 28-31 archived to milestones/v2.2-phases/
Requirements and roadmap snapshots archived to milestones/

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
This commit is contained in:
2026-04-13 16:00:35 +02:00
parent 92b84d2cd6
commit 2853477a75
62 changed files with 586 additions and 96 deletions

View File

@@ -0,0 +1,281 @@
---
phase: 29
plan: 01
type: backend
wave: 1
depends_on: []
files_modified:
- src/db/schema.ts
- src/shared/schemas.ts
- src/shared/types.ts
- src/server/routes/images.ts
- src/server/services/image.service.ts
- src/server/services/storage.service.ts
- src/server/services/item.service.ts
- src/server/routes/items.ts
- src/server/routes/threads.ts
- src/server/routes/global-items.ts
- package.json
autonomous: true
requirements: []
---
<objective>
Add dominant color extraction on image upload and extend the database schema with dominantColor and crop fields across items, globalItems, and threadCandidates tables. Install Sharp for server-side image processing. Update API schemas and services to accept/return the new fields.
</objective>
<tasks>
### Task 1: Install Sharp dependency
<task type="command">
<action>
Run `bun add sharp` and `bun add -d @types/sharp` to install the Sharp image processing library and its type definitions.
</action>
<verify>
<automated>grep '"sharp"' package.json && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- package.json contains `"sharp"` in dependencies
- @types/sharp in devDependencies
- `bun install` completes without errors
</acceptance_criteria>
</task>
### Task 2: Add schema fields to database
<task type="code">
<read_first>
- src/db/schema.ts
</read_first>
<action>
Add four new fields to THREE tables in `src/db/schema.ts`:
**items table** — add after `brand: text("brand")`:
```ts
dominantColor: text("dominant_color"),
cropZoom: doublePrecision("crop_zoom"),
cropX: doublePrecision("crop_x"),
cropY: doublePrecision("crop_y"),
```
**globalItems table** — add after `imageSourceUrl: text("image_source_url")`:
```ts
dominantColor: text("dominant_color"),
cropZoom: doublePrecision("crop_zoom"),
cropX: doublePrecision("crop_x"),
cropY: doublePrecision("crop_y"),
```
**threadCandidates table** — add after `imageSourceUrl: text("image_source_url")`:
```ts
dominantColor: text("dominant_color"),
cropZoom: doublePrecision("crop_zoom"),
cropX: doublePrecision("crop_x"),
cropY: doublePrecision("crop_y"),
```
</action>
<verify>
<automated>grep -c "dominant_color" src/db/schema.ts | grep -q "3" && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- `src/db/schema.ts` contains `dominantColor: text("dominant_color")` in items, globalItems, and threadCandidates tables (3 occurrences)
- `src/db/schema.ts` contains `cropZoom: doublePrecision("crop_zoom")` in all 3 tables
- `src/db/schema.ts` contains `cropX: doublePrecision("crop_x")` in all 3 tables
- `src/db/schema.ts` contains `cropY: doublePrecision("crop_y")` in all 3 tables
</acceptance_criteria>
</task>
### Task 3: [BLOCKING] Push schema changes to database
<task type="command">
<action>
Run `bun run db:generate` to generate the Drizzle migration, then `bun run db:push` to apply it to the database.
</action>
<verify>
<automated>bun run db:push 2>&1 | tail -5</automated>
</verify>
<acceptance_criteria>
- Migration generated successfully
- `bun run db:push` completes without errors
- Database contains dominant_color, crop_zoom, crop_x, crop_y columns on items, global_items, and thread_candidates tables
</acceptance_criteria>
</task>
### Task 4: Create dominant color extraction utility
<task type="code">
<read_first>
- src/server/services/storage.service.ts
- src/server/services/image.service.ts
</read_first>
<action>
Create a new function `extractDominantColor` in `src/server/services/image.service.ts`:
```ts
import sharp from "sharp";
/**
* Extract the dominant color from an image buffer.
* Resizes to 1x1 pixel for a perceptually weighted average.
* Returns hex string like '#a3b2c1' or null on failure.
*/
export async function extractDominantColor(buffer: Buffer | ArrayBuffer): Promise<string | null> {
try {
const { data } = await sharp(Buffer.from(buffer))
.resize(1, 1)
.raw()
.toBuffer({ resolveWithObject: true });
const r = data[0];
const g = data[1];
const b = data[2];
return `#${r.toString(16).padStart(2, '0')}${g.toString(16).padStart(2, '0')}${b.toString(16).padStart(2, '0')}`;
} catch {
return null;
}
}
```
Keep the existing `fetchImageFromUrl` function. Add the import for sharp at the top.
</action>
<verify>
<automated>grep "extractDominantColor" src/server/services/image.service.ts && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- `src/server/services/image.service.ts` exports `extractDominantColor` function
- Function accepts `Buffer | ArrayBuffer` and returns `Promise<string | null>`
- Uses `sharp(buffer).resize(1, 1).raw().toBuffer()` to extract color
- Returns hex string in format `#rrggbb`
- Returns null on error (try/catch)
</acceptance_criteria>
</task>
### Task 5: Integrate dominant color extraction into upload endpoints
<task type="code">
<read_first>
- src/server/routes/images.ts
- src/server/services/image.service.ts
</read_first>
<action>
Update `src/server/routes/images.ts` to extract dominant color during upload:
**POST `/` (direct upload):**
1. After `const buffer = await file.arrayBuffer();`
2. Add: `const dominantColor = await extractDominantColor(buffer);`
3. Change response from `{ filename }` to `{ filename, dominantColor }`
**POST `/from-url`:**
1. In `src/server/services/image.service.ts`, update `fetchImageFromUrl` to also extract dominant color
2. After `await uploadImage(Buffer.from(buffer), filename, contentType);`
3. Add: `const dominantColor = await extractDominantColor(buffer);`
4. Change return from `{ filename, sourceUrl: url }` to `{ filename, sourceUrl: url, dominantColor }`
5. Update `FetchImageResult` interface to include `dominantColor: string | null`
Import `extractDominantColor` in images.ts from `../services/image.service`.
</action>
<verify>
<automated>grep "dominantColor" src/server/routes/images.ts && grep "dominantColor" src/server/services/image.service.ts && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- `POST /api/images` response includes `dominantColor` field (string or null)
- `POST /api/images/from-url` response includes `dominantColor` field
- `FetchImageResult` interface has `dominantColor: string | null`
- Dominant color extraction happens before the response is sent
</acceptance_criteria>
</task>
### Task 6: Update Zod schemas for new fields
<task type="code">
<read_first>
- src/shared/schemas.ts
</read_first>
<action>
Update `src/shared/schemas.ts`:
**createItemSchema** — add after `brand: z.string().optional()`:
```ts
dominantColor: z.string().nullable().optional(),
cropZoom: z.number().nullable().optional(),
cropX: z.number().nullable().optional(),
cropY: z.number().nullable().optional(),
```
**createCandidateSchema** — add after `globalItemId: z.number().int().positive().optional()`:
```ts
dominantColor: z.string().nullable().optional(),
cropZoom: z.number().nullable().optional(),
cropX: z.number().nullable().optional(),
cropY: z.number().nullable().optional(),
```
**upsertGlobalItemSchema** — add after `tags`:
```ts
dominantColor: z.string().nullable().optional(),
cropZoom: z.number().nullable().optional(),
cropX: z.number().nullable().optional(),
cropY: z.number().nullable().optional(),
```
updateItemSchema and updateCandidateSchema already use `.partial()` so they inherit the new fields automatically.
</action>
<verify>
<automated>grep -c "dominantColor" src/shared/schemas.ts | grep -q "3" && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- `createItemSchema` contains `dominantColor`, `cropZoom`, `cropX`, `cropY` fields
- `createCandidateSchema` contains the same 4 fields
- `upsertGlobalItemSchema` contains the same 4 fields
- All use `z.number().nullable().optional()` for crop fields
- All use `z.string().nullable().optional()` for dominantColor
</acceptance_criteria>
</task>
### Task 7: Update storage service to return dominant color with image URLs
<task type="code">
<read_first>
- src/server/services/storage.service.ts
</read_first>
<action>
The `withImageUrl` and `withImageUrls` functions in `src/server/services/storage.service.ts` currently enrich records with `imageUrl`. They already pass through all record fields via spread operator, so `dominantColor`, `cropZoom`, `cropX`, `cropY` will automatically be included in the response when they exist on the record.
No changes needed to storage.service.ts — the spread operator `{ ...record, imageUrl }` already forwards all fields.
Verify this by confirming the return type `T & { imageUrl: string | null }` preserves all properties of T.
</action>
<verify>
<automated>grep "...record" src/server/services/storage.service.ts && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- `withImageUrl` function uses spread operator `{ ...record, imageUrl }` which preserves dominantColor and crop fields from the source record
- No changes needed — verify existing behavior is sufficient
</acceptance_criteria>
</task>
</tasks>
<verification>
1. `bun run lint` passes
2. `bun test` passes (existing tests not broken)
3. Database has new columns: `SELECT column_name FROM information_schema.columns WHERE table_name = 'items' AND column_name LIKE '%crop%' OR column_name = 'dominant_color';`
4. Upload endpoint returns dominantColor in response body
</verification>
<success_criteria>
- Sharp installed and importable
- 3 tables have dominantColor + crop fields
- Image upload extracts and returns dominant color
- Zod schemas accept new fields
- All existing tests pass
</success_criteria>
<threat_model>
| Threat | Severity | Mitigation |
|--------|----------|------------|
| Sharp buffer overflow via malformed image | Medium | Sharp handles this internally with libvips bounds checking; wrapped in try/catch returning null |
| DoS via large image processing | Low | Existing 5MB file size limit applies before Sharp processing |
| Stored XSS via dominantColor field | Low | Value is a hex color string extracted server-side, not user input; rendered as CSS backgroundColor |
</threat_model>
<must_haves>
- [ ] Sharp dependency installed
- [ ] dominantColor field on items, globalItems, threadCandidates
- [ ] Crop fields (cropZoom, cropX, cropY) on all 3 tables
- [ ] Upload endpoints return dominantColor
- [ ] Schema pushed to database
</must_haves>

View File

@@ -0,0 +1,50 @@
---
phase: 29
plan: 01
subsystem: backend
tags: [schema, image-processing, sharp]
key-files:
created: []
modified:
- src/db/schema.ts
- src/shared/schemas.ts
- src/server/services/image.service.ts
- src/server/routes/images.ts
- package.json
metrics:
tasks: 7
commits: 5
files-changed: 6
---
# Plan 29-01 Summary: Schema + Dominant Color Extraction
## What was built
- Installed Sharp image processing library for server-side color extraction
- Added `dominant_color`, `crop_zoom`, `crop_x`, `crop_y` columns to items, global_items, and thread_candidates tables
- Created `extractDominantColor()` function that resizes image to 1x1 pixel for weighted average color
- Integrated color extraction into both image upload endpoints (direct and from-url)
- Updated Zod schemas for items, candidates, and global items to accept new fields
- Generated Drizzle migration (db:push deferred — requires running database)
## Commits
| Task | Commit | Description |
|------|--------|-------------|
| 1 | cee1500 | Install Sharp for image processing |
| 2 | 36363a8 | Add dominantColor and crop fields to schema |
| 3 | b637b10 | Generate migration for image presentation fields |
| 4 | e305fa7 | Add dominant color extraction via Sharp |
| 5 | 2696b78 | Extract dominant color in image upload endpoints |
| 6 | 3480473 | Add image presentation fields to Zod schemas |
| 7 | — | No changes needed (storage service already spreads fields) |
## Deviations
- Task 3 (db:push): Database not accessible in dev environment — migration generated but push deferred to deployment. This is non-blocking for frontend work.
## Self-Check: PASSED
- Sharp installed: YES
- dominant_color in 3 tables: YES (grep confirms 3 occurrences)
- Zod schemas updated: YES (3 schemas)
- Upload returns dominantColor: YES
- Lint passes: YES

View File

@@ -0,0 +1,566 @@
---
phase: 29
plan: 02
type: frontend
wave: 1
depends_on: []
files_modified:
- src/client/components/GearImage.tsx
- src/client/components/ItemCard.tsx
- src/client/components/GlobalItemCard.tsx
- src/client/components/CandidateCard.tsx
- src/client/components/CandidateListItem.tsx
- src/client/components/ImageUpload.tsx
- src/client/components/ComparisonTable.tsx
- src/client/components/CatalogSearchOverlay.tsx
- src/client/routes/items/$itemId.tsx
- src/client/routes/global-items/$globalItemId.tsx
- src/client/routes/global-items/index.tsx
- src/client/routes/threads/$threadId/candidates/$candidateId.tsx
autonomous: true
requirements: []
---
<objective>
Create the GearImage shared component that renders images with object-contain + dominant color background fill, and replace all inline image elements across 12 surfaces with GearImage. This delivers the core visual change: fit-within framing instead of hard crops.
</objective>
<tasks>
### Task 1: Create GearImage component
<task type="code">
<read_first>
- src/client/components/ItemCard.tsx (current image rendering pattern)
- src/client/components/GlobalItemCard.tsx (current image rendering pattern)
</read_first>
<action>
Create `src/client/components/GearImage.tsx`:
```tsx
interface GearImageProps {
src: string;
alt: string;
dominantColor?: string | null;
cropZoom?: number | null;
cropX?: number | null;
cropY?: number | null;
aspectRatio?: string;
className?: string;
cover?: boolean;
}
export function GearImage({
src,
alt,
dominantColor,
cropZoom,
cropX,
cropY,
aspectRatio = "4/3",
className = "",
cover = false,
}: GearImageProps) {
const hasCrop = cropZoom != null && cropZoom > 1;
const bgColor = dominantColor || "#f3f4f6";
if (cover) {
return (
<img
src={src}
alt={alt}
className={`w-full h-full object-cover ${className}`}
/>
);
}
if (hasCrop) {
return (
<div
className={`aspect-[${aspectRatio}] overflow-hidden ${className}`}
style={{ backgroundColor: bgColor }}
>
<img
src={src}
alt={alt}
className="w-full h-full object-cover"
style={{
transform: `scale(${cropZoom}) translate(${cropX ?? 0}%, ${cropY ?? 0}%)`,
transformOrigin: "center center",
}}
/>
</div>
);
}
return (
<div
className={`aspect-[${aspectRatio}] overflow-hidden ${className}`}
style={{ backgroundColor: bgColor }}
>
<img
src={src}
alt={alt}
className="w-full h-full object-contain"
/>
</div>
);
}
```
Note: The `aspectRatio` in className uses Tailwind arbitrary values. Since the aspect ratio container is typically provided by the parent, the GearImage component renders as a child within the existing aspect-ratio div. Adjust the component to NOT wrap with its own aspect-ratio div when used inside cards (the parent already has `aspect-[4/3]`). Instead, the component should just render the image with the correct object-fit and background color:
Simplified version (preferred — parent controls aspect ratio):
```tsx
export function GearImage({
src,
alt,
dominantColor,
cropZoom,
cropX,
cropY,
className = "",
cover = false,
}: Omit<GearImageProps, 'aspectRatio'>) {
const hasCrop = cropZoom != null && cropZoom > 1;
const bgColor = dominantColor || "#f3f4f6";
if (cover) {
return (
<img src={src} alt={alt} className={`w-full h-full object-cover ${className}`} />
);
}
if (hasCrop) {
return (
<img
src={src}
alt={alt}
className={`w-full h-full object-cover ${className}`}
style={{
transform: `scale(${cropZoom}) translate(${cropX ?? 0}%, ${cropY ?? 0}%)`,
transformOrigin: "center center",
}}
/>
);
}
return (
<img src={src} alt={alt} className={`w-full h-full object-contain ${className}`} />
);
}
```
The **parent div** provides aspect ratio, overflow-hidden, and the `style={{ backgroundColor: dominantColor }}`. This matches the existing pattern where the parent `<div className="aspect-[4/3] bg-gray-50">` wraps the image.
</action>
<verify>
<automated>test -f src/client/components/GearImage.tsx && grep "object-contain" src/client/components/GearImage.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- `src/client/components/GearImage.tsx` exists
- Exports `GearImage` component
- Default rendering uses `object-contain` (not `object-cover`)
- When `cover` prop is true, uses `object-cover`
- When crop values exist and cropZoom > 1, uses CSS transform with scale and translate
- Accepts `dominantColor`, `cropZoom`, `cropX`, `cropY` props
</acceptance_criteria>
</task>
### Task 2: Update ItemCard to use GearImage
<task type="code">
<read_first>
- src/client/components/ItemCard.tsx
- src/client/components/GearImage.tsx
</read_first>
<action>
In `src/client/components/ItemCard.tsx`:
1. Add `dominantColor`, `cropZoom`, `cropX`, `cropY` to `ItemCardProps` interface (all `number | null` or `string | null`)
2. Import `GearImage` from `./GearImage`
3. Replace the image div (around line 164-179):
Current:
```tsx
<div className="aspect-[4/3] bg-gray-50">
{imageUrl ? (
<img src={imageUrl} alt={name} className="w-full h-full object-cover" />
) : (
<div className="w-full h-full flex flex-col items-center justify-center">
<LucideIcon name={categoryIcon} size={36} className="text-gray-400" />
</div>
)}
</div>
```
New:
```tsx
<div
className="aspect-[4/3] overflow-hidden"
style={{ backgroundColor: imageUrl ? (dominantColor || "#f3f4f6") : undefined }}
>
{imageUrl ? (
<GearImage
src={imageUrl}
alt={name}
dominantColor={dominantColor}
cropZoom={cropZoom}
cropX={cropX}
cropY={cropY}
/>
) : (
<div className="w-full h-full bg-gray-50 flex flex-col items-center justify-center">
<LucideIcon name={categoryIcon} size={36} className="text-gray-400" />
</div>
)}
</div>
```
</action>
<verify>
<automated>grep "GearImage" src/client/components/ItemCard.tsx && ! grep "object-cover" src/client/components/ItemCard.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- ItemCard imports and uses GearImage component
- No `object-cover` remains in ItemCard.tsx
- `dominantColor` prop is passed to GearImage
- Parent div uses inline `backgroundColor` style from dominantColor
- Empty state (no image) still shows category icon on gray-50 background
</acceptance_criteria>
</task>
### Task 3: Update GlobalItemCard to use GearImage
<task type="code">
<read_first>
- src/client/components/GlobalItemCard.tsx
- src/client/components/GearImage.tsx
</read_first>
<action>
In `src/client/components/GlobalItemCard.tsx`:
1. Add `dominantColor?: string | null`, `cropZoom?: number | null`, `cropX?: number | null`, `cropY?: number | null` to `GlobalItemCardProps`
2. Import `GearImage` from `./GearImage`
3. Replace the image rendering (around line 31-54):
Current:
```tsx
<div className="aspect-[4/3] bg-gray-50">
{imageUrl ? (
<img src={imageUrl} alt={`${brand} ${model}`} className="w-full h-full object-cover" />
) : (
<div className="w-full h-full flex flex-col items-center justify-center">
{/* SVG placeholder */}
</div>
)}
</div>
```
New:
```tsx
<div
className="aspect-[4/3] overflow-hidden"
style={{ backgroundColor: imageUrl ? (dominantColor || "#f3f4f6") : undefined }}
>
{imageUrl ? (
<GearImage
src={imageUrl}
alt={`${brand} ${model}`}
dominantColor={dominantColor}
cropZoom={cropZoom}
cropX={cropX}
cropY={cropY}
/>
) : (
<div className="w-full h-full bg-gray-50 flex flex-col items-center justify-center">
{/* Keep existing SVG placeholder */}
</div>
)}
</div>
```
</action>
<verify>
<automated>grep "GearImage" src/client/components/GlobalItemCard.tsx && ! grep "object-cover" src/client/components/GlobalItemCard.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- GlobalItemCard imports and uses GearImage
- No `object-cover` in GlobalItemCard.tsx
- Props include dominantColor, cropZoom, cropX, cropY
</acceptance_criteria>
</task>
### Task 4: Update CandidateCard to use GearImage
<task type="code">
<read_first>
- src/client/components/CandidateCard.tsx
- src/client/components/GearImage.tsx
</read_first>
<action>
Same pattern as Task 2/3:
1. Add `dominantColor`, `cropZoom`, `cropX`, `cropY` to props interface
2. Import `GearImage`
3. Replace `<img className="w-full h-full object-cover">` with `<GearImage>` inside the existing `aspect-[4/3]` container
4. Update parent div to use inline `backgroundColor` style
</action>
<verify>
<automated>grep "GearImage" src/client/components/CandidateCard.tsx && ! grep "object-cover" src/client/components/CandidateCard.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- CandidateCard uses GearImage component
- No `object-cover` remaining
- Dominant color props threaded through
</acceptance_criteria>
</task>
### Task 5: Update CandidateListItem to use GearImage
<task type="code">
<read_first>
- src/client/components/CandidateListItem.tsx
- src/client/components/GearImage.tsx
</read_first>
<action>
Same pattern:
1. Add image presentation props to interface
2. Import GearImage
3. Replace `object-cover` image with GearImage
4. Update parent container background color
</action>
<verify>
<automated>grep "GearImage" src/client/components/CandidateListItem.tsx && ! grep "object-cover" src/client/components/CandidateListItem.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- CandidateListItem uses GearImage
- No `object-cover` remaining
</acceptance_criteria>
</task>
### Task 6: Update ComparisonTable to use GearImage
<task type="code">
<read_first>
- src/client/components/ComparisonTable.tsx
- src/client/components/GearImage.tsx
</read_first>
<action>
Same pattern: replace inline `<img className="w-full h-full object-cover">` with `<GearImage>`. Thread dominantColor and crop props from the data source.
</action>
<verify>
<automated>grep "GearImage" src/client/components/ComparisonTable.tsx && ! grep "object-cover" src/client/components/ComparisonTable.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- ComparisonTable uses GearImage
- No `object-cover` remaining
</acceptance_criteria>
</task>
### Task 7: Update CatalogSearchOverlay to use GearImage
<task type="code">
<read_first>
- src/client/components/CatalogSearchOverlay.tsx
- src/client/components/GearImage.tsx
</read_first>
<action>
CatalogSearchOverlay has 2 `object-cover` instances (search results and selected item preview). Replace both with GearImage. Thread dominantColor from global item data.
</action>
<verify>
<automated>grep "GearImage" src/client/components/CatalogSearchOverlay.tsx && ! grep "object-cover" src/client/components/CatalogSearchOverlay.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- Both image instances in CatalogSearchOverlay use GearImage
- No `object-cover` remaining in the file
</acceptance_criteria>
</task>
### Task 8: Update ImageUpload preview to use GearImage
<task type="code">
<read_first>
- src/client/components/ImageUpload.tsx
- src/client/components/GearImage.tsx
</read_first>
<action>
In `src/client/components/ImageUpload.tsx`:
1. Add `dominantColor?: string | null` to `ImageUploadProps`
2. Import GearImage
3. Replace the preview image (line 76-79):
Current:
```tsx
<img src={displayUrl} alt="Item" className="w-full h-full object-cover" />
```
New:
```tsx
<GearImage src={displayUrl} alt="Item" dominantColor={dominantColor} />
```
4. Update the parent container to use dominant color background:
```tsx
style={{ backgroundColor: displayUrl ? (dominantColor || "#f3f4f6") : undefined }}
```
</action>
<verify>
<automated>grep "GearImage" src/client/components/ImageUpload.tsx && ! grep "object-cover" src/client/components/ImageUpload.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- ImageUpload uses GearImage for preview
- No `object-cover` remaining
- Accepts dominantColor prop
</acceptance_criteria>
</task>
### Task 9: Update item detail page
<task type="code">
<read_first>
- src/client/routes/items/$itemId.tsx
- src/client/components/GearImage.tsx
</read_first>
<action>
In `src/client/routes/items/$itemId.tsx`:
1. Import GearImage
2. Replace the `object-cover` image (around line 245-250) with GearImage
3. Update the parent `aspect-[4/3]` div to use dominant color background via inline style
4. Thread dominantColor, cropZoom, cropX, cropY from the item data
</action>
<verify>
<automated>grep "GearImage" src/client/routes/items/\$itemId.tsx && ! grep "object-cover" src/client/routes/items/\$itemId.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- Item detail page uses GearImage
- No `object-cover` in the file
- Dominant color and crop fields used from item data
</acceptance_criteria>
</task>
### Task 10: Update global item detail page
<task type="code">
<read_first>
- src/client/routes/global-items/$globalItemId.tsx
- src/client/components/GearImage.tsx
</read_first>
<action>
In `src/client/routes/global-items/$globalItemId.tsx`:
1. Import GearImage
2. Replace the `object-cover` image (around line 65-70) with GearImage
3. This page uses `aspect-[16/9]` — keep that ratio on the parent container
4. Update background color to use dominant color
</action>
<verify>
<automated>grep "GearImage" src/client/routes/global-items/\$globalItemId.tsx && ! grep "object-cover" src/client/routes/global-items/\$globalItemId.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- Global item detail uses GearImage
- No `object-cover` remaining
- Aspect ratio 16/9 preserved
</acceptance_criteria>
</task>
### Task 11: Update global items index page
<task type="code">
<read_first>
- src/client/routes/global-items/index.tsx
- src/client/components/GearImage.tsx
</read_first>
<action>
In `src/client/routes/global-items/index.tsx`:
1. Import GearImage
2. Replace `object-cover` image with GearImage
3. Thread dominantColor from global item data
</action>
<verify>
<automated>grep "GearImage" src/client/routes/global-items/index.tsx && ! grep "object-cover" src/client/routes/global-items/index.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- Global items index uses GearImage
- No `object-cover` remaining
</acceptance_criteria>
</task>
### Task 12: Update candidate detail page
<task type="code">
<read_first>
- src/client/routes/threads/$threadId/candidates/$candidateId.tsx
- src/client/components/GearImage.tsx
</read_first>
<action>
In `src/client/routes/threads/$threadId/candidates/$candidateId.tsx`:
1. Import GearImage
2. Replace `object-cover` image with GearImage
3. This page uses `aspect-[16/9]` — keep that ratio
4. Thread dominantColor and crop fields from candidate data
</action>
<verify>
<automated>grep "GearImage" src/client/routes/threads/\$threadId/candidates/\$candidateId.tsx && ! grep "object-cover" src/client/routes/threads/\$threadId/candidates/\$candidateId.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- Candidate detail uses GearImage
- No `object-cover` remaining
- Aspect ratio 16/9 preserved
</acceptance_criteria>
</task>
### Task 13: Update LinkToGlobalItem with cover mode
<task type="code">
<read_first>
- src/client/components/LinkToGlobalItem.tsx
- src/client/components/GearImage.tsx
</read_first>
<action>
In `src/client/components/LinkToGlobalItem.tsx`:
The 32x32px thumbnail is too small for letterbox treatment. Use GearImage with `cover={true}` prop to keep `object-cover` for this tiny thumbnail:
Replace:
```tsx
<img className="w-8 h-8 rounded object-cover shrink-0" ... />
```
With:
```tsx
<GearImage src={...} alt={...} cover className="w-8 h-8 rounded shrink-0" />
```
</action>
<verify>
<automated>grep "GearImage" src/client/components/LinkToGlobalItem.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- LinkToGlobalItem uses GearImage with `cover` prop
- Small thumbnail renders with object-cover (intentional exception for tiny images)
</acceptance_criteria>
</task>
</tasks>
<verification>
1. `bun run lint` passes
2. `bun run build` passes (TypeScript compilation)
3. `grep -r "object-cover" src/client/ --include="*.tsx"` returns ONLY:
- `GearImage.tsx` (internal cover mode)
- `ProfileSection.tsx` (user avatar — out of scope)
- `routes/users/$userId.tsx` (user avatar — out of scope)
4. All 12 surfaces render images with `object-contain` by default
</verification>
<success_criteria>
- GearImage component exists and is used by all 12 gear image surfaces
- Default image display uses object-contain (fit-within)
- Dominant color background fills letterbox/pillarbox space
- Cropped images display with CSS transform
- LinkToGlobalItem uses cover mode for 32px thumbnails
- No regression in empty state (placeholder icons still show)
</success_criteria>
<threat_model>
| Threat | Severity | Mitigation |
|--------|----------|------------|
| XSS via dominantColor in style attribute | Low | dominantColor is server-extracted hex string, not user input; React escapes style values |
| Layout shift from object-contain | Low | Container maintains fixed aspect ratio; image loads within same bounds |
</threat_model>
<must_haves>
- [ ] GearImage component created at src/client/components/GearImage.tsx
- [ ] All 12 image surfaces use GearImage (except ProfileSection/user avatar)
- [ ] Default rendering uses object-contain, not object-cover
- [ ] Dominant color background on image containers
- [ ] LinkToGlobalItem uses cover mode for tiny thumbnails
</must_haves>

View File

@@ -0,0 +1,56 @@
---
phase: 29
plan: 02
subsystem: frontend
tags: [components, image-rendering, ui]
key-files:
created:
- src/client/components/GearImage.tsx
modified:
- src/client/components/ItemCard.tsx
- src/client/components/GlobalItemCard.tsx
- src/client/components/CandidateCard.tsx
- src/client/components/CandidateListItem.tsx
- src/client/components/ImageUpload.tsx
- src/client/components/ComparisonTable.tsx
- src/client/components/CatalogSearchOverlay.tsx
- src/client/components/LinkToGlobalItem.tsx
- src/client/routes/items/$itemId.tsx
- src/client/routes/global-items/$globalItemId.tsx
- src/client/routes/global-items/index.tsx
- src/client/routes/threads/$threadId/candidates/$candidateId.tsx
metrics:
tasks: 13
commits: 4
files-changed: 13
---
# Plan 29-02 Summary: GearImage Component + Surface Updates
## What was built
- Created `GearImage` shared component with three modes: contain (default), cover (tiny thumbnails), and crop (CSS transform)
- Created `imageContainerBg()` helper for consistent dominant color backgrounds
- Updated all 12 gear image surfaces to use GearImage
- Default rendering now uses `object-contain` instead of `object-cover`
- Parent containers use dominant color background for letterbox/pillarbox fill
- LinkToGlobalItem uses `cover` mode for 32px thumbnails (intentional exception)
## Commits
| Task | Commit | Description |
|------|--------|-------------|
| 1 | 06d3984 | Create GearImage component |
| 2-3 | 2865e65 | Update ItemCard and GlobalItemCard |
| 4-5 | 05c0918 | Update CandidateCard and CandidateListItem |
| 6-8 | 91846b5 | Update ComparisonTable, CatalogSearchOverlay, ImageUpload |
| 9-13 | 66d9c41 | Update detail pages and LinkToGlobalItem |
| lint | 9636033 | Lint fixes for formatting and unused parameter |
## Deviations
None.
## Self-Check: PASSED
- GearImage component exists: YES
- object-cover removed from all gear surfaces: YES (only remains in GearImage internal, ProfileSection avatar, users avatar)
- Build passes: YES
- Lint passes: YES

View File

@@ -0,0 +1,361 @@
---
phase: 29
plan: 03
type: fullstack
wave: 2
depends_on: [01, 02]
files_modified:
- src/client/components/ImageCropEditor.tsx
- src/client/components/ImageUpload.tsx
- src/client/routes/items/$itemId.tsx
- src/client/routes/global-items/$globalItemId.tsx
- src/client/routes/threads/$threadId/candidates/$candidateId.tsx
- src/client/hooks/useItems.ts
- package.json
autonomous: true
requirements: []
---
<objective>
Implement the zoom+pan image framing editor using react-easy-crop. Users can adjust image framing during upload (ImageUpload) and from detail pages (item, global item, candidate). Crop settings (zoom, x, y) persist to the database via existing CRUD endpoints.
</objective>
<tasks>
### Task 1: Install react-easy-crop
<task type="command">
<action>
Run `bun add react-easy-crop` to install the crop editor library.
</action>
<verify>
<automated>grep '"react-easy-crop"' package.json && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- package.json contains `"react-easy-crop"` in dependencies
</acceptance_criteria>
</task>
### Task 2: Create ImageCropEditor component
<task type="code">
<read_first>
- src/client/components/ImageUpload.tsx
- src/client/components/GearImage.tsx
</read_first>
<action>
Create `src/client/components/ImageCropEditor.tsx`:
```tsx
import { useCallback, useState } from "react";
import Cropper from "react-easy-crop";
import type { Area, Point } from "react-easy-crop";
interface CropResult {
zoom: number;
x: number;
y: number;
}
interface ImageCropEditorProps {
imageUrl: string;
dominantColor?: string | null;
initialZoom?: number;
initialX?: number;
initialY?: number;
aspect?: number;
onSave: (result: CropResult) => void;
onCancel: () => void;
}
export function ImageCropEditor({
imageUrl,
dominantColor,
initialZoom = 1,
initialX = 0,
initialY = 0,
aspect = 4 / 3,
onSave,
onCancel,
}: ImageCropEditorProps) {
const [crop, setCrop] = useState<Point>({ x: initialX, y: initialY });
const [zoom, setZoom] = useState(initialZoom);
const onCropComplete = useCallback((_croppedArea: Area, _croppedAreaPixels: Area) => {
// We use the crop/zoom state directly, not the callback values
}, []);
function handleSave() {
onSave({
zoom,
x: crop.x,
y: crop.y,
});
}
return (
<div className="flex flex-col gap-4">
{/* Crop area */}
<div className="relative w-full" style={{ aspectRatio: `${aspect}` }}>
<Cropper
image={imageUrl}
crop={crop}
zoom={zoom}
aspect={aspect}
onCropChange={setCrop}
onZoomChange={setZoom}
onCropComplete={onCropComplete}
minZoom={1}
maxZoom={3}
style={{
containerStyle: {
backgroundColor: dominantColor || "#f3f4f6",
borderRadius: "0.75rem",
},
}}
objectFit="contain"
/>
</div>
{/* Zoom slider */}
<div className="flex items-center gap-3 px-1">
<label htmlFor="crop-zoom" className="sr-only">Zoom</label>
<svg className="w-4 h-4 text-gray-400 shrink-0" fill="none" stroke="currentColor" viewBox="0 0 24 24" strokeWidth={1.5}>
<circle cx="11" cy="11" r="8" />
<path d="m21 21-4.3-4.3" />
<path d="M8 11h6" />
</svg>
<input
id="crop-zoom"
type="range"
min={1}
max={3}
step={0.01}
value={zoom}
onChange={(e) => setZoom(Number(e.target.value))}
className="flex-1 h-1.5 bg-gray-200 rounded-full appearance-none cursor-pointer accent-gray-900"
/>
<svg className="w-4 h-4 text-gray-400 shrink-0" fill="none" stroke="currentColor" viewBox="0 0 24 24" strokeWidth={1.5}>
<circle cx="11" cy="11" r="8" />
<path d="m21 21-4.3-4.3" />
<path d="M8 11h6M11 8v6" />
</svg>
</div>
{/* Action buttons */}
<div className="flex justify-between">
<button
type="button"
onClick={onCancel}
className="px-4 py-2 text-sm font-medium text-gray-600 hover:text-gray-900 transition-colors"
>
Cancel
</button>
<button
type="button"
onClick={handleSave}
className="px-4 py-2 text-sm font-semibold text-white bg-gray-900 hover:bg-gray-800 rounded-lg transition-colors"
>
Save framing
</button>
</div>
</div>
);
}
```
The component:
- Uses react-easy-crop `Cropper` with `objectFit="contain"` so images fit within the frame
- Min zoom 1.0 (fit-within), max zoom 3.0
- Zoom slider between zoom-out and zoom-in icons
- "Cancel" (ghost) and "Save framing" (primary) buttons
- Returns `{ zoom, x, y }` on save
- Background color uses dominant color from the image
</action>
<verify>
<automated>test -f src/client/components/ImageCropEditor.tsx && grep "react-easy-crop" src/client/components/ImageCropEditor.tsx && grep "Save framing" src/client/components/ImageCropEditor.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- `src/client/components/ImageCropEditor.tsx` exists
- Imports `Cropper` from `react-easy-crop`
- `objectFit="contain"` set on Cropper
- Min zoom 1, max zoom 3
- Zoom slider with range input
- "Cancel" button calls `onCancel`
- "Save framing" button calls `onSave` with `{ zoom, x, y }`
- Dominant color used as background
</acceptance_criteria>
</task>
### Task 3: Add crop editor to ImageUpload
<task type="code">
<read_first>
- src/client/components/ImageUpload.tsx
- src/client/components/ImageCropEditor.tsx
</read_first>
<action>
Update `src/client/components/ImageUpload.tsx`:
1. Add `onCropChange?: (crop: { zoom: number; x: number; y: number }) => void` to `ImageUploadProps`
2. Add `cropZoom?: number | null`, `cropX?: number | null`, `cropY?: number | null` to props
3. Add state: `const [showCropEditor, setShowCropEditor] = useState(false);`
4. After successful upload (`onChange(result.filename)`), set `setShowCropEditor(true)`
5. When crop editor is visible, replace the image preview area with the `ImageCropEditor` component
6. On save: call `onCropChange?.({ zoom, x, y })` and `setShowCropEditor(false)`
7. On cancel: `setShowCropEditor(false)`
8. Import `ImageCropEditor`
The crop editor appears inline in the same container where the preview image normally shows, replacing the static preview temporarily.
</action>
<verify>
<automated>grep "ImageCropEditor" src/client/components/ImageUpload.tsx && grep "showCropEditor" src/client/components/ImageUpload.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- ImageUpload imports and conditionally renders ImageCropEditor
- Editor appears after successful upload
- `onCropChange` callback fires with zoom/x/y values
- Editor can be dismissed via Cancel
- Save triggers crop change callback
</acceptance_criteria>
</task>
### Task 4: Add "Adjust framing" to item detail page
<task type="code">
<read_first>
- src/client/routes/items/$itemId.tsx
- src/client/components/ImageCropEditor.tsx
- src/client/hooks/useItems.ts
</read_first>
<action>
In `src/client/routes/items/$itemId.tsx`:
1. Import `ImageCropEditor`
2. Add state: `const [editingCrop, setEditingCrop] = useState(false)`
3. Below the image area (after the `aspect-[4/3]` div), add an "Adjust framing" button:
```tsx
{item.imageUrl && (
<button
type="button"
onClick={() => setEditingCrop(true)}
className="mt-2 text-sm text-gray-500 hover:text-gray-700 transition-colors"
>
Adjust framing
</button>
)}
```
4. When `editingCrop` is true, replace the GearImage area with `ImageCropEditor`:
```tsx
{editingCrop ? (
<ImageCropEditor
imageUrl={item.imageUrl}
dominantColor={item.dominantColor}
initialZoom={item.cropZoom ?? 1}
initialX={item.cropX ?? 0}
initialY={item.cropY ?? 0}
aspect={4 / 3}
onSave={async (crop) => {
await updateItem({ id: item.id, cropZoom: crop.zoom, cropX: crop.x, cropY: crop.y });
setEditingCrop(false);
}}
onCancel={() => setEditingCrop(false)}
/>
) : (
/* existing GearImage rendering */
)}
```
5. Use the existing `useUpdateItem` mutation to persist crop values
</action>
<verify>
<automated>grep "Adjust framing" src/client/routes/items/\$itemId.tsx && grep "ImageCropEditor" src/client/routes/items/\$itemId.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- Item detail page shows "Adjust framing" button when image exists
- Clicking button shows ImageCropEditor inline
- Save persists crop values via updateItem mutation
- Cancel returns to normal image view
</acceptance_criteria>
</task>
### Task 5: Add "Adjust framing" to global item detail page
<task type="code">
<read_first>
- src/client/routes/global-items/$globalItemId.tsx
- src/client/components/ImageCropEditor.tsx
</read_first>
<action>
Same pattern as Task 4 but for global item detail:
1. Import ImageCropEditor and useState
2. Add "Adjust framing" button below image
3. Toggle between GearImage and ImageCropEditor
4. Use `aspect={16/9}` to match the global item detail page aspect ratio
5. Use the appropriate mutation to persist crop values for global items
</action>
<verify>
<automated>grep "Adjust framing" src/client/routes/global-items/\$globalItemId.tsx && grep "ImageCropEditor" src/client/routes/global-items/\$globalItemId.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- Global item detail shows "Adjust framing" button
- ImageCropEditor uses aspect 16/9
- Crop values persist via mutation
</acceptance_criteria>
</task>
### Task 6: Add "Adjust framing" to candidate detail page
<task type="code">
<read_first>
- src/client/routes/threads/$threadId/candidates/$candidateId.tsx
- src/client/components/ImageCropEditor.tsx
</read_first>
<action>
Same pattern as Task 4/5 but for candidate detail:
1. Import ImageCropEditor and useState
2. Add "Adjust framing" button below image
3. Toggle between GearImage and ImageCropEditor
4. Use `aspect={16/9}` to match the candidate detail page aspect ratio
5. Use candidate update mutation to persist crop values
</action>
<verify>
<automated>grep "Adjust framing" src/client/routes/threads/\$threadId/candidates/\$candidateId.tsx && grep "ImageCropEditor" src/client/routes/threads/\$threadId/candidates/\$candidateId.tsx && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- Candidate detail shows "Adjust framing" button
- ImageCropEditor uses aspect 16/9
- Crop values persist via candidate update mutation
</acceptance_criteria>
</task>
</tasks>
<verification>
1. `bun run lint` passes
2. `bun run build` passes
3. ImageCropEditor component renders react-easy-crop Cropper
4. "Adjust framing" button appears on all 3 detail pages when image exists
5. Crop values round-trip: set in editor → save → reload page → image renders with saved crop
</verification>
<success_criteria>
- react-easy-crop installed
- ImageCropEditor component created with zoom slider and save/cancel actions
- ImageUpload shows crop editor after upload
- Item, global item, and candidate detail pages have "Adjust framing" button
- Crop values persist through CRUD endpoints
- Crop values render correctly via GearImage component
</success_criteria>
<threat_model>
| Threat | Severity | Mitigation |
|--------|----------|------------|
| Crop values outside expected range | Low | Server-side validation via Zod schema (nullable number) |
| react-easy-crop supply chain | Low | MIT license, 1M+ weekly downloads, actively maintained |
</threat_model>
<must_haves>
- [ ] react-easy-crop installed
- [ ] ImageCropEditor component with zoom slider
- [ ] Crop editor in ImageUpload (post-upload)
- [ ] "Adjust framing" on item detail page
- [ ] "Adjust framing" on global item detail page
- [ ] "Adjust framing" on candidate detail page
- [ ] Crop values persist to database
</must_haves>

View File

@@ -0,0 +1,49 @@
---
phase: 29
plan: 03
subsystem: fullstack
tags: [crop-editor, react-easy-crop, ui]
key-files:
created:
- src/client/components/ImageCropEditor.tsx
modified:
- src/client/components/ImageUpload.tsx
- src/client/routes/items/$itemId.tsx
- src/client/routes/threads/$threadId/candidates/$candidateId.tsx
- package.json
metrics:
tasks: 6
commits: 4
files-changed: 6
---
# Plan 29-03 Summary: Zoom+Pan Image Framing Editor
## What was built
- Installed react-easy-crop library
- Created ImageCropEditor component with zoom slider (1x-3x), save/cancel buttons, dominant color background
- Integrated crop editor into ImageUpload (shows after upload when onCropChange provided)
- Added "Adjust framing" button to item detail page with inline crop editor
- Added "Adjust framing" button to candidate detail page with inline crop editor
- Global item detail skipped (no update endpoint exists for global items)
## Commits
| Task | Commit | Description |
|------|--------|-------------|
| 1 | 6f4fd78 | Install react-easy-crop |
| 2 | 23f62fd | Create ImageCropEditor component |
| 3 | 78a097c | Integrate crop editor into ImageUpload |
| 4-6 | a18b9d3 | Add crop editor to item and candidate detail pages |
## Deviations
- Task 5 (global item detail): Skipped "Adjust framing" button because no PUT endpoint exists for global items. Crop fields are in the schema but cannot be updated from the frontend for global items.
## Self-Check: PASSED
- react-easy-crop installed: YES
- ImageCropEditor exists: YES
- ImageUpload has crop editor: YES
- Item detail has "Adjust framing": YES
- Candidate detail has "Adjust framing": YES
- Build passes: YES
- Lint passes: YES

View File

@@ -0,0 +1,271 @@
---
phase: 29
plan: 04
type: backend
wave: 2
depends_on: [01]
files_modified:
- scripts/backfill-dominant-colors.ts
autonomous: true
requirements: []
---
<objective>
Create a one-time backfill script that processes all existing images in the database to extract and store their dominant color. Handles items, globalItems, and threadCandidates with imageFilename, plus globalItems with external imageUrl.
</objective>
<tasks>
### Task 1: Create backfill script
<task type="code">
<read_first>
- src/db/schema.ts
- src/server/services/storage.service.ts
- src/server/services/image.service.ts
</read_first>
<action>
Create `scripts/backfill-dominant-colors.ts`:
```ts
/**
* Backfill dominant colors for all existing images.
* Run with: bun run scripts/backfill-dominant-colors.ts
*
* Idempotent — skips records that already have dominantColor set.
* Processes in batches of 10 concurrent requests.
*/
import { GetObjectCommand, S3Client } from "@aws-sdk/client-s3";
import { drizzle } from "drizzle-orm/postgres-js";
import { isNull } from "drizzle-orm";
import postgres from "postgres";
import sharp from "sharp";
import * as schema from "../src/db/schema";
const DATABASE_URL = process.env.DATABASE_URL;
if (!DATABASE_URL) throw new Error("DATABASE_URL required");
const client = postgres(DATABASE_URL);
const db = drizzle(client, { schema });
const s3 = new S3Client({
endpoint: process.env.S3_ENDPOINT,
region: process.env.S3_REGION ?? "us-east-1",
credentials: {
accessKeyId: process.env.S3_ACCESS_KEY!,
secretAccessKey: process.env.S3_SECRET_KEY!,
},
forcePathStyle: true,
});
const bucket = process.env.S3_BUCKET ?? "gearbox-images";
async function extractColor(buffer: Buffer): Promise<string | null> {
try {
const { data } = await sharp(buffer).resize(1, 1).raw().toBuffer({ resolveWithObject: true });
return `#${data[0].toString(16).padStart(2, "0")}${data[1].toString(16).padStart(2, "0")}${data[2].toString(16).padStart(2, "0")}`;
} catch {
return null;
}
}
async function fetchFromS3(filename: string): Promise<Buffer | null> {
try {
const response = await s3.send(new GetObjectCommand({ Bucket: bucket, Key: filename }));
const bytes = await response.Body?.transformToByteArray();
return bytes ? Buffer.from(bytes) : null;
} catch {
return null;
}
}
async function fetchFromUrl(url: string): Promise<Buffer | null> {
try {
const response = await fetch(url, { signal: AbortSignal.timeout(10000) });
if (!response.ok) return null;
return Buffer.from(await response.arrayBuffer());
} catch {
return null;
}
}
async function processBatch<T extends { id: number }>(
items: T[],
getBuffer: (item: T) => Promise<Buffer | null>,
updateFn: (id: number, color: string) => Promise<void>,
label: string,
) {
const BATCH_SIZE = 10;
let processed = 0;
let updated = 0;
let failed = 0;
for (let i = 0; i < items.length; i += BATCH_SIZE) {
const batch = items.slice(i, i + BATCH_SIZE);
const results = await Promise.allSettled(
batch.map(async (item) => {
const buffer = await getBuffer(item);
if (!buffer) { failed++; return; }
const color = await extractColor(buffer);
if (!color) { failed++; return; }
await updateFn(item.id, color);
updated++;
})
);
processed += batch.length;
console.log(` ${label}: ${processed}/${items.length} processed, ${updated} updated, ${failed} failed`);
}
}
async function main() {
console.log("=== Backfill Dominant Colors ===\n");
// Items with imageFilename but no dominantColor
const { eq, and, isNotNull } = await import("drizzle-orm");
const itemsToProcess = await db
.select({ id: schema.items.id, imageFilename: schema.items.imageFilename })
.from(schema.items)
.where(and(isNotNull(schema.items.imageFilename), isNull(schema.items.dominantColor)));
console.log(`Items: ${itemsToProcess.length} need processing`);
await processBatch(
itemsToProcess as { id: number; imageFilename: string }[],
(item) => fetchFromS3(item.imageFilename),
async (id, color) => {
const { eq } = await import("drizzle-orm");
await db.update(schema.items).set({ dominantColor: color }).where(eq(schema.items.id, id));
},
"Items",
);
// GlobalItems with imageSourceUrl (external URLs stored in S3)
const globalWithFile = await db
.select({ id: schema.globalItems.id, imageSourceUrl: schema.globalItems.imageSourceUrl })
.from(schema.globalItems)
.where(and(isNotNull(schema.globalItems.imageSourceUrl), isNull(schema.globalItems.dominantColor)));
console.log(`\nGlobal Items (with source URL): ${globalWithFile.length} need processing`);
await processBatch(
globalWithFile as { id: number; imageSourceUrl: string }[],
(item) => fetchFromUrl(item.imageSourceUrl),
async (id, color) => {
const { eq } = await import("drizzle-orm");
await db.update(schema.globalItems).set({ dominantColor: color }).where(eq(schema.globalItems.id, id));
},
"Global Items",
);
// GlobalItems with imageUrl (direct URLs)
const globalWithUrl = await db
.select({ id: schema.globalItems.id, imageUrl: schema.globalItems.imageUrl })
.from(schema.globalItems)
.where(and(isNotNull(schema.globalItems.imageUrl), isNull(schema.globalItems.dominantColor)));
console.log(`\nGlobal Items (with image URL): ${globalWithUrl.length} need processing`);
await processBatch(
globalWithUrl as { id: number; imageUrl: string }[],
(item) => fetchFromUrl(item.imageUrl),
async (id, color) => {
const { eq } = await import("drizzle-orm");
await db.update(schema.globalItems).set({ dominantColor: color }).where(eq(schema.globalItems.id, id));
},
"Global Items (URL)",
);
// Thread candidates
const candidatesToProcess = await db
.select({ id: schema.threadCandidates.id, imageFilename: schema.threadCandidates.imageFilename })
.from(schema.threadCandidates)
.where(and(isNotNull(schema.threadCandidates.imageFilename), isNull(schema.threadCandidates.dominantColor)));
console.log(`\nCandidates: ${candidatesToProcess.length} need processing`);
await processBatch(
candidatesToProcess as { id: number; imageFilename: string }[],
(item) => fetchFromS3(item.imageFilename),
async (id, color) => {
const { eq } = await import("drizzle-orm");
await db.update(schema.threadCandidates).set({ dominantColor: color }).where(eq(schema.threadCandidates.id, id));
},
"Candidates",
);
console.log("\n=== Backfill Complete ===");
process.exit(0);
}
main().catch((err) => {
console.error("Backfill failed:", err);
process.exit(1);
});
```
Note: The exact import patterns for drizzle-orm may need adjustment based on the project's existing database connection setup. Check `src/db/` for the actual connection pattern used and replicate it in the script.
</action>
<verify>
<automated>test -f scripts/backfill-dominant-colors.ts && grep "extractColor" scripts/backfill-dominant-colors.ts && grep "processBatch" scripts/backfill-dominant-colors.ts && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- `scripts/backfill-dominant-colors.ts` exists
- Script queries items, globalItems, threadCandidates with images but no dominantColor
- Processes in batches of 10 concurrent
- Extracts dominant color via Sharp resize(1,1)
- Updates database records with extracted color
- Skips records that already have dominantColor (idempotent)
- Logs progress: `Items: 45/123 processed, 42 updated, 3 failed`
- Handles errors gracefully (skips failed images, logs them)
- Exits with 0 on success, 1 on fatal error
</acceptance_criteria>
</task>
### Task 2: Add npm script for backfill
<task type="code">
<read_first>
- package.json
</read_first>
<action>
Add to `scripts` section in `package.json`:
```json
"backfill:colors": "bun run scripts/backfill-dominant-colors.ts"
```
</action>
<verify>
<automated>grep "backfill:colors" package.json && echo "PASS" || echo "FAIL"</automated>
</verify>
<acceptance_criteria>
- package.json contains `"backfill:colors"` script
- Script points to `scripts/backfill-dominant-colors.ts`
</acceptance_criteria>
</task>
</tasks>
<verification>
1. `bun run lint` passes (script follows project conventions)
2. Script is syntactically valid: `bun run scripts/backfill-dominant-colors.ts --help` or `bun check scripts/backfill-dominant-colors.ts`
3. Script handles missing S3 credentials gracefully (error message, not crash)
</verification>
<success_criteria>
- Backfill script exists and processes all 3 tables
- Script is idempotent (safe to re-run)
- Batch processing limits concurrency to 10
- Progress logging shows processing status
- npm script shortcut available
</success_criteria>
<threat_model>
| Threat | Severity | Mitigation |
|--------|----------|------------|
| S3 credential exposure in script | Low | Uses env vars from process.env, no hardcoded credentials |
| SSRF via globalItems imageUrl | Medium | Script only processes URLs already stored in the database (previously validated on ingestion); fetch has 10s timeout |
| Database overload from bulk updates | Low | Batch size of 10 limits concurrent DB writes |
</threat_model>
<must_haves>
- [ ] Backfill script at scripts/backfill-dominant-colors.ts
- [ ] Processes items, globalItems, threadCandidates
- [ ] Idempotent (skips existing dominantColor)
- [ ] Batch processing with concurrency limit
- [ ] Progress logging
- [ ] npm script shortcut
</must_haves>

View File

@@ -0,0 +1,44 @@
---
phase: 29
plan: 04
subsystem: backend
tags: [migration, backfill, sharp]
key-files:
created:
- scripts/backfill-dominant-colors.ts
modified:
- package.json
metrics:
tasks: 2
commits: 1
files-changed: 2
---
# Plan 29-04 Summary: Backfill Migration Script
## What was built
- Created `scripts/backfill-dominant-colors.ts` backfill script
- Processes items, globalItems (source URLs + image URLs), and threadCandidates
- Extracts dominant color via Sharp 1x1 resize
- Idempotent: skips records with existing dominantColor
- Batch processing with 10 concurrent requests
- Progress logging per table
- Added `backfill:colors` npm script
## Commits
| Task | Commit | Description |
|------|--------|-------------|
| 1-2 | 6509b33 | Create backfill script and npm shortcut |
## Deviations
None.
## Self-Check: PASSED
- Script exists: YES
- Processes all 3 tables: YES
- Idempotent (isNull check): YES
- Batch size 10: YES
- Progress logging: YES
- npm script exists: YES
- Lint passes: YES

View File

@@ -0,0 +1,169 @@
---
phase: 29-image-presentation
plan: 05
type: execute
wave: 1
depends_on: []
files_modified:
- src/client/components/ImageUpload.tsx
autonomous: true
gap_closure: true
requirements: []
must_haves:
truths:
- "After cropping in the upload crop editor, the GearImage preview immediately reflects the crop values without needing to save the form"
artifacts:
- path: "src/client/components/ImageUpload.tsx"
provides: "Local crop state that feeds GearImage preview"
contains: "cropZoom"
key_links:
- from: "ImageCropEditor onSave"
to: "GearImage cropZoom/cropX/cropY props"
via: "local state in ImageUpload"
pattern: "localCrop"
---
<objective>
Fix cropped image preview not updating immediately after cropping in edit mode.
Purpose: When a user crops an image via the ImageCropEditor inside ImageUpload, the preview should reflect the crop immediately — not only after form save and query refetch.
Output: ImageUpload component with local crop state that feeds into GearImage preview props.
</objective>
<execution_context>
@$HOME/.claude/get-shit-done/workflows/execute-plan.md
@$HOME/.claude/get-shit-done/templates/summary.md
</execution_context>
<context>
@.planning/PROJECT.md
@.planning/ROADMAP.md
@.planning/STATE.md
@src/client/components/ImageUpload.tsx
@src/client/components/GearImage.tsx
@src/client/components/ImageCropEditor.tsx
<interfaces>
<!-- GearImage accepts optional crop props -->
From src/client/components/GearImage.tsx:
```typescript
interface GearImageProps {
src: string;
alt: string;
dominantColor?: string | null;
cropZoom?: number | null;
cropX?: number | null;
cropY?: number | null;
className?: string;
cover?: boolean;
}
```
<!-- ImageCropEditor returns CropResult on save -->
From src/client/components/ImageCropEditor.tsx:
```typescript
interface CropResult {
zoom: number;
x: number;
y: number;
}
// onSave: (result: CropResult) => void;
```
<!-- ImageUpload current props -->
From src/client/components/ImageUpload.tsx:
```typescript
interface ImageUploadProps {
value: string | null;
imageUrl?: string | null;
dominantColor?: string | null;
onChange: (filename: string | null, dominantColor?: string | null) => void;
onCropChange?: (crop: { zoom: number; x: number; y: number }) => void;
}
```
</interfaces>
</context>
<tasks>
<task type="auto">
<name>Task 1: Add local crop state to ImageUpload and wire to GearImage preview</name>
<files>src/client/components/ImageUpload.tsx</files>
<action>
In ImageUpload.tsx, make these changes:
1. Add a local crop state to track the most recent crop values:
```typescript
const [localCrop, setLocalCrop] = useState<{ zoom: number; x: number; y: number } | null>(null);
```
2. In the ImageCropEditor onSave handler (around line 88-91), update localCrop before calling the parent onCropChange:
```typescript
onSave={(result) => {
setLocalCrop(result);
onCropChange(result);
setShowCropEditor(false);
}}
```
3. In the GearImage render (around line 110-114), pass localCrop values as props:
```typescript
<GearImage
src={displayUrl}
alt="Item"
dominantColor={dominantColor}
cropZoom={localCrop?.zoom}
cropX={localCrop?.x}
cropY={localCrop?.y}
/>
```
4. When the image is removed (handleRemove), also clear localCrop:
```typescript
function handleRemove(e: React.MouseEvent) {
e.stopPropagation();
setLocalPreview(null);
setLocalCrop(null);
onChange(null);
}
```
This ensures the GearImage preview immediately reflects crop adjustments without waiting for a server round-trip and query refetch.
</action>
<verify>
<automated>cd /home/jlmak/Projects/jlmak/GearBox && bunx tsc --noEmit --pretty 2>&1 | head -30</automated>
</verify>
<done>After using the crop editor on an uploaded image, the GearImage preview in ImageUpload immediately shows the cropped framing. Removing the image clears both the preview and crop state.</done>
</task>
</tasks>
<threat_model>
## Trust Boundaries
No new trust boundaries — this is a client-side-only state management fix within existing components.
## STRIDE Threat Register
| Threat ID | Category | Component | Disposition | Mitigation Plan |
|-----------|----------|-----------|-------------|-----------------|
| T-29-05-01 | T (Tampering) | localCrop state | accept | Client-side display only; actual crop values are persisted via existing server mutation in parent component |
</threat_model>
<verification>
1. TypeScript compiles without errors
2. Manual: Open item in edit mode, upload image, crop it, verify preview shows crop immediately (without clicking Save)
3. Manual: Open existing item in edit mode, click crop button, adjust, save framing — preview updates immediately
</verification>
<success_criteria>
- Cropped image preview updates in edit state immediately after cropping, without needing to save the form
- No TypeScript errors
- Image removal clears crop state
</success_criteria>
<output>
After completion, create `.planning/phases/29-image-presentation/29-05-SUMMARY.md`
</output>

View File

@@ -0,0 +1,34 @@
---
phase: 29-image-presentation
plan: 05
status: complete
gap_closure: true
started: 2026-04-13T12:00:00Z
completed: 2026-04-13T12:10:00Z
---
## Summary
Fixed cropped image preview not updating immediately in edit mode. Added `localCrop` state to `ImageUpload` that captures crop values from `ImageCropEditor` and passes them to `GearImage` as props. Previously, the preview only reflected crop settings after saving the form and refetching from the server.
## Accomplishments
- Added `localCrop` useState to ImageUpload for immediate crop feedback
- Wired ImageCropEditor onSave to set localCrop before forwarding to parent
- Passed localCrop values (cropZoom, cropX, cropY) to GearImage preview
- Clear localCrop on image removal to prevent stale state
## Key Files
### Modified
- `src/client/components/ImageUpload.tsx` — local crop state + GearImage prop wiring
## Self-Check: PASSED
- TypeScript compiles without errors (no new errors in ImageUpload.tsx)
- Local crop state correctly flows: ImageCropEditor → localCrop → GearImage props
- Image removal clears both preview and crop state
## Deviations
None — implemented exactly as planned.

View File

@@ -0,0 +1,111 @@
# Phase 29: Image Presentation - Context
**Gathered:** 2026-04-12
**Status:** Ready for planning
<domain>
## Phase Boundary
Replace hard-crop image display (`object-cover`) with fit-within framing across all image surfaces. Images are scaled to fit inside the aspect ratio container with adaptive dominant-color background fill. Users can adjust image framing via a zoom+pan editor available during upload and from item detail pages.
</domain>
<decisions>
## Implementation Decisions
### Fit Strategy & Fill Treatment
- **D-01:** Replace `object-cover` with `object-contain` across all image surfaces — images scale to fit inside the frame without cropping.
- **D-02:** Fill remaining space with the image's **dominant color** extracted server-side. This creates an adaptive background that makes the image feel intentional rather than letterboxed.
- **D-03:** Dominant color extraction happens **server-side on upload**, stored as a field (e.g., `dominantColor: '#abc123'`) on the item/globalItem record. No client-side computation.
- **D-04:** Existing images need a **backfill migration** — process all existing images to extract and store their dominant color.
### Aspect Ratio Policy
- **D-05:** Claude's discretion on whether to keep different ratios (4:3 cards, 16:9 global detail) or unify. Choose what looks best for gear product images.
### Scope of Changes
- **D-06:** Apply the new presentation to **every surface where images appear**: ItemCard, GlobalItemCard, CandidateCard, CandidateListItem, item detail pages, global item detail pages, comparison table, ImageUpload preview, catalog search overlay. Full consistency — no exceptions.
### User Crop Positioning
- **D-07:** Implement a **zoom + pan editor** — users can zoom in/out and drag to position the image within the frame.
- **D-08:** Editor available in **two places**: during image upload (ImageUpload component) and from item detail/edit pages (re-adjustable anytime).
- **D-09:** Crop settings stored **per-image** (not per-context). One set of zoom/pan coordinates applied everywhere the image appears. Store as fields on the image record (e.g., `cropZoom`, `cropX`, `cropY`).
- **D-10:** When crop settings exist, they override the default `object-contain` behavior — the image is displayed at the user-specified zoom and position within the frame, with dominant color fill for any remaining space.
### Claude's Discretion
- Zoom+pan editor component implementation (library vs custom)
- Dominant color extraction algorithm (Sharp, node-vibrant, or similar)
- DB schema for crop fields (on items table, globalItems table, or a separate image_settings table)
- Backfill migration strategy (background job, on-demand, or one-time script)
- Whether to generate server-side thumbnails for performance or keep CSS-only rendering
</decisions>
<canonical_refs>
## Canonical References
**Downstream agents MUST read these before planning or implementing.**
### Image Display Components (all need updating)
- `src/client/components/ItemCard.tsx``aspect-[4/3]` + `object-cover` (line ~164-170)
- `src/client/components/GlobalItemCard.tsx``aspect-[4/3]` + `object-cover` (line ~31-37)
- `src/client/components/CandidateCard.tsx` — uses `object-cover` pattern
- `src/client/components/CandidateListItem.tsx` — uses `object-cover` pattern
- `src/client/components/ImageUpload.tsx``aspect-[4/3]` + `object-cover` (line ~72-79)
- `src/client/components/ComparisonTable.tsx` — uses `object-cover` pattern
- `src/client/components/LinkToGlobalItem.tsx` — uses `object-cover` pattern
- `src/client/components/CatalogSearchOverlay.tsx` — uses `object-cover` pattern
### Image Detail Pages
- `src/client/routes/items/$itemId.tsx``aspect-[4/3]` + `object-cover` (line ~245-250)
- `src/client/routes/global-items/$globalItemId.tsx``aspect-[16/9]` + `object-cover` (line ~65-70)
- `src/client/routes/threads/$threadId/candidates/$candidateId.tsx` — uses `object-cover`
### Server-Side Image Handling
- `src/server/routes/images.ts` — Image upload endpoint
- `src/server/services/storage.service.ts` — S3/MinIO storage service
### Database Schema
- `src/db/schema.ts` — Items, globalItems tables (need dominantColor + crop fields)
</canonical_refs>
<code_context>
## Existing Code Insights
### Reusable Assets
- `ImageUpload` component — upload preview with aspect ratio container. Will host the zoom+pan editor.
- S3/MinIO storage pipeline — images uploaded via `/api/images`, stored in MinIO, served from `/uploads/`.
- Consistent `aspect-[4/3]` pattern across cards — refactoring can target this pattern systematically.
### Established Patterns
- All image containers use `aspect-[ratio]` + overflow-hidden + `object-cover` on the `<img>`. Switching to `object-contain` with background color is a targeted CSS change per component.
- No existing image processing on upload — adding dominant color extraction introduces a new server-side processing step.
### Integration Points
- `src/server/routes/images.ts` — Add dominant color extraction after upload
- `src/db/schema.ts` — Add `dominantColor` field to items and globalItems
- All card/detail components — Update image rendering to use contain + dominant color bg
- `ImageUpload` component — Add zoom+pan editor overlay
</code_context>
<specifics>
## Specific Ideas
- The adaptive dominant-color background should make images feel like they belong in the frame, not like they're floating in empty space.
- The zoom+pan editor should be intuitive — drag to move, pinch/scroll to zoom. Not a complex crop tool.
- Existing images all need backfill for dominant color — this affects catalog items seeded by MCP agents too.
</specifics>
<deferred>
## Deferred Ideas
None — discussion stayed within phase scope
</deferred>
---
*Phase: 29-image-presentation*
*Context gathered: 2026-04-12*

View File

@@ -0,0 +1,94 @@
# Phase 29: Image Presentation - Discussion Log
> **Audit trail only.** Do not use as input to planning, research, or execution agents.
> Decisions are captured in CONTEXT.md — this log preserves the alternatives considered.
**Date:** 2026-04-12
**Phase:** 29-image-presentation
**Areas discussed:** Fit strategy & fill treatment, Aspect ratio policy, Scope of changes, User crop positioning
---
## Fit Strategy & Fill Treatment
| Option | Description | Selected |
|--------|-------------|----------|
| Blurred background | Scale to fit, fill with blurred zoomed version of same image | |
| Solid background | Scale to fit, fill with solid color (white/gray) | |
| Adaptive background | Extract dominant color from image, use as fill | ✓ |
**User's choice:** Adaptive background
| Option | Description | Selected |
|--------|-------------|----------|
| Client-side on load | Canvas pixel sampling when image loads | |
| Server-side on upload | Extract once on upload, store in DB | ✓ |
| You decide | Claude picks | |
**User's choice:** Server-side on upload
---
## Aspect Ratio Policy
| Option | Description | Selected |
|--------|-------------|----------|
| Keep different ratios | 4:3 for cards, 16:9 for detail heroes | |
| Unify to 4:3 | Same everywhere | |
| Unify to 16:9 | Wider everywhere | |
| You decide | Claude picks based on gear images | ✓ |
**User's choice:** You decide (Claude's discretion)
---
## Scope of Changes
| Option | Description | Selected |
|--------|-------------|----------|
| Everywhere images appear | All 15+ surfaces — full consistency | ✓ |
| Cards and detail pages only | Main surfaces, skip comparison/upload | |
| You decide | Claude picks | |
**User's choice:** Everywhere images appear
---
## User Crop Positioning
| Option | Description | Selected |
|--------|-------------|----------|
| Focal point picker | Click to set focal point, x/y coordinates | |
| Zoom + pan editor | Zoom in/out and drag to position | ✓ |
| No user control | Skip for now, add later | |
**User's choice:** Zoom + pan editor
| Option | Description | Selected |
|--------|-------------|----------|
| On upload preview | Editor during upload only | |
| On item edit/detail | Editor from item detail page | |
| Both | Available during upload AND from item detail | ✓ |
**User's choice:** Both
| Option | Description | Selected |
|--------|-------------|----------|
| Per-image (one crop for all views) | Same framing everywhere | ✓ |
| Per-context | Different crop for card vs detail | |
**User's choice:** Per-image
---
## Claude's Discretion
- Aspect ratio policy (unify or keep different)
- Zoom+pan editor implementation (library vs custom)
- Dominant color extraction library
- DB schema design for crop and color fields
- Backfill migration strategy
## Deferred Ideas
None — discussion stayed within phase scope

View File

@@ -0,0 +1,251 @@
# Phase 29: Image Presentation - Research
**Researched:** 2026-04-12
**Status:** Complete
## 1. Current Image Architecture
### Display Pattern
Every image surface uses the same CSS pattern:
```
<div class="aspect-[4/3] overflow-hidden">
<img class="w-full h-full object-cover" />
</div>
```
15 total `object-cover` usages across the client (excluding the user avatar which uses `rounded-full`):
- **Cards:** ItemCard, GlobalItemCard, CandidateCard, CandidateListItem
- **Detail pages:** items/$itemId, global-items/$globalItemId, threads/$threadId/candidates/$candidateId
- **Overlays/search:** CatalogSearchOverlay (2 instances), ComparisonTable, LinkToGlobalItem
- **Upload preview:** ImageUpload
- **Global items index:** global-items/index.tsx
### Upload Pipeline
1. Client: `ImageUpload.tsx` → file validation → `apiUpload("/api/images", file)`
2. Server: `routes/images.ts` → generates UUID filename → `uploadImage(buffer, filename, contentType)` via `storage.service.ts`
3. Storage: S3-compatible (Garage/R2/MinIO) via `@aws-sdk/client-s3`
4. Retrieval: `getImageUrl()` returns presigned URLs; `withImageUrl()`/`withImageUrls()` enriches records
**No image processing exists today** — images are uploaded raw and served as-is. No Sharp, no node-vibrant, no server-side manipulation.
### Database Schema (PostgreSQL via Drizzle)
- `items.imageFilename` — text, nullable
- `items.imageSourceUrl` — text, nullable
- `globalItems.imageUrl` — text, nullable (external URL)
- `globalItems.imageSourceUrl` — text, nullable
- `threadCandidates.imageFilename` — text, nullable
- `threadCandidates.imageSourceUrl` — text, nullable
No fields for dominant color or crop positioning exist today.
## 2. Dominant Color Extraction
### Recommended: Sharp
- Already the de facto standard for Bun/Node image processing
- `sharp(buffer).stats()` returns per-channel mean/dominant values
- Can extract dominant color via `sharp(buffer).resize(1,1).raw().toBuffer()` (resize to 1x1 pixel = weighted average)
- Alternative: use `sharp(buffer).stats()` to get channel means, convert to hex
- Lightweight — no additional binary deps beyond what Sharp bundles
- Bun compatibility: Sharp works via Node-API
### Alternative: node-vibrant / color-thief-node
- Heavier, purpose-built for palette extraction
- Returns multiple palette swatches (Vibrant, Muted, DarkVibrant, etc.)
- Overkill for a single dominant color fill background
### Recommendation
Use **Sharp** — single dependency handles both dominant color extraction and any future image processing needs. Resize to 1x1 pixel for a perceptually weighted average color.
### Implementation Notes
- Extract dominant color in the upload handler (both `/api/images` POST and `/api/images/from-url`)
- Return `dominantColor` in the response alongside `filename`
- For globalItems with external `imageUrl`: extract on first access or via backfill script (fetch + process)
## 3. Schema Changes Required
### New Fields
**items table:**
```sql
ALTER TABLE items ADD COLUMN dominant_color text;
ALTER TABLE items ADD COLUMN crop_zoom double precision;
ALTER TABLE items ADD COLUMN crop_x double precision;
ALTER TABLE items ADD COLUMN crop_y double precision;
```
**global_items table:**
```sql
ALTER TABLE global_items ADD COLUMN dominant_color text;
ALTER TABLE global_items ADD COLUMN crop_zoom double precision;
ALTER TABLE global_items ADD COLUMN crop_x double precision;
ALTER TABLE global_items ADD COLUMN crop_y double precision;
```
**thread_candidates table:**
```sql
ALTER TABLE thread_candidates ADD COLUMN dominant_color text;
ALTER TABLE thread_candidates ADD COLUMN crop_zoom double precision;
ALTER TABLE thread_candidates ADD COLUMN crop_x double precision;
ALTER TABLE thread_candidates ADD COLUMN crop_y double precision;
```
### Drizzle Schema
Add to each table in `src/db/schema.ts`:
```ts
dominantColor: text("dominant_color"),
cropZoom: doublePrecision("crop_zoom"),
cropX: doublePrecision("crop_x"),
cropY: doublePrecision("crop_y"),
```
Apply via: `bun run db:generate` then `bun run db:push`
## 4. Zoom+Pan Editor
### Library Options
| Library | Size | Touch | Maintained | Notes |
|---------|------|-------|------------|-------|
| react-easy-crop | ~15KB | Yes | Active | Battle-tested, used by many production apps. Returns crop area coordinates. MIT. |
| react-zoom-pan-pinch | ~25KB | Yes | Active | More general-purpose (maps, images, diagrams). Heavier. |
| Custom (pointer events + CSS transform) | 0KB | Manual | N/A | Full control but significant effort for touch/gesture handling |
### Recommendation: react-easy-crop
- Provides crop area with zoom, rotation, position
- Returns `croppedAreaPixels` and `croppedArea` (percentage-based)
- We need percentage-based output for CSS rendering (so images display correctly at any container size)
- Output: `{ x, y, zoom }` where x/y are percentage offsets
### Storage Model
Store 3 values per image:
- `cropZoom: number` — zoom level (1.0 = fit, >1 = zoomed in)
- `cropX: number` — horizontal offset as percentage (-50 to 50)
- `cropY: number` — vertical offset as percentage (-50 to 50)
When crop settings are `null`, default to `object-contain` with dominant color fill.
When crop settings are present, use CSS `transform: scale(cropZoom) translate(cropX%, cropY%)` with `overflow: hidden`.
## 5. CSS Rendering Strategy
### Default (no crop): Contain + Dominant Color
```tsx
<div
className="aspect-[4/3] overflow-hidden rounded-xl"
style={{ backgroundColor: dominantColor || '#f3f4f6' }}
>
<img
src={url}
className="w-full h-full object-contain"
/>
</div>
```
### With Crop: Transform
```tsx
<div className="aspect-[4/3] overflow-hidden rounded-xl"
style={{ backgroundColor: dominantColor || '#f3f4f6' }}>
<img
src={url}
className="w-full h-full object-cover"
style={{
transform: `scale(${cropZoom}) translate(${cropX}%, ${cropY}%)`,
transformOrigin: 'center center',
}}
/>
</div>
```
### Shared Component
Extract a reusable `<GearImage>` component that encapsulates this logic:
```tsx
interface GearImageProps {
src: string;
alt: string;
dominantColor?: string | null;
cropZoom?: number | null;
cropX?: number | null;
cropY?: number | null;
aspectRatio?: string; // default "4/3"
className?: string;
}
```
All 15 image surfaces replace their inline `<img>` with `<GearImage>`.
## 6. Backfill Migration
### Strategy: One-time Script
- Script reads all images from S3 (items + globalItems + candidates with imageFilename)
- Downloads each, runs Sharp 1x1 resize, extracts dominant color
- Updates the DB record with `dominantColor`
- For globalItems with external `imageUrl`: fetch from URL, extract, update
- Run as: `bun run scripts/backfill-dominant-colors.ts`
### Considerations
- Rate limit S3 reads (batch of 10 concurrent)
- Skip records that already have `dominantColor` set (idempotent)
- Log progress: `Processing 45/123 images...`
- Handle errors gracefully (skip failed images, log them)
## 7. API Changes
### Upload Response Changes
Current: `{ filename }` or `{ filename, sourceUrl }`
New: `{ filename, dominantColor }` or `{ filename, sourceUrl, dominantColor }`
### Item/Candidate CRUD
- `POST /api/items` and `PUT /api/items/:id` — accept `dominantColor`, `cropZoom`, `cropX`, `cropY`
- Same for `POST /api/threads/:id/candidates` and `PUT /api/threads/:id/candidates/:id`
- GlobalItems: similar updates
### Zod Schema Updates
Add to item/candidate schemas in `src/shared/schemas.ts`:
```ts
dominantColor: z.string().nullable().optional(),
cropZoom: z.number().nullable().optional(),
cropX: z.number().nullable().optional(),
cropY: z.number().nullable().optional(),
```
## 8. Scope of Component Changes
### Full List (15 surfaces)
1. `src/client/components/ItemCard.tsx`
2. `src/client/components/GlobalItemCard.tsx`
3. `src/client/components/CandidateCard.tsx`
4. `src/client/components/CandidateListItem.tsx`
5. `src/client/components/ImageUpload.tsx`
6. `src/client/components/ComparisonTable.tsx`
7. `src/client/components/LinkToGlobalItem.tsx`
8. `src/client/components/CatalogSearchOverlay.tsx` (2 instances)
9. `src/client/routes/items/$itemId.tsx`
10. `src/client/routes/global-items/$globalItemId.tsx`
11. `src/client/routes/global-items/index.tsx`
12. `src/client/routes/threads/$threadId/candidates/$candidateId.tsx`
### ProfileSection.tsx excluded
The `object-cover` in `ProfileSection.tsx` is for user avatars (circular), not gear images. Out of scope.
## 9. Risks & Mitigations
| Risk | Impact | Mitigation |
|------|--------|------------|
| Sharp installation issues on Bun | Build failure | Sharp has Bun-compatible prebuilt binaries; test early |
| Backfill takes long for large catalogs | Blocks deployment | Make it idempotent, run post-deploy as async script |
| Zoom+pan UX complexity | Scope creep | Use react-easy-crop as-is, minimal customization |
| Dominant color looks wrong for some images | Visual jank | Fallback to neutral gray when extraction fails |
| Performance: CSS transforms on many cards | Scroll jank | Transform is GPU-accelerated; no perf concern for static transforms |
## Validation Architecture
### Testable Claims
1. All 15 image surfaces use `GearImage` component (grep for component name)
2. No remaining `object-cover` on gear images (grep, excluding avatar)
3. `dominantColor` field exists on items, globalItems, threadCandidates tables
4. Upload endpoints return `dominantColor` in response
5. Backfill script processes existing images without errors
6. Zoom+pan editor appears in ImageUpload and item detail edit mode
---
## RESEARCH COMPLETE

View File

@@ -0,0 +1,66 @@
---
status: diagnosed
phase: 29-image-presentation
source: [29-01-SUMMARY.md, 29-02-SUMMARY.md, 29-03-SUMMARY.md, 29-04-SUMMARY.md]
started: 2026-04-12T19:10:00Z
updated: 2026-04-13T12:15:00Z
---
## Current Test
[testing complete]
## Tests
### 1. Images use fit-within instead of crop
expected: Browse any page with item/catalog cards. Images should fit inside the frame without cropping — full image visible, no parts cut off.
result: pass
### 2. Dominant color background fill
expected: Where an image doesn't fill the entire frame, the empty space is filled with a color extracted from the image (not white or gray).
result: pass
### 3. Crop editor on item detail
expected: Open an item that has an image. In edit mode, you should see a crop icon button next to the trash icon, positioned as an overlay on the image. Clicking it opens a crop editor with zoom slider.
result: pass
reported: "Initially reported as issue but confirmed working on re-test — false claim"
### 4. Crop editor on image upload
expected: Upload a new image to an item. After the upload completes, a crop editor should appear automatically. After cropping, the preview should reflect the crop immediately.
result: issue
reported: "crop editor opens on upload correctly, but after cropping the cropped image isn't shown in the edit state always — after clicking save it is shown correctly"
severity: minor
### 5. Crop settings persist
expected: Adjust the crop on an item image, save it. Navigate away and come back — image displays with saved crop settings.
result: pass
### 6. Consistency across surfaces
expected: All image surfaces use the same fit-within + dominant color treatment.
result: pass
## Summary
total: 6
passed: 5
issues: 1
pending: 0
skipped: 0
blocked: 0
## Gaps
- truth: "Cropped image preview should update in edit state immediately after cropping"
status: failed
reason: "User reported: cropped image not shown in edit state after cropping, but renders correctly after save"
severity: minor
test: 4
root_cause: "ImageUpload component does not store or forward crop values to its GearImage preview after crop editor closes. onCropChange sends to server but no local state is updated. GearImage in ImageUpload receives zero crop props. Only after form save + query refetch do crop values appear."
artifacts:
- path: "src/client/components/ImageUpload.tsx"
issue: "GearImage preview (line 110-114) rendered without cropZoom/cropX/cropY props; no local crop state exists"
- path: "src/client/routes/items/$itemId.tsx"
issue: "onCropChange (line 288-293) fires server mutation but updates no local/form state"
missing:
- Add local crop state in ImageUpload that gets set from crop editor result and passed as props to GearImage
debug_session: ".planning/debug/crop-preview-edit-state.md"

View File

@@ -0,0 +1,237 @@
---
phase: 29
slug: image-presentation
status: draft
shadcn_initialized: false
preset: none
created: 2026-04-12
---
# Phase 29 — UI Design Contract
> Visual and interaction contract for image presentation changes. Generated by gsd-ui-researcher, verified by gsd-ui-checker.
---
## Design System
| Property | Value |
|----------|-------|
| Tool | none (Tailwind CSS v4 direct) |
| Preset | not applicable |
| Component library | none (custom components) |
| Icon library | Lucide (via custom LucideIcon wrapper) |
| Font | System default (inherited) |
---
## Spacing Scale
Declared values (must be multiples of 4):
| Token | Value | Usage |
|-------|-------|-------|
| xs | 4px | Icon gaps, inline padding |
| sm | 8px | Compact element spacing |
| md | 16px | Default element spacing |
| lg | 24px | Section padding |
| xl | 32px | Layout gaps |
| 2xl | 48px | Major section breaks |
| 3xl | 64px | Page-level spacing |
Exceptions: none
---
## Typography
No new typography introduced. All text elements use existing typographic scale from the app.
| Role | Size | Weight | Line Height |
|------|------|--------|-------------|
| Body | 14px | 400 | 1.5 |
| Label | 12px | 500 | 1.25 |
| Heading | 14px | 600 | 1.25 |
---
## Color
No new brand colors introduced. The only new color element is the **dominant color background** which is dynamically extracted per-image.
| Role | Value | Usage |
|------|-------|-------|
| Dominant (60%) | white (#ffffff) | Page background (unchanged) |
| Secondary (30%) | gray-50 (#f9fafb) | Card surfaces, fallback image bg |
| Accent (10%) | blue-50/green-50 | Weight/price badges (unchanged) |
| Dynamic fill | per-image dominant color | Image container background behind `object-contain` images |
| Fallback fill | gray-100 (#f3f4f6) | Image container background when dominant color unavailable |
Accent reserved for: weight badges (blue-50), price badges (green-50), category badges (gray-50)
---
## Image Container Specifications
### GearImage Component
A new shared component replaces all inline `<img>` elements for gear/product images.
| Property | Spec |
|----------|------|
| Component name | `GearImage` |
| File location | `src/client/components/GearImage.tsx` |
| Default aspect ratio | `4/3` (cards, upload preview) |
| Detail page ratio | `16/9` (global item detail, candidate detail) |
| Border radius | `rounded-xl` (12px) on detail pages; inherited from parent on cards |
| Overflow | `hidden` (always) |
### Default State (no crop)
```
Container: aspect-[4/3], overflow-hidden
Background: dominant color OR #f3f4f6 (gray-100 fallback)
Image: object-contain, w-full, h-full
Result: Full image visible, letterbox/pillarbox fill with dominant color
```
### Cropped State (user-defined zoom+pan)
```
Container: aspect-[4/3], overflow-hidden
Background: dominant color OR #f3f4f6
Image: w-full, h-full, object-cover
Transform: scale(cropZoom) translate(cropX%, cropY%)
Transform origin: center center
Result: User-framed view with cropped overflow hidden
```
### Empty State (no image)
```
Container: aspect-[4/3], bg-gray-50
Content: Centered LucideIcon (category icon), text-gray-400, size 36px
```
Unchanged from current behavior.
### Transition
No CSS transitions on the image itself. Background color applies immediately via inline `style={{ backgroundColor }}`.
---
## Zoom+Pan Editor Specifications
### Editor Trigger Points
| Location | Trigger | Behavior |
|----------|---------|----------|
| ImageUpload component | After image upload completes | Editor overlay appears on the uploaded image |
| Item detail page | "Adjust framing" button below image | Editor overlay replaces static image view |
| Global item detail page | "Adjust framing" button below image | Same as item detail |
| Candidate detail page | "Adjust framing" button below image | Same as item detail |
### Editor UI
| Element | Spec |
|---------|------|
| Library | react-easy-crop |
| Crop shape | rect |
| Aspect ratio | Matches container (4/3 for cards, 16/9 for detail pages where applicable) |
| Min zoom | 1.0 (fit-within, default) |
| Max zoom | 3.0 |
| Background | Dominant color of the image (or gray-100 fallback) |
| Controls | Zoom slider below the crop area |
| Save button | "Save framing" — primary action, bottom-right |
| Cancel button | "Cancel" — secondary/ghost, bottom-left |
| Button spacing | 8px gap between cancel and save |
### Editor Overlay Layout
```
+-------------------------------------------+
| |
| [react-easy-crop area] |
| (drag to pan, scroll to zoom) |
| |
+-------------------------------------------+
| [------- zoom slider -------] |
+-------------------------------------------+
| Cancel Save framing |
+-------------------------------------------+
```
- Overlay uses `fixed inset-0 z-50 bg-black/60` on mobile, `relative` inline on desktop detail pages
- On ImageUpload: overlay within the upload container
- On detail pages: replaces the image area inline (no modal)
### Editor Output
| Field | Type | Range | Description |
|-------|------|-------|-------------|
| cropZoom | number | 1.0 - 3.0 | Zoom level (1.0 = fit within) |
| cropX | number | -50 to 50 | Horizontal pan offset (percentage) |
| cropY | number | -50 to 50 | Vertical pan offset (percentage) |
When zoom is 1.0 and x/y are 0: equivalent to default `object-contain` (no crop applied).
---
## Copywriting Contract
| Element | Copy |
|---------|------|
| Adjust framing button | "Adjust framing" |
| Editor save CTA | "Save framing" |
| Editor cancel | "Cancel" |
| Zoom slider label | "Zoom" (sr-only) |
| Empty image placeholder | "Click to add photo" (unchanged) |
| Backfill progress (admin) | "Processing images... {N}/{total}" |
---
## Surface-by-Surface Spec
Each surface adopts the `GearImage` component. All surfaces use 4/3 ratio except where noted.
| # | Surface | File | Ratio | Has Editor | Notes |
|---|---------|------|-------|------------|-------|
| 1 | ItemCard | `components/ItemCard.tsx` | 4/3 | No | Card only, editor on detail page |
| 2 | GlobalItemCard | `components/GlobalItemCard.tsx` | 4/3 | No | Card only |
| 3 | CandidateCard | `components/CandidateCard.tsx` | 4/3 | No | Card only |
| 4 | CandidateListItem | `components/CandidateListItem.tsx` | 4/3 | No | Small thumbnail |
| 5 | ImageUpload | `components/ImageUpload.tsx` | 4/3 | Yes | Editor after upload |
| 6 | ComparisonTable | `components/ComparisonTable.tsx` | 4/3 | No | Table cell image |
| 7 | LinkToGlobalItem | `components/LinkToGlobalItem.tsx` | 1/1 | No | Small 32px thumbnail, keep object-cover for tiny icons |
| 8 | CatalogSearchOverlay | `components/CatalogSearchOverlay.tsx` | 4/3 | No | Search result cards (2 instances) |
| 9 | Item detail | `routes/items/$itemId.tsx` | 4/3 | Yes | Full editor access |
| 10 | Global item detail | `routes/global-items/$globalItemId.tsx` | 16/9 | Yes | Full editor access |
| 11 | Global items index | `routes/global-items/index.tsx` | 4/3 | No | List card |
| 12 | Candidate detail | `routes/threads/$threadId/candidates/$candidateId.tsx` | 16/9 | Yes | Full editor access |
### LinkToGlobalItem Exception
The 32x32px thumbnail in LinkToGlobalItem is too small for letterbox treatment. Keep `object-cover` with `rounded` for this surface. The GearImage component should accept a `cover` prop to force object-cover mode for tiny thumbnails.
---
## Registry Safety
| Registry | Blocks Used | Safety Gate |
|----------|-------------|-------------|
| npm (react-easy-crop) | react-easy-crop | MIT license, 500k+ weekly downloads, active maintenance |
No shadcn blocks used in this phase.
---
## Checker Sign-Off
- [x] Dimension 1 Copywriting: PASS
- [x] Dimension 2 Visuals: PASS
- [x] Dimension 3 Color: PASS
- [x] Dimension 4 Typography: PASS
- [x] Dimension 5 Spacing: PASS
- [x] Dimension 6 Registry Safety: PASS
**Approval:** approved 2026-04-12

View File

@@ -0,0 +1,78 @@
---
phase: 29
slug: image-presentation
status: draft
nyquist_compliant: false
wave_0_complete: false
created: 2026-04-12
---
# Phase 29 — Validation Strategy
> Per-phase validation contract for feedback sampling during execution.
---
## Test Infrastructure
| Property | Value |
|----------|-------|
| **Framework** | Bun test runner + Playwright |
| **Config file** | `bunfig.toml` / `playwright.config.ts` |
| **Quick run command** | `bun test` |
| **Full suite command** | `bun test && bun run test:e2e` |
| **Estimated runtime** | ~30 seconds (unit) + ~60 seconds (E2E) |
---
## Sampling Rate
- **After every task commit:** Run `bun test`
- **After every plan wave:** Run `bun test && bun run test:e2e`
- **Before `/gsd-verify-work`:** Full suite must be green
- **Max feedback latency:** 30 seconds
---
## Per-Task Verification Map
| Task ID | Plan | Wave | Requirement | Threat Ref | Secure Behavior | Test Type | Automated Command | File Exists | Status |
|---------|------|------|-------------|------------|-----------------|-----------|-------------------|-------------|--------|
| 29-01-01 | 01 | 1 | D-01,D-02,D-03 | — | N/A | unit | `bun test tests/services/image.service.test.ts` | ❌ W0 | ⬜ pending |
| 29-01-02 | 01 | 1 | D-04 | — | N/A | integration | `bun test tests/services/image.service.test.ts` | ❌ W0 | ⬜ pending |
| 29-02-01 | 02 | 1 | D-01,D-06 | — | N/A | grep | `grep -r "GearImage" src/client/` | N/A | ⬜ pending |
| 29-03-01 | 03 | 2 | D-07,D-08,D-09 | — | N/A | unit+E2E | `bun test && bun run test:e2e` | ❌ W0 | ⬜ pending |
*Status: ⬜ pending · ✅ green · ❌ red · ⚠️ flaky*
---
## Wave 0 Requirements
- [ ] Test stubs for dominant color extraction service
- [ ] Test stubs for crop field persistence
*Existing test infrastructure (Bun test runner, Playwright) covers framework needs.*
---
## Manual-Only Verifications
| Behavior | Requirement | Why Manual | Test Instructions |
|----------|-------------|------------|-------------------|
| Dominant color background looks correct | D-02 | Visual quality subjective | Upload 5 varied images, verify background colors feel intentional |
| Zoom+pan editor is intuitive | D-07 | UX quality subjective | Open editor, zoom in/out, pan, verify coordinates save and render |
| Letterbox/pillarbox appearance | D-01 | Visual consistency check | View tall and wide images on cards and detail pages |
---
## Validation Sign-Off
- [ ] All tasks have `<automated>` verify or Wave 0 dependencies
- [ ] Sampling continuity: no 3 consecutive tasks without automated verify
- [ ] Wave 0 covers all MISSING references
- [ ] No watch-mode flags
- [ ] Feedback latency < 30s
- [ ] `nyquist_compliant: true` set in frontmatter
**Approval:** pending

View File

@@ -0,0 +1,42 @@
---
phase: 29
status: passed
verified: 2026-04-12
---
# Phase 29: Image Presentation — Verification
## Goal
Images display within the fixed aspect ratio using fit-within framing (letterbox/pillarbox) instead of hard crops, preserving the full image.
## Must-Haves Verification
| # | Must-Have | Status | Evidence |
|---|-----------|--------|----------|
| 1 | GearImage component with object-contain | PASS | `src/client/components/GearImage.tsx` contains `object-contain` |
| 2 | All 12 gear surfaces use GearImage | PASS | `object-cover` only in GearImage internal, ProfileSection, users avatar |
| 3 | Dominant color background fill | PASS | `imageContainerBg()` helper used in all parent containers |
| 4 | dominantColor field on items, globalItems, threadCandidates | PASS | 3 occurrences of `dominant_color` in schema.ts |
| 5 | Crop fields on all 3 tables | PASS | cropZoom, cropX, cropY on items, globalItems, threadCandidates |
| 6 | Upload endpoints return dominantColor | PASS | Both POST routes return dominantColor |
| 7 | Zod schemas accept new fields | PASS | 3 schemas updated |
| 8 | Zoom+pan editor component | PASS | ImageCropEditor.tsx with react-easy-crop |
| 9 | Editor in ImageUpload | PASS | Shows after upload when onCropChange provided |
| 10 | "Adjust framing" on item detail | PASS | Button renders when image exists |
| 11 | "Adjust framing" on candidate detail | PASS | Button renders when image exists |
| 12 | Backfill migration script | PASS | scripts/backfill-dominant-colors.ts |
| 13 | Build passes | PASS | `bun run build` succeeds |
| 14 | Lint passes | PASS | `bun run lint` — 0 issues |
## Score: 14/14
## Human Verification Items
1. **Visual quality**: Upload images of various aspect ratios (portrait, landscape, square) and verify letterbox/pillarbox backgrounds look intentional with dominant color fill
2. **Crop editor UX**: Open item detail, click "Adjust framing", verify zoom slider and drag-to-pan work smoothly
3. **Cross-surface consistency**: View the same image on ItemCard, item detail, and candidate card — verify framing is consistent
## Notes
- Database migration generated but db:push deferred (no database accessible in dev environment). Must run `bun run db:push` before deployment.
- Global item detail "Adjust framing" skipped — no update endpoint exists for global items.
- Pre-existing test failures (311 fails) unrelated to this phase — `setup_items` relation issues in pglite test setup.