Current proof
Abizor ran the public wheel quickstart on an external target repository.
This proof shows the self-serve path working outside the Abizor source
repository. A separate target repo opened a small PR, installed
Abizor from the public wheel, ran the CI proof, published a live
GitHub Check projection, uploaded artifacts, and passed
abizor verify-proof locally.
What was verified
Existing PR, GitHub Actions, live Check, and verified bundle.
The target repository was Abizor/abizor-external-target-proof, not the Abizor source repository.
GitHub Actions installed Abizor from https://abizor.dev/downloads/abizor-0.1.0-py3-none-any.whl.
The workflow ran abizor ci-proof, reached the merge boundary, published the Abizor GitHub Check, and uploaded proof artifacts.
A clean local virtual environment installed the public wheel and verified the downloaded bundle with abizor verify-proof.
Canonical truth
The event log remains the proof record.
Canonical truth remains the Abizor event log.
The Change Record, GitHub Check, summary, PR comment body, manifest, publish receipt, proof report, and this public page are projections or evidence over that event log.
Evidence
Proof identifiers and artifact hashes.
Abizor/abizor-external-target-proof#127260288557805041352051da841787f1cabdd24a043deb78910e98f1d2de62150027f203aa3fb6bcbc5ba5cce2ca079805f1bc3d5608800ee8155aba0f7351e61ab34927ac6cdd94d9d5228c77cb3ef312a4eea57ebde9c253cc0bc848d6428197520b92b0679c6d7e988f9c385a82efe09780be6c2cf4ff70c38dfecb22b95eda609c488c1df3d815ef7fe51cfb36dc3c949727a2fe60c41fc51c6353059Output
The downloaded proof bundle verified locally.
verified: event log, manifest, and Change Record artifacts match
Boundary
What this proof does not claim.
This proof did not create, merge, or deploy the pull request.
It did not use PyPI, a hosted app, hosted API, dashboard, billing flow, or GitHub App.
It does not claim hosted customer access, compliance, security-audit, regulated-enterprise, or production-deployment coverage.