35 lines
1.3 KiB
Markdown
35 lines
1.3 KiB
Markdown
---
|
|
id: TASK-27
|
|
title: Trigger audit generation after PageSpeed audit
|
|
status: In Progress
|
|
assignee: []
|
|
created_date: '2026-06-05 12:10'
|
|
updated_date: '2026-06-05 19:30'
|
|
labels: []
|
|
dependencies: []
|
|
priority: high
|
|
ordinal: 29000
|
|
---
|
|
|
|
## Description
|
|
|
|
<!-- SECTION:DESCRIPTION:BEGIN -->
|
|
Wire the existing AI audit generation queue into the current automated flow so completed PageSpeed audit runs schedule audit_generation for the same lead.
|
|
<!-- SECTION:DESCRIPTION:END -->
|
|
|
|
## Acceptance Criteria
|
|
<!-- AC:BEGIN -->
|
|
- [ ] #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
|
|
<!-- AC:END -->
|
|
|
|
## Implementation Notes
|
|
|
|
<!-- SECTION:NOTES:BEGIN -->
|
|
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.
|
|
<!-- SECTION:NOTES:END -->
|