chore(workflows): recompile daily-repo-status lockfile against current source

[arnaudlh]

Why

PR #136 regenerated the gh-aw lock files before PR #127 (move daily-status to 08:00 SGT) landed on main. After both merges, the committed daily-repo-status.lock.yml carries frontmatter_hash for the pre-SGT source (schedule: daily), but the source .md on main now uses the cron form. Every dispatched/scheduled run fails the integrity check:

ERR_CONFIG: Lock file '.github/workflows/daily-repo-status.lock.yml' is outdated!
The workflow file '.github/workflows/daily-repo-status.md' frontmatter has changed.
Run 'gh aw compile' to regenerate the lock file.

Observed in run 26559296328.

What

Recompiled with gh aw v0.76.1 against the current source. Only daily-repo-status.lock.yml drifted; issue-triage-agent.lock.yml matches its source.

Diff is a hash refresh + drop of a stale inline comment + churn on generated heredoc tokens (GH_AW_PROMPT_*, GH_AW_SAFE_OUTPUTS_CONFIG_*, GH_AW_MCP_CONFIG_*).

[sendtoshailesh]

Review summary

Surgical recompile to fix a lockfile-vs-source drift that's breaking every daily-repo-status run. Verified the diff is exactly the minimal hash refresh + stale comment drop + heredoc token churn described in the PR body — no smuggled drift.

Correctness

• ✅ frontmatter_hash rotated 894339bb… → e28027ab…, compiler_version stays v0.76.1 (no compiler bump).
• ✅ gh-aw-manifest line (actions SHAs + container digests) is unchanged — none of the recent gh-aw version drift sneaks in. Goal of "only recompile, no sweep" achieved.
• ✅ Cron preserved at 0 0 * * * (matches daily-repo-status.md set by chore(daily-status): move schedule to 08:00 SGT (00:00 UTC) #127 = 08:00 SGT).
• ✅ Only daily-repo-status.lock.yml touched; PR body's claim that issue-triage-agent.lock.yml was already in sync is consistent with the single-file diff.
• ✅ All non-+++/--- diff lines fall into {metadata header, dropped stale comment, GH_AW_PROMPT_* / GH_AW_SAFE_OUTPUTS_CONFIG_* / GH_AW_MCP_CONFIG_* heredoc token churn} — verified with a filtered diff.
• ✅ All 5 checks pass (Analyze, Markdown Lint, Structural Validation, actionlint, CLA).
• 🎁 Bonus: the dropped # Friendly format: daily (scattered) comment at the old line 58 was the exact stale comment I flagged in my chore(daily-status): move schedule to 08:00 SGT (00:00 UTC) #127 review — recompile cleans it up for free.

Minor nits (non-blocking)

1. The PR body framing — "PR chore: regenerate gh-aw lock files with v0.76.1 #136 regenerated the gh-aw lock files before PR chore(daily-status): move schedule to 08:00 SGT (00:00 UTC) #127 (08:00 SGT) landed on main" — is inverted by merge timestamps: per gh api, chore(daily-status): move schedule to 08:00 SGT (00:00 UTC) #127 merged 2026-05-28T00:12:09Z and chore: regenerate gh-aw lock files with v0.76.1 #136 merged 2026-05-28T04:50:32Z (≈4.5h later). The real root cause is that chore: regenerate gh-aw lock files with v0.76.1 #136's branch was compiled against the pre-chore(daily-status): move schedule to 08:00 SGT (00:00 UTC) #127 source even though it merged after — i.e. it was rebased/regenerated before the SGT cron landed. The fix is still correct; just worth tightening the wording for the historical record.
2. Suggest adding a gh aw compile --check (or equivalent) to PR CI on changes to .github/workflows/*.md so this exact drift fails fast next time instead of breaking every scheduled run on main.

LGTM — unblocks scheduled daily status runs.