docs: add condition field documentation for CEL-based conditional function execution

- Add condition section to book/04-using-functions with examples and CEL patterns
- Update kptfile schema reference to include the condition field

Signed-off-by: SurbhiAgarwal1 <agarwalsurbhi1807@gmail.com>

Author: SurbhiAgarwal1

documentation/content/en/book/04-using-functions/_index.md

@@ -375,6 +375,68 @@ will merge each function pipeline list as an associative list, using
 `name` as the merge key. An unspecified `name` or duplicated names may
 result in unexpected merges.
 
+### Specifying `condition`
+
+The `condition` field lets you skip a function based on the current state of the resources in the package.
+It takes a [CEL](https://cel.dev/) expression that is evaluated against the resource list. If the expression
+returns `true`, the function runs. If it returns `false`, the function is skipped.
+
+The expression receives a variable called `resources`, which is a list of all KRM resources passed to
+this function step (after `selectors` and `exclude` have been applied). Each resource is a map with
+the standard fields: `apiVersion`, `kind`, `metadata`, `spec`, `status`.
+
+For example, only run the `set-labels` function if a `ConfigMap` named `app-config` exists in the package:
+
+```yaml
+# wordpress/Kptfile (Excerpt)
+apiVersion: kpt.dev/v1
+kind: Kptfile
+metadata:
+  name: wordpress
+pipeline:
+  mutators:
+    - image: ghcr.io/kptdev/krm-functions-catalog/set-labels:latest
+      configMap:
+        app: wordpress
+      condition: resources.exists(r, r.kind == 'ConfigMap' && r.metadata.name == 'app-config')
+```
+
+When you render the package, kpt shows whether the function ran or was skipped:
+
+```shell
+$ kpt fn render wordpress
+Package "wordpress":
+
+[RUNNING] "ghcr.io/kptdev/krm-functions-catalog/set-labels:latest"
+[PASS] "ghcr.io/kptdev/krm-functions-catalog/set-labels:latest"
+
+Successfully executed 1 function(s) in 1 package(s).
+```
+
+If the condition is not met:
+
+```shell
+$ kpt fn render wordpress
+Package "wordpress":
+
+[SKIPPED] "ghcr.io/kptdev/krm-functions-catalog/set-labels:latest" (condition not met)
+
+Successfully executed 1 function(s) in 1 package(s).
+```
+
+Some useful CEL expression patterns:
+
+- Check if a resource of a specific kind exists:
+  `resources.exists(r, r.kind == 'Deployment')`
+- Check if a specific resource exists by name:
+  `resources.exists(r, r.kind == 'ConfigMap' && r.metadata.name == 'my-config')`
+- Check the count of resources:
+  `resources.filter(r, r.kind == 'Deployment').size() > 0`
+
+The `condition` field can be combined with `selectors` and `exclude`. The condition is evaluated
+after selectors and exclusions are applied, so `resources` only contains the resources that
+passed the selection criteria.
+
 ### Specifying `selectors`
 
 In some cases, you want to invoke the function only on a subset of resources based on a

documentation/content/en/reference/schema/kptfile/kptfile.yaml

@@ -71,6 +71,16 @@ definitions:
                     this is primarily used for merging function declaration with upstream counterparts
                 type: string
                 x-go-name: Name
+            condition:
+                description: |-
+                    `Condition` is an optional CEL expression that determines whether this
+                    function should be executed. The expression is evaluated against the list
+                    of KRM resources passed to this function step (after `Selectors` and
+                    `Exclude` have been applied) and should return a boolean value.
+                    If omitted or evaluates to true, the function executes normally.
+                    If evaluates to false, the function is skipped.
+                type: string
+                x-go-name: Condition
             selectors:
                 description: |-
                     `Selectors` are used to specify resources on which the function should be executed