[bug] Intake Triage agent job: MODULE_NOT_FOUND for merge_awf_model_multipliers.cjs (5 failures in 8d, v0.77.5)

[austenstone]

Summary

The agent job in workflows using gh-aw v0.77.5 on github/actions-sales (Actions Specialist Intake Triage) fails immediately at the Execute GitHub Copilot CLI step with:

Error: Cannot find module '/home/runner/work/_temp/gh-aw/actions/merge_awf_model_multipliers.cjs'
    at Function._resolveFilename (node:internal/modules/cjs/loader:1430:15)
    ...
Node.js v22.23.1
code: 'MODULE_NOT_FOUND'
##[error]Process completed with exit code 1.

The activation job succeeds. The agent job blows up before Copilot ever runs. Failure signature is identical across all 5 runs, so this reads like a v0.77.5 setup step that's not materializing the .cjs shim into _temp/gh-aw/actions/.

Recurrence pattern (last 8 days)

All are the same intake-triage workflow, same signature, same error, always the agent job:

Issue	Failed run	Date
github/actions-sales#924 (latest run)	28559150351	2026-07-02 01:33 UTC
github/actions-sales#924	(prior in same issue)	2026-07-01 19:38 UTC
github/actions-sales#922		2026-06-29
github/actions-sales#919		2026-06-26
github/actions-sales#914		2026-06-25

Blast radius: every specialist intake through github/actions-sales on those days silently missed AI triage. Humans have to manually route.

Environment (from failed run 28559150351)

• GH_AW_VERSION: v0.77.5
• COPILOT_MODEL: claude-sonnet-4.6
• GH_AW_WORKFLOW_ID_SANITIZED: intaketriage
• COPILOT_AGENT_RUNNER_TYPE: STANDALONE
• Node.js v22.23.1
• Runs on ubuntu-latest (github-hosted)

Suggested fast path

Check what step is supposed to write merge_awf_model_multipliers.cjs into _temp/gh-aw/actions/ in v0.77.5. Likely one of the pre-agent compile/materialize steps is either skipped, conditioned wrong, or the shim was renamed/moved and the loader wasn't updated.

Context

Filing on behalf of @austenstone (specialist queue owner) — 5 silent misses is over the threshold for opening the bug upstream rather than continuing to comment on symptomatic actions-sales issues. Happy to test a candidate fix on our intake workflow if a v0.77.6 lands.

[github-actions]

🔍 Workflow Health Manager — Jul 2 Health Scan

Severity: P1 (High)

Flagged as a P1 regression in today's health scan. Context:

• 5 failures in 8 days on v0.77.5 — the agent job dies immediately at the Execute GitHub Copilot CLI step before the workflow even runs
• The activation job succeeds, so the issue is in the agent-phase bundle packaging
• Pattern: MODULE_NOT_FOUND for merge_awf_model_multipliers.cjs — this file appears to have been dropped or path-changed in the v0.77.5 release

Health Score Impact: Counts against workflow health (73/100 today, ↓2 from Jul 1).

Recommended action: Verify merge_awf_model_multipliers.cjs is included in the v0.77.5 release artifact and correctly referenced in the agent entrypoint. Rollback to v0.77.4 as a mitigation if a hotfix cannot land quickly.

References: §28568253334

Generated by 🏥 Workflow Health Manager - Meta-Orchestrator · 73.6 AIC · ⌖ 8.52 AIC · ⊞ 7.8K · ◷

[github-actions]

🏷️ Issue Triaged

Hi @austenstone! I've categorized this issue as bug based on the following analysis:

Reasoning: The issue explicitly reports a MODULE_NOT_FOUND error (merge_awf_model_multipliers.cjs) causing consistent workflow failures across 5 runs on v0.77.5 — a clear regression/bug in a specific release.

View Triage Details

Analysis

• Keywords detected: MODULE_NOT_FOUND, Error, v0.77.5, fails immediately, 5 failures in 8 days
• Issue type indicators: Reproducible crash at a known step, consistent failure signature across multiple runs, version-pinned regression
• Confidence: High

Recommended Next Steps

• Investigate whether the merge_awf_model_multipliers.cjs shim is correctly packaged/materialized during the agent job setup in v0.77.5
• Check the release diff between v0.77.4 and v0.77.5 for any changes to the actions directory packaging
• Consider pinning affected workflows to a prior known-good version while a fix is developed

References: Triage run §28601543069

Warning

Firewall blocked 1 domain

The following domain was blocked by the firewall during workflow execution:

• awmgmcpg

To allow these domains, add them to the network.allowed list in your workflow frontmatter:

network:
  allowed:
    - defaults
    - "awmgmcpg"

See Network Configuration for more information.

Generated by 🔧 Issue Triage Agent · 27.6 AIC · ⌖ 6.94 AIC · ⊞ 4.8K · ◷

[austenstone]

🤖 AI-generated heartbeat update, review before treating as final word.

v0.82.1 does NOT fix this. The workflow auto-bumped from v0.77.5 → v0.82.1 (lock file compiler_version confirms) and still hits the identical failure:

2026-07-02T01:33:30.5890195Z Error: Cannot find module '/home/runner/work/_temp/gh-aw/actions/merge_awf_model_multipliers.cjs'
2026-07-02T01:33:30.5904443Z   code: 'MODULE_NOT_FOUND',

Run: 28559150351

Updated failure timeline on github/actions-sales/intake-triage.lock.yml:

Date	gh-aw version	Result
2026-06-12	(pre-bump)	✅ success
2026-06-19	(pre-bump)	✅ success
2026-06-25	v0.77.5	❌ MODULE_NOT_FOUND
2026-06-26 (×2)	v0.77.5	❌ MODULE_NOT_FOUND
2026-06-29	v0.77.5	❌ MODULE_NOT_FOUND
2026-07-01	v0.82.1	❌ MODULE_NOT_FOUND (same signature)
2026-07-02	v0.82.1	❌ MODULE_NOT_FOUND (same signature)

Regression window is 6/19 → 6/25 (one week, one release delta) but the fix window is open — v0.82.1 shipped without addressing it. Please retitle to reflect versions affected, or bump severity: 8 days, 5+ silent failures, every issue filed to github/actions-sales in that window has skipped auto-triage.

Downstream compensating action noted on my end (austenstone-notes observation): considering escalation to Copilot Coding Agent for a manual triage backfill if this stretches past 10 days.

[austenstone]

🤖 AI-generated heartbeat, loop-close.

@copilot-swe-agent opened PR #43299 at 04:38Z (2026-07-04) implementing the compatibility shim path I flagged in my earlier comment — adds actions/setup/js/merge_awf_model_multipliers.cjs that re-exports from merge_frontmatter_models.cjs.

That's the minimal fix that should unblock all workflows still compiled against the legacy path (v0.77.5 and any lock-file-pinned intermediates through v0.82.1). Will confirm as fixed once #43299 merges and the next scheduled intake-triage run turns green.

[pelikhan]

@austenstone try recompiling with the latest release.

[austenstone]

🤖 AI-generated heartbeat cycle 23 update, review before treating as final word.

Thanks @pelikhan — recompiled with v0.81.6 stable (was on v0.82.1 prerelease, latest-latest is v0.82.2 prerelease). PR opened at github/actions-sales#927 for the intake-triage.lock.yml bump. Scope kept narrow to intake-triage only (account-research-brief.lock.yml on v0.67.0 was left alone as it's not failing).

Assuming that merges and the next intake-triage run turns green, I'll close this issue. If it fails identically I'll try v0.82.2 next.

/cc @austenstone (heartbeat autonomously opened PR #927 on your behalf — labeled AI-generated in the description)