Update the proposal

Signed-off-by: Michi Mutsuzaki <michi@isovalent.com>

cilium/CFP-25694-move-cilium-cli-to-cilium-repo.md

@@ -56,7 +56,7 @@ compatibility of `cilium-cli` with respect to `cilium` versions.
 
 ### 3. Release `cilium-cli` from [cilium/cilium-cli] repository
 
-We do not need to change the release process / cadence to accomplish the goals
+You do not need to change the release process / cadence to accomplish the goals
 defined in this CFP. Continue releasing `cilium-cli` from [cilium/cilium-cli] at
 its own cadence using its own versioning that is independent of [cilium/cilium]
 versioning as you have been doing in [cilium/cilium-cli] repository.
@@ -92,11 +92,25 @@ This proposal impacts users who depend on [cilium/cilium-cli] as a library.
   version, and transitively find the `github.com/cilium/cilium/cli` version to
   depend on.
 
-### Key Question: Do we lose any test coverage?
-
-### Key Question: How do we run CI for CLI? More specifically, how do we ensure that changes to Cilium CLI remain compatible with older released versions of Cilium?
-
-### Key Question: Where do we store the release artifacts? Will the cilium/cilium repository release page contain both CNI and CLI releases? Or do we keep cilium-cli for CLI releases?
+### Key Question: How do you run CI for CLI? More specifically, how do you ensure that changes to Cilium CLI remain compatible with older released versions of Cilium?
+
+Here is the list of GitHub workflows that currently run for each pull requests in [cilium/cilium-cli]
+using the latest version of Cilium:
+
+- https://github.com/cilium/cilium-cli/blob/main/.github/workflows/aks-byocni.yaml
+- https://github.com/cilium/cilium-cli/blob/main/.github/workflows/eks-tunnel.yaml
+- https://github.com/cilium/cilium-cli/blob/main/.github/workflows/eks.yaml
+- https://github.com/cilium/cilium-cli/blob/main/.github/workflows/externalworkloads.yaml
+- https://github.com/cilium/cilium-cli/blob/main/.github/workflows/gke.yaml
+- https://github.com/cilium/cilium-cli/blob/main/.github/workflows/kind.yaml
+- https://github.com/cilium/cilium-cli/blob/main/.github/workflows/multicluster.yaml
+
+[cilium/cilium] has a similar coverage using CI images instead of released images,
+so it's probably an overkill to port all of these workflows to [cilium/cilium]. My
+proposal is to move https://github.com/cilium/cilium-cli/blob/main/.github/workflows/kind.yaml
+to [cilium/cilium], and run this workflow for pull requests that modify files
+under `cli/` directory. This ensures that any changes under `cli/` directory get
+tested against a released version of Cilium.
 
 ## Alternatives to Consider