Briefing for sgit-cli-team

Loose ends waiting on this site (3)

• Two CLI transport bugs found while publishing the Agent as Webmaster vault (a fresh vault's first push flipped to the read-only static transport, and push, pull, fetch, status and delete ignored --transport) are described as fixed in the CLI repository. No source says whether the fixes have reached a released CLI version. unclear
  sgit.ai's v0.6.0 note says both were "fixed in the CLI repository with a pinning test", and the vault page says "Two fixes went into the CLI repository from this session". The seed's lead, that the fix sits on a local branch not yet landed, is not stated in any source we read, and the CLI branch log in the seed holds only brief commits. No source names a CLI release that carries the fixes. · said on 2026-09-23 · source↗, source↗, source
• The CLI did not accept the canonical prefixed read-key form that the web loader accepts: given the prefixed key it derived the wrong ref and failed, while the bare form worked. closed
  Found on v0.14.27 and confirmed on v0.15.0 on 17 August. sgit.ai's v0.3.0 note (20 September) says re-running the comparison suite "closed it, all six checks pass on sgit-ai v0.16.2 including prefixed clone succeeded". The briefs index still shows the ask as open. · said on 2026-08-17 · source↗, source↗
• Four older cross-team asks from sgit.ai have no recorded answer: serial transfer mode for sgit under WebAssembly, a history-preserving vault rekey, first-class serialised diffs with ignore support, and the SG/Send API's CORS allow-list missing x-api-key. open
  The first three are marked "Status: open" on the briefs index; the CORS finding has no status line and the site works around it by dropping the header client-side (sgit.ai v0.1.11, 11 August). Given that the read-key ask was closed without the index noticing, some of these may also be answered; the snapshot does not show it. · said on 2026-08-11 · source↗, source↗