## LGE CX Dashboard Backend Repository Rules ### Deliverable and Domain - This Spring Boot backend serves the LGE appliance penetration, purchase, category, profile, and trend dashboard. - Treat approved planning material and acceptance criteria as the scope boundary. Preserve year, category, variable, filter, calculation, and response semantics used by the frontend. - Statistics endpoints, Excel upload, persisted survey data, variable/year metadata, and statistics cache behavior form one coordinated data contract. - Do not infer a new statistic, category mapping, aggregation rule, or visualization requirement from source names alone. ### Statistics, Upload, and Cache Safety - Preserve denominators, weighting, missing values, category membership, ordering, decimal precision, rounding, totals, and cache-key semantics when changing a statistic. - Validate Excel structure, headers, cell types, file size, and partial-failure behavior at the upload boundary. Never use customer source data as an unrestricted test fixture. - Keep cache invalidation explicit when uploaded data, variables, years, or calculation behavior changes. - Preserve backward-compatible request and response shapes so frontend and backend can deploy independently. ### Shared Library and Verification - Consume `com.kri.common:starter:beta.1.6.3` and use public `com.kri.common.feature.*` APIs. Do not duplicate a KriCommon feature locally. - `AGENTS.md` and `CLAUDE.md` are generated. Edit `.agent/profile.yml` or `.agent/project.md`, then recompose instead of editing generated files. - Use the Gradle Wrapper and the narrowest safe compile and tests. Do not connect to real MySQL, upload customer workbooks, or call production integrations without separate approval.