maas-nightly-qe-impact

MaaS Nightly QE Impact

Notify the merge team when a MaaS autofix may require follow-up in downstream nightly test or CI repos. This skill is informational only — it does not block merge or trigger re-iteration.

Step 1: Confirm context

1. Read .autofix-context/ticket.json for the ticket key and summary. If the file is missing or malformed, write an empty findings file and stop.
2. Read autofix-output/.autofix-verdict.json. If verdict is not committed, write an empty findings file and stop:

mkdir -p .autofix-context/extension-findings
echo '[]' > .autofix-context/extension-findings/maas-nightly-qe-impact.json

1. Load the static trigger catalog from ${CLAUDE_SKILL_DIR}/references/impact-triggers.md and repo paths from ${CLAUDE_SKILL_DIR}/references/repo-locations.md.

Step 2: Analyze the code change

Collect the diff against the target branch:

TARGET=$(git rev-parse --abbrev-ref origin/HEAD 2>/dev/null | sed 's|^origin/||')
BASE="origin/${TARGET:-main}"
git diff --name-only "${BASE}...HEAD" 2>/dev/null || git diff --name-only HEAD~1
git diff "${BASE}...HEAD" 2>/dev/null | head -2000

Classify changed files against the trigger catalog. Flag a category when the diff touches matching paths or introduces matching concepts (env vars, CRD fields, namespace names, API routes, NetworkPolicy selectors, deployment names).

High-signal patterns (learned from models-as-a-service#1051):

• Namespace moves (INFRA_NAMESPACE, odh-ai-gateway-infra, redhat-ai-gateway-infra, controller vs infra namespace)
• Secret relocation (maas-db-config, cross-namespace DB URLs)
• Renamed reconciler fields (MaaSAPINamespace → InfraNamespace)
• NetworkPolicy label selectors affecting Gateway ↔ maas-api traffic
• Deploy/script changes under scripts/deploy.sh, scripts/setup-database.sh, scripts/validate-deployment.sh
• New or changed API endpoints under /v1/ or /internal/v1/
• CRD schema changes for MaaS resources (Tenant, MaaSAuthPolicy, etc.)