[Bug] Persistent ESLint Parsing Error in bats-tests-runner.agent.js (Line 690)

[ashleyshaw]

Describe the bug

A persistent ESLint parsing error occurs at line 690 in .github/agents/bats-tests-runner.agent.js:

690:1  error  Parsing error: Unexpected token

Attempts to clean up the file, remove trailing content, and forcefully rewrite the ending have not resolved the error. The file appears to end cleanly after the module.exports block, with no visible extra content, but the error persists. This may be due to an invisible character, encoding issue, or a deeper ESLint/parser bug.

Script/Workflow affected

• Script name: bats-tests-runner.agent.js
• Workflow name: JS Linting (npm run lint:js)
• File path: .github/agents/bats-tests-runner.agent.js

To Reproduce

1. Run npm run lint:js
2. Observe the parsing error at line 690

Expected behavior

Linting should pass if the file ends cleanly after the export block.

Actual behavior

Parsing error persists at the end of the file, blocking pre-commit and CI.

Environment

• OS: macOS
• Shell: zsh
• Script version/commit: develop branch, 23 Oct 2025

Logs

npm run lint:js
690:1  error  Parsing error: Unexpected token

Additional context

• File has been repeatedly cleaned and truncated after the export block.
• No visible extra content or syntax errors remain.
• May require manual inspection for hidden characters or ESLint parser update.

Potential Changelog Entry

Fixed

• Persistent parsing error at end of bats-tests-runner.agent.js resolved

Definition of Ready (DoR) Checklist

• Bug description is clear and reproducible
• Affected script/workflow identified
• Environment details provided
• Potential impact assessed

Definition of Done (DoD) Checklist (for maintainers)

• Bug confirmed and reproducible
• Fix implemented
• Tests updated/added to prevent regression
• Documentation updated if needed
• Changelog entry added
• Fix verified in all affected environments