自動翻譯(co-op-translator.yml)
## 測試指導
### 測驗應用程式測試
```bash
cd quiz-app
# Run lint checks
npm run lint
# Test build process
npm run build
# Manual testing: Start dev server and verify quiz functionality
this repository.
## Development Commands
- **Build**: `npm run build` - Compiles TypeScript to JavaScript in dist/
- **Test**: `npm test` - Runs Vitest tests with ESM support
- **Type Check**: `npm run lint` - Runs TypeScript
step, for example for a small change or while iterating.
3. **A human then tested it themselves**: in the app, against the local relay
(through the app or `curl
target thread root:
```sh
buzz messages send --channel --reply-to \
--mention --content '!cancel'
```
## The tests that enforce this
- `lib/agentConfigCore.test.mjs` — field model per harness × scope, clearing
policy. Update when the capability
gotchas.
- **Modular pipelines** — see [modular.md](references/modular.md) for modular pipeline conventions, patterns, and gotchas.
- **Tests** — see [testing.md](references/testing.md) for test conventions: required test layers, tester mixins, and dummy-component rules.
- **Reporting
editing it. Check only verified checklist items; explain skipped or inapplicable checks in `Testing`.
## Code Quality
- No `any` unless absolutely necessary.
- **NEVER use `ReturnType<>`** — use the actual type name.
- **NEVER
agents MUST analyze the affected
`test/openapi-test` coverage and update the API IT scenario matrix, test
cases, and coverage registry in the same change set. If the functional path
cannot
process communication must go through the IPC bridge (`packages/desktop/src/preload/`).
See [docs/architecture/overview.md](docs/architecture/overview.md) for details.
## Testing
**Framework**: Vitest 4 (`vitest.config.ts`). Project coverage target is ≥ 80%; ordinary changes should add focused tests
SECURITY.md` and `SECURITY-NOTICE.md` — when touching parsing, files, subprocesses, generated content, or dependencies.
5. Existing tests closest to the code being changed.
For the progressive-disclosure research/evaluation initiative, also read:
- `docs/research/progressive-disclosure-evals.md
from the OpenAI API schema. Follow `CONTRIBUTING.md` before
changing generated files. Handwritten policy, automation, tests, and examples
should remain small and should not alter exported SDK APIs unless the change
Agent Instructions
Project context (architecture, commands, conventions, tests) is in `CLAUDE.md`. This file holds the rules for every coding agent working in this repository.
## Non-Interactive Shell Commands
limit.
- **Naming an interactive element has a cost:** named participants are skipped by hit-testing while a transition runs ([csswg#10930](https://github.com/w3c/csswg-drafts/issues/10930)) — clicks and hover fall through
work with the cognee repository: how it’s organized, how to build, test, lint, and contribute. It mirrors our actual tooling and CI while providing quick commands for local development
Manager**: Use `pnpm` instead of `npm` for Node.js package management in this repository.
## Build & Test
> [!IMPORTANT]
> **Test Coverage**: The `codecov/patch` check requires that new or modified lines are covered
skill references, compatibility mirrors, or validation.
- `bug-fixing`: fixing a defect and choosing regression tests.
- `cross-sdk-parity`: aligning TypeScript and Python behavior, generated client bumps, or API contract drift