24da72b7f4
All checks were successful
PR Check — Frontend / frontend (pull_request) Successful in 1m55s
REVIEW.md, from the suggestions of the first review of #460: - stacked-PR pitfall: fs_commands.rs compiles two CSV files of src/__fixtures__/samples/ through include_str!, outside the paths of check-rust; - high level: .claude/settings.json and .mcp.json, a pull_request_target trigger, an install step that changes the toolchain or the PATH (the check-workflow list is now given as examples of the principle), a lock origin whose host or scheme changes even with a new version, and a diff that removes or bypasses a consent (price consent lives on the front); - db.ts and dataExportService.ts stay normal (Max's decision of 2026-10-18), and the data zone now names the lock, the profile switch and the restore; - release zone: cargo-xwin and the Rust toolchain, installed unpinned at each tag, also run with the signing key; - windows-sys guard: EXPECTED joins CRATES and PIN; - identifier: changing it orphans the databases and the app_data_dir files (license key, activation token, token fallback); the keychain service is a constant and does not follow. scripts/review-levels.py is the calibration script of the PR body, now in the repo: pages of 50 files read until an empty page (the instance caps pages at 50), the new rules above, comment lines ignored by the workflow checks, and --check, which compares its patterns with the Haut table without network access. Fresh run: 3/28/8 on the 39 reference PRs and 6/33/12 on the 51, unchanged. Refs #456 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> |
||
|---|---|---|
| .. | ||
| build-latest-json.sh | ||
| build-latest-json.test.mjs | ||
| check-latest-json.jq | ||
| review-levels.py | ||