Squashed 'pgxntool/' changes from bed3604..b67064b

b67064b Release 2.2.0 (#77)
d949d6d Fix stale README/CLAUDE.md docs; rename internal-only test shim (#76)
6d7822c ci: grant actions:write so bun cache save succeeds (#75)
2738f59 README.asc: fix stale docs, document undocumented API surface (#74)
d1d3bee Add make pgxntool-version to print the embedded pgxntool version (#73)
493a0f8 Fix parallel-build SQL corruption, remote hardcoding, and add safety checks (#61)
3b0e3de Fix make pgtle PGTLE_VERSION=X being silently ignored (#66)
21b35ef ci: skip paired-test-PR requirement for doc-only PRs (#71)
55efd03 Rename EXTENSION_VERSION_FILES to EXTENSION__CURRENT_VERSION__FILES (#69)
9d0a856 Fix pgtle.sh rejecting non-numeric version aliases like 'stable' (#57) (#63)
9c2f75f Docs: versioned SQL file tracking tradeoffs and update-testing pattern (#60)
c38cf2a ci: never check out fork PR head in claude-code-review pull_request_target job (#70)
aab8f2b pgtle_versions.md: fix wrong uninstall_extension() version claim (#59)
e2c9174 README.asc: make tag creates a git tag, not a branch (#58)
eb84bc6 Stamp 2.1.0
9fbe6f4 Fix results ordering, control file whitespace, ENABLE_* override, debug levels (Postgres-Extensions#31)
88bb4f2 Add Claude Code GitHub Actions workflows (Postgres-Extensions#41)
af5bbbb ci: pass repo owners to run-tests.yml for fork-account matching (Postgres-Extensions#40)
c7928af Fix repo-root guard to work inside a git worktree (Postgres-Extensions#39)
b062fca ci: point reusable test workflow at @master
b6cdbfd Add CI workflows and multi-session PR guard (Postgres-Extensions#33)
1ba0987 Stamp 2.0.3
1931cbe Fix pgxntool-sync remote and make it runnable without make (Postgres-Extensions#37)
8176304 Stamp 2.0.2
3e142ab Fix parse_control_file: remove comments before stripping quotes (Postgres-Extensions#27)
cacc301 Stamp 2.0.1
bf1db6b Fix bash 3.2 / Linux compatibility issues (Postgres-Extensions#26)
62d0fcb Fix broken ifeq for --load-language=plpgsql on PG < 13 (Postgres-Extensions#24)
121f0b3 Stamp 2.0.0
ad3ca7e Remove .source support; add test/install, test/build, and verify-results (Postgres-Extensions#18)
c010cf8 Fix bash 3.2 compatibility (Postgres-Extensions#23)
abeb9d3 Remove .source file support from pg_regress integration (Postgres-Extensions#22)
08c1879 Stamp 1.1.2
6e0dad2 Fix double --dbname bug that defeated unique test database names
639756c Stamp 1.1.1
6ba3176 Fix pg_tle exception handler and empty upgrade files (Postgres-Extensions#15)
3b8cb2a Stamp 1.1.0
550a901 Remove commit.md (maintained in pgxntool-test)
d73ca93 Add unique test database names to prevent conflicts (Postgres-Extensions#13)
9b344be Add update-setup-files.sh for 3-way merging after pgxntool-sync (Postgres-Extensions#12)
ab7f6e2 Stamp 1.0.0
3a571ba Add pg_tle support and modernize test infrastructure (Postgres-Extensions#11)
b96ea6d Add support for Claude code; build and doc improvements (Postgres-Extensions#9)
e9c24de Fix pg_regress on versions > 12 (Postgres-Extensions#5)
REVERT: bed3604 Fix pg_regress on versions > 12 (Postgres-Extensions#5) (Postgres-Extensions#6)

git-subtree-dir: pgxntool
git-subtree-split: b67064b16ca2eb30761c078511dc8c974938480f

Author: jnasbyupgrade

.claude/CLAUDE.md

@@ -0,0 +1,28 @@
+# Claude Development Notes
+
+This file contains guidance for Claude Code when working in this repository.
+It is excluded from distributions via `.gitattributes export-ignore`.
+
+## CI Monitoring After Every Push
+
+**REQUIRED**: After every `git push`, immediately start a background task to
+monitor the CI run for that push. If you pushed to both pgxntool and
+pgxntool-test, start a background task for each repo — do not monitor them
+sequentially.
+
+Use `gh run watch` or poll with `gh run list` / `gh pr checks` in the
+background task. Report failures to the user as soon as they are detected;
+do not wait for all jobs to finish before reporting.
+
+## Multiple Concurrent Sessions
+
+It is common to have multiple Claude Code sessions open simultaneously across
+pgxntool and pgxntool-test. To avoid cross-session interference:
+
+**If you are asked to do something on an existing PR that you did not open or
+are not already working on in this session, immediately ask for confirmation
+before proceeding.** For example: "I see PR #32 exists. Were you asking me to
+work on that, or did you mean to send this to a different session?"
+
+This applies to: editing PR branches, pushing to them, closing/reopening them,
+adding commits, modifying PR descriptions, or any other PR-level action.

.claude/development.md

@@ -0,0 +1,47 @@
+# pgxntool Development Guidelines
+
+**THIS FILE IS FOR PGXNTOOL DEVELOPERS ONLY.**
+
+If you are an extension developer using pgxntool in your project, this file does not
+apply to you. See the top-level `CLAUDE.md` instead.
+
+## Critical: Work from pgxntool-test, Not Here
+
+**NEVER make changes to pgxntool directly from this repository.**
+
+pgxntool development must be done from a checkout of **pgxntool-test**, which contains
+the full test infrastructure. Working here directly means you cannot run tests, and
+any changes you commit cannot be validated before merging.
+
+**Correct workflow:**
+1. Clone or use an existing checkout of `pgxntool-test`
+2. Work in a worktree: both `pgxntool/` and `pgxntool-test/` will be siblings
+3. Make changes to `pgxntool/` from within that pgxntool-test context
+4. Run the test suite via `make test` in pgxntool-test before committing
+
+**See:** https://github.com/Postgres-Extensions/pgxntool-test for the full development
+workflow.
+
+---
+
+## Makefile Variable Assignment Rules
+
+**RULE: Do not use `:=` (simply expanded) unless you have a specific need for immediate evaluation.**
+
+Use `=` (recursively expanded) for standard variable assignments. Reserve `:=` for cases where the right-hand side must be evaluated exactly once at assignment time — for example, when assigning the result of a `$(call ...)` function that references the variable being set (which would cause infinite recursion with `=`).
+
+When a variable must also override command-line values, combine `override` with `:=` — but only where `override` is genuinely needed.
+
+## Debug Level Rules (lib.sh `debug` function)
+
+`debug LEVEL "msg"` prints when `DEBUG >= LEVEL`. LEVEL encodes how noisy/esoteric a message is — how far you'd crank `DEBUG` before you'd want to see it — **not** code nesting depth. A top-level line can warrant a high level if it's esoteric, and loop-body detail is usually high precisely because it's noisy. Judge by signal-to-noise.
+
+The tiers are anchors, not strict multiples of 10 — any value in range is fine, leaving room to fine-tune between existing calls without renumbering:
+
+- **10**: Critical errors, important warnings
+- **20**: Warnings, significant state changes
+- **30**: General debugging, function entry/exit, array operations
+- **40**: Verbose details, loop iterations
+- **50+**: Maximum verbosity (per-iteration innards)
+
+Note: The BATS test helper `debug` function (in `tests/lib/helpers.bash` in pgxntool-test) uses a separate 1–5 scale controlled by `$TESTDEBUG`. The two systems are independent.

.gitattributes

@@ -1,4 +1,8 @@
 .gitattributes export-ignore
+.claude/ export-ignore
+.github/ export-ignore
+*.md export-ignore
+.DS_Store export-ignore
 *.asc export-ignore
 *.adoc export-ignore
 *.html export-ignore

.github/workflows/CLAUDE.md

@@ -0,0 +1,71 @@
+# .github/workflows — CI Architecture
+
+## Workflow files
+
+- **`ci.yml`** — main CI for pgxntool pull requests. Runs `check-test-pr` (verifies
+  the paired pgxntool-test PR's CI passed), then optionally runs `test` (only for the
+  commit-with-no-tests path — see below).
+- **`protect-label.yml`** — enforces that only maintainers with write access can apply
+  or remove the `commit-with-no-tests` label.
+
+## Normal CI flow (paired test PR exists)
+
+When a pgxntool PR has a corresponding open PR in pgxntool-test with the same branch
+name, the `check-test-pr` job polls (up to 20 minutes) for that test PR's CI to
+complete and pass. If it passes, pgxntool CI passes — **no tests run here**. Tests run
+exactly once, in pgxntool-test's own CI.
+
+## commit-with-no-tests path
+
+When a maintainer applies the `commit-with-no-tests` label (and no paired test PR
+exists), the `test` job runs tests directly in pgxntool CI against pgxntool-test/master.
+This is the rare exception, not the norm.
+
+## Doc-only bypass
+
+`check-test-pr` checks this first, before the paired-test-PR lookup or the
+`commit-with-no-tests` label: if every changed file in the PR is pure
+documentation (`*.md`, `*.asc`, `*.adoc`, `*.asciidoc`, anywhere including
+under `.claude/`, but never under `.github/` — workflow definitions carry
+real behavioral weight regardless of extension), it skips both the paired
+branch requirement and the `test` job entirely. `claude-code-review.yml` is
+a separate workflow gated by its own `if:` and always still runs.
+
+## Cross-repo reusable workflow — tradeoffs and constraints
+
+The `test` job calls a reusable workflow from pgxntool-test:
+```yaml
+uses: Postgres-Extensions/pgxntool-test/.github/workflows/run-tests.yml@<ref>
+```
+
+GitHub Actions requires the `uses:` ref to be a **static string** — expressions like
+`${{ }}` are not supported in the repo/path portion or the `@ref` suffix in practice.
+
+### The @branch → @master ref
+
+While developing on a feature branch where pgxntool-test also has changes, this ref
+is set to `@<branch>` so CI can find `run-tests.yml` before it lands on master.
+
+**IMPORTANT**: This ref must be updated to `@master` before pgxntool merges. The
+correct merge order is: **pgxntool-test merges first**, then update this ref to
+`@master`, then pgxntool merges.
+
+**For Claude**: Do NOT leave a `@<branch>` ref without explicit user approval. The
+user merges directly from the PR page — there are no manual steps between merges.
+See `.github/workflows/CLAUDE.md` in pgxntool-test for the full picture.
+
+### Changes to run-tests.yml
+
+`run-tests.yml` lives in pgxntool-test and is the single source of truth for all test
+steps. If it changes, pgxntool's CI uses `@master` — so it won't see the new version
+until pgxntool-test merges. This is acceptable because:
+- Changes to `run-tests.yml` require a paired test PR (not commit-with-no-tests)
+- When a paired test PR exists, pgxntool's `test` job is skipped anyway
+- The two scenarios are mutually exclusive in practice
+
+## Label name
+
+The label `commit-with-no-tests` is defined as a const (`NO_TEST_LABEL`) in `ci.yml`
+and as `LABEL` in `protect-label.yml`. The job-level `if:` condition in
+`protect-label.yml` must also use the literal string (YAML can't reference JS consts)
+— keep these in sync if the label name ever changes.