v0.1.4 Homebrew release ships none of the quantcli contract (no --since/--until/--format, no prime, no auth status)

[DTTerastar]

The currently published Homebrew cask crono-export 0.1.4 (symlinked at /opt/homebrew/bin/crono-export) was built from before the contract migration commits landed on main. As a result the released binary is missing every quantcli contract feature that has already been merged on main:

Feature	On main (HEAD)	In v0.1.4 binary
--since/--until flags	yes	missing (still has --start --end --days --today)
--format markdown|json	yes	missing
Markdown default output	yes	missing (still JSON-only)
prime subcommand	yes	missing
auth / auth status subcommand	yes	missing

Repro:

$ crono-export --version 2>/dev/null; crono-export --help | head -5
crono-export reads your personal Cronometer data via the same export
endpoints the web app uses and prints it as JSON on stdout.

$ crono-export biometrics --since today
error: unknown flag: --since
$ crono-export prime
error: unknown command "prime" for "crono-export"
$ crono-export auth status
error: unknown command "auth" for "crono-export"

git log v0.1.4..HEAD on the source repo shows 10+ feature commits (bc94322 feat: add 'prime', a5c227d feat!: harmonize date flags, c1a4879 feat: markdown by default, 5fd727b feat: add 'auth status', 054064e feat!: drop --json shortcut, default --format, etc.) that have never been tagged/released.

Expected: cut a new tag (v0.2.0 — there are breaking flag renames) and update the Homebrew cask so installed users get the contract-conformant CLI. Without this, every other contract issue in this repo is moot for end users.

Severity: blocker

[DTTerastar]

Closing — this was filed against the released binary. We're testing main pre-release; binary version isn't a code bug.