bin/compare_fresh_vs_update: reference cat_tools#67 and fix a stale job name

cat_tools#67 proposes generalizing this script's object-discovery-and-
diff technique into a real cat_tools feature; note it as a natural
follow-up. Also fix test/README.md's mention of the now-removed
extension-update-test job (folded into test earlier in this stack).

Author: jnasbyupgrade

bin/compare_fresh_vs_update

@@ -16,6 +16,15 @@
 # already updated to `EXECUTE FUNCTION`). Unlike that PR, this is committed,
 # reusable tooling rather than a one-off manual diff.
 #
+# Postgres-Extensions/cat_tools#67 proposes generalizing this exact
+# capability - "list every object an extension owns, with each object's
+# actual definition" - into a real, user-facing cat_tools feature, not
+# test-only plumbing tied to one extension's update path. If that lands,
+# this script's object-discovery-and-rendering logic (extension_members()
+# below, and the per-kind comparisons) is a natural candidate to
+# reimplement on top of it rather than staying a bespoke,
+# count_nulls-specific copy.
+#
 # What's compared, per object the extension owns (discovered live via
 # pg_depend - see extension_members(), not a hardcoded object list, so a
 # newly added function is automatically covered without editing this

test/README.md

@@ -25,7 +25,7 @@ then invoke via `runtests()`.
   strictness, and behavior across `anyarray`/`json`/`jsonb` and both
   trigger functions.
 - `../bin/compare_fresh_vs_update` — not part of the pgTAP suite itself: a
-  standalone script the `extension-update-test` CI job runs after
+  standalone script the `test` CI job's update leg runs after
   `TEST_LOAD_SOURCE=update`, which installs fresh and 0.9.6-then-updated
   copies of the extension in their own scratch databases and diffs
   `pg_get_functiondef`/comments/ACLs for every object the extension owns.