⚙️ setup: rename workflow to build-flow.yml

[warengonzaga]

Rename the repository's Build Flow caller from build.yml to build-flow.yml so its filename clearly identifies the publishing orchestrator. The workflow contents, triggers, permissions, pinned action, and job configuration remain byte-for-byte unchanged.

Update the workflow links and npm trusted-publisher instructions in AGENTS.md and docs/RELEASING.md to use build-flow.yml. npm account settings are not modified by this PR; configure that filename when completing the initial publishing setup.

Validation: Bun YAML parsing, exact workflow-byte comparison against the dev base, a tracked-file search for stale build.yml references, and git diff --check passed. No engine tests were added because runtime source and workflow behavior are unchanged. The hosted Build Flow run passed on d841ee3083334d46997d5beec122ac17fe9b5c13, and its recorded workflow path is .github/workflows/build-flow.yml. Node 22/24/26 and the CodeQL scan job passed. Independent review and Copilot found no actionable issues.

GitHub reports seven successful checks, five expected publication/release skips, and one neutral CodeQL comparison. The comparison cannot determine newly introduced alerts against the old .github/workflows/build.yml:scan configuration after the rename; the scan itself succeeded. This comparison coverage limit remains visible rather than being reported as a passed check.

[github-advanced-security]

You are seeing this message because GitHub Code Scanning has recently been set up for this repository, or this pull request contains the workflow file for the Code Scanning tool.

What Enabling Code Scanning Means:

• The 'Security' tab will display more code scanning analysis results (e.g., for the default branch).
• Depending on your configuration and choice of analysis tool, future pull requests will be annotated with code scanning analysis results.
• You will be able to see the analysis results for the pull request's branch on this overview once the scans have completed and the checks have passed.

For more information about GitHub Code Scanning, check out the documentation.

[Copilot]

Copilot review overview

🟢 Approval recommended

The rename is complete, references are consistent, and workflow contents remain unchanged.

Review effort: Balanced
Findings: None

What changed in this PR

Renames the Build Flow caller for clarity while preserving workflow behavior.

Changes:

• Renames the workflow to build-flow.yml.
• Updates documentation and npm trusted-publisher references.

File	Description
.github/​workflows/​build-flow.yml	Preserves the existing Build Flow configuration under the new filename.
AGENTS.md	Updates workflow and npm configuration references.
docs/​RELEASING.md	Updates release links and trusted-publisher instructions.

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[warengonzaga]

Clean Workflow review complete at d841ee3 against dev 3a5b427. No actionable findings or unresolved threads. The workflow rename preserves every byte of its configuration, all tracked links and npm trusted-publisher guidance use build-flow.yml, and the final YAML/reference/whitespace checks pass. Independent review and the completed Copilot review are clean. The current-head Build Flow run passed, including Node 22/24/26 and the CodeQL scan. The separate CodeQL comparison remains neutral because the old build.yml scan configuration is absent after the rename; introduced-alert comparison is unavailable, not passed. The PR is conflict-free. npm account settings and publication were not changed.