CI for facts that live on the web

When vendor docs change, get the tested code update.

Reality CI reads the exact source page on demand, daily, or weekly and compares its typed value with your repository. A real change becomes a native GitHub Check and cited pull request; a page redesign repairs itself and stays quiet.

No GitHub Actions workflow to add or maintain.

Layout-only changes self-heal and stay quiet.

Nothing is ever auto-merged.

Install the GitHub App only on repositories you choose. Merge the one-time setup PR; verification begins after that merge.

No commit required Run now · daily · weekly
GitHub documentation

Newest REST API version

2026-03-10

docs.github.com/rest/api-versions

Reality CI · Selected repositorymain

Scheduled verification

Source compared with code

Daily

Source captured

GitHub docs · Bright Data snapshot saved

Verified

Repository lock

github-api-version · 2022-11-28

Verified

Meaning changed

2022-11-28 → 2026-03-10

PR ready
GitHub Check Review

Update GitHub API version

cited PR · tests pass · human merge

Bright Datareads the source
Trigger.devruns the job
OpenCodeOpenCodeupdates code
GitHubgets the result

When it runs

It runs on your schedule, not only when somebody commits.

Reality CI is a GitHub App backed by durable scheduled jobs. It posts results through the native Checks API; it does not inject a workflow into your repository.

GitHub App

Repository access

Only selected repositories

Product repository
Internal SDK
Documentation

Choose the repository

Install the GitHub App only where Reality CI should work.

Source

Latest API version

2026-03-10

Code

apps/pipeline/src/github.ts

API_VERSION = 2022-11-28

Describe one source fact

Paste the authoritative page and describe the exact value your code assumes. Bright Data builds its dedicated extractor.

Verification scheduleDaily · 06:00 UTC

Source captured

Bright Data · cited snapshot

Lock compared

3 facts · 1 semantic change

Pull request ready

Tests pass · human merge required

Review and activate

Confirm the typed baseline, then merge the one-time setup pull request. Manual or scheduled checks begin after merge.

What gets added to your repo

One small lock file connects
a source page to the code that depends on it.

docs.github.com/rest/api-versionsAuthoritative source

Newest supported GitHub REST API version

2026-03-10

from the supported versions table

Captured with cited evidence
reality.lock.jsoncommitted
{
  "github-api-version": {
    "source": "docs.github.com/rest/api-versions",
    "field": "latest_api_version",
    "baseline": "2026-03-10",
    "anchor": "packages/core/src/github-api-version.ts",
    "cadence": "daily"
  }
}

Two kinds of change

Layout noise is repaired.
Meaningful change reaches you.

Self-healed

The page moved.
The fact did not.

A redesigned page breaks extraction. Reality CI sends the failing URL and original intent to Bright Data, heals the same stable Scraper Studio collector, and reruns it.

Selector stopped matchingLayout drift
Collector repaired and rerunSame ID
2026-03-10 still matches Check green
Semantic drift

The fact changed.
Your code may need to.

GitHub publishes a newer supported API version. OpenCode searches an isolated checkout, makes the smallest repository update, runs its checks, and Reality CI opens a pull request with the exact documentation snapshot attached.

github-api-version.ts1 file changed
- API_VERSION = '2022-11-28';
+ API_VERSION = '2026-03-10';
Human review required

One calm workspace

See what is trusted, running, or waiting for review.

Repositories hold fact contracts. Facts hold source evidence. Activity preserves the complete run history when you reconnect.

Open your workspace
Selected repository
main
GitHub REST API2026-03-10Verified
Next.js Node requirement>= 20.9Checking
Verification interval15 minutesVerified
Vendor API version2022 → 2026Review ready

No silent dependency drift

When a vendor changes its contract, have the code update ready before production finds out.