feat(resolvers): binky_rhythm_status query in state-hub resolver

Due-items for the three Binky operating-rhythm definitions
(BINKY-WP-0004-T02). Dueness derives from hub progress events recorded
by the executing session (binky_daily_brief / binky_mail_intake /
binky_weekly_review, detail.repo scoped); weekly_review carries
milestone_moved from event_type=milestone events in the last 7 days
(RISK-005 signal). Definitions' resolver comments updated; definitions
stay enabled:false until cutover (BINKY-WP-0004-T06).

7 new tests; resolver test file 31/31 green. Pre-existing failures in
test_railiance_ops_inventory_wiring/test_schedule_health are untouched.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

activity-definitions/binky-daily-rhythm.md

@@ -16,10 +16,11 @@ context_sources:
     params:
       repo: binky-control
     bind_to: context.rhythm
-# Proposed resolver (not yet implemented): returns
-# {items: [{kind: "daily_brief", due: bool, date: "YYYY-MM-DD"}]} — due is
-# true when no brief exists for today in binky-control/briefs/. Implementing
-# it is part of the BINKY-WP-0003-T06 follow-up workplan proposal.
+# Resolver implemented (BINKY-WP-0004-T02): returns
+# {items: [{kind: "daily_brief", due: bool, date: "YYYY-MM-DD",
+# last_run_at}]} — due is true when no binky_daily_brief progress event with
+# detail.repo=binky-control exists for today (Europe/Berlin). The executing
+# session must record that event on completion (idempotence guard).
 ---
 
 # Binky Daily Operating Rhythm