[Self-Heal] Add self-scheduling auto-repair workflow

[badMade]

This PR introduces a complete, self-adapting, self-scheduling CI auto-repair system. It adds an idempotent 6-step repair pipeline (scripts/self_heal.mjs), a dynamic scheduling system (scripts/compute_schedule.mjs), and the corresponding GitHub Action workflows (self-heal.yml, compute-schedule.yml). The system gracefully handles drift and failures, avoids loops, limits itself to specific safe paths, and computes its own schedule based on a rolling lookback window of repository commit telemetry and recent self-heal PR success/failure streaks.

---

PR created automatically by Jules for task 1052234786077372673 started by @badMade

[google-labs-jules]

👋 Jules, reporting for duty! I'm here to lend a hand with this pull request.

When you start a review, I'll add a 👀 emoji to each comment to let you know I've read it. I'll focus on feedback directed at me and will do my best to stay out of conversations between you and other bots or reviewers to keep the noise down.

I'll push a commit with your requested changes shortly after. Please note there might be a delay between these steps, but rest assured I'm on the job!

For more direct control, you can switch me to Reactive Mode. When this mode is on, I will only act on comments where you specifically mention me with @jules. You can find this option in the Pull Request section of your global Jules UI settings. You can always switch back!

New to Jules? Learn more at jules.google/docs.

---

For security, I will only act on instructions from the user who triggered this task.

[gemini-code-assist]

Code Review

This pull request introduces a self-healing CI pipeline designed to automatically address project drift and CI failures. It includes a multi-step repair script, a health check utility, and a telemetry-based scheduling script, along with supporting documentation and dependencies. Feedback focuses on improving the robustness of the health check by using "--if-present" for linting to avoid masking failures, ensuring consistent exit codes in the repair script to prevent empty pull requests, and adding "typesync" to the project's dependencies to support the type synchronization step.

[gemini-code-assist]

The current implementation using || echo masks actual linting failures. If an npm run lint script is added to the project and it fails due to linting errors, the health check will still report success because the echo command ensures a zero exit code. Using the --if-present flag is a more robust way to skip the check only if the script is missing while still failing on actual linting errors.

Suggested change

	allPassed = allPassed && runCommand('npm run lint || echo "No lint script found, skipping"', 'Lint');
	allPassed = allPassed && runCommand('npm run lint --if-present', 'Lint');

[gemini-code-assist]

There is an inconsistency in exit codes for the "healthy with no diff" state. Here it exits with 0, but line 102 exits with 1 specifically to "prevent empty PR". If the CI workflow triggers a Pull Request creation based on a successful exit code, this line will cause an unnecessary or empty PR to be opened when the project is already healthy.

Suggested change

	process.exit(0);
	process.exit(1);

[gemini-code-assist]

The self_heal.mjs script relies on typesync (line 55), but it is not listed in the project's dependencies. Adding it to devDependencies ensures it is available in the CI environment and avoids the overhead and potential security risks of downloading it via npx on every run.

Suggested change

	"typescript": "^5.8.2",
	"typescript": "^5.8.2",
	"typesync": "^0.11.1",