@raishin/vanguard-frontier-agentic 2.8.0 → 2.9.0

package/skills/azure/azure-landing-zone-architect/references/landing-zone-architecture-operations.md

@@ -0,0 +1,68 @@
+# Azure Landing Zone Architecture Operations
+
+Use this reference for current, source-grounded service behavior and the hard review gates that the lean `SKILL.md` intentionally does not carry.
+
+## What people get wrong
+
+- Drawing a management-group tree before clarifying operating model and ownership.
+- Treating a landing-zone accelerator deployment as proof that governance is complete.
+- Putting every workload under one subscription because it is simpler today.
+- Ignoring identity, security, monitoring, backup, policy, and cost baselines in a network-only design.
+- Copying hub-spoke without proving routing, DNS, inspection, and shared-service ownership.
+
+## Officially grounded service shape
+
+Microsoft Learn evidence says Azure landing zones are platform foundations spanning platform and application landing zones, management groups, subscriptions, policy inheritance, connectivity, identity, governance, security, management, and platform automation. The design-areas guidance explicitly calls out billing/tenant, identity/access, resource organization, network topology/connectivity, security, management, governance, and platform automation/DevOps as decisions that affect the foundation.
+
+- A landing zone separates platform shared services from application landing zones while preserving governance and autonomy.
+- Management-group and subscription design control policy inheritance, RBAC scope, chargeback, quota, and blast radius.
+- The platform needs identity/access, governance, management, security, network connectivity, and automation decisions before workload scale.
+- Application landing zones need guardrails but must still let workload teams operate within defined boundaries.
+- Implementation options are starting points; documented design areas must be tailored to business and technical requirements.
+
+## Non-negotiable design rules
+
+- Start with design areas and decision records, not tooling preference.
+- Require explicit ownership for platform subscriptions, application subscriptions, policies, connectivity, monitoring, and incident response.
+- Prefer least-privilege and subscription democratization with policy guardrails over central bottlenecks or unmanaged autonomy.
+- Document exceptions, inheritance boundaries, and migration path for brownfield environments.
+- Never claim production readiness without current-state evidence and operational ownership.
+
+## Minimal safe implementation flow
+
+- Scope business units, environments, regulatory boundaries, connectivity model, identity model, and platform-team responsibilities.
+- Map current or proposed management groups, subscriptions, policy inheritance, RBAC, and shared services.
+- Evaluate each landing-zone design area for missing decisions and unsafe coupling.
+- Rank architecture gaps by blast radius and irreversibility: tenant, management group hierarchy, connectivity, policy, identity, and logging first.
+- Return a staged target architecture with blockers, decision points, and safe next actions.
+
+## High-risk assumptions to kill
+
+- A management-group diagram is not a landing zone unless identity, governance, network, security, management, cost, and automation decisions are explicit.
+- Deploying an accelerator is not proof that the operating model, ownership, exceptions, and brownfield migration risks are solved.
+- Subscription democratization fails if application teams get autonomy without inherited guardrails, monitoring, budget visibility, and recovery boundaries.
+- Hub-spoke is not automatically correct; routing, DNS, inspection, private access, shared-service ownership, and failure domains decide fitness.
+- Broad platform Owner assignments and shared identities destroy the very blast-radius boundaries landing zones are meant to create.
+
+## Safe command/code verification targets
+
+- Inspect architecture docs or IaC for management group hierarchy, platform/application subscription split, environment isolation, and policy inheritance.
+- Review role-assignment patterns for group-based least privilege, PIM/JIT where appropriate, and separation between platform and application responsibilities.
+- Check networking artifacts for hub/spoke or alternative topology, DNS, egress inspection, private endpoint strategy, route tables, and connectivity ownership.
+- Verify governance, security, management, backup, cost, and diagnostic baselines are assigned at intentional scopes with exception handling.
+- Confirm subscription vending or onboarding automation can repeatedly create governed landing zones without hard-coded tenant-specific secrets or one-off manual grants.
+
+## Safe verification targets
+
+- Management group and subscription model supports platform/application separation and environment isolation.
+- Policy, RBAC, diagnostic, security, cost, and backup baselines are inherited where intended.
+- Connectivity design includes routing, DNS, private access, inspection, and failure domains.
+- Subscription vending or onboarding process can produce repeatable, governed application landing zones.
+- Brownfield migration steps avoid breaking existing workloads and preserve rollback options.
+
+## When to push back
+
+- The user wants Terraform/Bicep before design decisions are made.
+- The architecture depends on broad permanent Owner assignments.
+- Shared services have no owner, budget, monitoring, or recovery model.
+- A single subscription or network boundary is hiding compliance, quota, or blast-radius problems.

