You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
📖 ask: docs coverage and vendor checklist for Ask AI help (phase 3 of #19177) #19182
Phase 3 of the Ask AI help design. Design: src/docs/design/dashboard-ask-ai-help.md in #19179. Parent: #19177.
Blocked by #19181 (phase 2, hub panel). Nothing goes live before the docs are ready.
Scope (docs coverage, mostly in the docs repo)
Fill the gaps in the docs repo sync list and nav map for the operator pages the dashboard relies on: the main dashboard page, hosted hub and hub deployment pages, and any other page a "?" mark links to that the site lacks (re-check against the docs repo main branch first).
A generated UI map page (section heading, sidebar location, the Settings tab that changes it) built from the dashboard section registry so the words people type match the screen and cannot drift.
Keep design records, ADRs and runbooks out of what the vendor ingests (exclude at the sync list if the vendor has no per-source patterns), and keep issues, pull requests and chat out.
A vendor-side checklist for the project owner, with no credentials in the repo: enable PII masking for questions, scope the customization to dashboard help and off-topic refusal, review the enabled-domains list, ask for a higher per-team chat limit, and use coverage-gap analytics to feed doc fixes back.
Update the telemetry page and the dashboard docs to say what Ask sends and where consent lives.
Done when
Real navigation questions ("where do I add a repo", "how do I pause an agent") return a correct cited link on the hub.
The PR body says this is partial/non-closing work (Refs/Part of or leave-open wording), so Hive will not add a closing keyword. GitHub will not show its issue-list PR icon without a closing keyword; the stage comment is the link.
scanner (2026-11-19 06:38 UTC): Scanner verification: docs#740 (merged) covers scope item 1 (sync list and nav map for the dashboard help guides) and the item 3 exclusions in part. Still open: item 2 (generated UI map page from the dashboard section registry), item 4 (vendor-side checklist for the project owner), and item 5 (telemetry page and dashboard docs wording on what Ask sends and where consent lives). This phase is also blocked on phase 2 (✨ ask: hub panel for optional Ask AI help (phase 2 of #19177) #19181); its hub panel PR ✨ ask: hub panel for optional Ask AI help #19202 is currently conflicting, so the UI map and consent wording cannot be finalised until that lands. Not claiming yet; will pick up the remainder once the phase 2 PRs merge. Labelling verified-open.
Claiming this for the docs coverage and vendor-side checklist work. Re-checking the page list against current main/v5 and the docs site sync list first; PRs will reference this issue.
@clubanderson you now hold this issue (human on hive hosted-available-oke-11-placeholder-r05x); the claim ledger comment above tracks it. Reply /unclaim to release.
hive: 📖 Dashboard UI map, docs-site help links and a Settings entry per tab #19201 (Dashboard UI map page with generated sidebar and Settings tables plus sign-in steps, v5 help links to docs.hivecommons.dev for published pages, a Settings entry per tab, checklist status in the design record). Refs, not Fixes.
Vendor-side checklist: PII masking for questions is on, a widget integration limited to the docs domain exists, and a customization scopes answers to Hive Commons help with polite off-topic refusal. A higher chat limit, GitHub Discussions as a source and the issues source rename were requested through CNCF.
Remaining here: the Ask-specific telemetry and consent wording once phases 1 and 2 ship, the two Kapa source exclusions (ADR URL prefix, design-record selector), and moving the UI map into the docs-site Dashboard nav after it syncs.
PR #19201 has merged (#19201) and referenced this issue with a non-closing Refs #19182 rather than a closing keyword.
This issue remains open because the merged PR did not use Closes / Fixes / Resolves. If the fix should close it on merge, use a closing keyword in the PR body; use the opt-in hive: needs-confirmation marker only when the reporter genuinely must verify before closure.
Activity
hivecommons-hive commentedon Nov 19, 2026
🔓 Claim by agent
scannerreleased (holding agent relaunched).Claim history
Karibhou(contributor on hive hosted-available-oke-11-placeholder-r05x)Karibhou(contributor; human claim: assigned by clubanderson)clubanderson(human on hive hosted-available-oke-11-placeholder-r05x)scanner(agent on hive hosted-available-oke-11-placeholder-r05x)scanner(agent; holding agent relaunched)hivecommons-hive commentedon Nov 19, 2026
Hive status — updated in place; edits do not notify. Full history is in the Activity Monitor.
PR #19192 covers this issue: #19192
The PR body says this is partial/non-closing work (
Refs/Part ofor leave-open wording), so Hive will not add a closing keyword. GitHub will not show its issue-list PR icon without a closing keyword; the stage comment is the link.clubanderson commentedon Nov 19, 2026
Claiming this for the docs coverage and vendor-side checklist work. Re-checking the page list against current main/v5 and the docs site sync list first; PRs will reference this issue.
hivecommons-hive commentedon Nov 19, 2026
@clubanderson you now hold this issue (human on hive hosted-available-oke-11-placeholder-r05x); the claim ledger comment above tracks it. Reply
/unclaimto release.clubanderson commentedon Nov 19, 2026
PRs for this issue:
Vendor-side checklist: PII masking for questions is on, a widget integration limited to the docs domain exists, and a customization scopes answers to Hive Commons help with polite off-topic refusal. A higher chat limit, GitHub Discussions as a source and the issues source rename were requested through CNCF.
Remaining here: the Ask-specific telemetry and consent wording once phases 1 and 2 ship, the two Kapa source exclusions (ADR URL prefix, design-record selector), and moving the UI map into the docs-site Dashboard nav after it syncs.
11 remaining items
📖 docs: move the Dashboard UI map into the Dashboard nav group (#743)
📖 docs: prepare Ask AI dashboard help coverage (#19192)
github-actions commentedon Nov 19, 2026
PR #19201 has merged (#19201) and referenced this issue with a non-closing
Refs #19182rather than a closing keyword.This issue remains open because the merged PR did not use
Closes/Fixes/Resolves. If the fix should close it on merge, use a closing keyword in the PR body; use the opt-inhive: needs-confirmationmarker only when the reporter genuinely must verify before closure.