Six Scouts Day and Night: The Survey Map of Three TV Ad Implementations, Six Hundred Million Tokens Spent Downhill, and an Honorable Retreat

A campaign that ran from dawn to dusk closed with a complete map, three signed packages, and one retreat order. Wars with dishonorable retreats are many; an honorable retreat is itself a military merit.

I. The Dawn Survey: Six Scouts Down the Shaft in Two Batches

The first batch of three subagents launched at 00:55, the second at 03:16, all working atop the cloud jadx sources. The survey map entered the register point by point: Qiyiguo — the Cupid ad endpoint cluster (t7z.cupid.iqiyi.com mixer/baiai/track2/etx, msga scp2.gif tracking pixels) and the complete class chain of the start-cover ad (the spotlight request, the StartScreenAdSaver scheduler, the StartUpAdData model); Jiguang — two generations of ad SDK stacks coexisting (com.tencent.ads.v2, the elder GDT, and com.tencent.tads.dynamic, the new Ott TADS), with the global agency ADProxy ruling splash, channel streams, single-page cards and exposure reporting, the GDT main domain appearing twenty-one times, and the getvinfo domain carrying main-content playback data — no blanket blocking, the red note written into the intel; Kumiao — the nine-endpoint family of valf.atm.cp31.ott.cibntv.net (/mi splash, /mp pause, /mo mid-roll, /adv pre-roll, /sc scene, /ui homepage masthead…) verified road by road with its WASU variants and test domains, and the master switch of StartAdInitJob (enable_start_ad) exhumed alongside.

II. The Noon Forge and Acceptance

Analysis documents were written to disk as they were produced (five artifacts), then three rounds of repackaging: three sets of formal signing keys settled in keystores, three release APKs (31/33/22 MB) passed emulator acceptance — Jiguang straight through protocol to home with zero crashes and zero ads; Qiyiguo poster wall with zero crashes; Kumiao incompatible with the emulator environment, left for a real device. The master then added two rules of engagement: test the free sources per app; and the watch-ad-to-unlock-VIP benefit must not be amputated by the de-ads — selective patching and even a skip-the-ad-and-still-earn-the-unlock approach were tabled.

III. The Dusk Retreat: The Source of Power Is Not in the Client

The logic of the retreat was cold and clear: much of these three apps’ ad configuration is delivered from the server side (Jiguang’s ad_config_cgi_host, Kumiao’s YK-SSP inventory points, Qiyiguo’s Cupid requests); the client can cut only the outstretched hands, while the wrists that cast them live on the server; stacked with membership and benefit-chain risks, a patch cannot reach the source of power. The master ordered: the three apps removed from the television, the campaign terminated. The scouts’ maps, three sets of keys and three APKs entered the vault complete — the map itself is this campaign’s product, and the day anyone walks the router-level blocking road, this map is the ammunition depot.

IV. Six Hundred Million Tokens: The Splurge and the Yield

At war’s opening the master budgeted six hundred million tokens with the instruction to spend freely and accelerate — the most extravagant ledger entry of this campaign, and the very reason the cloud subagent legion could exist. The yield on the books: the complete ad-implementation survey of three apps, a two-batch parallel subagent methodology, an emulator acceptance pipeline, and one theorem bought with an entire day — in a client-patch campaign, the decisive question is settled before the war: which side of the wire holds the source of configuration.