chutes-build 1.0.0 → 1.0.2

package/CHANGELOG.md

@@ -6,6 +6,133 @@ project follows [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
 ## [Unreleased]
 
+## [1.0.2] - 2026-08-11
+
+Three faults a user meets in the first minute. All reproduced against the live
+service with a real API key, not inferred from the source.
+
+### Fixed
+
+- **`/model` offered a single model.** `ModelFetchAuth::resolve` treated any stored
+  credential as a *session*, and logging in with an API key stores one — so
+  `auth.json` holding a `chutes::api_key` entry sent the catalogue fetch down the
+  session path, which asks the router proxy. That proxy advertises exactly one
+  model: itself. `llm.chutes.ai/v1/models` returns thirteen. The request URL was
+  already right for API keys; only the classification was wrong. `models` now
+  lists all fourteen, with the configured default marked — a default the product
+  previously could not resolve even when the user had named it.
+- **"Sign in with Chutes" could not complete.** The re-base replaced the fork's
+  OAuth scopes with upstream's — `grok-cli:access`, `api:access`,
+  `conversations:*`, `workspaces:*` — none of which exist at `api.chutes.ai`. Its
+  discovery document offers `account:read`, `chutes:read`, `chutes:invoke`; an
+  authorization server rejects scopes it does not know. Restored to the minimum the
+  client uses. OAuth still requires an application you register yourself at
+  [chutes.ai](https://chutes.ai/docs/sign-in-with-chutes/overview) — there is no
+  shared client id, by design — and the API key remains the primary method.
+- **The welcome screen disagreed with its own input bar.** The wordmark blended
+  from a fixed gray because the re-base replaced `theme.accent_assistant` with
+  upstream's `theme.gray`. It takes the accent again, so the centre of the screen
+  and the prompt border move together.
+- The feedback prompt's default still read "You've been using Grok Code
+  productively!". It lives in `prod/mc/cli-chat-proxy-types`, outside the crates
+  the 1.0.1 sweep looked at — found by searching the shipped binary rather than
+  the tree.
+
+### Changed
+
+- **Silver is the brand accent.** Not a rename of the green: in this palette one
+  constant carried both the brand and the *meaning* of success and of a diff's
+  insertion side. Those are now two families. `SILVER` takes the chrome — wordmark,
+  assistant, model and command labels, active prompt border, H1 rule — and green
+  stays exactly where it says something, because a silver diff against a red one is
+  unreadable. The silver is cool on purpose: these neutral grays are warm, so a
+  warm silver would sink into the furniture.
+
+## [1.0.1] - 2026-08-11
+
+### Fixed (the TUI wore upstream's identity)
+
+- **The splash showed Grok's wordmark.** `assets/logo/logo07.txt` and
+  `logo05.txt` were byte-identical to upstream's: the re-base overwrote the Chutes
+  wordmark and 1.0.0 shipped it, so every start drew the wrong brand. Restored. A
+  sweep of every asset in the tree says these two were the only ones taken.
+- **A Chutes user was offered a subscription to another company's product.**
+  Hitting a usage limit produced "Upgrade to SuperGrok" and "Upgrade to SuperGrok
+  Heavy"; a restricted command said it "requires SuperGrok". The buttons already
+  pointed at chutes.ai/pricing — the fork had rebranded where they *go* and left
+  what they *say*. This one predates the re-base; v0.4.3 carries the same strings.
+- The screen-mode settings described opening "plain grok", the welcome gate read
+  "SuperGrok subscription required", and the feedback prompt opened with "You've
+  been using Grok Code productively!".
+
+Rust identifiers, crate names, telemetry event types and model ids such as
+`grok-4.5` are deliberately untouched: `AGENTS.md` keeps them so upstream diffs
+stay readable, and a model name is data rather than branding.
+
+The wordmark's hash is now pinned by a test, so a merge that takes upstream's
+side there fails instead of shipping. The loss was silent by nature: nothing
+compiles differently, no test read the bytes, and the only symptom was on screen.
+
+### Security
+
+- **The `agent serve` token comparison no longer rests on a function that
+  disclaims the property it was chosen for.** It used
+  `ring::constant_time::verify_slices_are_equal`, which ring now deprecates as an
+  "internal function not intended for external use with no promises regarding side
+  channels" — while the reason for calling it at all is that `==` on `&str` returns
+  at the first differing byte, and over a socket with no rate limit that leaks the
+  token one byte at a time. It now uses `subtle::ConstantTimeEq`, which is
+  maintained for this and also resists the compiler folding the comparison back
+  into an early return. No new code enters the build: `subtle` was already in the
+  graph through rustls, so the lock file moves by one line.
+
+### Fixed
+
+- **`--help` had upstream's branding back in it.** The re-base took upstream's
+  wording over the fork's in five places a user reads, three of them flag *names*:
+  `--grok-ws-origin` and `--grok-ws-url`, which 0.4.3 spelled `--chutes-ws-*` and
+  kept hidden, so the re-base both renamed them and put internal plumbing into the
+  top-level help; `--xai-api-base-url`, described as "the public xAI API base URL"
+  when it overrides the Chutes inference base URL; the positional-prompt example,
+  which read ``grok "fix the bug"`` beside a `chutes-build` example on the same
+  line; and the `screen_mode` help, which said "To default plain `grok` to
+  minimal". Found by installing the published 1.0.0 the way a user gets it and
+  reading every help surface — the step the release procedure asks for and which
+  had not been done. `leader/mod.rs` passes those flags to the child process, so
+  the rename covers it too.
+
+### Repository and CI
+
+- **`xai-grok-shell --lib auth::` runs on Windows.** It failed 24 there, and the
+  CI step had never executed at all, because the pager step above it always failed
+  first. A provider command goes through `cmd /C` off Unix — deliberately, for
+  exit-code propagation — while the fixtures were POSIX one-liners. They now drive
+  `auth-provider-fixture`, a real helper invoked with `args`, so no shell
+  interprets them. Two lock tests read the lock file through a second handle while
+  holding it, which Windows refuses; they read through the holding handle now, as
+  the product does.
+- **The Linux job reaches its end.** It had not passed in the last twenty runs, so
+  four steps below the failure — auth and session integration, agent construction
+  and bundled skills, Chutes-native tools, and clippy — had not run either. Behind
+  them were a banned `tokio::process::Command::spawn` in a test the ban does not
+  describe, and a doc comment separated from the function it documents.
+- **That job's 60-minute limit was sized for the broken state.** The first run to
+  reach the end spent 59.7 minutes on work that passed and was killed during the
+  cache *save* — which left the next run cold, slower, and killed in the same
+  place. Raised to 90, matching Windows. Measured twice since at 65 and 67 minutes:
+  the cost is roughly 45 minutes of tests plus 11 of clippy, not compilation, so a
+  warm cache moves it very little and the headroom is about a quarter.
+- **All five CI jobs pass.** Windows had been red since 1.0.0 landed and Linux had
+  not finished in over twenty runs; this is the first complete green run.
+- `RUSTSEC-2026-0249` is recorded in `deny.toml`: `smartstring` is unmaintained —
+  archived, not vulnerable — and reaches this tree only as a non-optional
+  dependency of `rhai`, whose latest stable we already use, so no bump closes it.
+  It turned the dependency job red on a documentation-only commit, an hour after
+  the same check passed, because that job reads the live advisory database.
+- A flaky history-delivery test asked for a repaint and a result in one condition;
+  it fails when the daemon is *fast* enough to answer before the eager snapshot,
+  which is why widening its deadline had not helped.
+
 ## [1.0.0] - 2026-08-07
 
 Chutes Build is re-based onto `xai-org/grok-build` 1.0.0 (`afbc0fb`) and adopts
@@ -99,6 +226,47 @@ upstream instead:
   578. Two were real defects rather than test bugs: the trust hole above, and a
   home-directory guard no test on Windows could reach.
 
+### Fixed (Windows, and these were the product)
+
+The pager's Windows suite had sixty-six failures. Most were fixtures written for
+POSIX, but five were defects users would meet:
+
+- **`doctor fix` could not apply anything.** The managed-config writer opened the
+  parent directory as a file, to `sync_all` it after the rename. That sync is
+  Unix-only — Windows has no durability barrier for a directory — so off Unix the
+  handle was captured and never read, and Windows cannot produce one at all:
+  `File::open` on a directory needs `FILE_FLAG_BACKUP_SEMANTICS`, which `std` does
+  not set. Every fix planned, then failed to write, reporting "access denied"
+  against the directory rather than the file.
+- **No file path written in agent prose was clickable.** The scanner that turns
+  paths into `file://` overlays matched `~?/…` only, so `C:\Users\me\x.md` was
+  never recognised. Only tool headers worked, because those receive the path
+  directly instead of finding it in text.
+- **Tab completion in the extensions modal destroyed the path.** It rebuilt the
+  directory prefix by looking for a `/`; a Windows path has none, so completing
+  `C:\src\plugin-s` replaced the whole field with `plugin-source`. The directory
+  listing, gated on the text ending in `/`, never triggered either.
+- **The memory-search header showed `\MEMORY.md`.** The path shortener looked for
+  `/` alone, so the separator after the memory root survived — and a nested result
+  was not shortened at all, painting the whole `\xai-…\sessions\…` tail.
+- **A test fixture named `nul` proved nothing**, because on Windows that name is
+  the null device wherever it appears: the write went nowhere and the NUL-byte
+  refusal it existed to check was never reached.
+
+### Fixed (releases carried an unstripped binary)
+
+`release-dist` keeps symbols on purpose, for sidecars extracted "before stripping
+post-build" — and that post-build strip had never been written. The npm packages
+therefore shipped the profile's full DWARF: `linux-arm64-gnu` reached 938 MB
+unpacked and the registry refused it outright with `413 Payload Too Large`.
+Stripping now happens between the build and the smoke test, so the run check, the
+package, its checksum and the release asset all see the binary that ships. Linux
+falls from ~890 MB to ~130 MB; Windows needs none, since MSVC keeps debug info in
+a separate `.pdb`.
+
+The macOS packages for this version were published before that fix and are larger
+than the rest; they cannot be replaced, because an npm version is immutable.
+
 ### Authentication
 
 Upstream ships an OAuth application everyone signs in through, so its

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "chutes-build",
-  "version": "1.0.0",
+  "version": "1.0.2",
   "description": "Privacy-first, open-source coding agent for the Chutes ecosystem",
   "license": "Apache-2.0",
   "author": "Michael Gasperini (Mikesoft)",
@@ -37,12 +37,12 @@
     "check": "npm test && npm run verify:release && npm pack --dry-run"
   },
   "optionalDependencies": {
-    "chutes-build-darwin-arm64": "1.0.0",
-    "chutes-build-darwin-x64": "1.0.0",
-    "chutes-build-linux-arm64-gnu": "1.0.0",
-    "chutes-build-linux-x64-gnu": "1.0.0",
-    "chutes-build-win32-arm64": "1.0.0",
-    "chutes-build-win32-x64": "1.0.0"
+    "chutes-build-darwin-arm64": "1.0.2",
+    "chutes-build-darwin-x64": "1.0.2",
+    "chutes-build-linux-arm64-gnu": "1.0.2",
+    "chutes-build-linux-x64-gnu": "1.0.2",
+    "chutes-build-win32-arm64": "1.0.2",
+    "chutes-build-win32-x64": "1.0.2"
   },
   "keywords": [
     "ai",