chore: sync workflow templates

[stranske]

Sync Summary

Files Updated

• agents-guard.yml: Agents guard - enforces agents workflow protections (Health 45)
• reference_packs.py: Validates and resolves reference pack configuration for shared runner prompt assembly
• orchestrator_skill.py: Validates and resolves exported Orchestrator skill context for remote Codex lanes
• runner_lib/ (1 files): Shared runner prompt assembly, output parsing, and dispatch debounce helpers
• langchain_client.py: LangChain client builder - multi-provider client with slot-based fallback and configuration
• llm_registry.py: LLM model registry helper - shared slot/model selection and blocked-model enforcement

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: 0b04de717dcadc23aea9e2eca0b8679d27e90666
Template hash: 76689bc445fd
Sync branch: sync/workflows-76689bc445fd
Consumer repo: stranske/Trend_Model_Project
Manifest: .github/sync-manifest.yml

[coderabbitai]

Warning

Review limit reached

@stranske, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 2 seconds. Learn how PR review limits work.

To continue reviewing without waiting, enable usage-based billing in the billing tab.

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, the refill rate gradually slows as usage increases. The highest same-day bursts are limited more strictly.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro Plus

Run ID: e4d6bc8a-895b-46df-8d4d-347cc16325df

📥 Commits

Reviewing files that changed from the base of the PR and between ec78830 and e5801c6.

📒 Files selected for processing (6)

• .github/workflows/agents-guard.yml
• scripts/orchestrator_skill.py
• scripts/reference_packs.py
• scripts/runner_lib/core.py
• tools/langchain_client.py
• tools/llm_registry.py

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch sync/workflows-76689bc445fd

---

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

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: e5801c604e

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

Reject dot-only reference packs before deleting

In a repo whose .github/reference_packs.json defines a pack named . or .. and .github/orchestrator_skill.json selects that pack, the existing pack-name regex allows it, so matching[0].checkout_path becomes .reference/. or .reference/... This newly added rmtree then deletes the whole .reference directory, or walks up and removes the workspace contents before suppressing the resulting FileNotFoundError; reject dot-only names or resolve/assert the path stays below a safe .reference/<name> directory before deleting.

Useful? React with 👍 / 👎.

[stranske]

Closing as stale: newer replacement sync PR #5617 exists from Workflows sync wave sync/workflows-591316374281 after stranske/Workflows#2498 merged.