perform opportunistic cleanup.
- **Keep the docs true.** When documentation disagrees with code, verify the code and fix the stale documentation in the same task. Update a topic whenever a change
JAVA-XXXX` matching the Jira ticket (e.g., `JAVA-6143`)
- **Commits:** Keep commits logical and reviewable — each commit should be a coherent unit of change
- **TODO comments:** Must reference a Jira
code
- Do not: modify the C API binding layer without understanding the libmongocrypt contract
## Key Packages
- `com.mongodb.crypt.capi` — mongocryptd C API bindings (JNA) — **security-critical, do not modify without human
review
totals, never their sum.
- Automatic approval applies only to external PR workflow runs, not codereview, merging, or publishing. Agents updating this guide must not remove or weaken these rules
Cycles
For a given task, you should:
1. Research. Search the web, read existing code, look up system/dependency headers / implementations of related functionality. Figure out best practices and common pitfalls
source of truth. If this guide disagrees with the code, follow the code and update the guide; tests document expected behavior and should change only when behavior intentionally changes
bundle is the VM code the route carries as an inline string, while the code hosting it sits in the framework output.
**The gate does not cover the world adapters
compiled
`dist/index.js` for a `browser` target and asserts the output excludes registry-only code,
proving the package.json `sideEffects: false` claim against real compiled output rather than
merely asserting it — plus
command like `ls src/shared/` over a hand-maintained one); verify claims against the code before writing them; delete anything that has gone stale — an outdated note is worse than none
agent plugins (coding-agent skills+MCP bundles or OpenClaw/Hermes-style harnesses), AI framework packages (LangChain/LlamaIndex-style), or direct application clients via apify-client. Use when planning, creating, or reviewing an integration that
CopyPrompt` when a page should give readers a prompt they can copy into a coding agent.
## Routing and proxy guidelines
- Keep App Router route files as thin adapters around package
public type changed). Sample
fixtures and AGENTS.md edits don't.
## Resources
- [Ship a GitHub codereview bot with Hono and Redis](https://vercel.com/kb/guide/ship-a-github-code-review-bot-with-hono-and-redis) — Walks through building a GitHub
requires them.
## Change Traceability Review
- Use `.agents/skills/change-traceability-review/SKILL.md` as the Story/Spec/Test/Risk evidence-chain review guide, not a code-style guide.
- Before review, merge, or commit of a non-trivial change
every branch, commit, PR, and review comment as **public**.
Never put real secrets, credentials, tokens, private URLs/hostnames, customer
data, or production payloads in code, tests, docs, comments, examples, commits