package/skills/azure/azure-landing-zone-architect/references/mcp-and-evidence.md

@@ -1,25 +1,26 @@
-# MCP and Evidence Path
+# Documentation and Evidence Path
 
-## Evidence path
+## Preferred evidence order
 
-Prefer evidence in this order:
+1. Microsoft Learn documentation through the user's configured documentation MCP for documented Azure behavior.
+2. Sampled read-only Azure or Kubernetes evidence, when safely available, for current configured-environment observations.
+3. Sanitized user-provided evidence.
+4. Clearly labeled inference.
 
-1. Microsoft Learn Azure landing-zone guidance:
-   - landing-zone design areas,
-   - identity and access design area,
-   - governance design area,
-   - security design area,
-   - implementation options when delivery model matters.
-2. Microsoft Learn Azure architecture guidance when network topology is part of the decision.
-3. Azure MCP evidence, if the client exposes the relevant namespaces and live tenant inspection reduces guesswork.
+## What each evidence type can prove
 
-Useful Azure MCP namespaces from repo-backed specs:
+- Microsoft Learn documentation can prove documented service behavior, supported concepts, and recommended patterns.
+- Sampled read-only evidence can prove the sampled configured state at the time observed.
+- Sanitized user evidence can prove only what the snippet shows.
+- None of these alone prove broad regional availability, future success, full account posture, or production readiness.
 
-- `cloudarchitect`
-- `wellarchitectedframework`
-- `policy`
-- `role`
-- `group`
-- `subscription`
+## Safe usage pattern
 
-Use MCP evidence to confirm current hierarchy, scope, or governance reality. Do not use it as an excuse to skip design-area reasoning.
+- State whether each claim is documentation-based, sampled-current-state, user-provided, or inference.
+- Use read-only queries before recommending changes.
+- Do not include sensitive internal identifiers, tenant identifiers, subscription identifiers, or secrets in committed docs or final findings.
+- If no sampled evidence is available, say the review is documentation-based and list the exact evidence still needed.
+
+## Asset guidance
+
+Use Microsoft Learn documentation through the user's configured documentation MCP for documented landing-zone design areas and patterns. Use sampled read-only Azure evidence only to inspect current hierarchy, policies, RBAC, resources, and diagnostics, and label it as sampled evidence.

package/skills/azure/azure-landing-zone-architect/references/official-sources.md

@@ -1,19 +1,28 @@
 # Official Sources
 
-Load these only when needed:
+Use these sources to ground the skill. Microsoft Learn documentation proves documented Azure behavior; it does not prove the user's tenant, RBAC, quotas, deployed resources, or production readiness.
 
