# M16-GAP-00232 Status

status: done
task: armature.collection_unsolo_all operator LOCAL_EXACT slice
updated: 2026-08-22 America/New_York

scope:

- The minimal fixture contains three bone collections with one bone each; the middle collection starts solo while all collections remain visible and the middle collection is active.
- Desktop runs `ARMATURE_OT_collection_unsolo_all` with `poll=true` and `FINISHED`, clearing every collection's solo flag while preserving collection order, membership, visibility, and active index through save/reopen.
- Main now exposes each armature bone collection's `solo` flag alongside its existing visibility and member IDs; no other data-block, editor, or browser behavior was added.

evidence:

- The generator, desktop checker, production web-engine build, npm comparator, direct comparator, and task-context checks passed. Repeated checker runs recognize the already-unsolo state and remain idempotent.
- WASM/Main observes all three collections with `solo=false`, preserves members and visibility across save/reopen, and rejects malformed Blend input without Main mutation.
- Chromium-only policy was preserved; no Firefox/WebKit run was made.

nextTask: `M16-GAP-00233`