name: luci-ci
description: "Configure or diagnose Luci CI for ci.bugabinga.net, including .ci/*.kdl workflows, run status/logs, caches, publishing, schedules, and push path filters. Also use after pushing a repository with .ci."
path: .ci
Luci CI
Before configuring or diagnosing Luci, fetch the current machine reference at https://ci.bugabinga.net/llms.txt; it is authoritative for grammar, behavior, CLI, routes, and security constraints.
If that reference cannot be fetched, report the failure and inspect bugabinga.net/services/luci source when available; do not guess syntax or reuse remembered fields. Human reference: https://ci.bugabinga.net/docs.
Work only on repository configuration and run diagnostics; do not modify Luci infrastructure or implementation unless explicitly asked.
Read repository instructions and every direct .ci/*.kdl file before editing; keep orchestration thin and delegate to the repository's canonical CI command, running it locally when possible.
Access the CLI with ssh ci ...$args; ssh ci status and ssh ci help are read-only. Status, repository, run-detail, log, and docs commands are read-only.
After a push, find the run whose revision matches each pushed commit (ssh ci repo <repo>, then ssh ci show <run-id> for the full proquint) and show https://ci.bugabinga.net/runs/<full-proquint>; short displayed prefixes become ambiguous.
No matching run → say so; path filters or missing push triggers may skip it.
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.
---
name: luci-ci
description: "Configure or diagnose Luci CI for ci.bugabinga.net, including .ci/*.kdl workflows, run status/logs, caches, publishing, schedules, and push path filters. Also use after pushing a repository with .ci."
path: .ci
---
# Luci CI
- Before configuring or diagnosing Luci, fetch the current machine reference at <https://ci.bugabinga.net/llms.txt>; it is authoritative for grammar, behavior, CLI, routes, and security constraints.
- If that reference cannot be fetched, report the failure and inspect `bugabinga.net/services/luci` source when available; do not guess syntax or reuse remembered fields. Human reference: <https://ci.bugabinga.net/docs>.
- Work only on repository configuration and run diagnostics; do not modify Luci infrastructure or implementation unless explicitly asked.
- Read repository instructions and every direct `.ci/*.kdl` file before editing; keep orchestration thin and delegate to the repository's canonical CI command, running it locally when possible.
- Access the CLI with `ssh ci ...$args`; `ssh ci status` and `ssh ci help` are read-only. Status, repository, run-detail, log, and docs commands are read-only.
- After a push, find the run whose revision matches each pushed commit (`ssh ci repo <repo>`, then `ssh ci show <run-id>` for the full proquint) and show `https://ci.bugabinga.net/runs/<full-proquint>`; short displayed prefixes become ambiguous.
No matching run → say so; path filters or missing push triggers may skip it.
- 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.