---
name: luci-ci
description: "Create, edit, review, or diagnose Luci CI configuration for ci.bugabinga.net. Use for .ci/*.kdl files, failed or missing runs, run status, logs, caches, publishing, schedules, and push path filters."
path: .ci
---

# Luci CI

Before configuring or diagnosing Luci, fetch the current machine reference:

```text
https://ci.bugabinga.net/llms.txt
```

Treat that response as authoritative for grammar, behavior, CLI, routes,
and security constraints.
If it cannot be fetched, report the failure and inspect the current
`bugabinga.net/services/luci` source when available; do not guess syntax or
reuse remembered fields.
The human reference is `https://ci.bugabinga.net/docs`.

Work only on repository configuration and run diagnostics.
Do not modify Luci infrastructure or implementation unless explicitly asked.
Keep orchestration thin and delegate to the repository's canonical CI command.
Read repository instructions and every direct `.ci/*.kdl` file before editing.
Run the delegated command locally when possible.

Access the luci cli via:

```nu
ssh ci ...$args
ssh ci status
ssh ci help
```

Status, repository, run-detail, log, and docs commands are read-only.
Manual submissions and reruns mutate public CI state; do not execute them
without explicit approval.
Configuration changes take effect only after the selected commit reaches the
public repository.
Never claim a revision ran or deployed without matching live run evidence.