fetches now 302 (info/refs) or 307 (a bare upload-pack post) to the repo's artifacts remote with the knot's read token as url userinfo, so git talks to artifacts directly. git keeps the knot as origin and comes back through it on the next fetch for a fresh token. pushes are still forwarded so the knot sees the ref updates. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>