docs: Kiro follow-up after #51

Add kiro to the packaged 10x-cli-guide profile table and correct
AGENTS.md co-ownership docs: non-Claude tools share universal content
and conflict only when bytes diverge.

docs/reference/platform-support.md

@@ -74,13 +74,11 @@ The CLI auto-detects your tool from project markers on first run. Override anyti
 ```
 
 Kiro reads the root `AGENTS.md` as steering context, so it writes to the same
-file as Codex CLI, Devin Desktop and Generic. Two profiles can hold the same
-sentinel block only when their course-rules content is byte-identical — for Kiro
-that means Generic. Installing Kiro alongside Codex CLI or Devin Desktop in one
-project leaves the first owner's block untouched and reports the rules as
-`conflict: skipped (incompatible_shared_owner)`; every other artifact still
-installs normally. Pick one of those profiles per project, or accept that only
-the first one to run keeps the course rules.
+file as Codex CLI, Devin Desktop and Generic. Delivery currently treats every
+non-Claude tool as the same universal content, so those profiles can co-own the
+sentinel when the bytes match. A conflict (`incompatible_shared_owner`) arises
+only when the delivered content diverges; skills, prompts and configs still
+install independently of that rules outcome.
 
 Kiro is detected from `.kiro/steering/`, `.kiro/specs/`, `.kiro/hooks/`,
 `.kiro/settings/` or a bare `.kiro/` directory.

skills/10x-cli-guide/SKILL.md

@@ -241,6 +241,7 @@ Full skill trees land under the selected profile's `skills/<canonical-name>/`:
 | codex | `.agents/` | `AGENTS.md` |
 | devin-desktop | `.devin/` | `AGENTS.md` |
 | gemini | `.gemini/` | `GEMINI.md` |
+| kiro | `.kiro/` | `AGENTS.md` |
 | generic | `.ai/` | `AGENTS.md` |
 
 Profile changes may offer migrate, delete eligible managed files, or keep both;