Record daily triage schema canary blocker

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

@@ -108,7 +108,9 @@ prompt: |
   Curated digest:
   {context.daily_triage_digest}
 
-  Return JSON matching schemas/daily-triage-report.json:
+  Return only JSON matching
+  `/home/worsch/the-custodian/schemas/daily-triage-report.json`. Do not wrap
+  the JSON in Markdown fences or add prose before or after it:
   {
     "summary": "short operator-facing summary",
     "recommendations": [
@@ -120,7 +122,7 @@ prompt: |
       }
     ]
   }
-output_schema: schemas/daily-triage-report.json
+output_schema: /home/worsch/the-custodian/schemas/daily-triage-report.json
 review_required: false
 report_sinks:
   - type: working-memory
@@ -159,9 +161,10 @@ Daily triage may recommend but must not execute:
 
 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.
+`model_params` values through the llm-connect HTTP boundary. activity-core also
+passes the `output_schema` JSON to llm-connect as `model_params.json_schema`
+when the backend can enforce structured output. 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: