gatekeeper with a different layout.
- Public modules are explicit subpath exports in [`package.json`](package.json). Document new public
symbols with JSDoc and add the subpath to the README inventory.
## Documentation ownership
extract logic to separate modules
- Use Hono's context methods (`c.json()`, `c.html()`) for responses
## Documentation
- `README.md` - User-facing documentation (setup, configuration, usage)
- `AGENTS.md` - This file, for AI agents
Development documentation
ARCHITECTURE.md`, `PITFALLS.md` |
**Capabilities:**
- Web search for current ecosystem information
- Context7 MCP integration for library documentation
- Writes research documents directly to disk (reduces orchestrator context load)
---
### gsd-phase-researcher
**Role:** Researches
proceed**. Return a short explanation of what is missing.
### Project Guides
Follow the documentation on contributing too and extending garak. See:
* For selecting contributions: `docs/source/contributing.rst`
* For writing code: `docs/source/extending.rst`
* When
Model Context Protocol (MCP)
This repository contains the MCP specification, documentation, and blog.
## Contribution Policy for AI Agents
If you are an AI agent (Claude, GitHub Copilot, Codex, or similar
implementation. Understand what they do before deciding what we should do.
4. **Document what you found.** When creating a PR or closing an issue, link to the Next.js test, issue
exempt: query parameters carry tokens
and identifiers.
## Comments
Doc comments are the public API documentation. `pkg.go.dev` renders them, so
write for a reader who cannot see the implementation, and follow
skills must work outside a source checkout and use installed CLI help plus published documentation as their sources of truth.
- `.agents/skills/` contains internal contributor and maintainer workflows for developing OpenShell
workers project.
- If checked out as a submodule, be aware that there is additional documentation and context in the
root of that repository that is not present here. Look
validity until a promise settles and fd ownership under
`TAKE_OWNERSHIP` remain KJ's documented contracts, named at the `// Safety:` comments.
- **kj-rs-io is workerd's provider
with the test suite
in this directory. **The tests are the normative artifact**; this document
maps behaviors to the tests that assert them. Every test runs against the
C++ streams
with the test suite in this directory. **The tests are
the normative artifact**; this document maps behaviors to the tests that
assert them. Every test runs against the C++ streams
with the test suite in this directory. **The tests
are the normative artifact**; this document maps behaviors to the tests
that assert them. Every test runs against the C++ streams
with the test suite in this directory.
**The tests are the normative artifact**; this document maps behaviors to
the tests that assert them. Every test runs against the C++ streams
pinned by naming its flag in **both** configs.
Each suite's ` -cpp.wd-test` documents its pinned set with a one-line
reason per flag, and the suite's AGENTS.md tables
with — the test
suite in this directory. **The tests are the normative artifact**; this
document indexes every specified behavior to the test that asserts it. Both
the C++ implementation (`src/workerd/api/streams/encoding