What problem does it solve? Per-project runtime code can accidentally spawn Worker processes locally, bypassing host admission, budgets, the host event lane, and every host-facing status surface. This Skill enforces the invariant that only the host-scoped redskilled daemon creates Worker processes when you change runtime source under apps/plugin-dev/src. ## Core Features & Use Cases - Host-Owned Birth Routing: Makes per-project runtime state (argv, workspace, opaque project label) the payload sent to the daemon through the birth port, so only the host creates Workers. - Fail-Closed Behavior: Returns the structured repair from the birth port when the daemon is unavailable instead of falling back to a local spawn. - Ratchet Tracking: Extends HOST_OWNED_BIRTH_SITES with each module's path, former responsibility, and replacement route, keeping removed modules declared with removed: true so renames or resurrections stay observable. - Use Case: While refactoring a per-project module in apps/plugin-dev/src, use this Skill to ensure every Worker request reaches the daemon birth port and host-owns-birth-guard.test.ts passes. ## Quick Start Use the guard-process-birth skill to review my changes under apps/plugin-dev/src and confirm all Worker births route through the redskilled daemon.
