Code Insights And Ownership

Operator wants a weekly trend of `TODO(security)` count across the codebase. Defines a Code Insight with a search query and a 30-day window.

Per docs/code_insights/references, a search-based insight runs the query at each sample point against historical commits, returning a time series. Verify the query is well-scoped (`type:diff` for added/removed counts or plain content for current state). Sampling cadence and backfill horizon are con…

Operator wants a chart of language version counts: each capture of `node>=([0-9.]+)` in `package.json` is grouped into a series.

Per docs/code_insights, capture-group insights use regexp patterntype with a single capture group whose match becomes the series key. Verify the regexp is anchored and the capture group is non-greedy enough to avoid swallowing trailing JSON. Cite the capture-group insight guide.

Operator creates a personal dashboard with 6 insights, then asks why teammates do not see it.

Per docs/code_insights, dashboards have user/organization/global scope. Personal dashboards are not visible to others. Operator should re-scope the dashboard to org or share the insight URLs; viewers still see only repos their ACL covers.