chore(scripts): add real-world managerdomain fallback probe#4286
Merged
chore(scripts): add real-world managerdomain fallback probe#4286
Conversation
Ad-hoc developer tool that hits live DNS / public web against a small
fixture of known publisher-manager pairs and asserts the
AdAgentsValidationResult envelope.
Not for CI — meant as a manual probe to confirm the fallback path
still does what we think against real managed-network publishers.
Caught three real-world divergences during initial run, captured in
the fixture rationales as TODOs for follow-up:
1. craftgossip's adagents.json fails JSON validation.
2. homestratosphere's fallback to mediavine.com does not reach the
scope gate — likely a validator schema delta against Mediavine's
agent_url field naming.
3. freestar.com 404s on /.well-known, so its delegating publishers
fail closed today.
Existed as a manual curl exercise before — moving the fixture set
into version control so the next regression is caught on demand. The
original gap fixed in #4283 (property-level scoping) is exactly what
this would have caught.
Usage:
npx tsx server/scripts/probe-managerdomain-fallback.ts --verbose
Refs #4173, #4200, #4283.
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.
Ad-hoc developer tool (`server/scripts/probe-managerdomain-fallback.ts`) that hits live DNS / public web against a small fixture of known publisher-manager pairs and asserts the `AdAgentsValidationResult` envelope.
Not for CI — meant as a manual probe a developer runs after touching `adagents-manager.ts` to confirm the path still does what we think against real managed-network publishers. Existed as a manual `curl` exercise before; moving the fixture set into version control so the next regression is caught on demand rather than after merge.
The original gap fixed in #4283 (property-level scoping rejected by the gate) is exactly what this would have caught — every fixture against a real Raptive/Mediavine/Freestar-managed site would have failed the strict envelope, and a developer running the probe before merging #4204/#4210/#4251 would have surfaced it.
Fixtures
What the initial run surfaced
Three real-world divergences captured in fixture rationales as TODOs:
Each is a follow-up; the script captures the current state so future regressions surface as fixture failures.
Usage
```
npx tsx server/scripts/probe-managerdomain-fallback.ts
npx tsx server/scripts/probe-managerdomain-fallback.ts --verbose
```
Exit 0 on all-pass, 1 on any fixture failing its envelope.
Refs #4173, #4200, #4283.