ci: prepare default-disabled Kody fix proposal caller

[jaywedgeworth22]

Summary

• Adds a default-disabled GitHub Actions workflow for generating Kody DeepSeek fix proposals after a successful check run is associated with a pull request.
• Restricts execution to the first workflow attempt and the configured Kody check app and bot. Runs without an associated PR, or with multiple associated PRs, are skipped.
• Invokes the pinned reusable autofix workflow with the swift profile and limits proposal inputs to Sources/CodeCaps/ and Sources/QuotaCore/.
• Keeps the integration non-operational by default with a daily attempt limit of 0, a pending budget policy, and no enabled repository variable. MiniMax routing and budget integration remain explicitly out of scope until a reviewed replacement and secure activation setup are ready.
• Grants the proposal job access to repository contents, pull requests, checks, and actions.

Concurrency behavior

The workflow groups work by repository and associated PR, with check-run ID as a fallback, and does not cancel an in-progress run. However, the default concurrency queue allows only one pending run per group, so a newer event can still replace an unstarted proposal run for the same PR.

[kody-ai]

Code Review Completed! 🔥

The code review was successfully completed based on your current configurations.

Kody Guide: Usage and Configuration

Interacting with Kody

• Request a Review: Ask Kody to review your PR manually by adding a comment with the @kody start-review command at the root of your PR.

• Validate Business Logic: Ask Kody to validate your code against business rules by adding a comment with the @kody -v business-logic command.

• Provide Feedback: Help Kody learn and improve by reacting to its comments with a 👍 for helpful suggestions or a 👎 if improvements are needed.

Current Kody Configuration

Review Options

The following review options are enabled or disabled:

Options	Enabled
Bug	✅
Performance	✅
Security	✅
Business Logic	✅

Access your configuration settings here.

​

[kody-ai]

🤔 Insufficient Task Context

I found a task linked to this PR, but it only contains minimal information (title only, no description or acceptance criteria). To perform a meaningful business rules validation, I need more details.

🔍 What I need to validate:

• Business requirements and acceptance criteria
• Expected behavior and business rules
• Edge cases and constraints to consider

💡 How to improve the task context:

• Add a description to the linked ticket
• Include acceptance criteria or business rules
• Describe the expected behavior after the change

⚠️ Important:

A task title alone is not sufficient to determine whether the implementation is correct or complete.

---

💡 This validation runs automatically only on the first review of a pull request. To run it again, comment @kody -v business-logic.

[kody-ai]

Concurrency cancellation in .github/workflows/kody-fleet-autofix.yml silently drops serialized Kody runs for the same PR: under GitHub's default queue: single, each newly queued run cancels the previous pending run regardless of cancel-in-progress: false, which protects only the in-progress run, so a third near-simultaneous check completion can prevent fix proposals for the reviewed head SHA even though the daily slot remains. Key the group by github.event.check_run.id (falling back to github.event.check_run.pull_requests[0].number) so each eligible trigger owns its slot while the callee's per-UTC-day kody-reserve group and create-only attempt tags bound paid work, or use queue: max if per-PR serialization must remain.

concurrency:
  # Key on the check run id: a per-PR group serializes runs, and under the
  # default `queue: single` the pending run is canceled when a newer one is
  # queued, silently dropping proposals even with cancel-in-progress: false.
  group: kody-caller-${{ github.repository_id }}-${{ github.event.check_run.id || github.event.check_run.pull_requests[0].number }}
  cancel-in-progress: false

Prompt for LLM

File .github/workflows/kody-fleet-autofix.yml:

Line 16 to 18:

Concurrency cancellation in `.github/workflows/kody-fleet-autofix.yml` silently drops serialized Kody runs for the same PR: under GitHub's default `queue: single`, each newly queued run cancels the previous pending run regardless of `cancel-in-progress: false`, which protects only the in-progress run, so a third near-simultaneous check completion can prevent fix proposals for the reviewed head SHA even though the daily slot remains. Key the group by `github.event.check_run.id` (falling back to `github.event.check_run.pull_requests[0].number`) so each eligible trigger owns its slot while the callee's per-UTC-day `kody-reserve` group and create-only attempt tags bound paid work, or use `queue: max` if per-PR serialization must remain.

Suggested Code:

concurrency:
  # Key on the check run id: a per-PR group serializes runs, and under the
  # default `queue: single` the pending run is canceled when a newer one is
  # queued, silently dropping proposals even with cancel-in-progress: false.
  group: kody-caller-${{ github.repository_id }}-${{ github.event.check_run.id || github.event.check_run.pull_requests[0].number }}
  cancel-in-progress: false

_{Talk to Kody by mentioning @kody}

_{Was this suggestion helpful? React with 👍 or 👎 to help Kody learn from this interaction.}

​

​