Skip to content

fix: bound annotation geometry to assets - #693

Merged
JArmandoAnaya merged 1 commit into
mainfrom
fix/525-annotation-geometry-bounds
Aug 18, 2026
Merged

fix: bound annotation geometry to assets#693
JArmandoAnaya merged 1 commit into
mainfrom
fix/525-annotation-geometry-bounds

Conversation

@JArmandoAnaya

Copy link
Copy Markdown
Contributor

Summary

Spatial annotations on assets with recorded dimensions now reject only when their geometry has no overlap with the asset frame. Partial boxes, paths, and polygons remain valid; classification annotations and assets without recorded dimensions retain their existing behavior.

Pre-labeling filters mapped model regions with no overlap before the atomic write, reports them separately from unmappable labels, and publishes that count through REST, CLI, MCP, and the completed-run dialog.

Validation

bash scripts/check.sh

The full gate ran with Node 24.19.0 and covered Python tests, static checks, generated-artifact drift, frontend build/test/lint, Chromium end-to-end tests, and the real-server browser cycle.

Found, not fixed

None.

Closes #525

@JArmandoAnaya
JArmandoAnaya marked this pull request as ready for review August 18, 2026 21:06
@JArmandoAnaya
JArmandoAnaya merged commit ff88f1d into main Aug 18, 2026
15 checks passed
@JArmandoAnaya
JArmandoAnaya deleted the fix/525-annotation-geometry-bounds branch August 18, 2026 21:06
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Annotation geometry is not bounds-checked against its asset

1 participant