fix(USE-001): add standardized ERR_* error codes to two non-conformant handlers

[Copilot]

Two handlers were throwing bare errors without the ERR_* prefixes required by error_codes.cjs, breaking structured logging and alerting rules (conformance check USE-001).

Changes

• close_entity_helpers.cjs: Added ERR_API import; replaced bare throw commentError with a wrapped error that includes the ERR_API prefix and preserves the original as { cause: commentError } for stack trace retention.
• generate_safe_outputs_tools.cjs: Added ERR_CONFIG import; prefixed both throw new Error(msg) calls (missing source tools file, missing config file) with ERR_CONFIG.

// Before
throw commentError;
throw new Error(`Error: Source tools file not found at: ${toolsSourcePath}`);

// After
throw new Error(`${ERR_API}: Failed to add comment to ${entityConfig.displayName} #${entityNumber}: ${errorMsg}`, { cause: commentError });
throw new Error(`${ERR_CONFIG}: Source tools file not found at: ${toolsSourcePath}`);

[Copilot]

Pull request overview

This PR brings two safe-output setup/handler scripts into USE-001 conformance by ensuring thrown errors include standardized ERR_* prefixes for structured logging.

Changes:

• Added ERR_CONFIG to generate_safe_outputs_tools.cjs and prefixed missing-file error messages.
• Added ERR_API to close_entity_helpers.cjs and replaced a bare rethrow with a wrapped Error that includes an error code and preserves the original error via cause.

Show a summary per file

File	Description
actions/setup/js/generate_safe_outputs_tools.cjs	Prefixes missing source/config file errors with ERR_CONFIG for standardized error codes.
actions/setup/js/close_entity_helpers.cjs	Wraps comment-posting failures with an ERR_API-prefixed error and attaches the original error as cause.

Copilot's findings

Tip

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

• Files reviewed: 2/2 changed files
• Comments generated: 2

[Copilot]

This change introduces a standardized ERR_CONFIG prefix for missing-file errors, but the existing unit tests for the missing source/config file cases only assert that the script throws (they don’t assert the error message starts with ERR_CONFIG:). Adding an assertion for the thrown error message would prevent regressions in USE-001 conformance.

[Copilot]

The new wrapped throw (with ${ERR_API}: ... and { cause: commentError }) isn’t covered by tests. Since this file already has a Vitest suite, add a unit test that forces callbacks.addComment to reject when continueOnCommentError is false and assert the returned error message includes the ERR_API: prefix (and optionally that the thrown Error has the expected cause).