SIR-1523 - Validate watched saves before upload

[KeinerM]

What changed

• Added per-save validation to raisely start for campaign styles and components before upload.
• On validation failure, the watcher now prints the validator error inline and skips upload for that save.
• Refactored watcher setup into a testable registration function so watcher behavior can be verified directly.
• Added tests covering invalid SCSS saves, invalid component saves, watcher persistence after failure, and successful recovery on the next valid save.

---

Note

Medium Risk
Medium risk because it changes raisely start watcher behavior and introduces token-dependent validation before uploads, which could affect developer workflows if validation or watcher wiring is incorrect.

Overview
Adds per-save validation to raisely start watchers: campaign stylesheet saves now call validateCampaignSass before uploadStyles, and component saves call validateComponent before updateComponentFile/updateComponentConfig, failing the ora loader inline and skipping the upload on validation errors.

Refactors watcher logic into exported, dependency-injectable helpers (handleCampaignChange, handleComponentChange, registerStartWatchers) and adds Vitest coverage to ensure invalid saves don’t upload, subsequent valid saves recover, and watcher callbacks keep running after failures.

Risk Assessment (Framework v2.0)

Dimension	Tier	Score	Rationale
Security	1	Low	No findings
Sensitive domains	1	Medium	Touches token-backed validation flow used during uploads (auth-adjacent), though no auth/permissions logic is changed
Data integrity	1	Low	No data access changes
Deployment	1	Low	No infra/CI/deploy changes
Scope	2	Medium	Moderate refactor of existing watcher logic plus new tests
Architecture	2	Low	Localized to start command and related validation calls
Feature flags	2	Low	Internal dev-tooling behavior change; feature flags not applicable
Dependencies	2	Low	No dependency changes

Mitigating Factors

• Adds focused unit tests for failure and recovery paths.

Findings

#	Finding	Status	Resolution

Outstanding findings: 0
Overall risk: MEDIUM
Decision: APPROVED
Rationale: Single Tier 1 Medium (auth-adjacent token validation before uploads) with good unit coverage and no open findings.

^{Reviewed by Cursor Bugbot for commit a451eb9. Bugbot is set up for automated code reviews on this repo. Configure here.}

[cursor]

Cursor Bugbot has reviewed your changes and found 3 potential issues.

^{❌ Bugbot Autofix is OFF. To automatically fix reported issues with cloud agents, have a team admin enable autofix in the Cursor dashboard.}

^{Reviewed by Cursor Bugbot for commit 6f305bb. Configure here.}