feat(content): refresh validated decision pages with evidence-first handoffs

## What to build

Use the evidence from #5928 to refresh two or three existing high-intent WorldMonitor decision pages rather than creating a high-volume content queue. Cover the strongest validated country-risk, chokepoint/supply-chain, crisis, or developer/MCP questions, and treat #4998 as completed page creation—not permission to publish another generic comparison page.

Each page should help a reader make a decision, verify the evidence, and take the next product action.

## Acceptance criteria

- [ ] Page selection is based on observed demand, indexation health, useful engagement, and a credible product handoff from #5928; record the chosen query, audience, and conversion goal.
- [ ] Each selected page gives a direct answer near the top, states who it is and is not for, and explains the relevant WorldMonitor workflow.
- [ ] Mutable prices, capability counts, coverage claims, and competitor comparisons are dated and linked to authoritative primary sources; unsupported absolutes are removed.
- [ ] Each page includes current provenance/methodology, honest limitations, a visible publication or update date, and only supportable tables or statistics.
- [ ] Existing canonical URLs are updated rather than duplicated; contextual internal links connect the page to its related guide, evidence, and next step.
- [ ] The next action is intent-matched: free dashboard, Pro workflow, API documentation, or MCP connection.
- [ ] Blog/content SEO contracts, generated metadata, sitemap integration, and production build validation pass.
- [ ] No fixed page quota, mass-generated copy, backlink exchange, or citation-guarantee language is introduced.

## Blocked by

- #5928 — operational first-party visibility and outcome collection.

## AI search execution handoff — 6 September 2026

## Blocked by

The usable selection evidence from #6036, which executes the existing measurement implementation. A closed implementation issue or a technically valid empty report does not satisfy this gate. Retain the historical #5928 reference for context.

## Before marking ready for implementation

The coordinator must record each selected query ID, exact canonical URL, owner, authoritative source files, required generated outputs, evidence of the user problem, intended product handoff, and verification commands. Select only the pages justified by #6036; do not fill a quota.

Until those fields exist, this is an evidence-blocked issue, not an autonomous instruction to choose arbitrary pages. If pages share a generator, sitemap or template, use one writer for the set. Split into child issues only when the page scopes are independently verifiable and the write sets are disjoint; shared generator work remains with one owner.

## Collision boundaries

- The measurement collector, scorecard, README, query registry and completed baseline records remain read-only during a page refresh.
- Comparison content and necessary sitemap changes require release from #7767 and any active #7749 writer before this issue can reserve them.
- `/use-cases/` changes must honor #6852's pilot decision and evidence window. Do not duplicate that evaluation or expand the pilot from weak evidence.
- Do not change query text or success criteria after reading outcomes to make a page appear successful. A necessary new query contract is separate measurement-owner work.

## Evidence required at handoff

Retain the existing issue's criteria for direct answers, primary sources, dates, limitations, accurate entitlements, preserved canonical URLs and intent-matched product actions. Deliver before/after rendered evidence, the verified source data, affected checks and the exact PR head. Post-change measurement uses a later dated cycle owned by the collection task; it must not overwrite the selection baseline or claim causality from one comparison.

No new publication campaign, outreach, tracking system, forced page quota, reviewer request, merge or deployment is authorized by this addendum.

Start by resolving the evidence gate in #6036 and #5928, then record the selected query IDs, canonical URLs, owners, sources, generated outputs, and product handoffs. Inspect the existing canonical pages and the shared content SEO contracts, metadata, sitemap integration, and production-build validation named here. Done means the selected pages meet the acceptance criteria and the affected checks pass.

Written by the indexing model from the issue text.