refactor: remove main-version, use umami-server-3.0.3 for QA

- Remove main-version orphan branch (simplify workflow)
- QA workflows now test umami-server-3.0.3 directly
- Packaging only via to-package (no auto-package on main push)
- Apply DRY: simplify workflow headers, point to CONTRIBUTING.md
- Document auto-save timing in agent.md (15s idle recommendation)

Breaking: main-version branch deleted, QA now explicit version-based

Author: boly38

.github/CONTRIBUTING.md

@@ -65,28 +65,23 @@ ncc build index.js
 
 This project uses **orphan branches** to distribute packaged versions of the action (with all dependencies bundled in `dist/`).
 
-**Two types of orphan branches exist:**
-
-1. **`main-version`** - Auto-generated from the `main` branch
-   - Used for QA and testing the latest development version
-   - Always points to the latest packaged version of `main`
-
-2. **`umami-server-X.Y.Z`** - Version-specific branches (defined in `package.json::orphanBranch`)
-   - Used for stable releases compatible with specific Umami server versions
-   - Examples: `umami-server-3.0.3` for Umami v3.0.3, `umami-server-2.17.0` for Umami v2.17.x
+**Orphan branches** are named after the Umami server version they support (e.g., `umami-server-3.0.3`).
+- Defined in `package.json::orphanBranch`
+- Used for stable releases and QA testing
+- Examples: `umami-server-3.0.3` for Umami v3.0.3, `umami-server-2.17.0` for Umami v2.17.x
 
 ### The `to-package` branch mechanism
 
 To trigger packaging, use the **`to-package` branch** as a pointer:
 
 ```bash
-# To package the current main branch → creates/updates 'main-version'
+# To package the current main branch → creates/updates orphan branch from package.json::orphanBranch
 git checkout main
 git branch -f to-package
 git push origin to-package --force
 
-# To package a specific version → creates/updates orphan branch from package.json
-git checkout v6.0.2
+# To package a specific version tag
+git checkout v7.0.0
 git branch -f to-package
 git push origin to-package --force
 ```
@@ -97,9 +92,7 @@ git push origin to-package --force
 
 1. Workflow `.github/workflows/main_ci_and_package_action.yml` is triggered with `MUST_BE_PACKAGED=true`
 2. The workflow checks out the commit pointed by `to-package`
-3. The workflow determines the target orphan branch name **from that commit's `package.json`**:
-   - If source branch is `main` → `ORPHAN_BRANCH=main-version` (hardcoded)
-   - Otherwise → `ORPHAN_BRANCH=$(jq -r .orphanBranch package.json)` (reads from checked-out commit)
+3. The workflow reads the target orphan branch name **from that commit's `package.json::orphanBranch`**
 4. The code is packaged using `@vercel/ncc` → all deps bundled in `dist/`
 5. A tag `last-<ORPHAN_BRANCH>` is created/updated to mark the source commit
 6. The `dist/` content is force-pushed to the orphan branch `<ORPHAN_BRANCH>`
@@ -126,11 +119,11 @@ git push origin to-package --force
 
 3. **Point `to-package` to the version you want to publish:**
    ```bash
-   git checkout v6.0.2  # The commit containing the orphanBranch value
+   git checkout v7.0.0  # The commit containing the orphanBranch value
    git branch -f to-package
    git push origin to-package --force
    ```
-   💡 The workflow will read `package.json::orphanBranch` from this commit (v6.0.2)
+   💡 The workflow will read `package.json::orphanBranch` from this commit (v7.0.0)
 
 4. **Verify the workflow execution** in GitHub Actions
    - Check that `main_ci_and_package_action.yml` completes successfully

.github/workflows/main_ci_and_package_action.yml

@@ -1,20 +1,9 @@
 # 📦 CI/CD Pipeline with Packaging
 #
-# This workflow performs:
-# 1. CI: Tests, audit, coverage for all triggers
-# 2. PACKAGING: Creates distributable orphan branches (only on 'to-package' or 'main' push)
+# CI: Tests, audit, coverage for all triggers
+# PACKAGING: Creates orphan branches via 'to-package' branch
 #
-# 🎯 PACKAGING MECHANISM:
-# To package a branch, point 'to-package' to it:
-#   git checkout <target-branch>   # e.g., main, v6.0.2, etc.
-#   git branch -f to-package
-#   git push origin to-package --force
-#
-# The target orphan branch is determined by the package.json OF THE COMMIT pointed by 'to-package':
-#   - Source = 'main' → orphan branch = 'main-version' (hardcoded for QA/testing)
-#   - Source = other  → orphan branch = package.json::orphanBranch of that commit (for releases)
-#
-# 📚 See CONTRIBUTING.md section "HowTo publish a new umami-server compatible branch"
+# 📚 Full documentation: .github/CONTRIBUTING.md "HowTo publish a new umami-server compatible branch"
 #
 name: main_ci_and_package_action
 permissions:
@@ -28,7 +17,7 @@ on:
   push:
     branches:
       - to-package  # 📦 Packaging trigger: points to the branch to package
-      - main        # 🧪 CI + creates 'main-version' orphan branch
+      - main        # 🧪 CI only (no packaging)
   pull_request:
     paths:
       - 'lib/**'
@@ -133,17 +122,12 @@ jobs:
         run: pnpm install -g @vercel/ncc
         if: env.MUST_BE_PACKAGED == 'true'
 
-      - name: PACKAGE - SETUP - Define ORPHAN_BRANCH name
+      - name: PACKAGE - SETUP - Define ORPHAN_BRANCH name from package.json
         id: get_branch
         if: env.MUST_BE_PACKAGED == 'true'
         run: |
