L 9fc59ded1c fix: handle raw m2. macaroon tokens from Fly.io CLI Sessions API (#1552) ... Root cause of 'no tokens found in header' after browser OAuth: The Fly.io CLI Sessions API returns raw macaroon tokens (e.g. m2.XXXX) WITHOUT the 'FlyV1 ' prefix. _sanitize_fly_token only handled fm2_ tokens, so m2. tokens fell through unchanged and were sent as: Authorization: Bearer m2.XXXX Fly.io's Machines API expects FlyV1 macaroon format, not Bearer. Fixes: - _sanitize_fly_token: add m2.* case that wraps as 'FlyV1 m2.XXX' - _try_fly_browser_auth polling: eagerly wrap any non-FlyV1 token with 'FlyV1 ' prefix at the source, before it's echoed back to the caller Token format handling after fix: m2.XXXX → FlyV1 m2.XXXX ← CLI Sessions API (was broken) fm2_XXXX → FlyV1 fm2_XXXX ← still handled (unchanged) FlyV1 fm2_XXXX → FlyV1 fm2_XXXX ← already correct (unchanged) eyJhbGci... → Bearer eyJ... ← legacy JWT (fallback to manual) Co-authored-by: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>		2026-02-20 23:54:34 -08:00
..
common.sh	fix: handle raw m2. macaroon tokens from Fly.io CLI Sessions API (#1552)	2026-02-20 23:54:34 -08:00