LLM contribution policy

Given the rise of LLMs and that a standard library is a fundamental building block of the entire ecosystem, it may be appropriate to establish a policy.

Questions:

* does https://gitlab.haskell.org/ghc/ghc/-/wikis/contributing/AI already cover the *code* of base?
* what about LLM generated proposals?
* what about core libraries
* although I'd expect CLC to not interfere with maintainers decisions, I could see that a core library turning to vibecoding may be hard to hand over to a new contributor, which may subvert CLCs ability to ensure a well-maintained state

Start by reviewing the linked GHC contributing/AI policy and the questions in this issue about base code, LLM-generated proposals, and core libraries. Done would require an agreed contribution policy that clearly addresses those cases; no repository files or tests are identified.

Written by the indexing model from the issue text.