Complete shadow signal notification workflow

[Pigbibi]

Summary

• schedule the long-horizon shadow signal workflow weekly after Friday US market close
• create or update a dated long-horizon-shadow issue instead of creating duplicate issues on reruns
• append an Actions job summary and document that GitHub Issues are the notification channel while the signal remains shadow-only

Validation

• python -m pytest -q
• python scripts/validate_latest_signal.py examples/latest_signal.example.json
• python scripts/post_shadow_signal_request.py --help

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 9ee7f4e8c9

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Use the Friday market date for scheduled issues

Because this cron fires at 02:30 UTC on Saturday, the new issue step later falls back to dt.date.today() and titles the request with Saturday's date. For the weekly post-Friday-close run, that asks the bridge for an as_of/signal_history date that is one day after the Friday market session, which can misdate the shadow artifact and break point-in-time replay assumptions. Pass the intended market date into post_shadow_signal_request.py or derive it explicitly instead of using the runner's UTC date.

Useful? React with 👍 / 👎.