---
description: "Mandatory check for consistency across related files when changing core logic or configurations."
globs: ["**/*"]
---
# Cross-File Consistency Audit

To prevent "Missing Update" errors, whenever you modify a core service, configuration, or data type, you MUST double-check the following related files:

## 1. Environment & Config
- If you add/change environment variables in **`src/`**, update **`.env.example`** and clarify in the next **`SESSION_SUMMARY.md`**.
- Check **`vite.config.ts`** or relevant config files if build-time changes are made.

## 2. Types & Interfaces
- If you modify a data structure in **`src/types.ts`**, check all components and services that consume it.
- Ensure **`src/constants.ts`** (INITIAL_DATA) is updated if the schema of `AstroData` changes.

## 3. Documentation Alignment
- Every major logic change MUST be reflected in **[PROJECT_STATUS.md](file:///Users/keira/Documents/GitHub/Vedic-astro-mar/PROJECT_STATUS.md)**.
- Follow the hierarchy defined in **[.cursor/rules/session-start.mdc](file:///Users/keira/Documents/GitHub/Vedic-astro-mar/.cursor/rules/session-start.mdc)**.

## 4. PURPOSE
The goal is to ensure that code changes don't leave "ghost dependencies" or outdated configuration examples, maintaining a clean and accurate repository at all times.