[BLCCoreStudio]

Summary

Upgrades cloud/ansible from a compact schema-v1 overview into a schema-v3 deep technical reference centered on Ansible's real execution model: control-node resolution of inventory, variables, playbooks, plugins, and collections into scheduled task execution across managed systems.

Changes

• distinguish ansible-core from the broader ansible community package and document their independent version/content model
• explain control-node and managed-node trust boundaries, agentless execution constraints, action/module execution, connection plugins, and remote runtime requirements
• deepen inventory, groups, dynamic inventory, variables/precedence, facts, magic variables, playbooks, modules, roles, handlers, and FQCN-based collection usage
• document plugin classes and supply-chain implications for actions, connections, inventory, vars, lookups, filters, callbacks, strategies, and custom content
• cover idempotency, changed_when, failed_when, handlers, failure semantics, blocks/rescue, check/diff mode, privilege escalation, Vault, no_log, and SSH trust
• add scheduling/concurrency guidance for strategies, forks, serial, throttle, run_once, delegation, async tasks, retries, and rolling deployments
• cover reproducible execution environments, collection dependencies, large-fleet performance, Terraform/Kubernetes ownership boundaries, common failure modes, debugging, upgrade discipline, and security
• verify GPL-3.0-or-later from the canonical ansible-core project metadata
• add Technology Universe coverage metadata and typed relationships to Terraform and Kubernetes

Quality bar

The module treats Ansible as a privileged control-plane runtime and plugin ecosystem, not merely 'YAML over SSH'. It makes host scheduling, variable resolution, execution location, concurrency, idempotency, supply chain, and failure semantics explicit enough to reason about real production automation.