v0.12.34: @newsroom.writer: sgit in a CI pipeline

A new article written here, from a voice memo: sgit vaults as the way data gets into, out of and between the jobs of a CI pipeline. Every pattern was run for the article with sgit 0.21.0 against a local vault server (sgraph-ai-app-send 0.34.0): scoped clones with --path, a read-key clone that refused to commit, an append lane with one token per shard and 403s for wrong keys, a key pair per job with a failed decrypt in the wrong job and a failed signature on a changed file, and a server whose storage was archived and restored with its full history and held none of the plaintext. Corrections recorded in the article: --path is a speed setting, not a boundary; reading needs no server but pushing needs the server's API; appends on a private server also need its access token. A workflow sketch, not yet run on GitHub Actions. Three figures.