msilich OpenShift update readiness and execution
Assess the requested current-to-target update with evidence, then accompany execution only when explicitly requested.
Start here
- Read the shared domain contract.
- Read the source map and the local sections relevant to this task.
- Use readiness.md before an update. Use execution.md for an approved update or a stalled update.
- Use openshift-api to verify schemas and openshift-mcp to perform permitted operations.
This skill depends on the other nine skills being installed as sibling directories. Resolve every path from this file. Missing documentation, a version mismatch, a denied access or an unknown schema must remain explicit; do not silently proceed with a substitute. Pure document lookup belongs to openshift-docs.
Report
State the evidence-backed result, target and observed versions, local source path and section, changes actually performed, verification, and any remaining unknowns.