v3.8.0-alpha.5 — Hotfix: botched findProjectRoot() migration
Pre-release
Pre-release
·
139 commits
to main
since this release
The v3.8.0-alpha.2
findProjectRoot()migration insertedconst { findProjectRoot } = require('./hook-runtime.cjs');inside an array literal in 4 hook files, producing aSyntaxError: Unexpected token 'const'. The bug stayed latent while the installed plugin was 3.7.4; updating to the 3.8.0-alpha line surfaced it ("Failed with non-blocking status code: …/af-config-utils.cjs:498"). Any hook thatrequire()d an affected lib failed to load.
Fixed
SyntaxErrorin 4 hook files — hoisted the lazyrequire('./hook-runtime.cjs')out of the array literal to a valid statement position (immediately before the array, preserving the lazy-require to avoid a circular dependency withhook-runtime.cjs):aura-frog/hooks/lib/af-config-utils.cjs(isAgentTeamsEnabled, line 498) —af-config-utilsis required by 12 hooks, so this was the highest-impact instance.aura-frog/hooks/lib/record-workflow-event.cjs(getActiveWorkflowId)aura-frog/hooks/lib/team-bridge.cjs(resolveWorkflowDir)aura-frog/hooks/subagent-init.cjs(workflow-state path resolution)
- Verified:
node -cclean across all hooks + libs (0 syntax errors); each fixed module loads andfindProjectRoot()resolves; full suite 627/627 green.
Note: backfilled tag. plugin.json was not bumped to alpha.5 at the time (it stayed alpha.4); this release marks the hotfix commit that the CHANGELOG documents as alpha.5.