chore: sync workflow templates

[stranske]

Sync Summary

Files Updated

• aggregate_agent_metrics.py: Aggregates downloaded weekly agent metrics - required by agents-weekly-metrics.yml
• source_context.js: Classifies PR workflow source context for issue, local, automation, sync, Dependabot, review follow-up, and direct GitHub work
• coverage_monitor_summary.js: Machine-readable weekly coverage monitor checkpoint
• weekly_metrics_artifacts.js: Bounded weekly metrics artifact selection contract
• agents_pr_meta_keepalive.js: PR metadata handling for keepalive
• agents_pr_meta_update_body.js: Updates PR body with agent metadata

Files Skipped

• pr-00-gate.yml: File exists and sync_mode is create_only
• ci.yml: File exists and sync_mode is create_only
• dependabot.yml: File exists and sync_mode is create_only
• AGENTS.md: Repo keeps historical Agents.md casing to avoid case-only path conflicts
• llm_slots.json: None

---

Review Checklist

• CI passes with updated workflows
• No repo-specific customizations were overwritten

Source: stranske/Workflows
Source SHA: 559c76326138b8e3fc9720d212747bbe2556ea3f
Template hash: 3e5a27aaceee
Sync branch: sync/workflows-3e5a27aaceee
Consumer repo: stranske/Trend_Model_Project
Manifest: .github/sync-manifest.yml

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 91b3925608

ℹ️ 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]

Honor explicit non-issue markers before inferring issue refs

resolveNonIssueWorkflowSourceContextForBodySync now nulls explicit non-issue context whenever issueNumber is present, but in this script issueNumber is derived from extractIssueNumberFromPull in agents_pr_meta_keepalive.js, which accepts broad #<digits> matches from PR title/body. That means a PR with an explicit non-issue marker (for example <!-- workflow-source:local_request -->) plus an incidental hash number can be misclassified as issue-driven, and run() will fetch/sync from that issue and overwrite PR body metadata incorrectly; previously explicit non-issue markers short-circuited this path.

Useful? React with 👍 / 👎.

[Copilot]

Copilot encountered an error and was unable to review this pull request. You can try again by re-requesting a review.