Refresh APM integration files

Co-authored-by: mrjf <180956+mrjf@users.noreply.github.com>

Author: Copilot

.github/agents/agentic-workflows.agent.md

@@ -19,7 +19,6 @@ This is a **dispatcher agent** that routes your request to the appropriate speci
 - **Creating shared components**: Routes to `create-shared-agentic-workflow` prompt
 - **Fixing Dependabot PRs**: Routes to `dependabot` prompt — use this when Dependabot opens PRs that modify generated manifest files (`.github/workflows/package.json`, `.github/workflows/requirements.txt`, `.github/workflows/go.mod`). Never merge those PRs directly; instead update the source `.md` files and rerun `gh aw compile --dependabot` to bundle all fixes
 - **Analyzing test coverage**: Routes to `test-coverage` prompt — consult this whenever the workflow reads, analyzes, or reports on test coverage data from PRs or CI runs
-- **CLI commands and triggering workflows**: Routes to `cli-commands` guide — consult this whenever the user asks how to run, compile, debug, or manage workflows from the command line, or when they need the MCP tool equivalent of a `gh aw` command
 
 Workflows may optionally include:
 
@@ -130,17 +129,6 @@ When you interact with this agent, it will:
 - "Analyze coverage trends over time"
 - "Add a coverage gate that blocks PRs below a threshold"
 
-### CLI Commands Reference
-**Load when**: The user asks how to run, compile, debug, or manage workflows from the command line; needs the MCP tool equivalent of a `gh aw` command; or is in a restricted environment (e.g., Copilot Cloud) without direct CLI access.
-
-**Reference file**: https://github.com/github/gh-aw/blob/main/.github/aw/cli-commands.md
-
-**Use cases**:
-- "How do I trigger workflow X on the main branch?"
-- "What's the MCP equivalent of `gh aw logs`?"
-- "I'm in Copilot Cloud — how do I compile a workflow?"
-- "Show me all available gh aw commands"
-
 ## Instructions
 
 When a user interacts with you:
@@ -159,10 +147,6 @@ gh aw init
 # Generate the lock file for a workflow
 gh aw compile [workflow-name]
 
-# Trigger a workflow on demand (preferred over gh workflow run)
-gh aw run <workflow-name>             # interactive input collection
-gh aw run <workflow-name> --ref main  # run on a specific branch
-
 # Debug workflow runs
 gh aw logs [workflow-name]
 gh aw audit <run-id>
@@ -190,7 +174,4 @@ gh aw compile --validate
 - Workflows must be compiled to `.lock.yml` files before running in GitHub Actions
 - **Bash tools are enabled by default** - Don't restrict bash commands unnecessarily since workflows are sandboxed by the AWF
 - Follow security best practices: minimal permissions, explicit network access, no template injection
-- **Network configuration**: Use ecosystem identifiers (`node`, `python`, `go`, etc.) or explicit FQDNs in `network.allowed`. Bare shorthands like `npm` or `pypi` are **not** valid. See https://github.com/github/gh-aw/blob/main/.github/aw/network.md for the full list of valid ecosystem identifiers and domain patterns.
 - **Single-file output**: When creating a workflow, produce exactly **one** workflow `.md` file. Do not create separate documentation files (architecture docs, runbooks, usage guides, etc.). If documentation is needed, add a brief `## Usage` section inside the workflow file itself.
-- **Triggering runs**: Always use `gh aw run <workflow-name>` to trigger a workflow on demand — not `gh workflow run <file>.lock.yml`. `gh aw run` handles workflow resolution by short name, input parsing and validation, and correct run-tracking for agentic workflows. Use `--ref <branch>` to run on a specific branch.
-- **CLI commands reference**: For a complete guide on all `gh aw` commands and their MCP tool equivalents (for restricted environments), see https://github.com/github/gh-aw/blob/main/.github/aw/cli-commands.md

.github/instructions/agentic-workflows.instructions.md

@@ -0,0 +1,16 @@
+---
+description: "Agentic workflow recompilation: always recompile after changing workflow files"
+---
+
+# Agentic Workflows
+
+After modifying any `.md` workflow file under `.github/workflows/`, always
+recompile both agentic workflows and APM integration files before committing:
+
+```bash
+gh aw compile
+apm compile
+```
+
+Commit the regenerated `.lock.yml` and integration files together with your
+changes. The CI `APM Self-Check` job will fail if generated files are stale.

apm.lock.yaml

@@ -24,6 +24,7 @@ local_deployed_files:
 - .github/agents/python-architect.agent.md
 - .github/agents/supply-chain-security-expert.agent.md
 - .github/agents/test-coverage-expert.agent.md
+- .github/instructions/agentic-workflows.instructions.md
 - .github/instructions/changelog.instructions.md
 - .github/instructions/cicd.instructions.md
 - .github/instructions/cli.instructions.md
@@ -46,6 +47,7 @@ local_deployed_file_hashes:
   .github/agents/python-architect.agent.md: sha256:7587ee7c684c61046a83dfa1b7e39d1345f2f119c3395478e3ca2dbbaaaff0e9
   .github/agents/supply-chain-security-expert.agent.md: sha256:8fb8cc426d6af17ba084a28b3f026c2b475b62e3ca63ed2f88b83bd823f877af
   .github/agents/test-coverage-expert.agent.md: sha256:bc588d89530362469502bfbea788df892a9a0b00e630cd0f3926d3dfd2c2a9e2
+  .github/instructions/agentic-workflows.instructions.md: sha256:fc90017f6db18b7aa443668efcdf0ff8dc201fe5c42cbca36e600a5945e210c4
   .github/instructions/changelog.instructions.md: sha256:1e51ec4c74e847967962bd279dc4c6e582c5d3578490b3c28d5f3acd3e05f73e
   .github/instructions/cicd.instructions.md: sha256:9c0fafc74f743aa97e5adba2168d66c9e3a327b135065e3b804bdbb5f04cda5d
   .github/instructions/cli.instructions.md: sha256:8e39e8d5047ce88575cb02f87c2bcede584dfef258bd86f7466c7badf136541a