3 Commits
Author SHA1 Message Date
Aleksander DygońandClaude Opus 5.5 03c2ff34c2 Remove code comments and add the no-comments rule (#12604)
* Remove code comments and add the no-comments rule

Remove the comments from first-party code and configuration files:
TS/JS, JSX, CSS, SQL migrations, Swift, Kotlin, Gradle, shell,
Docker, systemd, Nix, YAML, TOML, JSONC and GritQL.

Keep only what a tool reads: license headers, shebangs, compiler
and lint directives, JSDoc types in plain .js files, generated file
headers, GritQL scope lines, the install-server.sh help text and the
openbot-boat-pre-stop marker. Vendored code, fixtures and released
schemas keep their comments.

Add the rule to AGENTS.md, and change the docs that asked for
comments. Add two i18n keys that only comments named to
RELEASED_SOURCE_KEYS.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Keep comments that are data in strings

The benchmark task files in opencode-free-models-bench.ts tell the
model what each function must do. The sample file and HTML page in
the two stories are display content. Put their comments back.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Keep released migrations and mobile native inputs unchanged

check:migrations compares each released migration with v0.73.0 byte
for byte, so restore src/backend/migrations. A change to a native
build input of apps/mobile makes a new runtime version, so restore
those files and the extra fingerprint sources.

List these files and the comment markers that a tool reads in
AGENTS.md. Remove the last requests for comments in
src/renderer/AGENTS.md.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-19 12:19:28 +01:00
Aleksander DygońandClaude Opus 5.5 5a0d304c5f Retry network failures in the macOS release (#2252)
* Retry network failures in the macOS release

Apple's ticket service and GitHub downloads sometimes drop the connection on the
hosted macOS runners. Releases v0.38.1 to v0.40.0 then needed 2 to 4 attempts.

- Build step: also retry when stapler or a download loses the connection.
- Signature check and Host installer: give stapler five attempts.
- Runtime downloads: retry a network error, HTTP 429 or 5xx two times.
  The SHA-256 checks after the download do not change.

Refs #2249

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Use the retrying download for all runtime installers

The Claude, Codex and cua-driver installers fetched their files inline, so a
dropped connection still stopped the release. They now use the shared
download(). The checksum checks do not change.

Also cancel the body of a failed response before the next attempt, and retry
the macOS build only on the network errors that releases showed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-16 12:59:29 +02:00
NBandClaude Opus 5.5 e26b637ad0 Move shared runtime installer helpers to one module (#1458)
* Move shared runtime installer helpers to scripts/runtime-install.ts

The Claude, Codex, Grok, cua-driver and remote desktop installers had
copies of the same helpers. Put one copy of each in
scripts/runtime-install.ts:

- installValidatedTree (the remote desktop installer calls it for the
  platform/architecture directory)
- isCurrentInstallation, which now takes the verify function
- download (Grok and remote desktop)
- safeArchivePathParts, the common safety part of validateArchivePath
- escapeRegExp

Error messages, user agents and install paths do not change. The remote
desktop download now sets redirect: "follow" explicitly; that is the
fetch default, so the result is the same.

The cua-driver and pin-cua-driver downloads keep their own copies,
because their error messages (and the pin user agent) are different.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

* Keep remote-desktop-runtime-release.ts unchanged

The remote desktop workflow requires a recipeVersion increase when this
file changes. That increase changes the input digest and starts a new
native build and release. A refactor must not do that, so this file keeps
its own validateArchivePath.

Also run the cua-driver workflow when scripts/runtime-install.ts changes,
because install-cua-driver.ts now imports it.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

---------

Co-authored-by: Claude Opus 5.5 <noreply@anthropic.com>
2026-10-06 17:07:29 +02:00