Initial commit: SIC harness (backend, web, pi-adapter, configs, docs)

- pnpm monorepo: apps/api (Fastify + SQLite + SSE), apps/web (React+Vite), packages/shared, packages/pi-adapter
- Local auth (admin/webhook-runner roles) + Keycloak JWT ready
- Multi-session chat with reliable history (user persisted before LLM, assistant persisted after stream)
- Markdown knowledge base with /api/docs/search + /api/docs/:id
- YAML webhook catalog with backend-only execution, retry/backoff, audit (webhook_runs), and per-user rate limit
- Skills config (sre-on-call, blameless-postmortem, security-incident) injected into LLM system prompt
- LLM provider failover chain (config/models.yml fallback + LLM_FALLBACK_CHAIN override)
- Context-aware webhooks panel + backend id-mention safety net
- Per-message stats (time/duration/tokens/model), Markdown+GFM render, code & table copy/download buttons
- Vitest suite, end-to-end smoke test (scripts/smoke.mjs), per-session system prompt override
- /metrics Prometheus endpoint + /api/metrics JSON, request-id correlation
- dotenv with explicit repo-root path; envString/envNumber helpers (handles empty-string env)
- Runbooks + SOPs under knowledge/ in English; README, docs, and INDEX.md in English

knowledge/runbooks/service-restart.md

@@ -0,0 +1,32 @@
+---
+title: Service Restart Runbook
+tags: [service, restart, systemd, operations]
+owner: sre
+updated: 2026-06-15
+---
+
+# Service Restart Runbook
+
+## When to use it
+
+- The service is down or not responding to health checks.
+- Sustained performance drop that cannot be explained by load.
+- After a deploy that left the service in an inconsistent state.
+
+## Diagnosis
+
+1. Confirm the current state: `systemctl status <service>` or equivalent.
+2. Review the last 200 lines of the log.
+3. Check dependencies (DB, Redis, network).
+4. If there is no clear cause, escalate via the `service-restart` webhook.
+
+## Equivalent command
+
+```bash
+systemctl restart <service>
+```
+
+## Related webhooks
+
+- service-restart
+- log-tail