1.6 KiB
id, title, status, assignee, created_date, updated_date, labels, dependencies, priority, ordinal
| id | title | status | assignee | created_date | updated_date | labels | dependencies | priority | ordinal |
|---|---|---|---|---|---|---|---|---|---|
| TASK-27 | Trigger audit generation after PageSpeed audit | In Progress | 2026-06-05 12:10 | 2026-06-05 19:49 | high | 29000 |
Description
Wire the existing AI audit generation queue into the current automated flow so completed PageSpeed audit runs schedule audit_generation for the same lead.
Acceptance Criteria
- #1 Successful PageSpeed audit runs queue audit generation for the lead
- #2 Failed PageSpeed audit runs still queue audit generation when a lead was started so partial evidence can produce an audit
- #3 Existing dedupe in queueLeadAuditGeneration prevents duplicate audit_generation runs
- #4 Regression tests cover the PageSpeed-to-audit-generation handoff
Implementation Notes
Created accidentally while implementing the PageSpeed-to-audit-generation handoff. Superseded by TASK-13 because the handoff is a prerequisite for the audit/outreach review workspace. Do not implement separately.
Started verification pass. Implementation notes say TASK-27 is superseded by TASK-13, so only regression coverage and existing handoff will be checked.
Verified existing PageSpeed-to-audit-generation handoff in pageSpeedAction. Successful and failure paths queue audit generation for the started lead, queue failures are warning-logged, existing queueLeadAuditGeneration dedupe remains in place, and regression source tests pass. Verification: pnpm test 305/305; pnpm lint 0 errors.