add LLM policy

.github/pull_request_template.md

@@ -1,3 +1,5 @@
 Thank you for taking the time to improve this project. Please take a look at the [How to make a Pull Request](https://github.com/tubearchivist/tubearchivist/blob/master/CONTRIBUTING.md#how-to-make-a-pull-request) section to help get your contribution merged.
 
+Last updated: 2026-02-06
+
 You can delete this text before submitting.

CONTRIBUTING.md

@@ -71,9 +71,12 @@ Focus for the foreseeable future is on improving and building on existing functi
 
 This is a quick checklist to help streamline the process:
 
-- NEW: Make your PR against the [develop branch](https://github.com/tubearchivist/tubearchivist/tree/develop). That's where all active development happens. This simplifies the later merging into *master*, minimizes any conflicts and usually allows for easy and convenient *fast-forward* merging.
+- Make your PR against the [develop branch](https://github.com/tubearchivist/tubearchivist/tree/develop). That's where all active development happens. This simplifies the later merging into *master*, minimizes any conflicts and usually allows for easy and convenient *fast-forward* merging.
 - Show off your progress, even if not yet complete, by creating a [draft](https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/proposing-changes-to-your-work-with-pull-requests/about-pull-requests#draft-pull-requests) PR first and switch it as *ready* when you are ready.
 - Make sure all your code is linted and formatted correctly, see below.
+- Using a LLM or any tools based on LLM output is a mixed bag:
+  - If your PR introduces code generated by a LLM but it's not noticeable because the quality is indistinguishable from an experienced dev, then that is fine.
+  - If your PR is obviously just vibe coded, the PR will likely get rejected without a proper review. Limited maintainer time is better used elsewhere.
 
 ### Documentation Changes