[BLCCoreStudio]

Summary

Upgrades platform/argocd from a compact schema-v2 overview into a schema-v3 deep technical reference centered on Argo CD's actual reconciliation pipeline: source resolution, manifest generation, desired/live comparison, health assessment, sync policy, and repeated convergence.

Changes

• explain API server, repo server, application controller, ApplicationSet controller, Redis, and identity boundaries
• document Application, AppProject, ApplicationSet, resource tracking, diffing, health, sync modes, self-heal, prune, hooks, waves, and deletion semantics
• distinguish sync status from workload health and manifest-generation failures from Kubernetes apply failures
• cover Helm rendering correctly: Helm inflates charts while Argo CD owns application reconciliation lifecycle
• add Git revision strategy, multi-cluster delivery, ApplicationSet fleet behavior, promotion models, and resource ownership
• cover RBAC, project tenancy, cluster/repository credentials, repo-server/plugin trust, secret-delivery boundaries, and supply-chain concerns
• add reliability, disaster recovery, scaling, observability, operational debugging, anti-patterns, and a staged learning path
• add Technology Universe coverage metadata
• connect Argo CD deliberately to Kubernetes, Git, Helm, and Flux using typed relationships
• expand machine-readable and human-readable primary sources to current upstream architecture, sync, ApplicationSet, security, health, diffing, Helm, and disaster-recovery documentation

Quality bar

This follows the project's deep-dive standard without copying the Kubernetes or Helm modules mechanically. The organizing model is the Argo CD reconciliation pipeline and the trust/ownership boundaries operators need when Git, rendering, Argo CD, and Kubernetes disagree.