Attribute Kingston broad actions to public outreach with daily aggregates - #8
Merged
Merged
Conversation
Deploying with
|
| Status | Name | Latest Commit | Preview URL | Updated (UTC) |
|---|---|---|---|---|
| ✅ Deployment successful! View logs |
buscore-lighthouse | 4b82797 | Commit Preview URL Branch Preview URL |
Sep 09 2026, 11:54 PM |
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
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.
Kingston's current aggregate report loses action attribution, and all recent campaign labels were untagged. Add strict ingestion v3 for the existing broad actions and a report 1.2 that exposes independent public source/campaign/content totals while keeping historical actions unclassified.
reddit,outreach_2026_09andpost_02labels. Preserve strict v1/v2 clients and unattributed installation signals.kfh_outreach_daily; atomically write its independent margins and original totals. Keep original-table page labels compatible with a rollback Worker; migration 0016 stays unchanged.Validation: typecheck and 214 tests passed, including SQL constraints, atomic two-table rollback, mixed legacy/v3 history, migration reapplication/missing migration, retention and report validation. Shared validators and all seven fixtures match Smith exactly. No remote database mutation or production analytics request was made.
Release gate: deploy Smith 0.29.0 first. After owner review, merge this PR, apply exactly migration 0017 to the existing Lighthouse DB after checking pending migrations, verify its receipt, then dispatch the existing Deploy Lighthouse to Cloudflare manual main workflow. Deploy Kingston 0.2.0 last. Merging this PR uploads a version only; it does not apply SQL or promote production.
Read-only 2026-09-09 settings verification confirmed both Lighthouse Workers Builds triggers use
npx wrangler versions upload. Review publication can create a preview/version. No settings were changed.Exact files, seven review impacts and rollback.
Coordinated review PRs (release order): Smith #11 → Lighthouse #8 (migration + manual promotion) → Kingston #2.
GitHub validation: Governance Validation passed on the proposed commit.