PUBLIC GITHUB TEST

See one GitHub status action from start to finish.

This test used alienctl 0.2.0 at commit f6034bc61fa485518f4329357be6ad9e335e5938. GitHub created exactly two approved statuses on one test commit. The saved proof also shows two failures in the test tool.

Proof IDlive-github-v0.2.0-7d4c2ffd4b8a

Test time2026-08-04T09:11:45Z

Providerpublic GitHub test repository

File checkpassed; test-tool limits are shown

The exact action

Connectoralienctl.github.check-status

Actiongithub.check_status.apply

RepositoryOpen the test repository

Commit7d4c2ffd4b8a66c8d62be6e092b7640aed3950e2

Status namealienctl/proof/success-v0.2.0-run2

Resultsuccess

Public GitHub test commit showing two of two status checks passing — This public screenshot shows two passing checks on the test commit. The manifest stores the exact status names and GitHub IDs.

Five test cases

succeeded

GitHub accepted the status.

alienctl sent one approved status. GitHub accepted it. alienctl saved the result.

denied

alienctl denied the request.

The request named the wrong repository. alienctl denied it before it contacted GitHub.

cancelled

alienctl cancelled before sending.

alienctl saved the cancellation before the action started. GitHub received no status.

failed

GitHub rejected the status.

The request used a commit that does not exist. GitHub rejected it. alienctl saved the failure.

reconciled

alienctl checked an unclear result.

GitHub accepted the status, but the reply did not reach alienctl. alienctl used one read-only GET to find the status. It sent no second POST.

dispatching → outcome_unknown → one provider GET → reconciled
provider POST count during the check: 0
final GitHub status count: 2 / approved limit: 2

Download and check the proof

Manifest Test record File hashes

python3 scripts/validate_proof.py
cargo test -p alien-server execution_ --lib -- --test-threads=1

Read the test record and the test limits. Do not run the same live action again. A new live test needs a new approved test commit. It also needs a new credential that can access only the test repository.

Limits

The first test process ended with an error after all five checks reached the expected unclear-result state. GitHub and SQLite show the saved results.
The recovery process found the status. It then ended with an error because the test expected succeeded instead of the saved state reconciled.
The test used test-only authority and fault injection. It does not prove customer setup.
This proof does not show correctness, safety, compliance, return on investment, production readiness, or a guarantee of one external effect.