brilliant-msg caps pillow<12 — the one bound between the lock and pillow's entire security fix line

[LetsGetToWorkBro]

What happened

The main pillow fork in uv.lock (serving dream, hardware, vision, profile-mac since #651) sits at 11.3.0. Every open pillow advisory — ~18 GHSAs, mostly high: heap OOB writes in Image.paste()/crop()/ImageCmsTransform, decompression bombs, font parser bugs — is fixed in 12.1.1–12.3.0. One bound stands in the way:

$ curl -s https://pypi.org/pypi/brilliant-msg/json | \
    python3 -c "import json,sys; d=json.load(sys.stdin); print(d['info']['version'], [x for x in d['info']['requires_dist'] if 'illow' in x])"
7.0.0 ['pillow<12.0.0,>=11.1.0']

brilliant-msg is Brilliant Labs' own glasses-bridge SDK, so this is an upstream ask, not a local edit. Full context in decisions/0013 (pillow section).

Ask

1. Test brilliant-msg 7.0.0 against pillow 12.3. Its image path is small (frame encode for the display). If it passes, file the widening upstream at Brilliant Labs' repo with the test evidence — same discipline as surya-ocr pins pillow<11 — the last pillow-10.4.0 fork in the lock hangs on one upstream bound #654/decisions/0012: prove it, don't assume the cap is incidental.
2. When upstream lifts it: our side is one relock. The dream/hardware/vision fork moves to 12.3.x and the pillow section of the Dependabot alert wall clears.

Verifying a fix

cd host-python
uv lock && uv lock --check
python3 -c "import tomllib; print({p['version'] for p in tomllib.load(open('uv.lock','rb'))['package'] if p['name']=='pillow'})"
# expect 12.3.x on the main fork (10.4.0 remains until #654 lands too)
python -m pytest src/dreamlayer/tests/test_lockfile.py -q

Where

upstream (Brilliant Labs brilliant-msg); locally only host-python/uv.lock + decisions/0013