5758 - Navigation: Data errors - Rename visitDescriptionLinks & visitNationalDataPointLinks

[yaguzmang]

Addressing from the main PR todo:
"

• visitDescriptionLinks:
  • Move it to LinkService.validateLinks.
  • Why do we call visitDescriptionLinks, and what is the difference with triggerVerifyLinksWorker?"

To answer the question: “Why do we call visitDescriptionLinks, and what is the difference with triggerVerifyLinksWorker?”:

visitDescriptionLinks is now called LinksService.enqueueDescriptionLinksValidation, which better represents what it does. It doesn’t visit the links directly. It enqueues a verifyDescriptionLinks job.

triggerVerifyLinksWorker is different. It only makes sure a worker process exists to consume the queue (in-process in dev, no-op in e2e where a dedicated container runs, one-off dyno in production).

We don’t call triggerVerifyLinksWorker directly from enqueueDescriptionLinksValidation because the shared producer enqueueVerifyLinksJob (renamed from addVerifyLinksJob to align with the renames) already does that after adding the job to the queue.

In short: enqueueDescriptionLinksValidation schedules the validation, while triggerVerifyLinksWorker makes sure there is a worker to process it.

[mergify]

Merge Queue Status

• ✅ Entered queue — 2026-07-24 16:05 UTC · Rule: default · triggered by rule Automatic merge using squash
• ✅ Checks skipped · PR is already up-to-date
• ✅ Merged — 2026-07-24 16:06 UTC · at a48cffdbcbab58ecf02556ac2e4a017223e2bc2e · squash

This pull request spent 1 minute 15 seconds in the queue, including 9 seconds running CI.

Required conditions to merge

• #approved-reviews-by>=1
  • 5758 - Navigation: Data errors - Rename visitDescriptionLinks & visitNationalDataPointLinks #6163