standalone autoloader (`src/autoload.php`) for non-Composer installations.
- **Distribution Cleanliness**:
- All development, CI, test, documentation, and agent configuration files MUST be listed with `export-ignore` in [`.gitattributes`](.gitattributes) so Composer `--prefer
project-facing work and communication.
- Write all source code, comments, tests, fixtures, documentation, examples, configuration text, scripts, and user-facing strings in English.
- Use English for every GitHub artifact: issue
Named-vault routing (`@work update wiki`) works in every agent above, because `@name` is documented in the shared skills and bootstrap context that all of them load.
## Manual setup
Only
automatically. Do **not** add portless as a project dependency; it must be installed globally.
## Documentation
For any user-facing change (new feature, option, API change, bug fix, etc.), update
coding assistants (Kiro, Cursor, Claude Code, GitHub Copilot). For the human-readable documentation, see [docs/](./docs/README.md), [README.md](./README.md), or [docs/tutorial.md](./docs/tutorial.md).
This project is an **event-driven insurance claims processor
with `__enter__` and
`__exit__`, not `contextlib.contextmanager`. For destructors use `__dealloc__`
where possible, otherwise `__del__`.
### Documentation
The entirety of the public API should be documented in `api.rst
size` option. Managed
pools cannot be right-sized and are not checked.
### Document exemptions
When a call is deliberately exempt -- most often because it sits inside
`pytest.raises` and no pool
metapackage layer in the `cuda-python`
monorepo.
## Scope
- `cuda_python` is primarily packaging and documentation glue.
- It does not host substantial runtime APIs like `cuda_core`,
`cuda_bindings`, or `cuda
fast search tool inside a repository. It complements the
[README](README.md), which documents every flag; this file covers the few
things an agent has to get right.
## The mental model
agnostic, running locally, on Slurm, or on Ray clusters.
See [README.md](README.md) for detailed documentation on terminology, pipeline blocks, executors, and usage examples.
## Python Environment
- **Python Version:** 3.10+
- **Package Manager
Project Agent Guidelines
This document provides guidance for AI agents and contributors working on the
docker-agent codebase.
## Code Quality Standards
- Write clean, self-documenting code with minimal comments
- Follow
them: prune
narration, repeated rationale, and implementation history as you touch them.
- Add standalone documentation only for a durable user workflow, public
contract, or cross-cutting invariant. Keep implementation details
This is a reconstructed source tree, not pristine upstream. Prefer minimal, auditable changes, and document any workaround added because a module was restored with fallbacks or shim behavior
broadcast `[lane-claim]` to `AGENT:*` before any git-tracked edit; operator-suppressed broadcasts → the documented direct-DM fallback (peer-role/post-review-pickup); suppression is not a halt-state. Enforcement: `pull-request-workflow.md
rejecting something the driver doesn't support). Only the exception type of a supported, documented operation is part of the contract.
## Async conventions
- **Paired sync/async public surface.** Public methods that
over a raw byte buffer — prefer them for read-heavy paths where allocation matters.
- **Document structure.** `BsonDocument` keeps an ordered `List ` and lazily builds a name → index dictionary once
methods.
**Render is where bugs hide.** `Render` receives `RenderArgs ` carrying the active serializer registry, document serializer, and translation options. A definition rendered with the wrong document serializer produces silently-wrong