# AGENTS.md

These rules apply to the entire Lumbridge repository.

## Product boundary

Lumbridge is a terminal/workspace runtime and ACP client. It may host, supervise,
and observe coding harnesses, but must not silently impersonate them, harvest their
private credentials, or claim provider quota data that cannot be verified.

**Credential use is narrow and named.** A harness's stored credential may be read
only to ask that same provider a documented question about the user's own account,
and only where the answer cannot be obtained another way. Under that allowance a
credential must never be persisted, logged, copied into application state, written
to a crash report, or passed as a command-line argument; it must be released as
soon as the request it authorises has been made; and any request it authorises must
identify Lumbridge as the caller. A refresh token is never used — renewing a
credential is the harness's job, not Lumbridge's. Every such use is named in a
decision record, and each is switchable off by the user. Reading a credential for
anything other than a use recorded that way is out of bounds. See decision 0016.

## Research boundary

Upstream repositories are cloned outside this Git repository under the desktop
workspace's `Research/` directory. They are references, not vendored code.

- Do not copy upstream implementation code without an explicit license review.
- Record the source repository and relevant license for any adapted design.
- AGPL/GPL and unlicensed repositories may be studied for behavior and UX only
  unless the project deliberately changes its licensing strategy.

## Engineering rules

- Keep provider, harness, protocol, terminal, persistence, and UI boundaries
  separate. A provider is not a harness and ACP is not a provider API.
- Preserve a PTY fallback. ACP adds structure but must not be required to open a
  normal shell or run an arbitrary CLI.
- Keep secrets out of SQLite, logs, crash reports, command-line arguments, and
  repository files. Store only opaque secret references in application state.
- Usage values must include a provenance and confidence classification.
- Avoid platform behavior hidden behind scattered `cfg` blocks; isolate it in
  platform adapters with shared contract tests.
- No telemetry is enabled by default. Any future telemetry must be documented,
  opt-in, redacted, and independently disableable.

## Verification

Before committing Rust changes, run:

```bash
./scripts/ci.sh
```

Keep `bacon` running during development. Tests must use synthetic fixtures; real
agent transcripts, subscription state, private source, and credentials are never
test data.