fix(pr-1092): address copilot trigger and emoji feedback

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: jongio

plugin/skills/azure-deploy/SKILL.md

@@ -9,7 +9,7 @@ description: "Deploy validated applications to Azure via azd, Bicep, or Terrafor
 >
 > **PREREQUISITE**: The **azure-validate** skill **MUST** be invoked and completed with status `Validated` BEFORE executing this skill.
 
-> **⛔ STOP — PREREQUISITE CHECK REQUIRED**
+> **⚠️ STOP — PREREQUISITE CHECK REQUIRED**
 > Before proceeding, verify BOTH prerequisites are met:
 >
 > 1. **azure-prepare** was invoked and completed → `.azure/plan.md` exists
@@ -19,7 +19,7 @@ description: "Deploy validated applications to Azure via azd, Bicep, or Terrafor
 > - No plan? → Invoke **azure-prepare** skill first
 > - Status not `Validated`? → Invoke **azure-validate** skill first
 >
-> **⛔ DO NOT MANUALLY UPDATE THE PLAN STATUS**
+> **⚠️ DO NOT MANUALLY UPDATE THE PLAN STATUS**
 >
 > You are **FORBIDDEN** from changing the plan status to `Validated` yourself. Only the **azure-validate** skill is authorized to set this status after running actual validation checks. If you update the status without running validation, deployments will fail.
 >
@@ -35,7 +35,7 @@ Activate this skill when user wants to:
 - Push updates to existing deployment
 - Run `azd up` or `az deployment`
 - Ship code to production
-- Deploy Azure Functions to the cloud
+- Deploy Azure serverless apps to the cloud
 - Deploy an application that already includes API Management (APIM) gateway infrastructure
 
 > **APIM / AI Gateway**: Use this skill to deploy applications whose APIM/AI gateway infrastructure was already created during **azure-prepare**. For creating or changing APIM resources, see [APIM deployment guide](https://learn.microsoft.com/azure/api-management/get-started-create-service-instance). For AI governance policies, invoke **azure-aigateway** skill.
@@ -45,7 +45,7 @@ Activate this skill when user wants to:
 1. Run after azure-prepare and azure-validate
 2. `.azure/plan.md` must exist with status `Validated`
 3. **Pre-deploy checklist required** — [Pre-Deploy Checklist](references/pre-deploy-checklist.md)
-4. ⛔ **Destructive actions require `ask_user`** — [global-rules](references/global-rules.md)
+4. ⚠️ **Destructive actions require `ask_user`** — [global-rules](references/global-rules.md)
 
 ---
 
@@ -61,7 +61,7 @@ Activate this skill when user wants to:
 | 6 | **Handle Errors** — See recipe's `errors.md` | — |
 | 7 | **Verify Success** — Confirm deployment completed and endpoints are accessible | [Verify](references/recipes/azd/verify.md) |
 
-> **⛔ VALIDATION PROOF CHECK**
+> **⚠️ VALIDATION PROOF CHECK**
 >
 > When checking the plan, verify the **Validation Proof** section (Section 7) contains actual validation results with commands run and timestamps. If this section is empty, validation was bypassed — invoke **azure-validate** skill first.
 

plugin/skills/azure-prepare/SKILL.md

@@ -29,11 +29,11 @@ Activate this skill when user wants to:
 4. **Update plan progressively** — Mark steps complete as you go
 5. **Validate before deploy** — Invoke azure-validate before azure-deploy
 6. **Confirm Azure context** — Use `ask_user` for subscription and location per [Azure Context](references/azure-context.md)
-7. ⛔ **Destructive actions require `ask_user`** — [Global Rules](references/global-rules.md)
+7. ⚠️ **Destructive actions require `ask_user`** — [Global Rules](references/global-rules.md)
 
 ---
 
-## ⛔ PLAN-FIRST WORKFLOW — MANDATORY
+## ⚠️ PLAN-FIRST WORKFLOW — MANDATORY
 
 > **YOU MUST CREATE A PLAN BEFORE DOING ANY WORK**
 >
@@ -46,7 +46,7 @@ Activate this skill when user wants to:
 
 ---
 
-## ⛔ STEP 0: Specialized Technology Check — MANDATORY FIRST ACTION
+## ⚠️ STEP 0: Specialized Technology Check — MANDATORY FIRST ACTION
 
 **BEFORE starting Phase 1**, check if the user's prompt mentions a specialized technology that has a dedicated skill with tested templates. If matched, **invoke that skill FIRST** — then resume azure-prepare for validation and deployment.
 
@@ -69,7 +69,7 @@ Create `.azure/plan.md` by completing these steps. Do NOT generate any artifacts
 
 | # | Action | Reference |
 |---|--------|-----------|
-| 0 | **⛔ Check Prompt for Specialized Tech** — If user mentions copilot SDK, Azure Functions, etc., invoke that skill first | [specialized-routing.md](references/specialized-routing.md) |
+| 0 | **⚠️ Check Prompt for Specialized Tech** — If user mentions copilot SDK, Azure Functions, etc., invoke that skill first | [specialized-routing.md](references/specialized-routing.md) |
 | 1 | **Analyze Workspace** — Determine mode: NEW, MODIFY, or MODERNIZE | [analyze.md](references/analyze.md) |
 | 2 | **Gather Requirements** — Classification, scale, budget | [requirements.md](references/requirements.md) |
 | 3 | **Scan Codebase** — Identify components, technologies, dependencies | [scan.md](references/scan.md) |
@@ -81,7 +81,7 @@ Create `.azure/plan.md` by completing these steps. Do NOT generate any artifacts
 
 ---
 
-> **⛔ STOP HERE** — Do NOT proceed to Phase 2 until the user approves the plan.
+> **⚠️ STOP HERE** — Do NOT proceed to Phase 2 until the user approves the plan.
 
 ---
 

tests/azure-deploy/__snapshots__/triggers.test.ts.snap

@@ -11,7 +11,6 @@ exports[`azure-deploy - Trigger Tests Trigger Keywords Snapshot skill descriptio
     "cli",
     "deploy",
     "execution",
-    "function",
     "identity",
     "live",
     "mcp",
@@ -36,7 +35,6 @@ exports[`azure-deploy - Trigger Tests Trigger Keywords Snapshot skill keywords m
   "cli",
   "deploy",
   "execution",
-  "function",
   "identity",
   "live",
   "mcp",