STATE-WP-0072: daily triage prompt uses /workplans/index

Replace retired /workstreams/workplan-index and workstream_id query
aliases in the WSJF triage runner prompt.

runtime/prompts/daily_statehub_wsgi_triage.md

@@ -29,7 +29,7 @@ runner.
 - Read first, then decide. Do not edit workplans, canon, or task status during
   a daily review unless a later human request explicitly asks for an apply step.
 - Prefer existing State Hub read surfaces over ad hoc scans:
-  `/state/summary`, `/state/next_steps`, `/workstreams/workplan-index`,
+  `/state/summary`, `/state/next_steps`, `/workplans/index`,
   `/messages/`, and `.custodian-brief.md`.
 - Use local workplan files only to enrich the State Hub snapshot with task
   wording, stale frontmatter, and missing file-backed state.
@@ -50,14 +50,14 @@ available fallback and say so in the report.
 2. `GET http://127.0.0.1:8000/state/summary`
 3. `GET http://127.0.0.1:8000/messages/?to_agent=hub&unread_only=true`
 4. `GET http://127.0.0.1:8000/state/next_steps`
-5. `GET http://127.0.0.1:8000/workstreams/workplan-index`
+5. `GET http://127.0.0.1:8000/workplans/index`
 6. Local workplan files for candidate workplans that need closer inspection
 7. Read-only `git status --short` for repos named in top recommendations
 
 Optional enrichment:
 
-- `GET /tasks/?workstream_id=<id>` for a top-ranked workplan
-- `GET /progress/?workstream_id=<id>&limit=5` for staleness confidence
+- `GET /tasks/?workplan_id=<id>` for a top-ranked workplan
+- `GET /progress/?workplan_id=<id>&limit=5` for staleness confidence
 - State Hub domain summaries through MCP when available
 
 ## Candidate Set