#529)

Add a `schedule:` trigger (daily 03:17 UTC) to deploy-docs.yml so the
relyloop.com footer's "build SHA / merged PR / built X ago" stamp
auto-refreshes regardless of which paths the day's PRs touched.

Why. The existing trigger fires only when something under `website/**`
or the workflow file itself changes. This is correct for content
freshness — the public site genuinely only changes when its sources
change — but it leaves the build stamp pinned at the last
website-touching merge. After a week of active infra/chore PRs (like
the 12 corp-network install story PRs that landed today, none of
which touched `website/`), a reader visiting relyloop.com sees an
apparent week-old build and thinks the project is stale, even though
main has advanced ~30 commits.

The rebuild itself is a no-op when nothing in website/ has changed —
the generated site bytes are identical; only the stamp's SHA / PR /
timestamp refresh in the footer.

Timing rationale. 03:17 UTC is offset from the existing project crons
(codeql 04:31 Mon, scorecard 04:27 Mon, reconcile-tracking-issues 05:17
daily) for the project's "minute 17" convention and to avoid GHA peak-
load windows. The deploy uses concurrency group "pages" so timing
collisions with other workflows don't matter — they'd serialize.

Cost. ~30s of GHA time per day = negligible. The workflow already runs
on every website/ change, so we're not introducing new infrastructure;
just a more frequent trigger of an already-validated workflow.

Companion action: triggered the workflow once manually via
`gh workflow run deploy-docs.yml --ref main` to refresh the stamp
immediately (run 27644073762), so the site reflects today's main
(6920106 / #528) before the first cron fires tomorrow at 03:17 UTC.

Signed-off-by: SoundMindsAI <eric.starr@soundminds.ai>
Co-authored-by: Claude Opus 4.7 <noreply@anthropic.com>