[task] Audit workflows blocking npm registry access

[github-actions]

Objective

Identify all workflows with firewall enabled that are blocking registry.npmjs.org and need Node.js package registry access.

Context

The Daily Firewall Report (Discussion #3607) shows that registry.npmjs.org is being blocked 22 times across firewall-enabled workflows. This domain is essential for npm package installation and should be allowlisted for workflows that need Node.js ecosystem access.

Related to #3607

Approach

1. Review all workflows with network.firewall: true in their frontmatter
2. Check firewall logs to identify which workflows are blocking registry.npmjs.org
3. Determine which workflows legitimately need npm registry access (e.g., workflows that install Node.js packages, use npx commands, or reference npm in their descriptions)
4. Create a list of workflow files that need the node ecosystem identifier added

Files to Review

• .github/workflows/firewall.md
• .github/workflows/dev.firewall.md
• .github/workflows/daily-news.md
• .github/workflows/mcp-inspector.md
• .github/workflows/artifacts-summary.md
• .github/workflows/changeset.md
• All other workflows with firewall: true

Acceptance Criteria

• List of workflows that block registry.npmjs.org identified
• Each workflow assessed for legitimate npm registry needs
• Documentation of which workflows need node ecosystem identifier
• Results documented (comment on this issue or create a discussion)

Expected Output

A comment or discussion with:

## Workflows Needing Node Ecosystem Access

1. `workflow-name.md` - Reason: [uses npm/npx/node packages]
2. `another-workflow.md` - Reason: [description]

## Workflows That Don't Need npm Access

1. `workflow-name.md` - Reason: [no Node.js usage]

Related to #3607

AI generated by Plan Command for discussion #3607