fix: Introduce a Dedicated scripts/ Folder for Project Automation #416
Description
Problem Statement
Summit currently places multiple operational and bootstrapping scripts at the repository root (for example, theme checks, settings fetch scripts, etc.).
These scripts are critical to:
- Application startup
- Build-time validation
- Configuration bootstrapping
However, keeping them scattered at the root level leads to poor structure, discoverability issues, and long-term maintainability concerns.
Why This Is a Problem
The current approach:
- Clutters the repository root
- Makes it difficult for contributors to discover and understand project automation
- Blurs the line between application source code and tooling / operational scripts
- Scales poorly as more scripts are added (build hooks, checks, migrations, tooling, etc.)
- Lacks a clear convention for where new scripts should live
Proposed Solution
Introduce a top-level scripts/ directory and move all operational scripts into it.
Example Structure
/scripts
├── fetch-summit-settings.(js|sh)
├── check-if-theme-exists.(js|sh)
└── README.md