From 8b302f4c4a7c7bcc4d13b2c94508ee55bdc19b55 Mon Sep 17 00:00:00 2001 From: jnasbyupgrade Date: Sat, 29 Aug 2026 17:52:51 -0500 Subject: [PATCH] CLAUDE.md: put pgxntool's new PostgreSQL-only docs in the API-surface list Postgres-Extensions/pgxntool@adb779247dbb8ca487c2c430302357635f43e657 adds `POSTGRES-NOTES.asc` and `CLAUDE-POSTGRES.md` to pgxntool. Both ship to consumers via subtree, so the release review must look at them, but neither can ever produce a `HISTORY.asc` entry: they hold only guidance about PostgreSQL itself, so nothing in them describes pgxntool behavior. A claim in either file that turns out to be about pgxntool is itself the finding -- it belongs in `README.asc`/`CLAUDE.md` instead. Co-Authored-By: Claude Opus 5 (1M context) --- CLAUDE.md | 9 ++++++++- 1 file changed, 8 insertions(+), 1 deletion(-) diff --git a/CLAUDE.md b/CLAUDE.md index cc376fe..fc1fd8e 100644 --- a/CLAUDE.md +++ b/CLAUDE.md @@ -247,7 +247,14 @@ section once resolved. a behavior change, call it out in `HISTORY.asc` too. (For other files that are genuinely just internal dev documentation with no bearing on consumer projects, doc-only changes don't need a `HISTORY.asc` entry.) -7. Everything else is internal by default unless there's a specific +7. **`../pgxntool/POSTGRES-NOTES.asc` and `../pgxntool/CLAUDE-POSTGRES.md` + ship to consumers too, so review them for accuracy — but they never + generate `HISTORY.asc` entries.** They deliberately hold only guidance + about PostgreSQL itself, not about pgxntool, so nothing in them can + describe a pgxntool behavior change. If a claim in either one turns out + to be about pgxntool after all, that's the finding: it belongs in + `README.asc`/`CLAUDE.md` instead. +8. Everything else is internal by default unless there's a specific indication otherwise. ## Running Skills and Scripts