Make “split shared busy flags per action” a standing house rule

CODIFIED 2026-09-06 on the user’s instruction to fix this item; lands in PR #197 (feat/zigbee-completion-automation-v2, commit 15c7513). New AGENTS.md house rule: ‘Split shared busy flags per action: every independent async action in a component owns its own in-flight state (saving / aborting / aiBusy …); a single busy may gate only steps that are genuinely sequential in the same flow. A control must never be disabled by an unrelated request, and Abort/Cancel stays enabled while the thing it aborts is in flight (reference: FanCalibrateWizard, SoftCalWizard aiBusy, LabWetCalPanel in CalibratePage.tsx).’ Note: the original Location components/Wizard.tsx does not exist in the tree; the live instances were all in CalibratePage.tsx / SoftCalWizard.tsx and are already fixed. — REVIEW 2026-09-06: live instances handled; codifying needed sign-off. — ORIGINAL: make ‘split shared busy flags per action’ a standing house rule.