feat(newtab): Add hnt-backend-investigation skill - #32
Draft
mmiermans wants to merge 10 commits into
Draft
Conversation
mmiermans
force-pushed
the
add-hnt-backend-investigation-skill
branch
from
July 30, 2026 17:49
3dd3157 to
d0e16f9
Compare
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.
Adds
hnt-backend-investigationto the newtab plugin: a diagnostic workflow for Home New Tab backend incidents across Merino, the curated corpus, admin-api, the article crawler, and the ML section pipeline. Its output is an evidence-backedFINDINGS.mdcarrying a root cause and quantified impact. Two reference files hold the detail:references/data-sources.mdfor how to reach each system plus the data traps that silently produce wrong answers, andreferences/failure-modes.mdfor failure classes, invariants to check, and falsification moves. Table shapes, GCP project ids, the Merino corpus endpoint, and the Zyte API parameters were each verified against the live systems and the service repos. Docs/skill only; no code changes.Testing steps:
DEV:task for anything it cannot reach (corpus MySQL needs VPN, for instance) rather than stopping to waitFINDINGS.mdit writes, where every number should be reproducible from the queries saved alongside it