feat: query /reflect before and after running the agent in harnesses

[Copilot]

The harnesses previously called fetchAWFReflect only after the agent run. If a harness exits unexpectedly before reaching the post-run fetch, the proxy state is never captured.

Changes

• claude_harness.cjs / copilot_harness.cjs: Add a best-effort fetchAWFReflect call before the agent execution loop, immediately after startup validation. This writes the initial api-proxy /reflect snapshot to disk and logs it before any agent output, making proxy configuration available for diagnostics regardless of how the run ends.

• pi_provider.cjs: Add an agent_end handler that calls fetchAWFReflect after the Pi agent session finishes. The extension already fetched /reflect on agent_start (pre-run); this adds the matching post-run fetch for parity with the other harnesses.

The post-run call in the copilot and claude harnesses is unchanged — it remains as the authoritative snapshot for the step summary.

[pelikhan]

@copilot also update the pi agent api-proxy provider extension

[Copilot]

@copilot also update the pi agent api-proxy provider extension

Done in 91c864b. Added an agent_end handler to pi_provider.cjs that calls fetchAWFReflect after the agent session finishes, matching the pre/post-run pattern in the copilot and claude harnesses. The existing agent_start call (pre-run) is unchanged.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• https://api.github.com/repos/github/gh-aw/contents/.github%2Fworkflows%2Faudit-workflows.md
  • Triggering command: /opt/hostedtoolcache/node/24.14.1/x64/bin/node /opt/hostedtoolcache/node/24.14.1/x64/bin/node --experimental-import-meta-resolve --require /home/REDACTED/work/gh-aw/gh-aw/actions/setup/js/node_modules/vitest/suppress-warnings.cjs --conditions node --conditions development /home/REDACTED/work/gh-aw/gh-aw/actions/setup/js/node_modules/vitest/dist/workers/forks.js --quiet k/gh-aw/node_mod--verify git comm�� -m (http block)
• invalid.example.invalid
  • Triggering command: /usr/lib/git-core/git-remote-https /usr/lib/git-core/git-remote-https origin https://invalid.example.invalid/nonexistent-repo.git e/git conf�� user.email test@test.com git git-receive-packgit (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

[Copilot]

Pull request overview

This PR is intended to improve observability around AWF proxy state by capturing /reflect snapshots before agent execution begins and, for Pi, after the session ends.

Changes:

• Added a best-effort pre-run fetchAWFReflect call to the Copilot and Claude harnesses.
• Added a post-run agent_end fetchAWFReflect hook to the Pi provider for parity with other harnesses.
• Also includes unrelated documentation/catalog updates outside the stated /reflect harness scope.

Show a summary per file

File	Description
docs/src/content/docs/reference/frontmatter-full.md	Adds/removes frontmatter reference documentation entries unrelated to the harness /reflect change.
docs/src/content/docs/agent-factory-status.mdx	Updates the agent/workflow status table with additional workflow entries and engine labels.
actions/setup/js/pi_provider.cjs	Adds pre-run and post-run /reflect fetches via Pi SDK event handlers.
actions/setup/js/copilot_harness.cjs	Adds a pre-run /reflect fetch before entering the Copilot retry loop.
actions/setup/js/claude_harness.cjs	Adds a pre-run /reflect fetch before entering the Claude retry loop.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

Comments suppressed due to low confidence (1)

actions/setup/js/pi_provider.cjs:117

• The new agent_end /reflect fetch is not covered by tests. This file currently has no test companion even though nearby Pi extensions are covered (actions/setup/js/pi_steering_extension.test.cjs), so a regression in whether the handler is registered or awaited would go unnoticed.

  pi.on("agent_end", async () => {
    // Fetch AWF API proxy reflection data after the agent finishes for the post-run step summary.
    // This is best-effort: failures are logged but do not affect the agent exit code.
    await fetchAWFReflect({
      reflectUrl: AWF_API_PROXY_REFLECT_URL,
      outputPath: AWF_REFLECT_OUTPUT_PATH,
      timeoutMs: AWF_REFLECT_TIMEOUT_MS,
      modelsTimeoutMs: AWF_MODELS_URL_TIMEOUT_MS,
      logger: log,

• Files reviewed: 5/5 changed files
• Comments generated: 4