self-development: cover all agent runtimes in per-runtime docs

[kelos-bot]

🤖 Kelos Agent @gjkim42

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

Adds one new convention to AGENTS.md (with CLAUDE.md as its symlink) and the inline agentsMD copies in self-development/agentconfig.yaml and self-development/kelos-workers.yaml:

Cover every supported agent runtime in docs that describe per-runtime behavior. Kelos supports five agent runtimes (claude-code, gemini, codex, opencode, cursor) and they differ on instruction-file paths, env var names, and CLI flags accepted by the entrypoint. When a doc/README/example describes such per-runtime behavior — e.g., where spec.agentsMD is written, which file the agent reads on startup, which API-key variable the entrypoint honors — enumerate the behavior per runtime (one row per claude-code/gemini/codex/opencode/cursor) or explicitly say "Example uses Claude Code; see docs/agent-image-interface.md for the path your agent uses." Writing only the Claude Code path (e.g., ~/.claude/CLAUDE.md) silently misleads readers running the other four runtimes — they will look for a file the entrypoint never creates. This is the docs analogue of "Parameterize e2e tests across all supported agent types."

Motivating review feedback

PR #1209 (docs: clarify per-agent destination paths for agentsMD, merged 2026-05-24, fixes #1208). The merged change rewrote the spec.agentsMD docs in README.md and docs/reference.md to enumerate each agent's destination instead of describing only ~/.claude/CLAUDE.md. Per the PR description:

The README and docs/reference.md previously described spec.agentsMD as being written to ~/.claude/CLAUDE.md, which is only the destination used by the Claude Code entrypoint. Each agent entrypoint writes KELOS_AGENTS_MD to a different agent-specific path:

Agent	Path
claude-code	~/.claude/CLAUDE.md
gemini	~/.gemini/GEMINI.md
codex	~/.codex/AGENTS.md
opencode	~/.config/opencode/AGENTS.md
cursor	~/.cursor/AGENTS.md

A Gemini or Codex user reading the previous docs would expect their agentsMD content to land in ~/.claude/CLAUDE.md, which doesn't exist for their agent.

That is the exact failure mode this convention is meant to prevent on future docs PRs.

A related but distinct rule — Parameterize e2e tests across all supported agent types — is already proposed in open config-update PR #1162 (motivated by PR #1175 "this should not be a codex specific e2e test"). This PR adds the docs-side analogue: where the e2e rule says "test every runtime," the new rule says "document every runtime." Same underlying mistake (agent assumes Claude Code = all agents), different surface.

Scope notes

• CLAUDE.md is a symlink to AGENTS.md, so a single edit covers both surfaces.
• The same bullet is added to the inline agentsMD in self-development/agentconfig.yaml and self-development/kelos-workers.yaml, which is the existing pattern for keeping agentsMD in sync with AGENTS.md.
• No changes to other self-development/*.yaml spawners — they consume the convention list via the shared agentsMD; only the two files that inline that list need editing.
• No code or behavior change — text-only update to three files.
• Existing open config-update PRs (self-development: add CRD, e2e, agent-image, and Dockerfile-pin conventions from recent reviews #1162, self-development: label kelos-image-update PRs #1200, self-development: scope kelos-planner, kelos-reviewer, and kelos-api-reviewer with commentOn #1205, self-development: sweep sibling TaskSpawners when changing webhook filters #1214, self-development: add matrix-completeness convention to agent rules #1219, self-development: assert byte-equality in stream-forwarding tests #1223) each add distinct conventions on different themes; this PR's finding (per-runtime documentation coverage) is not duplicated in any of them. self-development: add CRD, e2e, agent-image, and Dockerfile-pin conventions from recent reviews #1162 is the closest neighbor — it codifies the e2e-test-matrix rule but does not cover the docs/README case.

Which issue(s) this PR is related to:

N/A

Special notes for your reviewer:

N/A

Does this PR introduce a user-facing change?

NONE

---

Summary by cubic

Add a docs rule to cover all supported agent runtimes whenever behavior differs by runtime. Updates AGENTS.md (and CLAUDE.md symlink) plus inline copies in self-development/agentconfig.yaml and self-development/kelos-workers.yaml to require enumerating paths/env/flags for claude-code, gemini, codex, opencode, and cursor (avoids misleading single-runtime paths like ~/.claude/CLAUDE.md).

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

Review in cubic