config: re-enable cursor profile after model-auto root-cause fix

Why: the earlier disable was a misdiagnosis — ActionRequiredError
looked like a monthly quota cap, but the real cause was the DM
executor not passing --model auto, so cursor fell back to a
quota-limited model. PR #644 (deps/development-manager) fixed the
executor; the quota itself was never exhausted.
Evidence: AGENT-EXECUTION.md validate ok; #644 in main since d2035c7.
Impact: restores cursor as first implementation/repair candidate.
Refs: AGENT-EXECUTION.md; PR #644

AGENT-EXECUTION.md

@@ -50,11 +50,11 @@ profiles:
     adapter: cursor
     executable: cursor-agent-stable
     model: auto
-    # Disabled 2026-10-20 by owner decision (task feature/docker-test-image,
-    # option 1): Cursor Ultra monthly usage cap exhausted — every dispatch
-    # dies with ActionRequiredError; limits reset 2026-11-10. Re-enable
-    # (enabled: true) after the cycle resets.
-    enabled: false
+    # Re-enabled 2026-10-20: the earlier disable was based on a misreading
+    # of ActionRequiredError — the real cause was the DM executor not
+    # passing --model auto (cursor fell back to a quota-limited model).
+    # Fixed by PR #644 (deps/development-manager pin); quota itself is fine.
+    enabled: true
 
   antigravity:
     adapter: antigravity