Installable Patrol modules

Make Patrol and Architecture Patrol installable Hive modules, analogous to honeycombs, implemented entirely through existing Hive hooks and workflow machinery instead of patrol-specific orchestration. Define or generalize a reusable module/package contract that can carry workflow descriptors, stage definitions, prompts/templates, hook declarations, schedules, event bindings, configuration schema/defaults, permissions, checkpoints, artifacts, version/provenance metadata, and documentation. A module hook must be able to launch its workflow either on a schedule or when a declared Hive/project/GitHub lifecycle event occurs, using existing event, scheduler, workflow, attempt, locking, retry, and artifact mechanisms with idempotency, deduplication, concurrency control, observability, and safe failure behavior. Provide install, update, list, inspect/status, enable/disable, and uninstall flows at appropriate user/project scopes; reuse the current honeycomb discovery/catalog/install conventions where possible and determine whether the right abstraction is a generalized installable module beneath honeycombs rather than a parallel system. Package the current Patrol and Architecture Patrol behavior as first-party modules and migrate existing users/configuration without losing behavior, with explicit compatibility aliases and deprecation for old entry points. Remove or retire bespoke patrol dispatch, scheduling, state, and recovery mechanics only after parity is proven. Include security/trust handling for remote modules, version pinning/lock data, deterministic validation, dry-run/doctor diagnostics, event and schedule fixtures, end-to-end tests that install both modules and prove scheduled plus event-triggered workflow runs, documentation for authoring and distributing modules, and dogfood migration of the existing patrols. Preserve unrelated dirty wiki files. Deliver a reviewed non-draft PR with green local and hosted CI, but do not merge or enable auto-merge.