AkurAI-Build

Latest change e11509261b6a2aa4ea9ef67250b0be01bfb4f53b - Restore paths swept in from uncommitted WIP by Ólafur Búi Ólafsson

---
name: pibun-read-only-health-check
description: Use after rebuilding Titan or restarting pi-bun services to perform a strictly read-only health check.
---

# pi-bun read-only health check

Use this procedure after a Titan reformat, service restart, or AkurAI platform recovery. Do not start, stop, restart, repair, or mutate anything.

## 1. Check systemd units

Inspect, without changing state:

```bash
systemctl status akurai-build.service --no-pager --lines=8
systemctl --user status omp-workbench.service --no-pager --lines=8
systemctl status akurai-node-tunnel.service --no-pager --lines=8
systemctl is-active docker.service
```

Record exact active/inactive state and recent failure lines. For the tunnel, treat `Permission denied (os error 13)` as a concrete host-permission failure, not a generic outage.

## 2. Probe Workbench locally

```bash
curl -sS -o /dev/null -w 'workbench_local=%{http_code}\\n' http://127.0.0.1:4173/health
curl -sS -o /dev/null -w 'workbench_root=%{http_code}\\n' http://127.0.0.1:4173/
```

HTTP 200 on both confirms the local Workbench surface responds.

## 3. Use read-only MCP checks

Run:

- `mcp__akurai_tasks_system_doctor` with `{}`
- `mcp__akurai_notes_system_status` with `{}`
- `mcp__akurai_passvault_system_status` with `{}`

Report returned health fields and bounded counts. Never use mutation tools.

## 4. Probe public roots

Probe only known service roots. If TLS uses a self-signed certificate on the Build host, use the existing sanctioned read-only probe mechanism or an explicitly certificate-skipping GET only to establish reachability. A service root returning HTTP 200 proves reachability. A `/health` endpoint returning 404 means that path is absent; do not label the service unhealthy without another failure signal.

## 5. Docker caveat

If `docker ps` returns permission denied for `/var/run/docker.sock`, report that the daemon may be active but container inventory was unavailable to the current user. Do not alter groups, socket permissions, or service state.

## Output

State clearly:

- healthy services and evidence;
- failed or inactive units with exact errors;
- reachability versus endpoint availability;
- any inspection limitations;
- that no mutations were performed.