agent-platform release v4.140.0

Changed

• The installation’s skills credential follows the tenant credential naming convention. The agent-manager component’s range starts at 2.3.0 (>=2.3.0 <3.0.0) and the migrate run’s BOM pin is 2.3.0: with agent-manager.skills.mintGitAuthSecret agent-manager mints tenant-credential-agent-manager-skills-token, composes it onto every git-skill agent and keeps its earlier name agent-manager-skills-token filled. The connectivity chart’s agent-manager migrate run gets the current name and the earlier ones (AGENT_MANAGER_SKILLS_GIT_AUTH_SECRET_NAME, AGENT_MANAGER_SKILLS_GIT_AUTH_PREVIOUS_SECRET_NAMES, derived as agent-manager’s chart derives them, agent-manager.skills.previousGitAuthSecretNames included) and moves every agent naming an earlier name to the current one once that Secret exists; a GitOps-owned agent gets the diff in the run’s report. Nothing is done by hand; the earlier Secret keeps working until no agent names it. make verify-migration asserts the run’s inputs.