Notebooks should execute without errors
- README files should be clear and accurate
- Follow existing code patterns in the repository
- Maintain consistency with other lessons
## Additional Notes
### Common Gotchas
1. **Python
career-ops project (parent/sibling repos, other codebases on the machine), knowledge from other Claude Code projects on the same machine, and cross-session inferences not written into an in-scope
finds the user's files, and it keeps your real pipeline out of it.
## Reviews and scope
`web/` is maintained as first-party: functional and correctness fixes are very
welcome
summing per-turn assistant usage**, not `result.usage` (last-turn only in current Claude Code). See `docs/benchmarks/call-sequence-analysis.md`.) The mechanism that drives everything here: **an agent falls back to Read/Grep the instant
REAL `senpi` binary through the drivers in `packages/omo-senpi/scripts/qa/`, which build their own isolated `SENPI_CODING_AGENT_DIR` and IGNORE a caller-provided one, so the real `~/.senpi/agent` is NEVER written
template asks how the *code* was written; drafting the description with a model is fine. The disclosure is never held against you, it tells a reviewer where to look. Silence
enforces squash-only merges, linear history, no deletion, no force-push, and one approving review. Two status checks belong in its `required_status_checks` rule:
| Context | Posted
scripts/generate-plugin-index.py --check
```
5. Open the PR, fill in their template, and wait for code-owner review.
To roll out a later update in their catalog, bump the pinned
this file, so edit `AGENTS.md` only. Local-only overrides (`CLAUDE.local.md`, `AGENTS.override.md`, `.claude/settings.local.json`) stay ignored.
## Code Conventions
- No Chinese comments in any source (Rust / TypeScript / any file). Comments and identifiers
remains English-only and is intentionally outside the machine-translation
pipeline as well.
### code/
- Runs end-to-end and exits 0 on the canonical command for the language.
- Self-terminating
changes to agent-loop behavior must be implemented and tested in both paths. When reviewingcode, check whether a change to either path also applies to the other and flag
Representation)
Located in `compiler/ir/`. Backend IR is used by all targets for:
- Lowering (transforming code to target-friendly form)
- Optimization
- Serialization to klibs
Backend implementations:
- `compiler/ir/backend.jvm/` - JVM backend
- `compiler/ir/backend.js/` - JavaScript
request already addresses the issue, do not submit a competing one without maintainer agreement.
## CodeReview Rules
For security reviews of Ruff and ty runtime changes, use the
[threat models
Authorship, labels, safety, review, and PR requirements. |
## Runtime entry points
When debugging or changing one integration, begin with its entry point:
| Runtime | Read first |
| --- | --- |
| Claude Code | `.claude-plugin/plugin.json`, `hooks/hooks.json
tool — not a grep, a partial skim, memory, or a summary — before planning, coding, or reviewing, and then follow every rule in it. A task touches billing when it meets