Improve docs request discoverability and intake guidance for `/docs` Slack command

[kwannoel]

Context

Slack transcript (no thread link provided):

[2026-02-17T21:49:27.120Z] <@U0AG7B6P9AL>: <@U0AF0DZ7C9Y> /docs

Search results from docs pipeline context lookup did not return related docs/PR/code references, which suggests the request lacks enough structured detail for direct docs action.

Problem

The /docs request format is not self-describing enough to produce actionable documentation work items when users submit only the command without context. This creates triage churn and delays, because maintainers have to follow up for the basics (feature area, current page, expected behavior, and target audience).

Suggested Fix

Add a short contributor-facing section in the docs contribution/discovery pages that explains how to submit effective /docs requests, including a lightweight template:

• Product/feature area
• Current docs URL (if any)
• What is missing/incorrect
• Expected outcome and user persona
• Repro steps or SQL examples (if relevant)

Also add one concrete good request example and one bad request example so users can quickly self-correct before submitting.