docs: Add self-healing description

Author: jennifer-shehane

docs/api/commands/prompt.mdx

@@ -382,9 +382,57 @@ describe('Campaign Management', () => {
 })
 ```
 
-## Viewing and exporting generated code
+## See self-healed steps in the Command Log
 
-At any time during or after a test run, you can view the exact Cypress code that `cy.prompt` generated from your natural language steps. This transparency is built into every `cy.prompt` execution.
+cy.prompt self-heals when the element it needs to interact with has changed since the last time the step ran.
+
+When `cy.prompt` self-heals a step, Cypress makes that change visible directly in the Command Log so you can understand exactly what changed and which element the step resolved to.
+
+<DocsImage
+  src="/img/api/prompt/cy-prompt-self-healed-command-log.png"
+  alt="Self-healed tag in the Command Log for a cy.prompt step"
+/>
+
+### Command Log
+
+You can see that a step self-healed in three places:
+
+- **Test** - The test entry shows when at least one `cy.prompt` step self-healed during the run.
+- **Prompt** - The `cy.prompt` command is marked when one or more of its steps self-healed.
+- **Step** - Individual prompt steps show a **Self-healed** tag when the element they resolved to has changed since the last time that step ran.
+
+<DocsImage
+  src="/img/api/prompt/cy-prompt-self-healed-prompt-level-logs.png"
+  alt="Console logs for a self-healed cy.prompt step"
+/>
+
+### Console logs
+
+Clicking a `cy.prompt` command or an individual self-healed step prints detailed Console logs in the Developer Tools, including:
+
+- **Resolved element** - The selector and element that this step resolved to after self-healing.
+- **Cached elements** - The previously resolved elements that the step checked before self-healing.
+- **Self-healed** - Whether the element was self-healed.
+
+If the element was self-healed via cache, the Console logs will show the resolved element within the cached elements. If the element was self-healed via AI, the Console logs will not have the resolved element within the cached elements.
+
+<DocsImage
+  src="/img/api/prompt/cy-prompt-self-healed-step-level-logs.png"
+  alt="Console logs for a self-healed cy.prompt step"
+/>
+
+This level of detail makes it easy to tell whether a self-heal reflects an intentional product change or an unexpected behavior so you can refine or rewrite the step if necessary.
+
+### Self-healed status definitions
+
+**Self-Healed via Cache** - A selector changed since the last time `cy.prompt` ran and the element resolved to another element using the existing cache entry. In this case, `cy.prompt` did **not** call AI; the cached mapping was able to resolve the new element.
+
+**Self-Healed via AI** - A selector changed since the last time `cy.prompt` ran and the element resolved to another element via an AI call because there was no matching cache entry. The Console logs make it clear that AI was used to find the new element.
+
+
+## View and export generated code
+
+At any time during or after a test run, you can view the exact Cypress code that `cy.prompt` generated from your natural language steps. Combined with the self-healed tags and Console details in the Command Log, this gives you a clear, auditable record of what happened during `cy.prompt` execution. This transparency is built into every `cy.prompt` execution.
 
 ### How to view generated code