Operator-only

Ch.4 Runtime Runbook

Versioned source: docs/ch4-runtime-runbook.md. This page serves the `/docs/ch4-runtime-runbook` target used by runtime health reports.

Operator entry point: Ch.4 运行健康.

Health vocabulary

Operators interpret every row as `ready|warning|blocking`. Doctors only receive safe recovery guidance and support codes.

执行模式

确认 Ch.4 使用本地受控执行模式。

Rscript

确认 R 执行和图形渲染依赖可用。

沙箱包装器

确认受信任 wrapper 已通过隔离探针。

资源限制

确认资源上限满足已登记 recipe。

Recipe registry

确认 allowlisted recipe 已加载。

临时目录权限

确认 scoped 临时目录可创建并清理。

Smoke readiness

确认 local-process smoke 或 CI-equivalent smoke 已解释。

Configuration placeholders

Use placeholders in support notes and screenshots: <RSCRIPT_BIN> and <SANDBOX_WRAPPER>. Keep real values in operator configuration only.

Smoke readiness

Run these checks before marking Smoke readiness as ready:

bash scripts/verify-ch4-sandbox-wrapper-macos-dev.sh
bash scripts/verify-ch4-sandbox-wrapper-docker.sh
CH4_RECIPE_INTEGRATION_SMOKE=1 npx vitest run src/lib/ch4-recipes/__tests__/local-process-smoke.test.ts

Complete Ch.1 to Ch.5 contract

Phase 43 defines runtime support: Ch.1 PICO, Ch.2 evidence review, Ch.3 protocol/QC readiness, Ch.4 runtime health and accepted result package, then Ch.5 caveat-preserving writing. Phase 44 owns final controlled-trial evidence.

Redaction boundary

Support material may include health row keys, opaque support codes, placeholders, and rerun commands. Do not include real local paths, environment values, raw execution output, patient-level rows, internal handles, source identifiers, package identifiers, or private artifact references.