docs(daemon): refresh stale comment for inline system prompt path

The inline path now carries the full runtime brief (CLI catalog,
workflow steps, persona, skills, project context) rather than just
identity/persona instructions, after #2353 / #2355. The pre-existing
comment still described it as "identity/persona instructions inline",
which would mislead future maintainers about why the inline payload is
load-bearing.

Also call out kiro/kimi alongside openclaw/hermes since they were added
to providerNeedsInlineSystemPrompt in #2328, and document the concrete
failure mode (issues stuck in todo) so the rationale is searchable.

Co-authored-by: multica-agent <github@multica.ai>

server/internal/daemon/daemon.go

@@ -1835,9 +1835,14 @@ func (d *Daemon) runTask(ctx context.Context, task Task, provider string, slot i
 	//   - hermes is driven through ACP and starts from a long-lived Hermes home;
 	//     deployments that cross a wrapper/container boundary can miss the
 	//     task-workdir AGENTS.md even when the prompt itself is delivered.
-	// Pass Multica-defined identity/persona instructions inline so the backend
-	// can prepend them to the turn payload instead of relying only on file
-	// discovery.
+	//   - kiro and kimi are wrapped through their own CLIs whose cwd handling
+	//     is opaque enough that we can't trust the file-based path either.
+	// Pass the full runtime brief inline (CLI catalog + workflow steps + agent
+	// identity/persona + skills + project context) so the backend prepends the
+	// same payload that file-based runtimes pick up from disk. Without this,
+	// these providers silently miss the workflow section and never call
+	// `multica issue status` / `multica issue comment add`, leaving issues
+	// stuck in `todo`.
 	if providerNeedsInlineSystemPrompt(provider) {
 		execOpts.SystemPrompt = runtimeBrief
 	}