feat(0.22.0): wire RCS control loop on bootstrap + doctor §23 closure verdict

[broomva]

Problem

bstack doctor reported a workspace's L1 layer "unstable" — and the investigation found the deeper cause: when bstack is instantiated, the control loop is declared but not closed.

• Split-brain: onboard.sh (the wizard) wired the loop via install-rcs-stability.sh; bootstrap.sh (the /bstack bootstrap command — what the SKILL.md tells agents to run) never did. Freshly-bootstrapped workspaces had governance files but an open loop: no L0/L1 audit hooks, no .control/audit/, no closure-arc definitions.
• Doctor under-reported closure: §16–18 (audit logs) and §21 (arcs) reported a missing/idle loop as soft [info]. There was no single verdict answering "is the loop wired, connected, and running?"

Note: the original "L1 unstable" reading came from doctor defaulting WORKSPACE="${BROOMVA_WORKSPACE:-$HOME/broomva}" — run from a sub-repo without BROOMVA_WORKSPACE, it measured the parent workspace. Flagged in CHANGELOG as a possible future UX fix; out of scope here.

Change

Makes /bstack bootstrap wire the loop, scaffold the loop definitions, and report loop liveness as a first-class verdict.

• bootstrap.sh Phase 3.5 — calls install-rcs-stability.sh (L0 PostToolUse + L1 Stop audit hooks + .control/audit/ + L3 gates), reusing the same idempotent installer the wizard uses. BSTACK_SKIP_RCS=1 escape for governance-only bootstrap.
• bootstrap.sh Phase 2 — scaffolds .control/arcs.yaml from template (the workspace's own editable loop definitions).
• doctor.sh §23 — control-loop closure verdict: substrate-absent / wired-but-idle / wired+running+closing, from W (hooks+dir) / R (audit logs fresh <7d) / C (workspace arcs + composite-ω resolvable). Soft by default; BSTACK_LOOP_STRICT=1 + --strict together fail CI on an idle loop. §19 already hard-gates a wired loop that is genuinely diverging, so §23 does not double-count.
• canary/01 asserts PostToolUse + .control/audit/ + .control/arcs.yaml + L0/L1 markers (14/14); docs + VERSION 0.21.10 → 0.22.0.

Dependency-chain (P14)

• upstream: install-rcs-stability.sh (reused, unchanged) → install-l3-stability.sh (writes to $WORKSPACE — verified no PWD bug); arcs.yaml.template; compute-budget-status.sh / compute-arc-status.sh.
• downstream: onboard.sh (already wired — now converges); repair.sh (already offers install-rcs); tests/canary/01; every workspace running bstack bootstrap / bstack doctor.

Verification (P11)

• canary 01–05 green; arcs-validation / repair-merge-hooks / onboard suites green.
• §23 verified across all three states + the wired+running+closing path (synthetic L0 event).
• Strict-flag interaction verified: BSTACK_LOOP_STRICT=1 alone → exit 0; with --strict → exit 1.
• Idempotency: bootstrap×2 and onboard↔bootstrap (both orderings) → zero duplicate hooks (disjoint _bstack_primitive markers).

Cross-Review (P20)

Strata B fresh-context adversarial review: 8.5/10, passes (≥7). No blocking findings. Four nits addressed in the same commit: BSTACK_LOOP_STRICT two-flag clarity (docs + Usage block + inline hint), tightened the C ("closing") signal to require the workspace's own arcs.yaml (not template fallback), corrected the || true comment (set -e without pipefail), fixed stale "28 skills" header → 31.

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@broomva, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 20 minutes and 23 seconds. Learn how PR review limits work.

Your organization has run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans include higher PR review limits than trial, open-source, and free plans. In all cases, reviews become available again over time. During sustained high-volume PR review activity, CodeRabbit may temporarily slow when the next review becomes available.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro

Run ID: 00439342-628b-4650-8138-0851dcdfad29

📥 Commits

Reviewing files that changed from the base of the PR and between e731305 and c6eb5c7.

📒 Files selected for processing (7)

• CHANGELOG.md
• VERSION
• references/new-workspace-flow.md
• scripts/bootstrap.sh
• scripts/doctor.sh
• scripts/skill-graduate.sh
• tests/canary/01-fresh-bootstrap.test.sh

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch feat/wire-control-loop-on-bootstrap

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}