Skip to content

feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow - #284

Merged
don-petry merged 41 commits into
mainfrom
dev-lead/issue-232-20260519-0317
May 20, 2026
Merged

don-petry merged 41 commits into
mainfrom
dev-lead/issue-232-20260519-0317

Conversation

@don-petry

@don-petry don-petry commented May 19, 2026 •

Copy link
Copy Markdown
Collaborator

Closes #232

Implemented by dev-lead agent. Please review.

Summary by CodeRabbit

  • New Features

    • Automated issue triage system now classifies newly opened and reopened issues, assigns relevant labels (up to 3), and posts a welcoming comment with clarifying questions.
  • Documentation

    • Added comprehensive documentation for the issue triage workflow.
  • Tests

    • Added test coverage for issue triage functionality.
  • Chores

    • Updated CI configuration.

Review Change Stack

Copilot AI review requested due to automatic review settings May 19, 2026 03:28
@coderabbitai

coderabbitai Bot commented May 19, 2026 •

Copy link
Copy Markdown

Warning

Rate limit exceeded

@don-petry has exceeded the limit for the number of commits that can be reviewed per hour. Please wait 57 minutes and 19 seconds before requesting another review.

You’ve run out of usage credits. Purchase more in the billing tab.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: b75c16ed-5f95-4225-ac52-5b5a4bc5b96f

📥 Commits

Reviewing files that changed from the base of the PR and between 306fe58 and 5eac9c3.

📒 Files selected for processing (1)
  • .github/workflows/issue-triage.md
📝 Walkthrough

Walkthrough

Adds an issue triage agentic workflow that automatically classifies new GitHub issues, selects up to three labels from an allowed set, and posts a single clarifying question, skipping issues already labeled. Includes a CLI tool for compiling and executing workflows, a two-job GitHub Actions runner with read-only triage and write-enabled apply stages, test scenarios and fixtures, validation tests, and documentation.

Changes

Issue Triage Agentic Workflow

