Enforce Build Size Limit Checking Process

[munlicode]

Overview

Enforce a build size limit checking process across all organization repositories. This process validates that build artifacts remain within acceptable size constraints.

Why

• Backend Size: Indicates whether backend is too large and needs to be decoupled into microservices
• Frontend Size: Indicates if frontend will load too slowly in browsers or risk users deleting the application due to size
• Maintainability: Size metrics help identify when projects need architectural refactoring

Implementation Plan

Phase 1: Define Size Limits

• Decide size categories by project type/purpose (frontend vs backend)
• Define size limits for:
  • Frontend frameworks (Astro, Vite, Electron)
  • Backend frameworks (Tauri, Rust, Python, Go)
  • Other components as needed
• Document size limit rationale and thresholds

Phase 2: Set Default Values

• Establish default size limits for each category
• Create configuration templates
• Document per-project overrides (if applicable)

Phase 3: CI/CD Integration

• Introduce size checking into CI/CD pipeline
• Apply to existing organization repositories
• Add to new repository templates
• Create monitoring and reporting

Acceptance Criteria

• Size checking is automated in CI/CD
• All org repositories validate build sizes
• Documentation is clear and maintained
• Process is scalable for new projects

Notes

This issue applies organization-wide but is maintained in the .github repository as a central policy.