Caprock Files

Changed

• Premium is ultramarine now. Every interactive element in this product is the brand amber, which left a subscribe button looking exactly like a range filter. Paid is a different kind of thing, so it gets a different hue — deliberately cool against a warm interface. Reserved strictly for surfaces where money is involved; an ultramarine that spread to ordinary controls would just be a second accent, and then nothing would be marked.

• The premium dialog offers a year or a lifetime, and not a month. At $5 the monthly plan is the cheapest way to hold a licence key for a month, which is a worse deal for the buyer than either commitment beside it. It remains on the site for anyone who seeks it out.

• The weekly report shows what would arrive, not a description of it. It was three rows reading "Sent / To / Contains", which describes an email without showing one — and behind glass that is a blurred settings screen. It now previews the message itself, with this machine's own repository names in it. Deliberately without figures: those are already free two panels down, and locking them would take something away rather than preview something new.

Added

• winget. winget install dspv.caprock, once Microsoft has merged the manifest for a release — the package manager already present on every Windows 10 and 11 machine, with no bucket to add first. Deferred until there was Windows demand (ADR-014); the first Windows user to build from source asked for it by name.

Unlike the Homebrew tap and the Scoop bucket, that repository is not ours: Microsoft reviews and merges every manifest, so a release reaches winget hours or days after it reaches everywhere else. That lag is the channel, not a fault to fix.

Fixed

• make build works on Windows. It did not, and the very first command in CONTRIBUTING.md failed on a fresh Windows clone: make with no sh on PATH falls back to cmd.exe, which understands none of mkdir -p, [ -d ], single-quoted -ldflags, or 2>/dev/null. It now uses the Bash that Git for Windows already installs.

The Windows CI job was green throughout — because CI never ran make. It invokes go build and go test directly, so every badge said the repository worked on Windows while its documented first step did not. A green matrix is not the same as a working repository, so this ships with a CI job that runs make build on Windows and checks the binaries exist.