aitbc1
37abc660da
Some checks failed
/ audit (push) Failing after 4s
ci-cd / build (push) Failing after 5s
ci / build (push) Failing after 3s
AITBC CLI Level 1 Commands Test / test-cli-level1 (18) (push) Failing after 14s
AITBC CLI Level 1 Commands Test / test-cli-level1 (20) (push) Failing after 5s
autofix / fix (push) Failing after 2s
security-scanning / audit (push) Failing after 1s
test / test (push) Failing after 3s
ci-cd / deploy (push) Has been skipped
CRITICAL FIX: Resolve act_runner host mode working directory issue Problem: - act_runner host mode does not persist working directory between steps - Each 'cd repo' command was being lost due to isolated step execution - npm install was still running in hostexecutor directory instead of repo Solution: - Add 'working-directory: repo' to every step after clone - Enforce working directory at step level instead of inside run commands - This bypasses act_runner host mode quirks completely Changes: - Update all 7 workflows to use working-directory: repo - Remove 'cd repo' from run commands (redundant with working-directory) - Keep git clone step outside working-directory (needs to run in default dir) - Add verification steps to confirm correct working directory Workflows updated: - ci.yml, audit.yml, fix.yml, test.yml, security-scanning.yml - cli-level1-tests.yml, ci-cd.yml This should finally resolve the ENOENT: no such file or directory errors for package.json by ensuring all npm commands execute in the correct repository directory.