docs: add CI optimization analysis for pre-release builds

[vjgit96]

Summary

Analysis of CI performance bottleneck for pre-release builds (LE-517).

Problem

Pre-release builds (PyPI + Docker) require 45-60 minute CI wait, causing significant delays when urgent last minute testing is needed.

Analysis

• Bottleneck identified: Both PyPI publishing and Docker builds wait for full CI suite
• Time impact: 45-60 minutes of 87-112 total minutes (53-67% wasted waiting)
• Cross-platform tests already validate: Installation, dependencies, server startup

Recommendation

Implement skip_ci parameter with safeguards:

• Explicit opt-in (default: false)
• Required justification
• Team notifications
• Audit trail

Key Findings

• Cross-platform tests already catch critical issues (broken installation, missing dependencies)
• Pre-releases are for finding issues - customers expect potential problems
• 50% time savings (100 min → 50 min) for urgent scenarios
• Risk is acceptable: ~10-15% chance of non-critical issues in pre-release context

Documentation

Full analysis in ci-skip-analysis.md including:

• Detailed workflow analysis
• Risk assessment
• Implementation code examples
• Usage guidelines
• Success metrics

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 3bc6b80e-46ab-4b5b-bd9b-39e91d4ee1c3

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch doc/ci-optimization-analysis

📝 Coding Plan

• Generate coding plan for human review comments

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands and usage tips.}

Tip

CodeRabbit can use Trivy to scan for security misconfigurations and secrets in Infrastructure as Code files.

Add a .trivyignore file to your project to customize which findings Trivy reports.

[github-actions]

Frontend Unit Test Coverage Report

Coverage Summary

Lines	Statements	Branches	Functions
	24.37% (8698/35681)	17.19% (4832/28095)	17.05% (1275/7474)

Unit Test Results

Tests	Skipped	Failures	Errors	Time
2783	0 💤	0 ❌	0 🔥	46.955s ⏱️

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.
⚠️ Please upload report for BASE (release-1.9.0@68edb4a). Learn more about missing BASE report.

Additional details and impacted files

@@               Coverage Diff                @@
##             release-1.9.0   #12207   +/-   ##
================================================
  Coverage                 ?   38.69%           
================================================
  Files                    ?     1633           
  Lines                    ?    80625           
  Branches                 ?    12156           
================================================
  Hits                     ?    31194           
  Misses                   ?    47654           
  Partials                 ?     1777           

Flag	Coverage Δ
backend	57.49% <ø> (?)
frontend	21.75% <ø> (?)
lfx	44.65% <ø> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

[Adam-Aghili]

LGTM. I thik we should implment this