refac: reorganize scripts and ci workflows

.github/pull_request_template.md

@@ -19,75 +19,74 @@ The most impactful way to contribute to Open WebUI is through well-written bug r
 **Before submitting, make sure you've checked the following:**
 
 - [ ] **Linked Issue/Discussion:** This PR references an existing [Issue](https://github.com/open-webui/open-webui/issues) or [Discussion](https://github.com/open-webui/open-webui/discussions) — `Closes #___` / `Relates to #___`. If one does not exist, create one first. PRs without a linked issue or discussion may be closed without review.
-- [ ] **Target branch:** Verify that the pull request targets the `dev` branch. **PRs targeting `main` will be immediately closed.**
-- [ ] **Description:** Provide a concise description of the changes made in this pull request down below.
-- [ ] **Changelog:** Ensure a changelog entry following the format of [Keep a Changelog](https://keepachangelog.com/) is added at the bottom of the PR description.
-- [ ] **Documentation:** Add docs in [Open WebUI Docs Repository](https://github.com/open-webui/docs). Document user-facing behavior, environment variables, public APIs/interfaces, or deployment steps.
-- [ ] **Dependencies:** Are there any new or upgraded dependencies? If so, explain why, update the changelog/docs, and include any compatibility notes. Actually run the code/function that uses updated library to ensure it doesn't crash.
-- [ ] **Testing:** Perform manual tests to **verify the implemented fix/feature works as intended AND does not break any other functionality**. Include reproducible steps to demonstrate the issue before the fix. Test edge cases (URL encoding, HTML entities, types). Take this as an opportunity to **make screenshots of the feature/fix and include them in the PR description**.
-- [ ] **Agentic AI Code:** Confirm this Pull Request is **not written by any AI Agent** or has at least **gone through additional human review AND manual testing**. If any AI Agent is the co-author of this PR, it may lead to immediate closure of the PR.
-- [ ] **Code review:** Have you performed a self-review of your code, addressing any coding standard issues and ensuring adherence to the project's coding standards?
-- [ ] **Design & Architecture:** Prefer smart defaults over adding new settings; use local state for ephemeral UI logic. Open a Discussion for major architectural or UX changes.
-- [ ] **Git Hygiene:** Keep PRs atomic (one logical change). Clean up commits and rebase on `dev` to ensure no unrelated commits (e.g. from `main`) are included. Push updates to the existing PR branch instead of closing and reopening.
-- [ ] **Title Prefix:** To clearly categorize this pull request, prefix the pull request title using one of the following:
-  - **BREAKING CHANGE**: Significant changes that may affect compatibility
-  - **build**: Changes that affect the build system or external dependencies
-  - **ci**: Changes to our continuous integration processes or workflows
-  - **chore**: Refactor, cleanup, or other non-functional code changes
-  - **docs**: Documentation update or addition
-  - **feat**: Introduces a new feature or enhancement to the codebase
-  - **fix**: Bug fix or error correction
+- [ ] **Target branch:** The pull request targets the `dev` branch. **PRs targeting `main` will be immediately closed.**
+- [ ] **Description:** A concise description of the changes is provided below.
+- [ ] **Changelog:** A changelog entry following [Keep a Changelog](https://keepachangelog.com/) format is included at the bottom.
+- [ ] **Documentation:** Relevant documentation has been added or updated in the [Open WebUI Docs Repository](https://github.com/open-webui/docs).
+- [ ] **Dependencies:** Any new or updated dependencies are explained, tested, and documented.
+- [ ] **Testing:** Manual tests have been performed to verify the fix/feature works correctly and does not introduce regressions. Screenshots or recordings are included where applicable.
+- [ ] **No Unchecked AI Code:** This PR is either human-written or has undergone thorough human review AND manual testing. Unreviewed AI-generated PRs may be closed immediately.
+- [ ] **Self-Review:** A self-review of the code has been performed, ensuring adherence to project coding standards.
+- [ ] **Architecture:** Smart defaults are preferred over new settings. Local state is used for ephemeral UI logic. Major architectural or UX changes have been discussed first.
+- [ ] **Git Hygiene:** The PR is atomic (one logical change), rebased on `dev`, and contains no unrelated commits.
+- [ ] **Title Prefix:** The PR title uses one of the following prefixes:
+  - **BREAKING CHANGE**: Changes affecting backward compatibility
+  - **build**: Build system or dependency changes
+  - **ci**: CI/CD workflow changes
+  - **chore**: Refactoring, cleanup, or non-functional changes
+  - **docs**: Documentation additions or updates
+  - **feat**: New features or enhancements
+  - **fix**: Bug fixes or corrections
   - **i18n**: Internationalization or localization changes
-  - **perf**: Performance improvement
-  - **refactor**: Code restructuring for better maintainability, readability, or scalability
-  - **style**: Changes that do not affect the meaning of the code (white space, formatting, missing semi-colons, etc.)
-  - **test**: Adding missing tests or correcting existing tests
-  - **WIP**: Work in progress, a temporary label for incomplete or ongoing work
+  - **perf**: Performance improvements
+  - **refactor**: Code restructuring
+  - **style**: Formatting changes (whitespace, semicolons, etc.)
+  - **test**: Test additions or corrections
+  - **WIP**: Work in progress
 
 # Changelog Entry
 
 ### Description
 
-- [Concisely describe the changes made in this pull request, including any relevant motivation and impact (e.g., fixing a bug, adding a feature, or improving performance)]
+- [Describe the changes, including motivation and impact]
 
 ### Added
 
-- [List any new features, functionalities, or additions]
+- [New features, functionalities, or additions]
 
 ### Changed
 
-- [List any changes, updates, refactorings, or optimizations]
+- [Changes, updates, refactorings, or optimizations]
 
 ### Deprecated
 
-- [List any deprecated functionality or features that have been removed]
+- [Deprecated functionality or features]
 
 ### Removed
 
-- [List any removed features, files, or functionalities]
+- [Removed features, files, or functionalities]
 
 ### Fixed
 
-- [List any fixes, corrections, or bug fixes]
+- [Bug fixes or corrections]
 
 ### Security
 
-- [List any new or updated security-related changes, including vulnerability fixes]
+- [Security-related changes or vulnerability fixes]
 
 ### Breaking Changes
 
-- **BREAKING CHANGE**: [List any breaking changes affecting compatibility or functionality]
+- **BREAKING CHANGE**: [Changes affecting compatibility or functionality]
 
 ---
 
 ### Additional Information
 
-- [Insert any additional context, notes, or explanations for the changes]
-  - [Reference any related issues, commits, or other relevant information]
+- [Any additional context, notes, or references to related issues/commits]
 
 ### Screenshots or Videos
 
-- [Attach any relevant screenshots or videos demonstrating the changes]
+- [Attach relevant screenshots or videos demonstrating the changes]
 
 ### Contributor License Agreement