Ty 83b58c23a3 fix(fe): read batchApply as a sibling of results, not a child ...

onPhotosReady read results.batchApply, but on the measure capture state
batchApply is a SIBLING of results, so the read was always undefined and every
batch photo fell through to processedBlob: undefined. The Photos-ready lineup
showed all four PNGs (calibration, overlay, and both batch siblings) yet only
two images reached Woo, because publish.py selects WHERE processed_blob IS NOT
NULL. Read s.capture.batchApply.

2026-09-25 21:10:25 -07:00

..

src

fix(fe): read batchApply as a sibling of results, not a child

2026-09-25 21:10:25 -07:00

tests

merge issue-89-metadata-lock → main (Create-string model, #89/#90)

2026-09-21 11:54:48 -07:00

Dockerfile

feat(capture): ship Milestone 1 browser capture app

2026-09-14 07:53:39 +00:00

index.html

feat(capture): ship Milestone 1 browser capture app

2026-09-14 07:53:39 +00:00

package-lock.json

feat(m4): crop_fill setting + tape-line prototype (#99)

2026-09-24 12:01:18 -07:00

package.json

feat(greenfield): rebuild SlabUploader M1-M3 on clean foundation, all gates green

2026-09-25 06:57:29 -07:00

playwright.config.ts

M3 Review→Publish UI (#77): one-column flow, searchable pickers, fig/feat tags, e2e

2026-09-20 14:34:24 -07:00

tsconfig.json

fix(capture): preserve PhotoStage preview aspect on first paint

2026-09-14 16:37:00 +00:00

vite.config.ts

chore(fe): vite dev proxy for local FastAPI (dev-only, not in Docker build)

2026-09-25 07:01:20 -07:00