chore: sync workflow templates

[stranske]

Sync Summary

Files Updated

• agents-issue-intake.yml: Issue intake - processes new issues for agent assignment
• agents-issue-optimizer.yml: Issue optimizer - LangChain-based issue formatting and optimization (Phase 1)
• agents-issue-format-guard.yml: Issue format guard - validates issues on open/edit/reopen, hold/exemption-label changes, and manual dispatch against AGENT_ISSUE_FORMAT, while durable/wontfix and bot issues remain exempt. Pause and needs-human labels hold dispatch. Any invalid non-exempt issue change on those triggers clears stale agents:formatted state, and hold removal revalidates on resume. Non-conforming unheld work gets agents:format so the optimizer repairs it. Requires .github/scripts/issue_format.py.
• agents-auto-label.yml: Auto-label - suggests/applies labels based on semantic matching (Phase 5A)
• issue_format.py: Pure-stdlib validator for AGENT_ISSUE_FORMAT compliance. Single fleet definition of agent-processable; used by agents-issue-format-guard.yml and callable directly by local filers to pre-flight before gh issue create (non-zero exit = unfit). Do not fork per repo.
• github-api-with-retry.js: GitHub API retry wrapper with exponential backoff and pagination support - required by agents-auto-pilot.yml

Files Skipped

• pr-00-gate.yml: File exists and sync_mode is create_only
• ci.yml: File exists and sync_mode is create_only
• renovate.json: File exists and sync_mode is create_only
• cross-repo-smoke.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: 498dc15ae7672865a19d3b8343dfbfd8cc2c6851
Template hash: f74d65a1c283
Consumer-sync plan ID: sha256:f74d65a1c283af1e33a7e225469f80de9dc1dc57f15ca4462bb2494f70ddd62d
Sync phase: canary
Sync branch: sync/workflows-f74d65a1c283
Consumer repo: stranske/Trend_Model_Project
Manifest: .github/sync-manifest.yml

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[coderabbitai]

Important

Review skipped

Auto reviews are limited based on label configuration.

🚫 Excluded labels (none allowed) (7)

• sync
• workflow:source-sync
• workflow:source-maintenance
• consumer-sync
• integration-sync
• workflows-sync
• template-sync

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: cc9299ac-557d-487e-be57-f9c5780f255a

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[Copilot]

Pull request overview

Syncs GitHub automation from stranske/Workflows into this consumer repo, adding/adjusting issue-automation workflows plus the shared issue-format validator and API retry helper that those workflows depend on.

Changes:

• Adds an issue format guard workflow and a pure-stdlib .github/scripts/issue_format.py validator to keep agents:formatted / agents:format state consistent and prevent formatting loops on closed/exempt issues.
• Updates issue optimizer workflow behavior (run naming, concurrency grouping, recursion guard robustness, validator enforcement, and lease release on failure).
• Adjusts auto-label workflow to source the eligibility action from a dedicated checkout path; tweaks API retry logging to stderr.

Reviewed changes

Copilot reviewed 6 out of 6 changed files in this pull request and generated no comments.

Show a summary per file

File	Description
.github/workflows/agents-issue-optimizer.yml	Improves optimizer run correlation/concurrency, recursion guard history window, enforces canonical issue-format validation, and releases agents:format on failed format runs.
.github/workflows/agents-issue-intake.yml	Prevents issue-intake bridge routing from running on closed issues.
.github/workflows/agents-issue-format-guard.yml	Introduces a guard workflow to validate issue bodies, clear stale labels, and dispatch the optimizer format phase when needed.
.github/workflows/agents-auto-label.yml	Checks out the eligibility action into a dedicated path and runs it from there before proceeding.
.github/scripts/issue_format.py	Adds the fleet-standard, pure-stdlib issue body validator used by the guard/optimizer to enforce AGENT_ISSUE_FORMAT.
.github/scripts/github-api-with-retry.js	Sends retry/backoff messages to stderr instead of stdout.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4fe37a618d

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

Route incomplete issues to a phase that can supply content

When an issue genuinely lacks task or acceptance details, dispatching phase=format cannot repair it: scripts/langchain/issue_formatter.py:102-104 explicitly preserves missing sections as - [ ] _Not provided._, while the newly added validator rejects that placeholder because it has neither a concrete task target nor a verification gate (.github/scripts/issue_format.py:248-263). The format run therefore fails before updating the body, so the guard's primary missing-section scenario is left unchanged rather than routed to machinery that can generate the required content.

Useful? React with 👍 / 👎.