Brooklyn Nicholson f174c0b6bb fix(pairing): scope the approve/revoke endpoints to a profile ... The gateway keeps one PairingStore per served profile, but every `/api/pairing` endpoint built the global one. An operator managing a named profile saw the wrong pending list, and approving wrote a grant into a whitelist their running gateway never consults — the user stays locked out while the UI shows them as approved. `_pairing_store(profile)` now resolves per profile and validates the name (400/404 on an unknown one). No `_profile_scope` needed: PairingStore resolves the profile's home itself, so nothing process-global is swapped across an await. Both GUIs had to change to match. The listing rides the query param — for the dashboard that meant deleting `pairing` from the "machine-global, must NOT be rewritten" exclusion list, a comment this change makes false. The mutating endpoints read the profile off the BODY, which no query-param rewrite reaches, so approve/revoke send it explicitly on both surfaces.		2026-07-29 18:43:50 -05:00
..
bootstrap-installer	fix(installer): release the update marker on success, not just on drop	2026-07-29 17:48:09 -05:00
desktop	fix(pairing): scope the approve/revoke endpoints to a profile	2026-07-29 18:43:50 -05:00
shared	refactor: drop the shared subpath export, keeping package.json untouched	2026-07-28 03:54:49 -05:00