docs: clarify pull request suggestions and contributor credit

.github/pull_request_template.md

@@ -0,0 +1,31 @@
+## Sharing fixes and features
+
+Thank you for helping improve this project! If you’ve fixed a bug
+or added something useful in your own fork, you’re very welcome
+to share it through a pull request. AI-assisted changes are
+welcome too. Seeing exactly what you changed and what worked
+for you can be a big help.
+
+I treat pull requests as suggestions and examples of possible
+solutions. Please keep in mind that I’m unlikely to formally
+review or merge them, even when they contain a valid fix or a
+great idea. I may use them as a reference while developing my
+own implementation.
+
+If your contribution helps shape a change I make, I’ll credit
+you and link to your PR in the resulting commit or release
+notes. Your help deserves recognition whether or not your
+code is merged.
+
+Please include a little context about the problem, what you
+changed, and any testing you’ve done.
+
+I appreciate you taking the time to share your work—thank you!
+
+---
+
+## Problem or feature
+
+## Suggested change
+
+## Testing

CONTRIBUTING.md

@@ -0,0 +1,23 @@
+# Sharing fixes and features
+
+Thank you for helping improve this project! If you’ve fixed a bug
+or added something useful in your own fork, you’re very welcome
+to share it through a pull request. AI-assisted changes are
+welcome too. Seeing exactly what you changed and what worked
+for you can be a big help.
+
+I treat pull requests as suggestions and examples of possible
+solutions. Please keep in mind that I’m unlikely to formally
+review or merge them, even when they contain a valid fix or a
+great idea. I may use them as a reference while developing my
+own implementation.
+
+If your contribution helps shape a change I make, I’ll credit
+you and link to your PR in the resulting commit or release
+notes. Your help deserves recognition whether or not your
+code is merged.
+
+Please include a little context about the problem, what you
+changed, and any testing you’ve done.
+
+I appreciate you taking the time to share your work—thank you!

README.md

@@ -106,6 +106,13 @@ apps are native C / Objective-C with an HTML/JS UI (WebView2 on Windows, WKWebVi
 
 [Windows] You can check if the GPU-PV driver setup is working by running gpu-test.exe inside your App Sandbox Windows VM, gpu-test.exe will show a box with 6 rotating cubes, each using a different rendering engine (D3D9, D3D10, D3D11, D3D12, OpenGL and Vulkan).  If one or more fail, they will not correctly show a rotating cube for that rendering API.  [gpu-test.zip](https://github.com/jamesstringer90/appsandbox/releases/download/v0.1.2/gpu-test.zip). Note: The rendering API succeeding means that the GPU-PV worked, but sometimes games or apps are coded in such a way that they will not detect the GPU-PV system correctly and still show an error.
 
+## Sharing fixes and features
+
+Thank you for sharing fixes and ideas! Pull requests, including AI-assisted changes
+from your own fork, are welcome as suggestions. They are unlikely to be formally
+reviewed or merged, but contributions that help shape a change will be credited.
+See the [contribution guidelines](CONTRIBUTING.md) for details.
+
 ## License
 
 AppSandbox is licensed under the [MIT License](LICENSE) — Copyright (c) 2026 James Stringer.