docs: point contributing guides at the GitHub project; require PostgreSQL coding standards

Rewrite CONTRIBUTING.md and documentation/docs/contribute.md for the
standalone commandprompt/open_pg_tde project:
- Replace the Percona Jira tracker with GitHub Issues, the Percona forums with
  GitHub Discussions, and "open a pull request to Percona" with pull requests
  against commandprompt/open_pg_tde.
- Drop the Percona CLA and community references and the old
  contrib/open_pg_tde (percona/postgres) clone layout.
- Update build/test and docs-build instructions for the standalone repo and
  upstream PostgreSQL 16+ (Material for MkDocs plugin set, meson test).

Make the PostgreSQL coding conventions a firm, permanent requirement: all C
code (extension and core patch) must satisfy
https://www.postgresql.org/docs/current/source.html. Recorded in a new
repo-root CLAUDE.md and called out in both contributing guides.

Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: OffgridwithJD

CLAUDE.md

@@ -0,0 +1,32 @@
+# open_pg_tde project instructions
+
+`open_pg_tde` is an open fork of Percona's `pg_tde`, maintained by Command Prompt, Inc.
+It provides Transparent Data Encryption for upstream PostgreSQL 16 and later.
+
+## Coding standards (required)
+
+All code in this project MUST satisfy the PostgreSQL coding conventions:
+https://www.postgresql.org/docs/current/source.html
+
+This applies to every C change, in both the extension and the core patch under
+`patches/postgresql/`. Follow PostgreSQL's formatting, brace, naming,
+error-reporting (`ereport`/`errcode`), and memory-management (palloc/memory
+context) conventions, and run `pgindent` where applicable. Match the style of
+the surrounding PostgreSQL code. This is a firm requirement for every
+contribution and every review.
+
+## How the project is built
+
+- Runs on upstream PostgreSQL 16/17/18 (16 is the floor; the extension has no
+  support below 16). It is NOT tied to a vendor server fork.
+- The core storage-manager and WAL extensibility is applied as a gated patch to
+  a stock PostgreSQL source tree: `patches/postgresql/<major>/`, applied with
+  `patches/postgresql/apply.sh`.
+- The patch is gated behind `USE_TDE_HOOKS` (`--enable-tde-hooks` /
+  `-Dtde_hooks`). With the flag off, the patched tree builds as unmodified
+  PostgreSQL. Verify both states with `patches/postgresql/verify-gate.sh`.
+- Docs are Material for MkDocs under `documentation/`.
+
+## Documentation style
+
+No em-dashes. Avoid unnecessary adjectives. Keep prose professional and factual.

CONTRIBUTING.md

@@ -1,110 +1,94 @@
-# Code contributing guide
+# Contributing guide
 
-Welcome to `open_pg_tde` - the Transparent Database Encryption for PostgreSQL!
-
-We're glad that you would like to become a Percona community member and participate in keeping open source open.
+Welcome to `open_pg_tde`, Transparent Data Encryption for PostgreSQL, maintained by Command Prompt, Inc.
 
 You can contribute in one of the following ways:
 