Layer / File(s) Summary
Test Scenarios — Expected Behavior
tests/aw/issue-triage/scenarios.md
Specifies four representative scenarios: bug report (bug + needs-triage labels, repro comment), feature request (enhancement label), question (question label), and already-labeled edge case (skip with no API writes). Also defines validation constraints: allowed-label whitelist, max-3-labels, and single-comment requirement.
Issue Triage Workflow Definition
\.github/workflows/issue-triage.md
Configures the workflow frontmatter (claude-sonnet-4-6 engine, read-only issues permissions, allowed-labels list, max 3 labels per run) and defines a triage prompt that classifies issues, applies labels with special rules for needs-triage and good-first-issue, and generates a single welcoming question. Skips issues already having 2+ labels. Specifies strict JSON-only output contract (normal: labels array + comment; skip: {"skip": true}).
Agentic Workflow CLI Tool
scripts/aw.sh
Implements three main commands: compile validates all workflow .md files against required frontmatter schema (name, trigger, engine, permissions); run loads a workflow by name, renders issue context into the prompt, calls Claude, and returns base64-encoded staged JSON; safe-output apply validates the result (honored skip flag, allowed-labels membership, max-label bounds, non-empty comment) and applies changes via gh CLI. Includes context loading from environment variables or AW_FIXTURE JSON, skip guards, and path-traversal protection.
GitHub Actions Runner Workflow
\.github/workflows/issue-triage-runner.yml
Two-job orchestration triggered on issue opened and reopened events. The triage job runs the CLI in staged mode with read-only permissions, base64-encodes the result, and outputs both result and skip-flag. The apply job depends on triage, runs only when skip is false, decodes the result via temp file, calls safe-output with write permissions, and cleans up.
Test Fixtures & Test Runner
tests/aw/issue-triage/fixtures/scenario-*.json, tests/aw/issue-triage/test_aw_run.sh
JSON fixtures define two test cases (unlabeled bug issue #101, already-labeled issue #102 with skip case). Bash test runner exercises five assertions without live Claude calls: skip detection from label-count, label-count bounds rejection, disallowed-label rejection, skip-flag no-op path, and empty-comment rejection. Uses strict mode with PASS/FAIL tracking.
Issue Triage Documentation
docs/aw/issue-triage.md
Documents the workflow purpose, two-job architecture (read-only triage + write apply with validation), permission model, staged vs live output modes, explicit skip condition behavior (no API writes when triggered), validation requirements for gh aw compile, and a smoke-test procedure referencing scenario specs.
CI Configuration Update
\.github/workflows/ci.yml
Minor adjustment to gitleaks step environment at end of file.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

🚥 Pre-merge checks | ✅ 4 | ❌ 1

❌ Failed checks (1 warning)

Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 50.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
✅ Passed checks (4 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Title check ✅ Passed The title clearly and concisely identifies the main change: implementing Phase 1 of the Issue Triage GitHub Agentic Workflow for issue #232.
Linked Issues check ✅ Passed The PR fulfills all coding requirements from #232: scenarios.md written first, issue-triage.md workflow created with correct trigger/engine/permissions, scripts/aw.sh implements compile/run/safe-output, tests added, and behavior documented in docs/aw/issue-triage.md.
Out of Scope Changes check ✅ Passed The minimal change to .github/workflows/ci.yml (one line adjustment to gitleaks environment) is a necessary fix to support the new workflow execution in CI and falls within scope.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch dev-lead/issue-232-20260519-0317

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

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

@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — human-pr (no-changes)

No changes were needed for this PR.

@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — fix-bot-comment (applied)

Changes committed and pushed.

@gemini-code-assist gemini-code-assist Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Code Review

This pull request introduces an automated "Issue Triage" agentic workflow, including a CLI tool for validation and execution, comprehensive documentation, and test scenarios. The workflow uses Claude to classify GitHub issues and apply labels or comments based on predefined rules. Review feedback identifies several critical issues in the aw.sh script, most notably a high-severity code injection vulnerability caused by direct variable interpolation into Python source code. Other feedback points out incorrect label formatting for the GitHub CLI, potential system argument limit issues when posting large comments, and opportunities to improve the security and efficiency of fixture parsing.

Comment thread scripts/aw.sh Outdated
Comment thread scripts/aw.sh Outdated
Comment thread scripts/aw.sh Outdated
Comment thread scripts/aw.sh Outdated

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Note

Copilot was unable to run its full agentic suite in this review.

Adds a new "Issue Triage" GitHub Agentic Workflow (Phase 1 of #232): a workflow definition, a runner, a generic gh aw CLI shell script, scenario spec, docs, and a CI compile check.

Changes:

  • New issue-triage workflow definition (.github/workflows/issue-triage.md) plus a two-job runner that stages Claude output and applies it via safe-output.
  • New scripts/aw.sh CLI implementing compile, run, and safe-output apply subcommands.
  • Docs, scenario spec, and a aw-compile CI job to validate workflow definitions.

Reviewed changes

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

Show a summary per file
File Description
.github/workflows/issue-triage.md Workflow frontmatter + Claude triage prompt template.
.github/workflows/issue-triage-runner.yml Actions runner: triage (read) → apply (write), bridged via base64-encoded JSON output.
scripts/aw.sh gh aw CLI: compile/validate, run (with skip guard + Claude invocation), safe-output apply.
.github/workflows/test.yml Adds aw-compile job running aw.sh compile --all in CI.
docs/aw/issue-triage.md User-facing docs for the workflow.
tests/aw/issue-triage/scenarios.md Behavioural scenario spec (bug / feature / question / already-labelled).

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comment thread scripts/aw.sh Outdated
Comment thread scripts/aw.sh Outdated
Comment thread scripts/aw.sh Outdated
Comment thread scripts/aw.sh Outdated
Comment thread .github/workflows/issue-triage-runner.yml Outdated
Comment thread .github/workflows/issue-triage.md
Comment thread scripts/aw.sh Outdated
Comment thread docs/aw/issue-triage.md Outdated
Comment thread tests/aw/issue-triage/scenarios.md
Comment thread scripts/aw.sh Outdated
@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead Fix CI — applied

PR: #284 | SHA: 961e1cc52567d9783c5e1b66efb1b48bd044966c
Fix committed and pushed. Waiting for CI.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 961e1cc525

ℹ️ 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".

Comment thread scripts/aw.sh Outdated
Comment thread .github/workflows/issue-triage-runner.yml
Comment thread scripts/aw.sh Outdated
Comment thread .github/workflows/issue-triage-runner.yml
Comment thread scripts/aw.sh Outdated
Comment thread scripts/aw.sh
Comment thread .github/workflows/issue-triage-runner.yml Outdated
@don-petry

Copy link
Copy Markdown
Collaborator Author

No description provided.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 568b293bdb

ℹ️ 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".

Comment thread .github/workflows/issue-triage-runner.yml
Comment thread .github/workflows/issue-triage.md
Comment thread scripts/aw.sh

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a563cc706e

ℹ️ 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".

Comment thread .github/workflows/issue-triage-runner.yml Outdated
Comment thread scripts/aw.sh Outdated
@don-petry

Copy link
Copy Markdown
Collaborator Author

@dev-lead - please fix this PR

@don-petry

Copy link
Copy Markdown
Collaborator Author

Dev-Lead — human (applied)

Changes committed and pushed.

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: a95a13fbff

ℹ️ 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".

Comment thread scripts/aw.sh
Comment thread .github/workflows/test.yml Outdated

@coderabbitai coderabbitai Bot left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 4

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
.github/workflows/issue-triage-runner.yml (1)

1-71: ⚠️ Potential issue | 🟠 Major | ⚡ Quick win

Use the required workflow template verbatim.

This workflow appears to be custom-authored rather than a verbatim template from standards/workflows/, which violates repo workflow policy.

As per coding guidelines, ".github/workflows/**/*.yml: All workflow changes must use templates from standards/workflows/ verbatim without modification".

🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

In @.github/workflows/issue-triage-runner.yml around lines 1 - 71, This workflow
("name: Issue Triage", jobs: triage and apply) must be replaced with the exact
verbatim template from standards/workflows/issue-triage-runner.yml; do not keep
custom edits (e.g., the anthropics/claude-code-action setup step, custom pip
install/run blocks, or modified actions/checkout ref) — fetch the canonical
template and copy its contents exactly into this file so the workflow matches
the required template bit-for-bit, preserving the template's job names (triage,
apply) and steps as-is.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.

Inline comments:
In @.github/workflows/issue-triage-runner.yml:
- Line 20: Update the two actions/checkout steps that currently use
actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd to set
persist-credentials: false so the checkout action does not pass the GITHUB_TOKEN
to later steps; locate the checkout invocations (the two places calling
actions/checkout) and add the persist-credentials: false input under each
checkout step.
- Line 28: Update both CI job steps that run "pip install pyyaml --quiet" (the
triage and apply job run steps) to pin PyYAML to a safe version; replace the
unpinned install with a pinned spec such as "pip install pyyaml==6.0.3 --quiet"
(or at minimum "pyyaml>=5.4") to ensure deterministic, vulnerability-patched
dependency resolution for the triage and apply job run commands.

In @.github/workflows/test.yml:
- Line 31: The pip install step currently runs "pip install pyyaml --quiet"
which lacks version pinning and the --only-binary flag; update that workflow
step (the run: pip install ... command in the GitHub Actions job) to pin pyyaml
to a specific safe version (e.g., ==6.0.2 or another vetted stable release) and
add --only-binary :all: to prevent execution of package setup scripts during
install.
- Line 28: The workflow uses an unpinned third-party action "uses:
actions/checkout@v6" which violates the policy; update both occurrences (the one
shown and the one in the unit-tests job) to pin the action to a specific commit
SHA by replacing the tag reference with the full commit hash for
actions/checkout (e.g., actions/checkout@<commit-sha>) so the workflow
references an immutable revision and satisfies the blanket policy.

---

Outside diff comments:
In @.github/workflows/issue-triage-runner.yml:
- Around line 1-71: This workflow ("name: Issue Triage", jobs: triage and apply)
must be replaced with the exact verbatim template from
standards/workflows/issue-triage-runner.yml; do not keep custom edits (e.g., the
anthropics/claude-code-action setup step, custom pip install/run blocks, or
modified actions/checkout ref) — fetch the canonical template and copy its
contents exactly into this file so the workflow matches the required template
bit-for-bit, preserving the template's job names (triage, apply) and steps
as-is.
🪄 Autofix (Beta)

Fix all unresolved CodeRabbit comments on this PR:

  • Push a commit to this branch (recommended)
  • Create a new PR with the fixes

ℹ️ Review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: ASSERTIVE

Plan: Pro

Run ID: ab0e7c2c-33a0-468e-b65f-b993f2e8d6e2

📥 Commits

Reviewing files that changed from the base of the PR and between c2ff45c and 14872f7.

📒 Files selected for processing (9)
  • .github/workflows/issue-triage-runner.yml
  • .github/workflows/issue-triage.md
  • .github/workflows/test.yml
  • docs/aw/issue-triage.md
  • scripts/aw.sh
  • tests/aw/issue-triage/fixtures/scenario-1-bug.json
  • tests/aw/issue-triage/fixtures/scenario-4-skip.json
  • tests/aw/issue-triage/scenarios.md
  • tests/aw/issue-triage/test_aw_run.sh

Comment thread .github/workflows/issue-triage-runner.yml
Comment thread .github/workflows/issue-triage-runner.yml Outdated
Comment thread .github/workflows/test.yml Outdated
Comment thread .github/workflows/test.yml Outdated
@don-petry

Copy link
Copy Markdown
Collaborator Author

@coderabbitai resolve

don-petry added a commit that referenced this pull request Jun 23, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Jun 23, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Jun 25, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Jun 25, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Jun 25, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Jun 25, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Jun 25, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 2, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 3, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 3, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 3, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 7, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 7, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 7, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 7, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 7, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 7, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 7, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 7, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 7, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 7, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 8, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 8, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 8, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 8, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
don-petry added a commit that referenced this pull request Aug 18, 2026
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(reviews): address review comments [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(bot): address bot feedback [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay]

* chore: apply manual instructions [skip ci-relay]

* chore: sync ci.yml with main to resolve merge conflict

* chore: sync test.yml with main to resolve merge conflict

* fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw)

* fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs)

* fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md

* fix(aw): use correct add-labels schema in issue-triage.md

* fix(aw): remove stale frontmatter from body of issue-triage.md

* fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body

---------

Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Phase 1: Issue Triage gh-aw workflow

3 participants