Use llm-connect profile for daily triage

activity-definitions/daily-statehub-wsjf-triage.md

@@ -90,7 +90,12 @@ human-readable report.
 id: daily-triage-report
 trusted_fields:
   - context.daily_triage_digest
-model: gpt-5.2
+model: custodian-triage-balanced
+temperature: 0.2
+max_tokens: 1400
+max_depth: 2
+model_params:
+  reasoning_effort: medium
 prompt: |
   Produce the Daily State Hub WSJF triage report from this curated digest.
 
@@ -150,6 +155,25 @@ Daily triage may recommend but must not execute:
 - security posture changes without an explicit approval path
 - canon promotion
 
+## LLM Backend And Depth
+
+The model backend for this activity is `llm-connect`. activity-core passes the
+instruction's `model`, `temperature`, `max_tokens`, `max_depth`, and
+`model_params` values through the llm-connect HTTP boundary; provider choice,
+API keys, model routing, and local-vs-remote backend policy stay behind that
+boundary.
+
+This definition starts with a balanced daily-triage profile:
+
+- `model: custodian-triage-balanced`
+- `max_depth: 2`
+- `model_params.reasoning_effort: medium`
+
+Tune these values from observed report quality during the three-run calibration
+in `CUST-WP-0044`. Especially critical cases, such as very high gain combined
+with high effort, may later use a deeper llm-connect profile or deterministic
+pre-scoring without changing the scheduling substrate.
+
 ## Notes
 
 This file lives in `the-custodian/activity-definitions/` because the