Ask the better question
The better question is what does that repo publish? And right behind it, who runs whose tests? Answer those two and the rest of your pipeline design mostly falls out.
A loose underline. Just enough weight to pull out the question.
Circle the thing that matters
In the source-coupled model, every repo is part of every other repo's build. With artifact coupling, each repo has one job: build, test, publish a versioned thing. Consumers pin a version. Upgrades are PRs you can review and revert.
One circle, not a page full of corrections.
Leave a mark in the margin
Flip it. The dependency triggers the consumer's tests. When a PR opens on shared-lib, it publishes a preview version (say 2.4.0-pr.123) and kicks off each known consumer's test suite with workflow_dispatch or repository_dispatch. The consumer runs its tests against that preview, then reports back by creating a check run on the producer's PR.
A paired bracket for the sentence you want to remember.