diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index ac30308..9e3ce90 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -285,5 +285,10 @@ jobs:
     # -----------------------------------------------------------------------
     uses: Postgres-Extensions/pgxntool-test/.github/workflows/run-tests.yml@master
     with:
+      # pgxntool: this PR's own branch, on its own account (a fork for fork PRs).
+      pgxntool-owner: ${{ github.event.pull_request.head.repo.owner.login }}
       pgxntool-branch: ${{ github.event.pull_request.head.ref }}
+      # pgxntool-test: no paired test PR in this path, so use canonical master
+      # from Postgres-Extensions only (never a fork's master).
+      pgxntool-test-owner: Postgres-Extensions
       pgxntool-test-ref: master
diff --git a/README.asc b/README.asc
index 03b9acc..db6162f 100644
--- a/README.asc
+++ b/README.asc
@@ -25,7 +25,9 @@ TODO: Create a nice script that will init a new project for you.
 
 == Development
 
-If you want to contribute to pgxntool development, work from the https://github.com/decibel/pgxntool-test[pgxntool-test] repository, not from this repository. That repository contains the test infrastructure and development tools needed to validate changes to pgxntool. This repository contains only the framework files that get embedded into extension projects via `git subtree`.
+If you want to contribute to pgxntool development, work from the https://github.com/Postgres-Extensions/pgxntool-test[pgxntool-test] repository, not from this repository. That repository contains the test infrastructure and development tools needed to validate changes to pgxntool. This repository contains only the framework files that get embedded into extension projects via `git subtree`.
+
+Changes are normally paired across both repos: a `pgxntool` change should come with a matching branch (same name, on the same account) and PR in `pgxntool-test`, and CI enforces this pairing. See the https://github.com/Postgres-Extensions/pgxntool-test#ci-and-contributing[CI and Contributing] section in pgxntool-test for the full workflow.
 
 == Usage
 Typically, you can just create a simple Makefile that does nothing but include base.mk:
diff --git a/README.html b/README.html
index a46c633..431358f 100644
--- a/README.html
+++ b/README.html
@@ -542,7 +542,10 @@ <h2 id="_install"><a class="anchor" href="#_install"></a><a class="link" href="#
 <h2 id="_development"><a class="anchor" href="#_development"></a><a class="link" href="#_development">2. Development</a></h2>
 <div class="sectionbody">
 <div class="paragraph">
-<p>If you want to contribute to pgxntool development, work from the <a href="https://github.com/decibel/pgxntool-test">pgxntool-test</a> repository, not from this repository. That repository contains the test infrastructure and development tools needed to validate changes to pgxntool. This repository contains only the framework files that get embedded into extension projects via <code>git subtree</code>.</p>
+<p>If you want to contribute to pgxntool development, work from the <a href="https://github.com/Postgres-Extensions/pgxntool-test">pgxntool-test</a> repository, not from this repository. That repository contains the test infrastructure and development tools needed to validate changes to pgxntool. This repository contains only the framework files that get embedded into extension projects via <code>git subtree</code>.</p>
+</div>
+<div class="paragraph">
+<p>Changes are normally paired across both repos: a <code>pgxntool</code> change should come with a matching branch (same name, on the same account) and PR in <code>pgxntool-test</code>, and CI enforces this pairing. See the <a href="https://github.com/Postgres-Extensions/pgxntool-test#ci-and-contributing">CI and Contributing</a> section in pgxntool-test for the full workflow.</p>
 </div>
 </div>
 </div>