-- [What is an Azure landing zone?](https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/) — use for platform versus application landing zones and the reference-architecture baseline.
-- [Azure landing zone design areas and conceptual architecture](https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/design-areas) — use for the design-area map and the dependency between resource organization, networking, governance, management, and automation.
-- [Azure landing zone design principles](https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/design-principles) — use for policy-driven governance, Azure-native alignment, and avoiding application-agnostic hierarchy mistakes.
-- [Deploy Azure landing zones](https://learn.microsoft.com/azure/architecture/landing-zones/landing-zone-deploy) — use for platform landing zone deployment approaches and application landing zone patterns.
-- [Platform landing zone vs. application landing zones](https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/#platform-landing-zone-vs-application-landing-zones) — use when teams are blurring shared platform services with workload-local ownership.
-- [Tailor the Azure landing zone architecture to meet requirements](https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/tailoring-alz) — use when the user wants to deviate from the reference architecture without pretending there is one canonical hierarchy.
-- [Ready your Azure environment for workloads](https://learn.microsoft.com/azure/cloud-adoption-framework/ready/) — use for the baseline expectation that management, governance, security, and monitoring apply across subscriptions.
-- [Azure MCP Server tools inventory](https://learn.microsoft.com/azure/developer/azure-mcp-server/tools/) — use to verify `cloudarchitect`, `policy`, `group`, `subscription`, `role`, or `wellarchitectedframework` before naming them.
+## Primary Microsoft Learn sources
 
-## Grounded insights worth carrying into the skill
+- https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/
+- https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/design-areas
+- https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/design-area/identity-access
+- https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/design-area/governance
+- https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/design-area/security
+- https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/design-area/management
+- https://learn.microsoft.com/azure/cloud-adoption-framework/ready/landing-zone/design-area/platform-automation-devops
+- https://learn.microsoft.com/azure/architecture/networking/architecture/hub-spoke
 
-- Microsoft’s landing-zone guidance is explicitly modular and should be tailored; a single canned hierarchy is usually a sign of lazy thinking.
-- Platform landing zones and application landing zones are different operating boundaries; mixing them casually creates ownership and governance confusion.
-- Azure AI workloads do not require a separate “AI landing zone” by default; Microsoft says they should usually fit inside normal application landing zones governed by the same design areas.
-- A landing zone is not complete if management, governance, monitoring, and recovery posture are still deferred.
+## Grounding notes
+
+- Documentation-based claim: Microsoft Learn evidence says Azure landing zones are platform foundations spanning platform and application landing zones, management groups, subscriptions, policy inheritance, connectivity, identity, governance, security, management, and platform automation. The design-areas guidance explicitly calls out billing/tenant, identity/access, resource organization, network topology/connectivity, security, management, governance, and platform automation/DevOps as decisions that affect the foundation.
+- Current-state claim: requires sampled read-only Azure evidence or sanitized user-provided evidence.
+- Inference: allowed only when labeled and tied to observed fields or documented behavior.
+- Do not include sensitive internal identifiers or secret material in findings.
+
+## Source use rules
+
+- Prefer Microsoft Learn documentation through the user's configured documentation MCP for current Azure service behavior.
+- Use sampled read-only Azure evidence only to validate current configured-environment observations.
+- If documentation and sampled evidence appear to conflict, report both and stop short of a production-ready verdict.
+- Re-check official sources before changing high-risk guidance, because cloud behavior and feature availability can change.

package/skills/azure/azure-landing-zone-architect/references/safety-checklist.md

@@ -0,0 +1,29 @@
+# Safety Checklist
+
+## Evidence labels
+
+- `documentation-based`: grounded in Microsoft Learn or official Kubernetes documentation where listed.
+- `sampled-current-state`: grounded in read-only Azure or Kubernetes observations from the user's configured tools.
+- `user-provided`: grounded in sanitized snippets supplied by the user.
+- `inference`: reasoned from evidence but not directly proven.
+
+## Mutation boundary
+
+- Default to read-only review.
+- Do not perform create, update, delete, rotate, purge, recover, apply, restart, drain, cordon, scale, rollout, role-assignment, policy-assignment, or network changes unless the user explicitly asks and approval is clear.
+- Prefer preview, dry-run, status, describe, what-if, list, show, and policy evaluation evidence before any mutation.
+
+## Credential and data boundary
+
+- Never ask users to paste credentials, tokens, tenant IDs, subscription IDs, customer data, private keys, kubeconfig contents, CA requester credentials, secret values, or connection strings.
+- Summarize sensitive evidence by field presence, control state, and risk; do not reproduce secret material.
+
+## Risk gates
+
+- Stop on ambiguous target, ambiguous principal, missing approval, missing rollback, or missing owner for high-impact assets.
+- Treat broad permissions, permanent privileged access, public exposure, purge authority, destructive operations, and live rollout changes as high-risk.
+- Separate documented product behavior from sampled configured-environment evidence.
+
+## Asset-specific hard line
+
+Do not prescribe a one-size-fits-all hierarchy, broad admin grants, or production-ready verdict without identity, governance, security, management, network, subscription, cost, and recovery dependencies being addressed.

package/skills/azure/azure-landing-zone-architect/references/workflow-and-output.md

@@ -1,86 +1,30 @@
 # Workflow and Output Contract
 
-## Workflow
+## Execution flow
 
-1. Classify the operating context.
-   - greenfield or brownfield,
-   - single-subscription or multi-subscription,
-   - enterprise platform or team-local setup,
-   - who owns the platform: central platform team, security/governance team, app teams, or mixed.
-2. State missing facts before pretending certainty.
-   - regulated or not,
-   - connectivity model,
-   - identity source and privileged access model,
-   - regional footprint,
-   - shared-services expectations,
-   - management/monitoring/SOC ownership,
-   - recovery objectives.
-3. Map the problem to landing-zone design areas.
-   - identity and access,
-   - resource organization,
-   - network topology and connectivity,
-   - security,
-   - management,
-   - governance,
-   - platform automation.
-4. Define the target platform model.
-   - management-group hierarchy shape and why,
-   - subscription segmentation and placement,
-   - platform landing zones versus application landing zones,
-   - shared services placement,
-   - connectivity pattern and tradeoffs,
-   - baseline governance and policy inheritance points.
-5. Stress-test dependencies that are often skipped.
-   - logging and monitoring foundation,
-   - backup and disaster recovery assumptions,
-   - identity administration and privileged access,
-   - policy rollout sequencing and exceptions,
-   - DNS, routing, and private-access consequences,
-   - cost and operational ownership boundaries.
-6. Challenge unsafe defaults.
-   - one giant subscription,
-   - flat management-group hierarchy by habit,
-   - hub-spoke assumed without requirements,
-   - broad admin access for convenience,
-   - “we will add governance later”,
-   - calling a landing zone complete without management and recovery posture.
-   - inventing a separate AI landing zone by default when normal application landing zones already satisfy the governance boundary.
-7. Route narrower follow-up work when needed.
-   - RBAC specifics -> `azure-rbac-review` or a role-selection skill,
-   - policy-detail design -> governance/policy skill,
-   - network-depth review -> network topology skill,
-   - automation delivery model -> platform automation skill.
+1. Scope the exact asset, environment boundary, owner, and requested decision.
+2. Load `official-sources.md`, then the component operations guide for service behavior and risk gates.
+3. Gather sampled read-only evidence only when available and safe.
+4. Compare observed posture against documented behavior, least-privilege expectations, and operational safety rules.
+5. Return a verdict with evidence level, blockers, safe next actions, and open questions.
 
-## Output contract
+## Required output
 
-Return all of the following:
+- `verdict`: pass, warn, fail, or blocked.
+- `evidence_level`: documentation-based, sampled-current-state, user-provided, inference, or mixed.
+- `scope`: what was reviewed and what was not reviewed.
+- `blockers`: issues that prevent a safe or production-ready conclusion.
+- `findings`: severity-labeled risks with source labels.
+- `safe_next_actions`: reversible actions first; mutation only with explicit approval.
+- `open_questions`: missing facts that would change the verdict.
 
-- **Architecture verdict**: whether the current or proposed landing-zone model is sound, risky, or incomplete.
-- **Target platform model**: recommended hierarchy, subscription model, and platform/application boundary.
-- **Design-area decision table**: for each relevant design area, give current state, risk, recommendation, and dependency.
-- **Unresolved risks**: explicit gaps, assumptions, and blocked decisions.
-- **Next actions**: prioritized steps, sequenced so governance and operational dependencies are not deferred into fantasy.
-- **Evidence used**: Microsoft Learn pages and any Azure MCP namespaces actually used.
+## Stress checks
 
-## Eval gate
+- What assumption would make this recommendation unsafe?
+- Which role, policy, network, lifecycle, or rollout action has the largest blast radius?
+- What evidence would disprove the claimed readiness?
+- Is the answer accidentally treating documentation as tenant-specific proof?
 
-The skill output is not acceptable unless it:
+## Response discipline
 
-1. distinguishes greenfield versus brownfield context,
-2. identifies platform ownership assumptions,
-3. covers every relevant landing-zone design area,
-4. separates platform landing zones from application landing zones,
-5. addresses management-group and subscription placement,
-6. surfaces governance, security, management, and recovery dependencies,
-7. states assumptions and unknowns explicitly,
-8. avoids broad-admin or one-size-fits-all hierarchy advice.
-
-Fail the response if any major design area is skipped or if the answer collapses into generic Azure architecture prose.
-
-## Safety notes
-
-- Do not recommend a single canonical management-group hierarchy without business and governance context.
-- Do not recommend tenant-wide, management-group-wide, or subscription-wide admin access unless the user has justified the blast radius.
-- Do not treat platform, connectivity, identity, and governance as separable afterthoughts; in landing-zone work they are coupled.
-- Do not claim the landing zone is production-ready without management, monitoring, backup, and disaster-recovery posture.
-- Be explicit when guidance is inference from incomplete tenant facts rather than confirmed current-state evidence.
+Use Microsoft Learn documentation through the user's configured documentation MCP for documented landing-zone design areas and patterns. Use sampled read-only Azure evidence only to inspect current hierarchy, policies, RBAC, resources, and diagnostics, and label it as sampled evidence.

package/skills/azure/azure-live-aks-rollout-guard/SKILL.md

@@ -4,8 +4,8 @@ description: Guard live AKS deployment rollouts with PDB audit, maxUnavailable/s
 allowed-tools: Read Grep Glob WebFetch
 metadata:
   author: "github: Raishin"
-  version: "0.1.0"
-  updated: "2026-05-05"
+  version: 0.1.4
+  updated: "2026-06-05"
   category: delivery
 ---
 
@@ -25,7 +25,7 @@ Use this skill when:
 
 ## Lean operating rules
 
-- Prefer Azure CLI (`az`) official documentation when available; fall back to Microsoft Learn docs and sanitized user evidence.
+- Prefer Microsoft Learn documentation through the user's configured documentation MCP; use sampled read-only Azure or Kubernetes evidence when the active client exposes it, then sanitized user evidence.
 - Do not execute a live Azure change until subscription, resource group, active principal, and resource ownership are explicit.
 - Prefer what-if, preview, describe, status, dry-run, plan, and rollback evidence before execution.
 - If the request skips preview or rollback design, push back.
@@ -36,9 +36,13 @@ Use this skill when:
 
 Load these only when needed:
 
+- [Azure AKS Rollout Operations](references/aks-rollout-operations.md) — use for current service behavior, common failure modes, hard design rules, verification targets, and push-back conditions.
 - [Preflight commands](references/preflight-commands.md) — CLI commands to run before any mutation.
 - [Rollback playbook](references/rollback-playbook.md) — concrete rollback steps for this service.
 - [Permission model](references/permission-model.md) — RBAC role definitions and PIM guidance.
+- [MCP and evidence path](references/mcp-and-evidence.md) — use when choosing documentation-based evidence, sampled read-only evidence, or sanitized user evidence.
+- [Safety checklist](references/safety-checklist.md) — use for evidence labels, live-operation gates, approval rules, credential boundaries, and current-state caveats.
+- [Workflow and output contract](references/workflow-and-output.md) — execution flow and final response contract.
 - [Official sources](references/official-sources.md) — authoritative Azure documentation links.
 
 ## Response minimum

package/skills/azure/azure-live-aks-rollout-guard/metadata.json

@@ -11,17 +11,22 @@
     "kiro",
     "other"
   ],
-  "summary": "Guard live AKS deployment rollouts with PDB audit, maxUnavailable/surge validation, rollout pause/undo gates, and post-rollout health verification.",
+  "summary": "Guard live AKS deployment and node-pool rollouts with PDB audit, maxUnavailable/surge validation, pause/undo gates, capacity checks, and post-rollout health verification.",
   "source_type": "original",
   "official_docs": [
-    "https://learn.microsoft.com/en-us/azure/aks/operator-best-practices-cluster-security",
-    "https://learn.microsoft.com/en-us/azure/aks/concepts-clusters-workloads",
-    "https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#rolling-update-deployment",
-    "https://kubernetes.io/docs/tasks/run-application/configure-pdb/"
+    "https://learn.microsoft.com/azure/aks/upgrade-aks-node-pools-rolling",
+    "https://learn.microsoft.com/azure/aks/upgrade-options",
+    "https://learn.microsoft.com/azure/aks/upgrade-conceptual",
+    "https://learn.microsoft.com/azure/aks/blue-green-node-pool-upgrade",
+    "https://learn.microsoft.com/azure/architecture/operator-guides/aks/aks-upgrade-practices",
+    "https://learn.microsoft.com/azure/aks/concepts-clusters-workloads",
+    "https://learn.microsoft.com/azure/aks/operator-best-practices-cluster-security",
+    "https://kubernetes.io/docs/tasks/run-application/configure-pdb/",
+    "https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#rolling-update-deployment"
   ],
-  "security_notes": "Never advance an AKS rollout without PDB audit and replica health check. kubectl rollout undo is safe but must be confirmed before execution to avoid double-rollback churn.",
-  "last_verified": "2026-04-30",
+  "security_notes": "Never advance an AKS rollout without target, principal, approval, PDB audit, replica health, capacity, and rollback evidence. Treat undo, drain, cordon, scale, and node-pool upgrade operations as live mutations requiring explicit approval.",
+  "last_verified": "2026-06-05",
   "path": "skills/azure/azure-live-aks-rollout-guard",
   "author": "github: Raishin",
-  "version": "0.1.0"
+  "version": "0.1.4"
 }

package/skills/azure/azure-live-aks-rollout-guard/references/aks-rollout-operations.md

@@ -0,0 +1,68 @@
+# Azure AKS Rollout Operations
+
+Use this reference for current, source-grounded service behavior and the hard review gates that the lean `SKILL.md` intentionally does not carry.
+
+## What people get wrong
+
+- Calling a rollout safe because kubectl apply succeeded.
+- Ignoring PDBs, replicas, readiness probes, and maxUnavailable until a drain is already blocked.
+- Using maxUnavailable to avoid quota issues without admitting the disruption tradeoff.
+- Starting a node-pool upgrade without IP, compute quota, and rollback-window evidence.
+- Running rollback commands twice because no one tracked current rollout state.
+
+## Officially grounded service shape
+
+Microsoft Learn evidence says AKS rolling upgrades add surge nodes, cordon and drain old nodes, optionally wait for soak time, reimage nodes, repeat, and remove surge nodes. Production node pools are recommended to use max surge rather than disruptive in-place unavailability where possible. Max unavailable can disrupt workloads and increase failures from unsatisfied PodDisruptionBudgets. Blue-green node-pool upgrade includes a final soak window during which rollback is available before old nodes are removed.
+
+- Deployment rollouts and AKS node-pool upgrades are separate but coupled failure domains.
+- AKS node rolling upgrades use surge, cordon, drain, optional soak, reimage, and cleanup phases.
+- PDBs can protect availability but can also block drains when configured too tightly for replicas and topology.
+- Blue-green upgrade provides a validation and rollback window, but rollback disappears after the final commit/removal point.
+- Read-only evidence can prove current health snapshots, not future rollout success.
+
+## Non-negotiable design rules
+
+- Stop if target subscription/resource group/cluster/namespace/workload/principal or approval is ambiguous.
+- Require preflight evidence for pods, deployments, events, PDBs, HPA, nodes, quotas, and recent errors before mutation.
+- Prefer pause/status/describe/dry-run/plan checks before apply, restart, drain, upgrade, or undo.
+- Define rollback trigger, command, owner, and verification before execution.
+- Sanitize outputs; never print tokens, kubeconfig contents, environment values, or customer data.
+
+## Minimal safe implementation flow
+
+- Confirm target and read-only context: cluster, namespace, workload, node pool, current principal, and requested operation.
+- Collect rollout status, deployment spec, PDBs, replicas, readiness, events, node health, capacity, and monitoring signals.
+- Compare rollout strategy, maxUnavailable/maxSurge, PDB, and drain/soak settings against documented AKS and Kubernetes behavior.
+- Gate mutation on explicit approval, rollback plan, and health criteria.
+- After action, verify deployment availability, events, logs/metrics summary, and rollback posture.
+
+## High-risk assumptions to kill
+
+- `kubectl apply` success is not rollout success; availability, events, probes, PDBs, HPA behavior, and monitored health must be checked.
+- A PDB can protect or deadlock a rollout; the math must fit replica count, maxUnavailable, topology, and node drain behavior.
+- Max surge consumes compute and IP quota, while max unavailable trades capacity for disruption; neither setting is safe without explicit evidence.
+- Force or bypass paths that ignore PDBs can create complete service unavailability and need explicit emergency justification.
+- Rollback is not real if revision history, previous ReplicaSet, blue-green soak window, or node-pool recovery path is unknown.
+
+## Safe command/code verification targets
+
+- Inspect deployment manifests for replicas, strategy, maxSurge, maxUnavailable, probes, termination grace, resource requests, and topology spread.
+- Review PDB and HPA manifests together to prove eviction allowance cannot deadlock under expected rollout or drain conditions.
+- Check AKS node-pool settings for max surge, max unavailable, drain timeout, soak duration, version skew, node image, zones, quotas, and subnet IP headroom.
+- Verify preflight commands use status/describe/events/dry-run style evidence before mutation and avoid printing kubeconfig, tokens, or environment values.
+- Confirm rollback playbook names the exact pause, undo, history, node-pool rollback/blue-green decision point, and post-rollback health checks.
+
+## Safe verification targets
+
+- Deployment has enough replicas and PDB allowance for expected disruption.
+- Node pools have surge/capacity/IP quota or an explicit accepted maxUnavailable tradeoff.
+- Readiness/liveness/startup probes and termination grace match rollout and drain behavior.
+- Rollback command and validation window are known before mutation.
+- Post-rollout status shows desired replicas available, no new critical events, and monitored health criteria met.
+
+## When to push back
+
+- The user asks to mutate a live cluster without explicit approval.
+- PDBs or replicas make disruption mathematically unavoidable.
+- Quota/capacity evidence is missing for surge-based upgrades.
+- Rollback cannot be explained before starting the rollout.

package/skills/azure/azure-live-aks-rollout-guard/references/mcp-and-evidence.md

@@ -0,0 +1,26 @@
+# Documentation and Evidence Path
+
+## Preferred evidence order
+
+1. Microsoft Learn documentation through the user's configured documentation MCP for documented Azure behavior.
+2. Sampled read-only Azure or Kubernetes evidence, when safely available, for current configured-environment observations.
+3. Sanitized user-provided evidence.
+4. Clearly labeled inference.
+
+## What each evidence type can prove
+
+- Microsoft Learn documentation can prove documented service behavior, supported concepts, and recommended patterns.
+- Sampled read-only evidence can prove the sampled configured state at the time observed.
+- Sanitized user evidence can prove only what the snippet shows.
+- None of these alone prove broad regional availability, future success, full account posture, or production readiness.
+
+## Safe usage pattern
+
+- State whether each claim is documentation-based, sampled-current-state, user-provided, or inference.
+- Use read-only queries before recommending changes.
+- Do not include sensitive internal identifiers, tenant identifiers, subscription identifiers, or secrets in committed docs or final findings.
+- If no sampled evidence is available, say the review is documentation-based and list the exact evidence still needed.
+
+## Asset guidance
+
+Use Microsoft Learn documentation through the user's configured documentation MCP for documented AKS behavior. Use sampled read-only Azure or Kubernetes evidence only for current cluster observations and label it as sampled evidence.

package/skills/azure/azure-live-aks-rollout-guard/references/official-sources.md

@@ -1,19 +1,37 @@
-# Official Sources: Azure Live AKS Rollout Guard
+# Official Sources
 
-## Azure AKS
+Use these sources to ground the skill. Microsoft Learn documentation proves documented Azure behavior; it does not prove the user's tenant, RBAC, quotas, deployed resources, or production readiness.
 
-- https://learn.microsoft.com/en-us/azure/aks/operator-best-practices-cluster-security
-- https://learn.microsoft.com/en-us/azure/aks/concepts-clusters-workloads
-- https://learn.microsoft.com/en-us/azure/aks/manage-azure-rbac
-- https://learn.microsoft.com/en-us/azure/aks/use-azure-ad
+## Primary Microsoft Learn sources
 
-## Kubernetes rolling updates and rollback
-
-- https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#rolling-update-deployment
-- https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#rolling-back-a-deployment
+- https://learn.microsoft.com/azure/aks/upgrade-aks-node-pools-rolling
+- https://learn.microsoft.com/azure/aks/upgrade-options
+- https://learn.microsoft.com/azure/aks/upgrade-conceptual
+- https://learn.microsoft.com/azure/aks/blue-green-node-pool-upgrade
+- https://learn.microsoft.com/azure/architecture/operator-guides/aks/aks-upgrade-practices
+- https://learn.microsoft.com/azure/aks/concepts-clusters-workloads
+- https://learn.microsoft.com/azure/aks/operator-best-practices-cluster-security
 - https://kubernetes.io/docs/tasks/run-application/configure-pdb/
+- https://kubernetes.io/docs/concepts/workloads/controllers/deployment/#rolling-update-deployment
+
+## Grounding notes
+
+- Documentation-based claim: Microsoft Learn evidence says AKS rolling upgrades add surge nodes, cordon and drain old nodes, optionally wait for soak time, reimage nodes, repeat, and remove surge nodes. Production node pools are recommended to use max surge rather than disruptive in-place unavailability where possible. Max unavailable can disrupt workloads and increase failures from unsatisfied PodDisruptionBudgets. Blue-green node-pool upgrade includes a final soak window during which rollback is available before old nodes are removed.
+- Current-state claim: requires sampled read-only Azure evidence or sanitized user-provided evidence.
+- Inference: allowed only when labeled and tied to observed fields or documented behavior.
+- Do not include sensitive internal identifiers or secret material in findings.
+
+## Source use rules
+
+- Prefer Microsoft Learn documentation through the user's configured documentation MCP for current Azure service behavior.
+- Use sampled read-only Azure evidence only to validate current configured-environment observations.
+- If documentation and sampled evidence appear to conflict, report both and stop short of a production-ready verdict.
+- Re-check official sources before changing high-risk guidance, because cloud behavior and feature availability can change.
+
+## Current Microsoft Learn deltas checked on 2026-06-05
 
-## Source-grounding rule
+- Production AKS upgrade guidance uses surge capacity as the normal safety path, but more surge is not automatically safer when quota, subnet IPs, or workload capacity are constrained.
+- MaxUnavailable behavior is constrained by node-pool type and can deadlock or disrupt workloads when PodDisruptionBudgets, drain timeout, or capacity are wrong.
+- Force upgrade bypasses normal disruption protections and must be treated as a high-risk live operation, not a routine rollout fix.
+- Rollback is not a generic one-command undo; capture current state and rollback limits before any node-pool or workload rollout mutation.
 
-Use official Microsoft Learn and Kubernetes.io documentation as source of truth.
-Do not override official guidance with secondary examples or training data assumptions.

package/skills/azure/azure-live-aks-rollout-guard/references/permission-model.md

@@ -16,13 +16,15 @@
     "Microsoft.ContainerService/managedClusters/agentPools/write"
   ],
   "AssignableScopes": [
-    "/subscriptions/<SUBSCRIPTION_ID>/resourceGroups/<TARGET_RG>/providers/Microsoft.ContainerService/managedClusters/<CLUSTER_NAME>"
+    "<cluster-resource-scope>"
   ]
 }
 ```
 
 `listClusterUserCredential` grants a user-level kubeconfig. What the user can do inside
 the cluster is governed by AKS-integrated Entra ID RBAC, not this control-plane role.
+Use the exact AKS cluster resource scope from approved change records; do not paste raw
+subscription identifiers into chat.
 
 ## Kubernetes RBAC (data plane — in-cluster namespace scope)
 
@@ -33,7 +35,7 @@ apiVersion: rbac.authorization.k8s.io/v1
 kind: Role
 metadata:
   name: rollout-guard
-  namespace: <TARGET_NAMESPACE>
+  namespace: <namespace-name>
 rules:
 - apiGroups: ["apps"]
   resources: ["deployments", "replicasets"]

package/skills/azure/azure-live-aks-rollout-guard/references/preflight-commands.md

@@ -1,34 +1,40 @@
 # Preflight Commands: Azure Live AKS Rollout Guard
 
+Use shell variables for examples instead of raw identifiers. Populate them from an approved change record or already configured shell context; never paste tenant, subscription, resource, or secret values into chat.
+
+## Evidence-variable convention
+
+Variables such as $AZURE_RESOURCE_GROUP_NAME, $APP_SERVICE_APP_NAME, or $KEY_VAULT_NAME are local operator placeholders. Do not commit real values, and redact them from shared evidence unless the change record explicitly allows disclosure.
+
 Run these commands before any AKS rollout mutation. Paste sanitized output as evidence.
 
 ## 1. Confirm identity and cluster target
 
 ```bash
