Dashboard linking — canonical entity metadata (M5, only if needed)

Problem

We might want YAML (or another registry) that says “the detail board for entity ticket is this slug,” so agents or UI can drill without an explicit slug in context.

Current decision (v1): we are not building that. We favor:

• Path conventions — e.g. /zendesk/tickets/list?…, /zendesk/tickets/detail?id=… (names humans and models can learn).
• Explicit links and search/list boards for agents.

This task exists so the idea is not lost—reopen only with evidence (e.g. repeated agent failure, user research).

Context

• ADR-002 — deferred to M5.
• Spec — v1 dashboard-root linking without canonical_for.
• Depends on dashboard-linking-v1 shipping first.

Possible Solutions

• Do nothing (close task) if conventions + catalog search stay sufficient.
• Optional canonical_for on face YAML with compile-time duplicate detection + small index for MCP.
• Sidecar JSON / manifest per project if we want registry without polluting every face file.

Plan

1. After v1 linking is in use, review agent evals / support patterns for “wrong drill target” or “cannot resolve entity → board.”
2. If pain is real, draft a short ADR update and minimal schema; implement with tests.
3. If not, mark this task cancelled with reason in Implementation Progress.

Implementation Progress

QA Exploration

N/A unless shipped.

• [ ] QA exploration completed (or N/A for non-UI tasks)

Review Feedback

• [ ] Review cleared