Split workflows in readme

[strawgate]

We have workflows for humans coordinating agents like issue triage, mention in * and PR review

And then we have continuous improvement and agent factory workflows let's split these out in the doc

[github-actions]

tl;dr: The workflow list is currently a single combined table in README.md and gh-agent-workflows/README.md; split it into a “Human-coordinated” section vs “Continuous improvement / agent factory” section to match the distinction described in the issue.

Recommendation
Split the workflow table(s) into two labeled sections so the human-in-the-loop workflows (issue triage, mention-in-*, PR review/PR checks fix) are distinct from the scheduled improvement/factory workflows; update both README.md and gh-agent-workflows/README.md so the entry points stay consistent.

Findings

The root README lists all workflows in a single table:

README.md:24-41
| Workflow | Trigger | Description |
| --- | --- | --- |
| PR Review | PR opened/updated | Automated code review with inline comments |
| Issue Triage | New issues | Investigate and provide implementation plans |
| Mention in Issue | `/ai` command | Answer questions, debug, create PRs |
| Mention in PR | `/ai` command | Review, fix code, push changes |
| PR Checks Fix | Failed PR checks | Analyze failures and optionally push fixes |
| Small Problem Fixer | Weekday schedule | Fix a small, related issue set and open a focused PR |
| Code Simplifier | Weekday schedule | Simplify overcomplicated code with high-confidence refactors |
| Test Improvement | Weekly schedule | Add targeted tests and clean up redundant coverage |
| Release Update Check | Weekly schedule | Open a PR updating pinned ai-github-actions workflow SHAs and suggest workflow changes |
| Bug Hunter | Weekday schedule | Find a reproducible, user-impacting bug and file an issue |
| Docs Drift | Weekday schedule | Detect code changes needing doc updates |
| Docs New Contributor Review | Weekly schedule | Review docs from a new contributor perspective |
| Project Summary | Daily schedule | Summarize recent activity and priorities |
| Breaking Change Detect | Weekday schedule | Detect undocumented public breaking changes |
| Semantic Function Clustering | Weekday schedule | Identify semantic function clustering refactor opportunities |

The gh-agent-workflows/README.md list is also a single combined table and includes additional scheduled workflows:

gh-agent-workflows/README.md:7-26
| Workflow | Trigger | Description |
| --- | --- | --- |
| [PR Review](pr-review/) | PR opened/updated | AI code review with inline comments |
| [Issue Triage](issue-triage/) | New issues | Investigate and provide implementation plans |
| [Mention in Issue](mention-in-issue/) | `/ai` in issues | Answer questions, debug, create PRs |
| [Mention in PR](mention-in-pr/) | `/ai` in PRs | Review, fix code, push changes |
| [PR Checks Fix](pr-checks-fix/) | Failed PR checks | Analyze failures and optionally push fixes |
| [Small Problem Fixer](small-problem-fixer/) | Weekday schedule | Fix small, related issues and open a focused PR |
| [Code Simplifier](code-simplifier/) | Weekday schedule | Simplify overcomplicated code with high-confidence refactors |
| [Test Improvement](test-improvement/) | Weekly schedule | Add targeted tests and clean up redundant coverage |
| [Release Update Check](release-update/) | Weekly schedule | Open a PR updating pinned ai-github-actions workflow SHAs and suggest workflow changes |
| [Bug Hunter](bug-hunter/) | Weekday schedule | Find reproducible bugs and file reports |
| [Docs Drift](docs-drift/) | Weekday schedule | Detect code changes needing doc updates |
| [Docs New Contributor Review](docs-new-contributor-review/) | Weekly schedule | Review docs from a new contributor perspective |
| [Project Summary](project-summary/) | Daily schedule | Summarize recent activity and priorities |
| [Downstream Health](downstream-health/) | Daily schedule | Monitor downstream repo quality |
| [Breaking Change Detect](breaking-change-detect/) | Weekday schedule | Detect undocumented public breaking changes |
| [Semantic Function Clustering](semantic-function-clustering/) | Weekday schedule | Identify function clustering refactor opportunities |
| [Stale Issues](stale-issues/) | Weekday schedule | Find resolved issues that can be closed |
| [Agent Efficiency](agent-efficiency/) | Weekday schedule | Analyze agent logs for inefficiencies |

Verification

No tests or commands were run (documentation-only change).

Detailed Action Plan

1. In README.md:24-41, split the single workflow table into two labeled sections (e.g., “Human-coordinated workflows” vs “Continuous improvement / agent factory workflows”).
2. Place PR Review, Issue Triage, Mention in Issue, Mention in PR, and PR Checks Fix under the human-coordinated section; keep the scheduled workflows under the continuous-improvement/agent-factory section.
3. Apply the same split to gh-agent-workflows/README.md:7-26, ensuring any additional scheduled workflows (e.g., Downstream Health, Stale Issues, Agent Efficiency) are grouped under the scheduled section.
4. If you want the root README to stay shorter, keep the split but add a note that the full list (including additional scheduled workflows) lives in gh-agent-workflows/README.md.

Related Items

Type	Link	Relevance
PR	#124	Adds a new workflow and mentions README table updates in summary
PR	#123	Adds new PR CI workflows that may need to be placed into the split sections
File	README.md:24-41	Current combined workflow table
File	gh-agent-workflows/README.md:7-26	Current combined workflow table including additional scheduled workflows

---

What is this? | From workflow: Issue Triage Agent

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #127

[strawgate]

/ai make a pr

[github-actions]

Update: opened a PR that splits the workflow tables into human-coordinated vs continuous improvement/agent factory sections in both README.md and gh-agent-workflows/README.md.

Testing: not run (documentation-only change).

---

What is this? | From workflow: Issue Assistant

Give us feedback! React with 🚀 if perfect, 👍 if helpful, 👎 if not. for issue #127