[HOLD] staged gate — keep OPEN to block planned work; remove an issue blocked-by:#160 label to release just it, or close to release all

[jasonhnd]

Staged planning HOLD gate for loopcoder work that is intentionally not started yet.

This issue carries a self-referential blocked-by:#160 label, so ready-set never dispatches it, and every issue labeled blocked-by:#160 stays blocked.

Currently holding:

• 0.3.x design spec: autonomous delivery loop (automation + perception) [blocked on #194] #161 — 0.4.0 (automation + perception)
• the 0.3.2 guardrails spec

To RELEASE only one batch: remove that issue blocked-by:#160 label (it becomes ready; the others stay held). Note: 0.3.2 has no loopreview dependency, so it can be released on its own, before 0.4.0.
To RELEASE everything: close this issue as completed.

Do not release a batch until you choose to start it.

[jasonhnd]

Closing this staged HOLD gate. Reorg 2026-06-28: 0.4.0 dropped as a separate held version; work flattened into a continuous 0.3.x line. 0.3.2 guardrails (spec #192) merged and released from hold. #161 (autonomous loop) is now gated directly on its real prerequisite, reliable loopreview (#194), via blocked-by:#194. The self-referential gate has served its purpose.