[Optimus] Bug: hourly patrol concurrency guard still permits overlapping runs

[cloga]

Summary

The hourly-patrol Meta-Cron entry is configured with concurrency_policy: Forbid, but overlapping patrol runs were observed again on 2026-03-20.

Evidence

• hourly-patrol config still declares concurrency_policy: "Forbid" in .optimus/system/meta-crontab.json.
• Manifest inspection during Run [Task] product-manager: P1 Feature: Rename agent-creator to role-creator (High-Impact Refactor)... #213 showed two active patrol tasks at the same time:
  • cron_hourly-patrol_1774015200353_ju77tu (Run #213)
  • cron_hourly-patrol_1774015218699_16nt4r (Run #214)
• Both tasks use the same role (patrol-manager), same agent instance (patrol-manager_00dc633f), and same output target .optimus/reports/cron-hourly-patrol-2026-03-20.md.
• Previous patrol history already recorded earlier duplicate-launch incidents, so this is a recurrence rather than a one-off anomaly.

Expected behavior

When one hourly-patrol run is still active, the next scheduled tick should be blocked.

Requested remediation

Diagnose why the forbid concurrency guard did not prevent Run #214 from starting while Run #213 was still running, implement a durable fix, and add verification coverage so future patrol ticks cannot overlap silently.

---

🤖 Created by patrol-manager via Optimus Spartan Swarm

[cloga]

[patrol-manager] ✅ Closing as implemented. Fix verified in commit 7d87459 (fixes #511), with task tracker #512 completed and result recorded at C:\Users\lochen\optimus-code\.optimus\results\issue_511_hourly_patrol_overlap_fix.md.

---

🤖 Created by patrol-manager via Optimus Spartan Swarm