engineering-conventions

To prevent production regressions in opencode-swarm core source files, load mandatory engineering invariants before coding to enforce init-path import safety, subprocess kill guarantees, and test mock isolation. This ensures modifications comply with non-negotiable runtime portability and safety rules.

Engineering invariants are non-negotiable rules for high-risk code paths that stop silent plugin startup failures by enforcing init-path timeout safety and import guards. Loading these invariants before modifying plugin initialization logic prevents hard-to-diagnose local vs CI validation mismatches.

Ensure subprocess kill guarantees and prevent unkillable subprocesses by applying targeted execution guardrails from mandatory engineering invariants to your subprocess utilities. This enforces strict safety rules during sandbox execution path modifications to avoid unkillable process regressions.

Yes, this engineering conventions skill applies directly to test infrastructure and sandbox environment overrides by enforcing test mock isolation and tool version parity. It ensures that local testing environments match CI validation requirements to prevent silent regression escapes.

Local tests pass but CI validation fails after modifying build configuration due to tool version parity mismatches and missing skill mirror contract compliance. Enforcing engineering invariants ensures local and CI environments maintain strict version parity during sandbox execution path changes.

Load engineering invariants before making any changes to opencode-swarm's plugin entry point, subprocess utilities, test setup, or build configuration. Applying these rules first ensures all modifications satisfy init-path timeout safety and skill mirror contract compliance to avoid regressions.