Task · GCI-0107

Expose estate versus selected-stack scope on dashboard headlines

Description

The operator relevance review found global collector/findings headlines next to stack-filtered tables and ranks, making selection look estate-wide or vice versa. P4 is visible wording/scope qualification only, no new selectors, formulas, metric names, data collection or series; preserve all user filters and query semantics.

Acceptance Criteria

Definition of Done

Implementation Plan

P4 visible population labels only across Cost/Maturity/Value/Risk/Dashboard usage/Coverage/shared Findings. Preserve selectors/formulas/data, inspect actual public artifacts and all/single/multi/prefix-collision context; truthful estate versus selected scope. Finalgate/CR as applicable and independent review before integration.

Implementation Notes

Independent proposal review found the initial named dashboard list narrower than P4 matrix. Expanded static-label scope to include Risk, Dashboard usage and Coverage; no dynamic-inventory or query change.

Loop13:2workerchange/verify cycles,1review-repair round. Original987ccb classifier independentlyFAIL3majors despite currentartifacts/CRgreen. Repaired53da4bd0c29c123d5177d515d7bffc3031225f90 conservatively closes mixedexpression, refgraph and missing/unsupportedsyntax cases; chronological12failures then187modulepasses2skips, completed0findingCRdelta. Same reviewer finaldeltaPASS6focusedpasses47subtests,11artifacts identicalfirstcandidate/nonpresentationidenticalpre-task. LandedfinalSHA; composedjustcheck2212passed2skipped13476subtests, stableclean858seconds; exactCI37500598373 required leaves success. Visibleestate/selection/mixed/unresolvedlabels, no query/data/statechange or browser/currentinventory guarantee.

Final Summary

Visible population scope across six dashboards and shared Findings, with conservative closed-grammar/ref-graph safety rather than substring inference.

View the source file on GitHub