2 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
NBandClaude Opus 5.5 04643172f3 Make dev scripts reject unknown options (#1427)
* Make dev scripts reject unknown options

Add one strict parser (`node:util` `parseArgs`, `strict: true`) in
`scripts/script-arguments.ts`. `dev:seed`, `dev:reset`, `dev:verify`,
`dev:bench`, and `dev:automation` use it. `--help` prints the usage and
exits 0 before any side effect. An unknown option prints the usage and
exits 2. Before this change, `dev:reset --help` deleted the dev profiles.

`dev:reset` now refuses while a profile has a live `SingletonLock`. It
checks all profiles before it deletes one, and prints each target before
it deletes it.

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

* Redact rejected arguments and detect a Windows dev profile lock

The error for an unknown argument repeats the typed value. Pass it
through redactText, because the value can be a token.

Chromium on Windows holds <profile>/lockfile, not SingletonLock. On
win32, treat lockfile as a live profile, so seed and reset do not
delete an open profile.

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

* Exit 2 when dev:automation gets an extra positional

cli.ts threw for an extra positional, and its catch set exit code 1.
readScriptArguments now takes maxPositionals and rejects the extra
positional with the usage and exit code 2, as for an unknown option.

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

---------

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