# Working under `dash/tray/`

The tray is a **display layer** ([`dash/AGENTS.md`](../AGENTS.md)).

## THE RULE

> **THE TRAY AND THE WEB DASHBOARD ARE DISPLAY LAYERS. NEITHER CONTAINS ISOLATED FEATURE
> LOGIC, SCHEDULERS OR JOBS. ALL LOGIC AND JOBS (REFRESH SCHEDULING, CLEAN, IMPORT, PAUSE)
> LIVE IN THE SHARED KYBERDASH APPLICATION (THE CLI ENGINE AND THE `kyberdash web` SERVER
> BUILT FROM IT) THAT BOTH SURFACES SHARE. BOTH SURFACES USE ONE DATASTORE (canon.db,
> resolved by dash/src/canon/paths.ts resolveCanonDbPath) AND ONE API LAYER
> (/api/kyber/*). NO AGENT OR DESIGN MAY VIOLATE THIS.**

Rule text and checklist: [`docs/rules/kyberdash-display-layer.md`](../../../docs/rules/kyberdash-display-layer.md).
Decision: [ADR 0033](../../../docs/adr/0033-kyberdash-surfaces-are-display-layers.md).
Architecture: [`docs/dash/architecture.md`](../../../docs/dash/architecture.md).

## Allowed here

- Rendering `ViewState`, the report, and what `/api/kyber/*` serves, plus the popover's own
  display preferences (selected harness, window of days, geometry).
- Loopback HTTP from Rust to the shared server, and invoking actions over it — a clean, an
  import, a pause, a shared setting. Asking the engine to act is not acting.
- Launching or attaching to the `kyberdash web` server named in `~/.kyberdash/server.json`,
  and killing only a server this process launched.
- Platform integration: the status item, autostart, window placement, IPC plumbing.

## Forbidden here

- A scheduler, a cadence or "is it due" check, or any timer that stands in for one. Polling
  to repaint the popover is display work; scheduling a job is not.
- Spawning CLI children to do a job (`refresh`, `clean`, `import-history`, `settings`,
  `otel`) — that is `JobHost` and `ReceiverHost` in `dash/src/jobs/**`, hosted by the
  server. `supervisor.rs` launching the server is the one legitimate process launch.
- Hosting the OTLP receiver, or a tray-local copy of any setting that belongs in
  `canon.db` metadata (`dash/src/settings/shared-settings.ts`).
- Value imports from `dash/src/**` in `dash/tray/ui/src/**` beyond the commented allowlist
  in `dash/src/architecture/display-layer.test.ts`; `import type` is always fine.
- Computing a domain result in the popover.

`dash/src/architecture/display-layer.test.ts` enforces all of this and runs in the test gate.

## Gates

Run each command from the repository root through the process watchdog, `scripts/proc-guard.sh run --`
([`dash/AGENTS.md`](../AGENTS.md#tests-that-start-processes)):

```bash
scripts/proc-guard.sh run -- npm --prefix dash run typecheck
scripts/proc-guard.sh run -- npm --prefix dash run lint          # already covers dash/tray/ui
scripts/proc-guard.sh run -- npm --prefix dash run test
scripts/proc-guard.sh run -- npm --prefix dash run check:reachable
```

The popover UI has its own gates after `npm --prefix dash/tray/ui ci`:

```bash
scripts/proc-guard.sh run -- npm --prefix dash/tray/ui run typecheck
scripts/proc-guard.sh run -- npm --prefix dash/tray/ui run test
scripts/proc-guard.sh run -- bash -c 'cd dash/tray/src-tauri && cargo fmt --check && cargo clippy -- -D warnings && cargo test'
```

`npm --prefix dash run lint` does not cover the Rust crate — `cargo fmt`, `cargo clippy` and
`cargo test` are yours to run for any change under `src-tauri/`.