Add information on how to contribute

- Added CONTRIBUTING.md
- Added reference to CONTRIBUTING.md in readme.md
- Added PR template

Author: utelle

.github/PULL_REQUEST_TEMPLATE.md

@@ -0,0 +1,51 @@
+## Description
+
+Please describe what this PR changes and why.
+
+## Problem Statement
+
+What concrete issue does this PR address?
+
+- [ ] Reproducible test case included
+- [ ] Compiler / sanitizer evidence provided
+- [ ] Verified incorrect behavior shown in code
+- [ ] Reference to external technical source (if applicable)
+
+If none apply, the PR may be closed without review.
+
+## Verification
+
+How was the issue verified?
+
+- [ ] Locally reproducible
+- [ ] Unit test added/updated
+- [ ] Static analysis / sanitizer output
+- [ ] Other (please specify)
+
+## Type of Change
+
+Please select the type of change:
+
+- [ ] Bug Fix (requires verifiable evidence)
+- [ ] Feature / Enhancement (new functionality)
+- [ ] Refactor (no behavior change)
+- [ ] Documentation
+- [ ] Other (please describe)
+
+## Problem / Motivation
+
+For Bug Fixes:
+- What is the observed issue?
+
+For Features:
+- What functionality is being added and why?
+
+For Refactors:
+- What is being improved internally and why?
+
+## Checklist
+
+- [ ] I have independently verified the issue
+- [ ] I am not submitting unverified or speculative changes
+- [ ] I understand that AI-assisted changes must be reviewed by a human before submission
+

.github/workflows/build.yml

@@ -15,21 +15,22 @@ on:
 
 env:
   AMALGAMATION: amalgamation
-  SQLITE_PATH: sqlite3
-  LIBICU_PATH: icu_precompiled
+  ARCHIVES:     archives
+  SQLITE_PATH:  sqlite3
+  LIBICU_PATH:  icu_precompiled
 
 jobs:
 
   build-windows:
     runs-on: windows-2022
     env:
       MODE: ${{ github.event.inputs.mode }}
-    strategy:
-      fail-fast: false
-      matrix:
-        platform:
-          - win32
-          - win64
+#    strategy:
+#      fail-fast: false
+#      matrix:
+#        platform:
+#          - win32
+#          - win64
 
     steps:
 
@@ -138,6 +139,16 @@ jobs:
           python ../scripts/amalgamate.py -v yes -c ../scripts/shell3mc.c.json  -s ../src
           dir
 
+      - name: Create ZIP
+        shell: pwsh
+        run: |
+          Compress-Archive -Path "build/package/*" -DestinationPath "build/artifact.zip"
+
+- name: Upload artifact
+  uses: actions/upload-artifact@v4
+  with:
+    name: build-artifact
+    path: build/artifact.zip
   build-linux:
     runs-on: ubuntu-24.04
     env:

CONTRIBUTING.md

@@ -0,0 +1,91 @@
+# Contributing Guidelines
+
+We welcome contributions. To ensure efficient and meaningful review, the following minimum requirements apply.
+
+---
+
+## 1. Change Type & Verifiable Statement
+
+Every pull request must clearly declare its type and provide appropriate justification.
+
+### Supported PR Types
+
+- **Bug Fix**
+  A PR that fixes a reproducible and verifiable issue.
+
+- **Feature / Enhancement**
+  A PR that introduces new functionality or improves existing behavior without fixing a bug.
+
+- **Refactor**
+  A PR that changes internal implementation without changing external behavior.
+
+- **Documentation**
+  A PR that only affects documentation.
+
+- **Other**
+  For changes that do not fit the categories above (must be explained clearly).
+
+---
+
+### 1a. Requirements for Bug Fixes
+
+Bug-fix PRs must include **verifiable evidence of the issue**, such as:
+
+- a reproducible test case
+- compiler or sanitizer output (e.g. ASan, UBSan)
+- clearly demonstrable incorrect behavior in the existing code
+- or a reliable technical reference
+
+Speculative statements (e.g. “might be unsafe”, “could be NULL”) are not sufficient without proof.
+
+---
+
+### 1b. Requirements for Features
+
+Feature PRs must include a clear description of:
+
+- what new functionality is introduced
+- why the change is useful
+- how the behavior changes for users or callers
+
+If applicable, feature PRs should also include tests or usage examples.
+
+---
+
+### 1c. Requirements for Refactoring
+
+Refactoring PRs must ensure:
+
+- no change in external behavior unless explicitly stated
+- justification for structural changes (readability, performance, maintainability, etc.)
+- tests remain valid or are updated accordingly
+
+---
+
+## 2. Human Review Required
+
+Automatically generated or assisted changes (including AI-assisted contributions) must be **reviewed and validated by a real person before submission**.
+
+The contributor is responsible for ensuring that:
+
+- the proposed change is technically correct
+- the issue description has been independently verified
+- the change is not based on speculation or unverified assumptions
+
+---
+
+## 3. No Substantive Value → No Merge
+
+Pull requests that:
+
+- only contain cosmetic or non-functional changes
+- address issues that are not demonstrably valid
+- or do not provide a verifiable improvement
+
+may be closed without further discussion.
+
+---
+
+## 4. Review Policy
+
+PRs that do not meet the above requirements may be **closed without entering a full review cycle**, in order to protect maintainers’ time and keep the project maintainable.

readme.md

@@ -17,10 +17,14 @@ The code was mainly developed under Windows, but was tested under Linux as well.
 
 For further version information please consult the [CHANGELOG](CHANGELOG.md).
 
-## How to participate
+## How to participate and/or contribute
 
 **Help in testing and discussing further development will be _highly_ appreciated**. Please use the [issue tracker](https://github.com/utelle/SQLite3MultipleCiphers/issues) to give feedback, report problems, or to discuss ideas.
 
+Before opening a pull request, please read our [Contributing Guidelines](CONTRIBUTING.md).
+
+PRs that do not include a verifiable problem statement or human-validated changes may be closed without review.
+
 ## Documentation
 
 Documentation of the currently supported cipher schemes and the C and SQL interfaces is provided on the [SQLite3 Multiple Ciphers website](https://utelle.github.io/SQLite3MultipleCiphers/).