Repository navigation

docs: categorize rejected xerial tests in the manifest #195

	name: PR Verification

	on:
	pull_request:
	types: [opened, synchronize, reopened]

	permissions:
	contents: read

	jobs:
	verify:
	name: Build & Test (Java ${{ matrix.java-version }})
	runs-on: ubuntu-latest
	strategy:
	fail-fast: false
	matrix:
	java-version: ['25', '26']
	steps:
	- name: Checkout code
	uses: actions/checkout@v7

	- name: Set up Amazon Corretto ${{ matrix.java-version }}
	uses: actions/setup-java@v6
	with:
	distribution: 'corretto'
	java-version: ${{ matrix.java-version }}
	cache: 'maven'

	- name: Verify vendored upstream integrity
	run: ./tools/export-upstream --verify

	- name: Self-check vendoring enforcement
	run: ./tools/export-upstream --self-test

	- name: Check Code Formatting (Spotless)
	run: mvn --batch-mode spotless:check

	- name: Validate reactor
	run: mvn --batch-mode validate

	- name: Run Tests and Verifications
	run: mvn --batch-mode clean verify

	xerial-control:
	# Reference probe, not a parity gate: the same vendored tests run against the pinned
	# xerial driver. A failure means the vendored test is not a valid reference or the
	# driver diverges without a recorded reason, not that libSQL must match xerial.
	name: Xerial Control (reference probe)
	runs-on: ubuntu-latest
	steps:
	- name: Checkout code
	uses: actions/checkout@v7

	- name: Set up Amazon Corretto 25
	uses: actions/setup-java@v5
	with:
	distribution: 'corretto'
	java-version: '25'
	cache: 'maven'

	- name: Run the xerial control profile
	run: mvn --batch-mode -pl libsql-conformance -am -Pxerial-control verify