Document the dashboard definition schema in the cloud CLI docs

[DjamilaBaroudi]

Local agents read commands/cloud.md (via the docs MCP) and get command syntax but no dashboard definition schema — so they reverse-engineer the state. One recent run invented a top-level tabs: block; tabs are actually a per-row tab: field, so that dashboard came out malformed.

Adds a "Dashboard definition" section to the dashboards docs:

• top-level keys (name, connection, filters, rows)
• row/widget shape (metric/chart/table, col grid, x/y/value encodings)
• tabs are per-row tab: — no top-level tabs: key (the exact mistake seen)
• a note that connection must be one the bound agent has
• a worked YAML example

Docs only.

[greptile-apps]

Unresolved filters cross-reference

The filters entry says “see below,” but the section proceeds through rows, widgets, and the example without defining the filter-control shape, leaving readers and agents to infer that part of the dashboard schema.

Prompt To Fix With AI

This is a comment left during a code review.
Path: docs/commands/cloud.md
Line: 655

Comment:
**Unresolved filters cross-reference**

The `filters` entry says “see below,” but the section proceeds through rows, widgets, and the example without defining the filter-control shape, leaving readers and agents to infer that part of the dashboard schema.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

Note: If this suggestion doesn't match your team's coding style, reply to this and let me know. I'll remember it for next time!

[greptile-apps]

Prompt To Fix All With AI

### Issue 1
docs/commands/cloud.md:655
**Unresolved filters cross-reference**

The `filters` entry says “see below,” but the section proceeds through rows, widgets, and the example without defining the filter-control shape, leaving readers and agents to infer that part of the dashboard schema.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (1): Last reviewed commit: "Document the dashboard definition schema..." | Re-trigger Greptile}

[greptile-apps]

_{Reviews (2): Last reviewed commit: "Define the filter-control shape in the d..." | Re-trigger Greptile}

[greptile-apps]

_{Reviews (3): Last reviewed commit: "Correct the filter schema against the da..." | Re-trigger Greptile}

[greptile-apps]

Date-range endpoints remain undocumented

When an agent follows the documented {{ filters.<name> }} pattern for a date-range filter, it references the range as one SQL value instead of using its .start and .end values, causing invalid date comparisons or failed dashboard queries.

Prompt To Fix With AI

This is a comment left during a code review.
Path: docs/commands/cloud.md
Line: 706

Comment:
**Date-range endpoints remain undocumented**

When an agent follows the documented `{{ filters.<name> }}` pattern for a `date-range` filter, it references the range as one SQL value instead of using its `.start` and `.end` values, causing invalid date comparisons or failed dashboard queries.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

[greptile-apps]

Prompt To Fix All With AI

### Issue 1
docs/commands/cloud.md:706
**Date-range endpoints remain undocumented**

When an agent follows the documented `{{ filters.<name> }}` pattern for a `date-range` filter, it references the range as one SQL value instead of using its `.start` and `.end` values, causing invalid date comparisons or failed dashboard queries.

---

For each issue above, determine whether it is valid and should be fixed. If so, fix it directly.

_{Reviews (4): Last reviewed commit: "Merge branch 'main' into docs-dashboard-..." | Re-trigger Greptile}

[greptile-apps]

_{Reviews (5): Last reviewed commit: "Fix docs build and document date-range/m..." | Re-trigger Greptile}