-          if [[ "${{ github.ref }}" == "refs/heads/main" ]]; then
-          echo "ORPHAN_BRANCH=main-version" >> $GITHUB_ENV
-          else
           echo "ORPHAN_BRANCH=$(jq -r .orphanBranch package.json)" >> $GITHUB_ENV
-          fi
         # nb: jq extracts from package.json using 'orphanBranch' as key
-        # warn: dont target 'main' as orphan branch
 
       - name: PACKAGE - BUILD - autonomous package Action with deps in dist/ and update last tag
         if: env.MUST_BE_PACKAGED == 'true'

.github/workflows/main_manual_qa_cloud.yml

@@ -1,16 +1,7 @@
-# 🧪 QA Test - Umami Cloud (using main-version orphan branch)
+# 🧪 QA Test - Umami Cloud (@umami-server-3.0.3)
 #
-# This workflow tests the PACKAGED version from the 'main-version' orphan branch.
-#
-# ℹ️ The 'main-version' branch is automatically updated when:
-#   - Pushing to 'main' branch (auto-packaging)
-#   - Forcing 'to-package' to point to 'main' then pushing it
-#
-# 🔄 To update 'main-version' with latest main:
-#   git checkout main && git pull
-#   git branch -f to-package && git push origin to-package --force
-#
-# 📚 See CONTRIBUTING.md "HowTo publish a new umami-server compatible branch"
+# Tests packaged orphan branch. To update version: edit 'uses:' line below.
+# 📚 Doc: .github/CONTRIBUTING.md "HowTo publish a new umami-server compatible branch"
 #
 name: main_manual_qa_cloud
 permissions:
@@ -22,7 +13,7 @@ on:
 
 jobs:
   umamiReportJob:
-    name: Manual QA Umami Cloud action-umami-report@main-version
+    name: Manual QA Umami Cloud action-umami-report@umami-server-3.0.3
     runs-on: ubuntu-latest
     env:
       UMAMI_LOGO: https://raw.githubusercontent.com/umami-software/website/refs/heads/master/public/images/umami-logo.png
@@ -33,9 +24,9 @@ jobs:
     #      umami_report: ${{ steps.umamiReport.outputs.umamiReport }}
     #      umami_one_line_report: ${{ steps.umamiReport.outputs.umamiOneLineReport }}
     steps:
-      - name: QA Umami report - orphanBranch=main-version
+      - name: QA Umami report - orphanBranch=umami-server-3.0.3
         id: umamiReportStep
-        uses: boly38/action-umami-report@main-version
+        uses: boly38/action-umami-report@umami-server-3.0.3
         with:
           umami-cloud-api-key: ${{secrets.UMAMI_TEST_CLOUD_API_KEY}}
           umami-site-domain: ${{secrets.UMAMI_TEST_CLOUD_SITE_DOMAIN}}

.github/workflows/main_manual_qa_host.yml

@@ -1,16 +1,7 @@
-# 🧪 QA Test - Umami Hosted (using main-version orphan branch)
+# 🧪 QA Test - Umami Hosted (@umami-server-3.0.3)
 #
-# This workflow tests the PACKAGED version from the 'main-version' orphan branch.
-#
-# ℹ️ The 'main-version' branch is automatically updated when:
-#   - Pushing to 'main' branch (auto-packaging)
-#   - Forcing 'to-package' to point to 'main' then pushing it
-#
-# 🔄 To update 'main-version' with latest main:
-#   git checkout main && git pull
-#   git branch -f to-package && git push origin to-package --force
-#
-# 📚 See CONTRIBUTING.md "HowTo publish a new umami-server compatible branch"
+# Tests packaged orphan branch. To update version: edit 'uses:' line below.
+# 📚 Doc: .github/CONTRIBUTING.md "HowTo publish a new umami-server compatible branch"
 #
 name: main_manual_qa_host
 permissions:
@@ -22,7 +13,7 @@ on:
 
 jobs:
   umamiReportJob:
-    name: Manual QA Umami Hosted action-umami-report@main-version
+    name: Manual QA Umami Hosted action-umami-report@umami-server-3.0.3
     runs-on: ubuntu-latest
     env:
       UMAMI_LOGO: https://raw.githubusercontent.com/umami-software/website/refs/heads/master/public/images/umami-logo.png
@@ -33,9 +24,9 @@ jobs:
     #      umami_report: ${{ steps.umamiReport.outputs.umamiReport }}
     #      umami_one_line_report: ${{ steps.umamiReport.outputs.umamiOneLineReport }}
     steps:
-      - name: QA Umami report - orphanBranch=main-version
+      - name: QA Umami report - orphanBranch=umami-server-3.0.3
         id: umamiReportStep
-        uses: boly38/action-umami-report@main-version
+        uses: boly38/action-umami-report@umami-server-3.0.3
         with:
           umami-server: ${{secrets.UMAMI_SERVER}}
           umami-user: ${{secrets.UMAMI_USERNAME}}

agent.md

@@ -61,6 +61,8 @@ env/                      ← Templates config locale (.env, init scripts)
 **Solutions**:
 - Préférer `intellij_get_file_text_by_path` après `multi_edit` (lit buffer IDE)
 - Éviter `grep`/`cat` immédiatement après édition (lit disque non sauvegardé)
+- **Auto-save IDE**: Settings → System Settings → Synchronization (recommandé: 15s idle)
+- Attendre ~15-20s avant `git status`/`git diff` après éditions multiples
 
 ### Exceptions acceptées