What does this PR do?

Fixes #25295 - Cron jobs fail with profile fragmentation when CLI and gateway use different profiles. Module-level constants CRON_DIR, JOBS_FILE, OUTPUT_DIR are resolved once at import time from get_hermes_home(), so all cron operations silently read/write from the wrong profile directory.

Related Issue

Fixes #25295

Type of Change

• Bug fix (non-breaking change that fixes an issue)

Changes Made

• cron/jobs.py - Added _resolve_cron_dir(), _resolve_jobs_file(), _resolve_output_dir() helpers that call get_hermes_home() dynamically. All internal code updated. Module-level constants preserved for backward compat.
• cron/scheduler.py - _build_job_prompt() updated to use _resolve_output_dir().
• hermes_cli/web_server.py - _call_cron_for_profile() updated to monkeypatch both resolve* helpers AND legacy module-level constants.
• tests/cron/test_cron_profile_fragmentation.py - 10 new tests
• tests/cron/test_25295_fail_without_fix.py - 2 new tests
• tests/cron/test_webserver_monkeypatch_compat.py - 4 new tests verifying web_server monkeypatch still works
• tests/cron/test_file_permissions.py - 3 tests updated

How to Test

1. Configure two profiles (default and alt)
2. Create a cron job under the alt profile
3. Start gateway with alt profile
4. Verify the job is visible and runs correctly

Checklist

Code

• I have read the Contributing Guide
• My commit messages follow Conventional Commits
• I searched for existing PRs to make sure this is not a duplicate
• My PR contains only changes related to this fix
• I have run pytest tests/cron/ -q and all 24 tests pass
• I have added tests for my changes
• I have tested on my platform: macOS (arm64)

Documentation and Housekeeping

• I have updated docstrings for the new helpers
• [N/A] cli-config.yaml.example - no config keys changed
• [N/A] CONTRIBUTING.md / AGENTS.md - no architecture changes
• Cross-platform impact: uses Path.mkdir(parents=True, exist_ok=True) - portable
• [N/A] Tool descriptions/schemas - no tool behavior changed