SPIKE: automated email analytics incremental#29080
Draft
cmraible wants to merge 44 commits into
Draft
Conversation
Documented the proposed separate automation analytics pipeline so the architecture can be reviewed before implementation.
no ref Captured the resolved architecture decisions for the automation analytics spike, including the separate pipeline, incremental aggregation model, and shared terminology before implementation starts.
no ref Prepared a concrete red/green implementation plan and spike notes template so the build can proceed in small, reviewable commits.
no ref Documented the lead-agent workflow for running the implementation spike with sequential implementation and validation subagents.
no ref Extracted shared fetch orchestration so newsletter behavior stays intact while automation can add an independent pipeline later.
no ref This prepares automated email analytics to resolve Mailgun delivered and opened events against automated email recipient rows.
no ref Validated that the welcome email automation poll persists Mailgun message ids on tracked recipient rows.
no ref Track automation sends only after a Mailgun message id has been recorded so sent counts remain traceable during the analytics spike.
no ref Covered the automation action revision sent count write in the repository test fixture.
no ref This proves the DB-backed automation processor updates recipient state and automation aggregates without touching newsletter member counters.
no ref Rerunning the same provider batch proves automation analytics counters are guarded by recipient state transitions.
no ref The automation analytics adapter now proves cursor reads and writes stay on automation job rows instead of newsletter job rows.
no ref Automation completion logs now include no-op counts when pipeline results expose them.
no ref Keep the final spike cleanup focused on removing unused runner adapter API and recording the aggregate flush production follow-up.
github-actions
Bot
added
the
migration
Contributor
|
It looks like this PR contains a migration 👀 General requirements
Schema changes
Data changes
|
Contributor
|
Important Review skippedDraft detected. Please check the settings in the CodeRabbit UI or the ⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: CHILL Plan: Pro Run ID: You can disable this status message by setting the Use the checkbox below for a quick retry:
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This is a spike; PR created to review and discuss the changes more easily, but we'll be breaking this down into a number of smaller PRs before merging.