-az account show --query "{subscription:id, name:name, user:user.name}"
-az aks show -g <RESOURCE_GROUP> -n <CLUSTER_NAME> \
+az account show --query "{subscriptionName:name, user:user.name}"
+az aks show -g $AZURE_RESOURCE_GROUP_NAME -n $AKS_CLUSTER_NAME \
   --query "{provisioningState:provisioningState, kubernetesVersion:kubernetesVersion, fqdn:fqdn}"
 ```
 
 ## 2. Fetch user-level kubeconfig
 
 ```bash
-az aks get-credentials -g <RESOURCE_GROUP> -n <CLUSTER_NAME> --overwrite-existing
+az aks get-credentials -g $AZURE_RESOURCE_GROUP_NAME -n $AKS_CLUSTER_NAME --overwrite-existing
 kubectl config current-context
 ```
 
 ## 3. Audit PodDisruptionBudgets in target namespace
 
 ```bash
-kubectl get pdb -n <NAMESPACE> -o wide
+kubectl get pdb -n $KUBERNETES_NAMESPACE -o wide
 # minAvailable or maxUnavailable must leave at least one pod available during rollout
 ```
 
 ## 4. Check current deployment rollout status
 
 ```bash
-kubectl rollout status deployment/<DEPLOYMENT_NAME> -n <NAMESPACE>
-kubectl get deployment <DEPLOYMENT_NAME> -n <NAMESPACE> -o jsonpath='{.spec.strategy}'
+kubectl rollout status deployment/$KUBERNETES_DEPLOYMENT_NAME -n $KUBERNETES_NAMESPACE
+kubectl get deployment $KUBERNETES_DEPLOYMENT_NAME -n $KUBERNETES_NAMESPACE -o jsonpath='{.spec.strategy}'
 ```
 
 ## 5. Verify node readiness and resource headroom
@@ -36,13 +42,13 @@ kubectl get deployment <DEPLOYMENT_NAME> -n <NAMESPACE> -o jsonpath='{.spec.stra
 ```bash
 kubectl get nodes -o wide
 kubectl top nodes
-kubectl get pods -n <NAMESPACE> -o wide
+kubectl get pods -n $KUBERNETES_NAMESPACE -o wide
 ```
 
 ## 6. Confirm maxSurge / maxUnavailable strategy
 
 ```bash
-kubectl get deployment <DEPLOYMENT_NAME> -n <NAMESPACE> \
+kubectl get deployment $KUBERNETES_DEPLOYMENT_NAME -n $KUBERNETES_NAMESPACE \
   -o jsonpath='{.spec.strategy.rollingUpdate}'
 # maxUnavailable=0 is safest for production; maxSurge=1 is a conservative default
 ```
@@ -50,6 +56,6 @@ kubectl get deployment <DEPLOYMENT_NAME> -n <NAMESPACE> \
 ## 7. Check HorizontalPodAutoscaler (if present)
 
 ```bash
-kubectl get hpa -n <NAMESPACE>
+kubectl get hpa -n $KUBERNETES_NAMESPACE
 # HPA minReplicas must exceed PDB minAvailable or the rollout will deadlock
 ```