Plan: Unit tests for BLOCKED:PERSISTENT → gated status transition#

Summary#

Add missing edge-case unit tests in internal-adapter.service.spec.ts and create a new phase-hooks.service.spec.ts to cover the BLOCKED:PERSISTENT → status=gated transition and the gated hook category side effect from commit #243.

Files#

File	Action	Description
`src/internal-adapter/internal-adapter.service.spec.ts`	modify	Add edge-case tests: already-gated task, transient block resolved before threshold
`src/hooks/phase-hooks.service.spec.ts`	create	Unit tests for `onPhaseBlocked` with `gated` category

Steps#

Add "already gated" edge case to internal-adapter.service.spec.ts: create a task with status=gated, fire BLOCKED:PERSISTENT, assert no error and status remains gated with updated gatePhase/gateReason.
Add "clears before threshold" edge case to internal-adapter.service.spec.ts: fire one BLOCKED:TRANSIENT (below MAX_TRANSIENT_RETRIES), then fire COMPLETE — assert status is NOT gated and task advances normally.
Create phase-hooks.service.spec.ts: test onPhaseBlocked with category='gated' for a non-refine/review phase — assert addLabel('agent-blocked') is called and comment body contains 🚫 Phase persistently blocked.
Test gated category early return for refine/review: call onPhaseBlocked with category='gated' and phase='refine' or phase='review' — assert no label added and no comment posted.

Verification#

npm run test passes with all new tests green
npm run lint passes with zero warnings
No production code changes

Risks#

PhaseHooksService constructor has four dependencies (GitHubService, ConfigService, CompoundService, EventService) — all must be mocked correctly in the new spec file.