docs(config): document the RMP_ENGINE flag in .env.example #2

Merged
hibryda merged 1 commit from chore/document-rmp-engine-flag into main 2026-06-02 21:26:27 +02:00
Owner

Small doc-of-config addition: the RMP step-4 RMP_ENGINE liveness-path flag was missing from .env.example (rule 14 — document every tunable). No behaviour change. Also serves as the live smoke-test for the newly-deployed RMP watchdog liveness path.

Small doc-of-config addition: the RMP step-4 RMP_ENGINE liveness-path flag was missing from .env.example (rule 14 — document every tunable). No behaviour change. Also serves as the live smoke-test for the newly-deployed RMP watchdog liveness path.
docs(config): document the RMP_ENGINE flag in .env.example
All checks were successful
pr-reviewer CI / tsc --noEmit (pull_request) Successful in 32s
pr-reviewer CI / vitest (pull_request) Successful in 58s
pr-reviewer CI / tsc build (pull_request) Successful in 33s
9462a51a75
The RMP step-4 liveness-path flag (RMP_ENGINE=1 → generic adapter+LivenessWatchdog;
default/empty → SessionSupervisor, byte-identical) was missing from the operator
env reference. Rule 14 — .env.example documents every tunable. No behaviour change.

hib-pr-reviewer review — PR #2 (hib/hib-pr-reviewer)

Round 1 — head 9462a51a7579, base main, trigger opened

TL;DR: APPROVE — docs-only entry; all referenced components, file paths, and behavioural claims verified against HEAD.

Summary

[quorum-converged] A=0 = B=0. Docs-only change adding RMP_ENGINE to .env.example. All claims in the comment were verified against the live codebase:

  • Referenced doc file docs/architecture/rmp-implementation-blueprint.md exists.
  • LivenessWatchdog and SessionSupervisor both exist in src/rmp/liveness-watchdog.ts and src/session-supervisor.ts.
  • Implementation in src/worker.ts:148 (const RMP_ENGINE_ENABLED = process.env.RMP_ENGINE === "1") matches the "read once at module load" description.
  • Startup log at src/worker.ts:1983-1984 confirms "The startup log prints the active path."
  • "byte-identical" claim consistent with blueprint doc (steps 1–4 change no behaviour) and worker.ts comment.
  • "Review Module Protocol" acronym expansion matches usage in src/rmp/*.ts files.
  • Placement after REVIEW_MODEL is logical (engine-config block before the bot-identity section separator).

No actionable findings.

Blast Radius

Single line added to .env.example with no functional change. The flag already existed in the codebase; this is purely documentation. Zero blast radius.

BLAST_SCORE: 0/10

CI status (head 9462a51a7579)

Overall: pending

3 checks: 3 pending

Check State Link
pr-reviewer CI / tsc build (pull_request) pending details
pr-reviewer CI / tsc --noEmit (pull_request) pending details
pr-reviewer CI / vitest (pull_request) pending details

Findings

No new findings this round.

Quorum converged on empty findings (A + B both returned 0).

Verdict

APPROVE


hib-pr-reviewer • round 1 • 0 findings • 2026-06-02T19:13:22.516Z → 2026-06-02T19:14:09.914Z • posted-as: pr-reviewer-bot • model: auto

<!-- hib-pr-reviewer round:1 --> ## hib-pr-reviewer review — PR #2 (hib/hib-pr-reviewer) **Round 1** — head `9462a51a7579`, base `main`, trigger `opened` **TL;DR:** APPROVE — docs-only entry; all referenced components, file paths, and behavioural claims verified against HEAD. ### Summary [quorum-converged] A=0 = B=0. Docs-only change adding `RMP_ENGINE` to `.env.example`. All claims in the comment were verified against the live codebase: - Referenced doc file `docs/architecture/rmp-implementation-blueprint.md` ✅ exists. - `LivenessWatchdog` and `SessionSupervisor` ✅ both exist in `src/rmp/liveness-watchdog.ts` and `src/session-supervisor.ts`. - Implementation in `src/worker.ts:148` (`const RMP_ENGINE_ENABLED = process.env.RMP_ENGINE === "1"`) ✅ matches the "read once at module load" description. - Startup log at `src/worker.ts:1983-1984` ✅ confirms "The startup log prints the active path." - "byte-identical" claim ✅ consistent with blueprint doc (steps 1–4 change no behaviour) and worker.ts comment. - "Review Module Protocol" acronym expansion ✅ matches usage in `src/rmp/*.ts` files. - Placement after `REVIEW_MODEL` is logical (engine-config block before the bot-identity section separator). No actionable findings. ### Blast Radius Single line added to `.env.example` with no functional change. The flag already existed in the codebase; this is purely documentation. Zero blast radius. **BLAST_SCORE: 0/10** ### CI status (head `9462a51a7579`) **Overall: ⏳ pending** 3 checks: 3 pending | Check | State | Link | |---|---|---| | pr-reviewer CI / tsc build (pull_request) | ⏳ pending | [details](/hib/hib-pr-reviewer/actions/runs/44/jobs/2) | | pr-reviewer CI / tsc --noEmit (pull_request) | ⏳ pending | [details](/hib/hib-pr-reviewer/actions/runs/44/jobs/0) | | pr-reviewer CI / vitest (pull_request) | ⏳ pending | [details](/hib/hib-pr-reviewer/actions/runs/44/jobs/1) | ### Findings **No new findings this round.** _Quorum converged on empty findings (A + B both returned 0)._ ### Verdict **APPROVE** --- <sub>hib-pr-reviewer • round 1 • 0 findings • 2026-06-02T19:13:22.516Z → 2026-06-02T19:14:09.914Z • posted-as: pr-reviewer-bot • model: auto</sub>
hibryda deleted branch chore/document-rmp-engine-flag 2026-06-02 21:26:28 +02:00
Sign in to join this conversation.
No reviewers
No labels
No milestone
No project
No assignees
2 participants
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set.

Reference
hib/hib-pr-reviewer!2
No description provided.