docs: update README and docs for dev preview readiness

[varshaprasad96]

Summary

• Rewrite README to cover AgentRuntime, AuthBridge webhook, MLflow integration, and all operator controllers
• Update architecture diagram to show full component set (AgentRuntime controller, AuthBridge webhook, MLflow controller)
• Fix broken doc links (a2a-signature-verification.md → agentcard-signature-verification.md, identity-binding-quickstart.md → agentcard-identity-binding.md)
• Add all docs to the documentation table (AuthBridge, controller-webhook interaction, MLflow, client registration)
• Add AgentRuntime Quick Start alongside manual label path
• Fix protocol label requirement: clarify that Deployments need protocol.kagenti.io/a2a for AgentCard auto-creation (was incorrectly stated as "no kagenti labels required")
• Remove hardcoded Helm chart version from install instructions

Test plan

• Verify all doc links in the Documentation table resolve correctly
• Verify Mermaid architecture diagram renders on GitHub
• Verify sample YAML links in Examples section resolve
• Cross-reference protocol label requirement against agentcardsync_controller.go shouldSyncWorkload()

Signed-off-by: @varshaprasad96 varshaprasad96@gmail.com
🤖 Generated with Claude Code

[r3v5]

Thanks, Varsha! LGTM

[varshaprasad96]

cc: @pdettori @cwiklik can we get a review on this please. It is just to ensure that README is updated, when customers from RH summit visit this repo. Thanks!

[ChristianZaccaria]

/lgtm, thank you!!

[zanetworker]

@pdettori can you have a look?

[pdettori]

Docs update is accurate — all claims about controller label behavior, config hash, and rolling updates verified against source (agentcardsync_controller.go, agentcard_controller.go, agentruntime_controller.go). All doc links and sample YAML references resolve.

A few wording suggestions inline — nothing blocking.

Assisted-By: Claude Code

[pdettori]

suggestion: "pointing to a clean Deployment" — the Deployment isn't fully clean since it carries the protocol.kagenti.io/a2a label. Consider "pointing to your Deployment" for consistency with the updated GETTING_STARTED.md heading ("Deploy a Deployment with Protocol Label").

[pdettori]

suggestion: "Deploy a clean Deployment" contradicts the fact that users must add protocol.kagenti.io/a2a (shown a few lines below). Consider: "Deploy a Deployment with a protocol label and create an AgentRuntime CR:" — consistent with GETTING_STARTED.md which was correctly updated.

[pdettori]

suggestion (accuracy/clarity): This could be read as "the protocol label alone triggers AgentCard creation." Since shouldSyncWorkload() requires both kagenti.io/type=agent (applied by AgentRuntime) and a protocol label, consider:

The operator will apply kagenti.io/type: agent labels and inject AuthBridge sidecars. Together with the protocol.kagenti.io/a2a label on the Deployment, this triggers automatic AgentCard creation for agent discovery.