Update self-development README with architecture visualization

[gjkim42]

Summary

• Add an ASCII architecture diagram showing the overall flow between triggers (GitHub issues, cron schedules), TaskSpawners, and their outputs (PRs, issues, triage reports)
• Remove the misplaced one-off tasks section that was leading the deploy instructions
• Add missing kelos-triage.yaml documentation
• Add summary tables (trigger, model, concurrency) for each TaskSpawner

Test plan

• Verify the ASCII diagram renders correctly on GitHub
• Confirm all TaskSpawner descriptions match their YAML definitions

🤖 Generated with Claude Code

---

Summary by cubic

Added an ASCII architecture diagram and expanded TaskSpawner docs to clarify the self-development flows and triage behavior. Documented the kelos/needs-input feedback loop and shared AgentConfig for consistent agent identity.

• New Features

  • Architecture diagram showing triggers → triage/workers → PR flow (CI + self-review) and cron agents, plus the kelos/needs-input loop.
  • Updated TaskSpawner docs with summary tables (trigger, model, concurrency) and a fuller kelos-triage flow (single triage comment, kind/* label, fixed/outdated/duplicate checks, priority, actor recommendation).

• Refactors

  • Removed the misplaced one-off tasks section; deploy steps now live under each TaskSpawner.
  • Standardized schedules and labels; clarified AgentConfig details (git identity, comment signatures, constraints).

^{Written for commit b15696b. Summary will update on new commits.}

[cubic-dev-ai]

1 issue found across 1 file

Prompt for AI agents (unresolved issues)

Check if these issues are valid — if so, understand the root cause of each and fix them. If appropriate, use sub-agents to investigate and fix each issue separately.


<file name="self-development/README.md">

<violation number="1" location="self-development/README.md:43">
P2: The diagram arrows from `kelos-fake-strategist` fan out to all three output types (New Issues, New PRs, Triage Reports), but this spawner only creates GitHub Issues. The "New PRs" and "Triage Reports" boxes should be connected to the spawners that actually produce them (`kelos-self-update` → PRs/Issues, `kelos-triage` → Triage Reports). Consider restructuring the bottom section to show aggregated system outputs rather than implying they all come from `kelos-fake-strategist`.</violation>
</file>

_{Reply with feedback, questions, or to request a fix. Tag @cubic-dev-ai to re-run a review.}