v20260819

Documents come back out, a binary can say which release it is, and the Windows installer works on the PowerShell that Windows actually ships.

Downloading a document

memorylake proj doc list --project <id>              # find the document id
memorylake proj doc download --project <id> <doc-id> # to the current directory
memorylake proj doc download --project <id> <doc-id> -o ~/Downloads/
memorylake proj doc download --project <id> <doc-id> -o - | head

The file lands under the name the server reports. -o takes a file path or a
directory; -o - streams to stdout for piping, with the summary on stderr so it
stays out of the pipe. An existing file is never replaced without --force, and
the write goes to a temporary file first, so an interrupted download cannot leave
a half-written file where a whole one used to be.

The bytes are streamed rather than buffered — the size of a document is the
server's business, not this process's memory. The endpoint answers with a
short-lived pre-signed storage URL rather than the bytes; that redirect is
followed automatically, your API key is not carried across to storage, and the
URL is never logged in full, because its query string is itself a credential.

Which release is this

memorylake version    # v20260819

Every build before this one reported 0.1.0 — the crate version, unchanged since
the first release — so an upgraded install and a stale one looked identical.
Release builds now carry their tag. A build that did not come from the release
workflow says 0.1.0 (dev build) instead of claiming a release it is not.

This is the first release that reports its own tag. v20260818.1 and earlier
still say 0.1.0, which is precisely the problem being fixed: if version prints
0.1.0 on a machine you just upgraded, the upgrade did not take.

Installing without prompts

The installers accept the credentials, so a link handed out by a console can
install and configure in one step with nothing to type — and CI, where there is
nobody to prompt, gets the same path:

curl -fsSL https://raw.githubusercontent.com/memorylake-ai/memorylake-cli/main/scripts/install.sh \
  | sh -s -- --api-key sk-… --workspace ws-… [--base-url URL]

# `irm | iex` cannot pass parameters, so Windows uses the environment
$env:MEMORYLAKE_API_KEY='sk-…'; $env:MEMORYLAKE_WORKSPACE='ws-…'
irm https://raw.githubusercontent.com/memorylake-ai/memorylake-cli/main/scripts/install.ps1 | iex

Every flag has an environment variable (MEMORYLAKE_API_KEY,
MEMORYLAKE_WORKSPACE, MEMORYLAKE_BASE_URL); a flag wins over its variable.
Supplied credentials replace whatever is already stored, which is the point
when a console hands out a key — but nothing is written unvalidated, so a key that
will not work leaves your existing configuration intact rather than overwriting
working credentials with broken ones.

A key on a command line is recorded in your shell's history. Prefer a short-lived
key where that matters.

Windows PowerShell 5.1

The installer that shipped in v20260818.1 failed on stock Windows PowerShell
5.1 — the default on Windows 10 and 11 — for three unrelated reasons:
RuntimeInformation does not exist on .NET Framework, response headers are typed
differently there, and 5.1 reads a .ps1 with no BOM as ANSI, which turned this
file's em dashes into stray quote characters and broke parsing several lines away
from anything that looked wrong.

All three are fixed. CI now parses the script under 5.1 as well as PowerShell 7 —
the two parsers disagree, so validating under 7 alone proved nothing — and rejects
any non-ASCII byte in it.

If a Windows install failed on v20260818.1, re-run the same one-liner.

Also

• The README is written for people using the CLI rather than developing it;
  CONTRIBUTING.md now holds the build, test and release details.
• The live test suite runs once per CI run instead of twice concurrently against
  the same account, which was producing failures that looked like permission and
  connectivity problems and needed a rerun to clear.

Upgrading

Re-run your install command. No flags or commands changed; --workspace and
everything else behave as before.

---

What's Changed

• docs: Rewrite the README for people using the CLI by @a1594834522-coder in #21
• fix: Make the PowerShell installer work on Windows PowerShell 5.1 by @a1594834522-coder in #22
• feat: Add project document download by @a1594834522-coder in #23
• feat: Report which release a binary is by @a1594834522-coder in #24
• fix: Run live tests once per CI run; let installers take credentials by @a1594834522-coder in #25

Full Changelog: v20260818.1...v20260819