nessarandClaude Opus 5.5
acdb19352a
Before the protocol, time the frozen engine on the two-year scenario, best of three, and fail any scenario whose mean planning time exceeds its multiplier times that calibration. Multipliers come from development-machine ratios with about 1.5x headroom until #286 tightens them. The 300-second timeout stays only as a hang guard. The benchmark keeps running on push and pull_request events because the push run gates image publication. This replaces the absolute 300-second acceptance protocol named in #78. Refs #285 Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
37 lines
2.4 KiB
Plaintext
37 lines
2.4 KiB
Plaintext
# Agent Rules and Verification Constraints
|
|
|
|
All AI agents (including Cline, Antigravity, Cursor, and Copilot) must adhere to the following rules before declaring a task complete:
|
|
|
|
1. **Test Coverage (>= 80%)**:
|
|
- The overall project code coverage (Statements, Lines, and Functions) must be maintained at **80% or higher**.
|
|
- Verify coverage by running:
|
|
```bash
|
|
bun scripts/generate-langs.js
|
|
NODE_OPTIONS=--max-old-space-size=2048 bunx vitest run --coverage --maxWorkers=1 --exclude='src/app/benchmark/**'
|
|
```
|
|
- If your changes introduce new code or modify existing code in a way that drops the coverage below 80%, you must write appropriate unit tests in `.spec.ts` files to bring it back up.
|
|
|
|
2. **Code Formatting (Prettier)**:
|
|
- All code files must be correctly formatted according to the project's Prettier config before finishing.
|
|
- Run the formatter with:
|
|
```bash
|
|
bun run format
|
|
```
|
|
|
|
3. **Successful Build**:
|
|
- The project must always build successfully for production without compilation or bundling errors before ending.
|
|
- Verify the build with:
|
|
```bash
|
|
bun run build
|
|
```
|
|
|
|
4. **CI Checks**:
|
|
- You must execute the local validation commands before completing your task. The Gitea workflow is `.gitea/workflows/ci.yml`; owner activation is tracked in issue #268, and local checks do not satisfy the migration gate. All of the following commands must pass:
|
|
- **Linting check**: `bun run lint` (or use `bun run lint:fix` to resolve auto-fixable issues)
|
|
- **Formatting check**: `bun run format:check`
|
|
- **TypeScript Type check**: `bunx tsc --noEmit -p tsconfig.app.json` and `bunx tsc --noEmit -p tsconfig.spec.json`
|
|
- **Unit Tests and Coverage**: generate the language registry, then run the coverage command in rule 1, matching the Gitea functional-test job.
|
|
- **CI policy and publication**: `node scripts/ci-policy.test.mjs` and `node scripts/ci-image.test.mjs`
|
|
- **Production Build**: `bun run build -- --configuration production`
|
|
- The separate performance benchmark is a required CI job with a relative gate: each scenario's budget is a multiple of the frozen engine's two-year calibration measured in the same run. Run it outside coverage with `NODE_OPTIONS=--max-old-space-size=2048 bunx vitest run src/app/benchmark/ --maxWorkers=1` when verifying performance; see `docs/benchmark/README.md`.
|