Clarify that verification is read-only in CLI workflows (#553)

* Clarify that verification is read-only in CLI workflows

Generated-By: mintlify-agent

* Remove redundant tip from verified content page

Generated-By: mintlify-agent

---------

Co-authored-by: mintlify[bot] <109931778+mintlify[bot]@users.noreply.github.com>

Author: mintlify[bot]

guides/verified-content.mdx

@@ -58,8 +58,10 @@ This guarantees that a verified badge always reflects content that an admin has
 
 Verification status is included in [charts and dashboards as code](/guides/developer/dashboards-as-code). When you run `lightdash download`, verified content includes verification metadata right in the YAML, so you can see which downloaded files represent approved content.
 
-This is especially useful when you're using an AI agent, the [Lightdash CLI](/references/lightdash-cli), or [agent skills](/guides/developer/agent-skills) to build on top of trusted content. You can point your agent at your verified charts and dashboards as a source of truth for approved patterns, metrics, and layouts.
+<Note>
+Verification metadata is currently **read-only** in content-as-code workflows. Running `lightdash download` includes verification status in the YAML, but `lightdash upload` does not write verification back. To apply or remove the verified badge, use the three-dot menu on a chart or dashboard in the Lightdash UI.
 
-<Tip>
-If you're building content with AI agents, starting from verified charts and dashboards is a great way to make sure new content is grounded in patterns your team has already reviewed and approved.
-</Tip>
+Full CLI support for writing verification status is being tracked in [this issue](https://github.com/lightdash/lightdash/issues/22138).
+</Note>
+
+Even though verification is read-only in the CLI today, you can still build on top of verified content. Anything marked as verified in the UI is visible in the downloaded YAML, so your trusted repository can reference those charts and dashboards as the source of truth for downstream work. This is especially useful when you're using an AI agent, the [Lightdash CLI](/references/lightdash-cli), or [agent skills](/guides/developer/agent-skills) to build on top of trusted content.