-1. Reach us on our [Forums](https://forums.percona.com/c/postgresql/pg-tde-transparent-data-encryption-tde/82).
+1. [Start a discussion or ask a question](https://github.com/commandprompt/open_pg_tde/discussions)
 2. [Submit a bug report or a feature request](#submit-a-bug-report-or-a-feature-request)
-3. [Submit a pull request (PR) with the code patch](#submit-a-pull-request)
-4. [Contribute to documentation](#documentation-contribution)
-
-By contributing, you agree to the [Percona Community code of conduct](https://github.com/percona/community/blob/main/content/contribute/coc.md).
+3. [Submit a pull request (PR) with a code patch](#submit-a-pull-request)
+4. [Contribute to the documentation](#documentation-contribution)
 
 ## Submit a bug report or a feature request
 
-All bug reports, enhancements and feature requests are tracked in [Jira issue tracker](https://jira.percona.com/projects/PG). If you would like to suggest a new feature / an improvement or you found a bug in `open_pg_tde`, please submit the report to the [PG project](https://jira.percona.com/projects/PG/issues).
+All bug reports, enhancements, and feature requests are tracked in [GitHub Issues](https://github.com/commandprompt/open_pg_tde/issues). If you found a bug, or you want to suggest a feature or an improvement, open an issue there.
 
-Start by searching the open tickets for a similar report. If you find that someone else has already reported your issue, then you can upvote that report to increase its visibility.
+Start by searching the open issues for a similar report. If someone has already reported it, add a reaction or a comment so we can gauge interest.
 
-If there is no existing report, submit your report following these steps:
+If there is no existing report, open a new issue and aim for a report that is:
 
-1. Sign in to [Jira issue tracker](https://jira.percona.com/projects/PG/issues). You will need to create an account if you do not have one.
-2. In the _Summary_, _Description_, _Steps To Reproduce_, _Affects Version_ fields describe the problem you have detected or an idea that you have for a new feature or improvement.
-3. As a general rule of thumb, try to create bug reports that are:
+* Reproducible: describe the steps to reproduce the problem, including the PostgreSQL major version.
+* Unique: check that no existing issue already describes it.
+* Scoped to a single bug: report one bug per issue.
 
-  * Reproducible: describe the steps to reproduce the problem.
-  * Unique: check if there already exists a JIRA ticket to describe the problem.
-  * Scoped to a Single Bug: only report one bug in one JIRA ticket
+For feature requests and enhancements, open an issue that describes your idea so we can discuss the design before you start on a large change.
 
 ## Submit a pull request
 
-Though not mandatory, we encourage you to first check for a bug report among Jira issues and in the PR list: perhaps the bug has already been addressed.
-
-For feature requests and enhancements, we do ask you to create a Jira issue, describe your idea and discuss the design with us. This way we align your ideas with our vision for the product development.
+Before writing code, check the [open issues](https://github.com/commandprompt/open_pg_tde/issues) and [open pull requests](https://github.com/commandprompt/open_pg_tde/pulls) in case the change is already in progress.
 
-If the bug hasn’t been reported / addressed, or we’ve agreed on the enhancement implementation with you, do the following:
+Then:
 
-1. [Fork](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo) this repository
+1. [Fork](https://docs.github.com/en/github/getting-started-with-github/fork-a-repo) this repository.
 
-2. Clone this repository on your machine
+2. Clone your fork.
 
-3. Create a separate branch for your changes. If you work on a Jira issue, please include the issue number in the branch name so it reads as `<JIRAISSUE>-my_branch`.
+3. Create a branch for your changes. If the change relates to an issue, include the issue number in the branch name, for example `123-encrypt-temp-files`.
 
-4. Make your changes. Follow the guidelines outlined in the [PostgreSQL Coding Standard](https://www.postgresql.org/docs/current/source.html) to improve code readability.
+4. Make your changes. Follow the [PostgreSQL coding standards](https://www.postgresql.org/docs/current/source.html) for C code.
 
-5. Test your changes locally. See the [Running tests](#running-tests) section for more information.
+5. Test your changes locally. See [Run tests](#run-tests).
 
-6. To update the documentation describing your changes, see [Documentation contribution](#documentation-contribution).
+6. If your change needs documentation, see [Documentation contribution](#documentation-contribution).
 
-7. Commit the changes. Add the Jira issue number at the beginning of your message subject, so that is reads as `<JIRAISSUE> : My commit message`.  Follow this pattern for your commits:
+7. Commit your changes with a clear message. If the change relates to an issue, reference it in the body, for example `Fixes #123`. Follow this pattern:
 
     ```
-    PG-1234:  Main commit message.
-    <Blank line>
-    Details of fix.
+    Short summary of the change
+
+    Details of the change and why it is needed.
     ```
 
     See the [commit message guidelines](https://gist.github.com/robertpainsi/b632364184e70900af4ab688decf6f53) for more information.
 
-8. Open a pull request to Percona
-9. Our team will review your code and if everything is correct, will merge it. Otherwise, we will contact you for additional information or with the request to make changes.
+8. Open a pull request against [`commandprompt/open_pg_tde`](https://github.com/commandprompt/open_pg_tde).
+
+9. A maintainer will review your code. If everything is correct, we merge it. Otherwise, we will follow up with questions or requests for changes.
 
 ### Build open_pg_tde
 
-To build `open_pg_tde` from source code, you require the following:
+`open_pg_tde` runs on upstream PostgreSQL 16 and later. You apply the `open_pg_tde` core patch to a PostgreSQL source tree, build it with the hooks enabled, and build the extension against that install.
+
+To build from source you need:
 
 * git
-* Meson
+* Meson and Ninja
 * gcc or clang
-* Percona Server for PostgreSQL 17 or later
+* OpenSSL development headers
 
-Refer to the [Building from source code](https://github.com/commandprompt/open_pg_tde?tab=readme-ov-file#building-from-sources-for-community-postgresql) section for guidelines.
+See the [install from source guide](documentation/docs/install-from-source.md) for the full steps, and [`patches/postgresql/README.md`](patches/postgresql/README.md) for the core patch series and per-version status.
 
 ### Run tests
 
-You can find the tests in the `sql` and `t` directories.
+The tests live in the `sql` and `t` directories.
 
-#### Run manually
-
-1. Change the directory to `open_pg_tde`
-
-2. Build and install `open_pg_tde` with the following commands:
+1. Build and install the extension against your patched PostgreSQL:
 
     ```sh
     meson setup -Dpg_config=/path/to/postgresql/bin/pg_config ./build
-    cd build
-    meson install
+    meson install -C ./build
     ```
 
-3. Start OpenKMIP
-
-4. Run the tests using the following command:
+2. Run the suite:
 
     ```sh
-    meson install && meson test --print-errorlogs
+    meson test -C ./build --print-errorlogs
     ```
 
-#### Run automatically
+    Some tests need a KMIP server or OpenBao; set `PG_TEST_REQUIRE_COSMIAN_KMS=1` or `PG_TEST_REQUIRE_OPENBAO=1` to require them. The frontend tools link against the server libraries, so set `LD_LIBRARY_PATH=/path/to/postgresql/lib` when running the suite.
 
-The tests are run automatically with GitHub actions once you create a pull request.
+Tests also run automatically through GitHub Actions when you open a pull request.
 
 ## Documentation contribution
 
-To contribute to the documentation, see the following [Documentation contribution guide](/documentation/documentation-contributing.md).
-
-## After your pull request is merged
-
-Once your pull request is merged, you are an official Percona Community Contributor. Welcome to the community!
+To contribute to the documentation, see the [documentation contributing guide](documentation/documentation-contributing.md).