coloradostartups.org

1 repoAPI data 2026-11-16 21:08 UTCsite data 2026-11-16 21:08 UTCbuilt 2026-11-16 21:08 UTC

Ideal state

A process is a map of at most six steps where quality, speed and consumption are decided, each scored by one Quality metric.

2 sources, newest 2026-11-04
  1. Claude Code: best practices 2026-11-04
  2. DORA's software delivery performance metrics 2026-01-05

Delivery

A change, from the approved plan to merged on the default branch

Ideal state

Small changes, planned first, green on first push, reviewed at the head and merged within a day, judged by lead time and failure, not volume.

4 sources, newest 2026-11-04
  1. Claude Code: best practices 2026-11-04
  2. Google engineering practices: speed of code reviews 2026-11-04
  3. Trunk Based Development: short-lived feature branches 2026-11-04
  4. DORA's software delivery performance metrics 2026-01-05
1

Plan

critical path

Quality

0%

PRs linking an issue

goal ≥ 100%

No per-repo data for this step.

Plan in an issue before code, and split the work into changes that each land on their own.

https://code.claude.com/docs/en/best-practices
  • GitHub Issues
  • Linked pull requests
2

Build

critical path

Quality

80%

Share over 400 lines

goal ≤ 10%

No per-repo data for this step.

Build in small changes, each pull request short enough to review in one sitting.

https://code.claude.com/docs/en/best-practices
  • coloradostartups.org pre-commit: runs content, contract, worktree_deps.py, cs_site_lint.py and 1 more through cs-site-route.sh
  • coloradostartups.org pre-push: refuses a push to main; runs content, contract, worktree_deps.py, cs_site_lint.py and 1 more through cs-site-route.sh; runs no tests
  • Short-lived branches
  • Git hooks
3

Check

critical path

Consumption

0.09 dollars

Runner dollars at list price, the latest merged PR

goal ≤ 0.36 dollars

No per-repo data for this step.

CI on the latest pull request costs no dollars: it runs within the included Actions minutes.

https://dora.dev/guides/dora-metrics/
  • GitHub Actions standard runners, ubuntu-slim for light jobs
  • Included Actions usage, a budget that stops at it
  • Free lanes: public repos, third-party free minutes
  • Pinned actions

Board

A feature, from a card on the project board to Done with its merged pull request

Ideal state

One fresh session takes one visual card to one merged pull request; open pull requests carry the limit, and nothing sits in progress unbuilt.

5 sources, newest 2026-11-10
  1. GitHub Docs: Best practices for Projects 2026-11-10
  2. Claude Code Docs: Manage costs effectively 2026-11-10
  3. Anthropic: How we built our multi-agent research system 2026-11-10
  4. DORA: Work in process limits 2026-11-10
  5. DORA: Working in small batches 2025-12-08
1

Card

critical path

Quality

0%

Cards read at a glance

goal ≥ 100%

No per-repo data for this step.

A feature is one card: a picture of its metric and steps, a table, and a pass-or-fail check.

https://code.claude.com/docs/en/best-practices
  • A draft card on the project board
  • quality/cards/picture.mjs
3

Start

critical path

Quality

0 cards

In progress, no open PR

goal ≤ 0 cards

No per-repo data for this step.

A fresh session takes one card; the card is in progress only while its pull request is open.

https://code.claude.com/docs/en/costs
  • One app session per card, in its own worktree
  • Workflow: Pull request linked to issue
4

Finish

critical path

Speed

4 PRs

Open PRs now

goal ≤ 10 PRs

No per-repo data for this step.

Finish before starting: merge a green pull request before opening another.

https://dora.dev/capabilities/wip-limits/
  • The app's PR monitor with Auto-fix
  • gh pr merge --match-head-commit

Code

A repo's code, from measured to simplified, deleted, explained, checked and held small

Ideal state

Code stays small and plain: the worst function is split first, unused lines are deleted, shared functions say what they do.

6 sources, newest 2026-11-10
  1. Microsoft Learn: Code metrics, cyclomatic complexity 2026-10-20
  2. GitHub Docs: Code Quality metrics and scores reference 2026-11-10
  3. Claude Code Docs: Tools reference 2026-11-10
  4. Anthropic: Effective context engineering for AI agents 2025-09-29
  5. PEP 257: Docstring Conventions 2024-04-17
  6. Claude Code Docs: Best practices for Claude Code 2026-11-10
4

Explain

Quality

90%

Shared functions with a header comment

goal ≥ 90%

No per-repo data for this step.

Every shared function says what it does where it starts.

https://peps.python.org/pep-0257/
  • A header comment or docstring

Triage

A finding, from intake to the issue or card that a merged pull request closes

Ideal state

A finding becomes a typed issue closed within a day, or a card on the board; each closes through its merged pull request.

5 sources, newest 2026-11-10
  1. GitHub Actions billing 2026-11-04
  2. GitHub Docs: About issues 2026-11-10
  3. GitHub Docs: Linking a pull request to an issue 2026-11-10
  4. GitHub Docs: Best practices for Projects 2026-11-10
  5. GitHub Docs: Using the built-in automations 2026-11-10
4

Fix

critical path

Consumption

–

Runner minutes per issue, the latest fix

goal ≤ 60 minutes

#94, the latest merged pull request that closed an issue, opened 2026-11-16 07:35 UTC, before 2026-11-16 07:43 UTC, where the runs read stop covering every workflow

No per-repo data for this step.

A fix costs few runner minutes: one small pull request, checked once.

https://docs.github.com/en/billing/concepts/product-billing/github-actions
  • One small pull request
  • CI on that pull request

Secure

A repo's security, from keys no session reads to alerts closed within a week

Ideal state

No session reads a key, scans run in minutes, the threat model stays current, reports have a private path, and alerts close within a week.

4 sources, newest 2026-11-10
  1. Claude Code: configure permissions 2026-11-04
  2. GitHub Docs: GitHub security features 2026-11-10
  3. GitHub Docs: Quickstart for securing your repository 2026-11-10
  4. GitHub Docs: Adding a security policy to your repository 2026-11-03

Document

A doc, from written visual first to linted, mapped to its files, published, read and loaded

Ideal state

Every fact a reader needs is present, correct and current, in short, visual docs a person finishes in two minutes and Claude loads cheaply.

5 sources, newest 2026-11-10
  1. GitHub Docs: Creating diagrams 2026-11-10
  2. GitHub Docs: Style guide 2026-11-10
  3. GitHub Docs: About the repository README file 2026-11-10
  4. Microsoft Style Guide: Scannable content 2023-06-20
  5. Claude Code Docs: Best practices 2026-11-10
6

Load

Consumption

553 tokens

Tokens past the reading goal

goal ≤ 0 tokens

No per-repo data for this step.

Claude loads no tokens past a doc's reading goal.

https://code.claude.com/docs/en/best-practices
  • Agent docs: CLAUDE.md, skills and rules

Contribute

An outside contribution, from idea to production, with AI agents reviewing, merging and deploying it

Ideal state

An outside idea becomes a merged change within a day, no fork code runs with a secret, and no person waits in the loop.

4 sources, newest 2026-11-12
  1. GitHub Docs: About discussions 2026-11-12
  2. GitHub Docs: Approving workflow runs from forks 2026-11-12
  3. GitHub Docs: Events that trigger workflows 2026-11-12
  4. Cloudflare Docs: Rollbacks 2026-11-12

Adopt Git Crafter

A repo, from copying the starters to running Git Crafter's CI and pages and staying current

Ideal state

A repo copies two starters and three CI files, pins Git Crafter to a full SHA, requires its check, and takes each release within days.

4 sources, newest 2026-11-05
  1. GitHub Actions: reuse workflows 2026-11-05
  2. GitHub Actions: secure use reference 2026-11-05
  3. GitHub: about rulesets 2026-11-05
  4. GitHub: Dependabot version updates 2026-11-05
1

Copy

critical path

Quality

100%

Actions pinned to a SHA

goal ≥ 100%

No per-repo data for this step.

Copy the starters, CI and pages callers and Dependabot entry; pin Git Crafter to a full SHA with its version.

https://docs.github.com/en/actions/reference/security/secure-use
  • templates/quality/config.json
  • templates/process/config.json
  • templates/ci/ci.yml
  • templates/ci/pages.yml
  • templates/ci/dependabot.yml

Measure

A repo's numbers, from collected to scored, published, goaled and fixed

Ideal state

Metrics are read live in CI, scored against sourced goals, published on every push, and each miss becomes a labeled issue a pull request closes.

4 sources, newest 2026-11-05
  1. Google SRE book: service level objectives 2026-11-05
  2. DORA's software delivery performance metrics 2026-01-05
  3. GitHub Pages: custom workflows 2026-11-05
  4. GitHub: link a pull request to an issue 2026-11-05
1

Collect

critical path

Consumption

0.09 dollars

Runner dollars at list price, the latest merged PR

goal ≤ 0.36 dollars

No per-repo data for this step.

Metrics are read live in CI for cents a pull request; a failed read is not measured, never 0.

https://dora.dev/guides/dora-metrics/
  • actions/pages in CI
  • quality/collect.mjs --local for session data
2

Score

critical path

Quality

0 dates

Dated claims older than their area

goal ≤ 0 dates

No per-repo data for this step.

A metric meets, nears or misses a goal that names its source, and every figure carries a recent read date.

https://sre.google/sre-book/service-level-objectives/
  • quality/score.mjs
  • Each goal's goal_source
4

Goal

critical path

Quality

72.2%

Issues with an area label

goal ≥ 100%

No per-repo data for this step.

Each miss becomes a typed issue with an area label if one pull request fixes it, else a board card.

https://sre.google/sre-book/service-level-objectives/
  • The work queue
  • Area labels

Deploy

A merged change, from build to live, and back when it fails

Ideal state

Merges deploy in minutes from a CI build, rarely fail, roll back within the hour, read per service for lead time, failure and recovery.

2 sources, newest 2026-07-15
  1. Cloudflare Workers: rollbacks 2026-07-15
  2. DORA's software delivery performance metrics 2026-01-05
1

Build

critical path

Consumption

–

CI minutes behind the latest deploy

goal ≤ 20 min

needs a Wrangler login; refreshed by a --local collect

No per-repo data for this step.

Every merge builds and deploys on its own; nobody deploys by hand.

https://dora.dev/guides/dora-metrics/
  • The deploy platform's build on merge
2

Ship

critical path

Speed

–

Latest deploy's time from merge to live

goal ≤ 24 h

needs a Wrangler login; refreshed by a --local collect

No per-repo data for this step.

A merged change is live within hours, not batched for later.

https://dora.dev/guides/dora-metrics/
  • Versioned deploys
3

Verify

critical path

Quality

–

Failed deploys, last 10

goal ≤ 5%

needs a Wrangler login; refreshed by a --local collect

No per-repo data for this step.

A deploy that fails its checks counts as a failed change.

https://dora.dev/guides/dora-metrics/
  • Deploy checks
  • The live page's text, read in the app's browser
  • Error tracking

Guard

An agent's tool call, through the repo's guards, to run or blocked

Ideal state

Guards block one-way doors and machine policy, each block names its fix, false alarms become tests, and a guard change adds one regression case.

2 sources, newest 2026-11-04
  1. Claude Code: configure permissions 2026-11-04
  2. Claude Code: hooks reference 2026-11-04
1

Call

critical path

Quality

–

Guard blocks per 100 tool calls

goal ≤ 0.05 blocks

transcripts and the guard log live on the machine that ran the sessions; refreshed by a --local collect there

No per-repo data for this step.

Deny rules and hooks block only one-way-door commands; most calls pass untouched.

https://code.claude.com/docs/en/permissions
  • coloradostartups.org pre-commit: runs content, contract, worktree_deps.py, cs_site_lint.py and 1 more through cs-site-route.sh
  • coloradostartups.org pre-push: refuses a push to main; runs content, contract, worktree_deps.py, cs_site_lint.py and 1 more through cs-site-route.sh; runs no tests
  • Claude Code permissions
  • PreToolUse hooks
2

Block

critical path

Speed

–

Seconds the latest block cost

goal ≤ 40 s

transcripts and the guard log live on the machine that ran the sessions; refreshed by a --local collect there

No per-repo data for this step.

A block names its fix, so the session moves on in seconds.

https://code.claude.com/docs/en/hooks
  • The guard's own fix line
3

Message

critical path

Consumption

–

Tokens the latest block cost

goal ≤ 250K tokens

transcripts and the guard log live on the machine that ran the sessions; refreshed by a --local collect there

No per-repo data for this step.

A block's message is short: the rule and the fix, nothing more.

https://code.claude.com/docs/en/hooks
  • Short hook output
4

False alarm

Quality

–

Guard blocks that were false alarms

goal ≤ 5%

transcripts and the guard log live on the machine that ran the sessions; refreshed by a --local collect there

No per-repo data for this step.

A block on a safe command is a false alarm, and it becomes a guard test.

https://code.claude.com/docs/en/hooks
  • A guard test per false alarm
5

Change

Quality

0 PRs

Enforcement PRs reverted or bugged

goal ≤ 0 PRs

No per-repo data for this step.

A guard fix lands with one regression case under the normal review, and a new rule needs a real incident.

https://code.claude.com/docs/en/hooks
  • One regression case
  • The normal review

Decide

A question or blocker, from where it arises to Claude's call or the owner's queue, then cleared for good

Ideal state

Claude makes every call its delegation allows and moves on; only questions and human steps reach the owner, and a false block is fixed once.

3 sources, newest 2026-11-10
  1. Claude Code: configure permissions 2026-11-04
  2. Claude Code: hooks reference 2026-11-04
  3. Claude Code Docs: Best practices 2026-11-10
1

Arise

critical path

Quality

–

Blockers that cost more than they help

goal ≤ 0 blockers

transcripts and the guard log live on the machine that ran the sessions; refreshed by a --local collect there

No per-repo data for this step.

A question or blocker surfaces once with its fix named; none costs more than it helps.

https://code.claude.com/docs/en/hooks
  • The bash guard's fix line
  • rules/delegation.md
2

Claude decides

critical path

Consumption

–

Tokens the latest block cost

goal ≤ 250K tokens

transcripts and the guard log live on the machine that ran the sessions; refreshed by a --local collect there

No per-repo data for this step.

Within its delegation Claude decides, records reason and reversal in the PR, and moves on.

https://code.claude.com/docs/en/best-practices
  • Decide without asking
  • The PR description
3

Owner's queue

Speed

–

Permission prompts per 100 tool calls

goal ≤ 0 prompts

transcripts live on the machine that ran the sessions; refreshed by a --local collect there

No per-repo data for this step.

Only questions and human steps reach the owner; any other prompt is a defect to remove.

https://code.claude.com/docs/en/permissions
  • The owner's queue
  • One question listing every item
4

Clear

critical path

Quality

–

Guard blocks that were false alarms

goal ≤ 5%

transcripts and the guard log live on the machine that ran the sessions; refreshed by a --local collect there

No per-repo data for this step.

Few blocks are false alarms; each one on a safe command becomes a guard fix by PR.

https://code.claude.com/docs/en/hooks
  • A guard fix by PR
  • One regression case

Ideal state

Every repo runs one CI standard on hosted runners, pinned to a SHA, and skips unchanged work so included minutes last the month.

2 sources, newest 2026-11-04
  1. GitHub Actions: reuse workflows 2026-11-04
  2. GitHub: about billing for GitHub Actions 2026-11-04

The CI standard

Runner dollars at list price, the latest merged PR

0.09 dollars

content-gates0 dollars
e2e0 dollars
pages0.06 dollars
scorecard0.01 dollars
secret-scan0 dollars
site-tests0.01 dollars

templates/ci/README.md

coloradostartups.org13 workflows

The slowest step of each stage95% or more pass85 to 94%Under 85%Not measuredRuns on the laptopA personBlue bar: median minutes

  1. Commit

    • pre-commit
      Median
      Not timed
      Pass rate
      not measured
      What runs
      runs content, contract, worktree_deps.py, cs_site_lint.py and 1 more through cs-site-route.sh
      Defined in
      .githooks/pre-commit
      Kind
      A hook on the laptop; nothing records its time
      Path
      The slowest step in its stage, on the rail
  2. Push

    • pre-push
      Median
      Not timed
      Pass rate
      not measured
      What runs
      refuses a push to main; runs content, contract, worktree_deps.py, cs_site_lint.py and 1 more through cs-site-route.sh; runs no tests
      Defined in
      .githooks/pre-push
      Kind
      A hook on the laptop; nothing records its time
      Path
      The slowest step in its stage, on the rail
  3. Pull request checks3.3 min

    • pages
      Median
      3.3 minutes
      Pass rate
      95% of runs passed; cancelled runs are left out
      What runs
      On every pull request that changes its inputs: build on ubuntu-latest
      Defined in
      .github/workflows/pages.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
      Path
      The slowest step in its stage, on the rail
    • ai-visibility
      Median
      0.6 minutes
      Pass rate
      100% of runs passed; cancelled runs are left out
      What runs
      On every pull request that changes its inputs: ai-visibility on ubuntu-slim
      Defined in
      .github/workflows/ai-visibility.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
    • cloud-test
      Median
      0.9 minutes
      Pass rate
      57.1% of runs passed; cancelled runs are left out
      What runs
      On every pull request that changes its inputs: cloud-test calls shared cloud-test.yml in 2 shards
      Defined in
      .github/workflows/cloud-test.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
    • content-gates
      Median
      0.8 minutes
      Pass rate
      100% of runs passed; cancelled runs are left out
      What runs
      On every pull request that changes its inputs: content-gates on ubuntu-slim
      Defined in
      .github/workflows/content-gates.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
    • dependency-age
      Median
      0.8 minutes
      Pass rate
      0% of runs passed; cancelled runs are left out
      What runs
      On every pull request that changes its inputs: dependency-age on ubuntu-slim
      Defined in
      .github/workflows/dependency-age.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
    • e2e
      Median
      0.3 minutes
      Pass rate
      95% of runs passed; cancelled runs are left out
      What runs
      On every pull request: e2e: changes on ubuntu-slim, then e2e: shard 1/2 and e2e: shard 2/2 in parallel on a runner chosen at run time, then e2e on ubuntu-slim
      Defined in
      .github/workflows/e2e.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
    • export-dry-run
      Median
      0.3 minutes
      Pass rate
      95% of runs passed; cancelled runs are left out
      What runs
      On every pull request that changes its inputs: export-dry-run on ubuntu-slim
      Defined in
      .github/workflows/export-dry-run.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
    • secret-scan
      Median
      0.3 minutes
      Pass rate
      100% of runs passed; cancelled runs are left out
      What runs
      On every pull request: secret-scan on ubuntu-slim
      Defined in
      .github/workflows/secret-scan.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
    • site-tests
      Median
      0.6 minutes
      Pass rate
      80% of runs passed; cancelled runs are left out
      What runs
      On every pull request: site-tests: changes on ubuntu-slim, then site-tests: tests on a runner chosen at run time, then site-tests on ubuntu-slim
      Defined in
      .github/workflows/site-tests.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
    • visual-check
      Median
      0.8 minutes
      Pass rate
      100% of runs passed; cancelled runs are left out
      What runs
      On every pull request that changes its inputs: visual-check on ubuntu-latest
      Defined in
      .github/workflows/visual-check.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
  4. Review

    • Pinned review and merge
      Median
      Not timed
      Pass rate
      not measured
      What runs
      The orchestrator reviews the head SHA, pins a review to it, and merges with gh pr merge --match-head-commit and that literal SHA
      Defined in
      code-os rules/delegation.md
      Kind
      A step a person takes
      Path
      The slowest step in its stage, on the rail
  5. Merge to main3.6 min

    • pages
      Median
      3.6 minutes
      Pass rate
      100% of runs passed; cancelled runs are left out
      What runs
      On every push to main: build on ubuntu-latest, then deploy on ubuntu-latest
      Defined in
      .github/workflows/pages.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
      Path
      The slowest step in its stage, on the rail
    • content-gates
      Median
      0.5 minutes
      Pass rate
      100% of runs passed; cancelled runs are left out
      What runs
      On every push to main that changes its inputs: content-gates on ubuntu-slim
      Defined in
      .github/workflows/content-gates.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
    • mcp-registry
      Median
      0.2 minutes
      Pass rate
      0% of runs passed; cancelled runs are left out
      What runs
      On every push to main that changes its inputs: mcp-registry on ubuntu-latest
      Defined in
      .github/workflows/mcp-registry.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
    • scorecard
      Median
      0.6 minutes
      Pass rate
      100% of runs passed; cancelled runs are left out
      What runs
      On every push to main: analysis on ubuntu-latest
      Defined in
      .github/workflows/scorecard.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
    • secret-scan
      Median
      0.4 minutes
      Pass rate
      100% of runs passed; cancelled runs are left out
      What runs
      On every push to main: secret-scan on ubuntu-slim
      Defined in
      .github/workflows/secret-scan.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
    • site-tests
      Median
      0.3 minutes
      Pass rate
      100% of runs passed; cancelled runs are left out
      What runs
      On every push to main: site-tests: changes on ubuntu-slim, then site-tests: tests on a runner chosen at run time, then site-tests on ubuntu-slim
      Defined in
      .github/workflows/site-tests.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
Every step as a table
StageStepKindMedianPass rate
Commitpre-commit (rail)Hooknot timednot measured
Pushpre-push (rail)Hooknot timednot measured
Pull request checkspages (rail)Workflow3.3 min95%
Pull request checksai-visibilityWorkflow0.6 min100%
Pull request checkscloud-testWorkflow0.9 min57.1%
Pull request checkscontent-gatesWorkflow0.8 min100%
Pull request checksdependency-ageWorkflow0.8 min0%
Pull request checkse2eWorkflow0.3 min95%
Pull request checksexport-dry-runWorkflow0.3 min95%
Pull request checkssecret-scanWorkflow0.3 min100%
Pull request checkssite-testsWorkflow0.6 min80%
Pull request checksvisual-checkWorkflow0.8 min100%
ReviewPinned review and merge (rail)Personnot timednot measured
Merge to mainpages (rail)Workflow3.6 min100%
Merge to maincontent-gatesWorkflow0.5 min100%
Merge to mainmcp-registryWorkflow0.2 min0%
Merge to mainscorecardWorkflow0.6 min100%
Merge to mainsecret-scanWorkflow0.4 min100%
Merge to mainsite-testsWorkflow0.3 min100%

Apart from the pipeline

The slowest step of each stage95% or more pass85 to 94%Under 85%Not measuredRuns on the laptopA personBlue bar: median minutes

  1. Scheduled0.2 min

    • deploy-gate
      Median
      0.2 minutes
      Pass rate
      100% of runs passed; cancelled runs are left out
      What runs
      On a schedule: deploy-gate on ubuntu-slim
      Defined in
      .github/workflows/deploy-gate.yml
      Kind
      An automated workflow: a GitHub Actions workflow or a Cloudflare build
      Path
      The slowest step in its stage, on the rail
Every step as a table
StageStepKindMedianPass rate
Scheduleddeploy-gate (rail)Workflow0.2 min100%

gh api graphql: HEAD:.github/workflows, HEAD:.githooks and HEAD:.github/cloud-test.json; each workflow's latest run timed, its pass rate over its last 20 runs read 2026-11-16 21:08 UTC

Ideal state

Many fast unit tests, fewer broad ones, few end-to-end; every suite runs in CI on every PR, and main stays green.

1 source, newest 2018-02-26
  1. Martin Fowler: The Practical Test Pyramid 2018-02-26

No suite runs on a local machine. A session dispatches one to cloud-test.

coloradostartups.org11 suites

Test cases by suite: not measured: the site's data has no tests.cases

SuiteWhenChecksMedianPass
content-gatesevery pull request that changes its inputs; every push to main that changes its inputsRule self-test (every rule's hit and miss samples, every window edge); Contract test (rules, settings, hooks and the gate table agree); Lint changed files; Hook self-test (pre-commit and pre-push behave in a throwaway repo); 3 more0.8 min100%
dependency-ageevery pull request that changes its inputsSelf-test (known-bad and known-clean lockfiles, no network); Every added version is old enough; npm audit, production dependencies0.8 min0%
deploy-gatea scheduleDeploy gate self-test; Fast-forward production to the commit main's gates passed0.2 min100%
e2eevery pull request; skips its work when nothing it checks changedDetect site changes; Pick the shards' runner; Build the site and run this shard's Playwright and axe specs; Fail on a failed, cancelled or unexpectedly skipped job; 1 more0.3 min95%
e2e: changesevery pull requestDetect site changes; Pick the shards' runner––
e2e: shard 1/2, e2e: shard 2/2every pull requestBuild the site and run this shard's Playwright and axe specs––
export-dry-runevery pull request that changes its inputs; dispatchSelf-tests (export and scan, known-bad and known-clean samples); Build the public tree in the runner's temp folder; gitleaks over the exported tree; export_scan over the exported tree (emails, phones, profiles, keys, links, image metadata)0.3 min95%
mcp-registrydispatch; every push to main that changes its inputsValidate server.json; Log in with GitHub OIDC; Publish to the MCP Registry0.2 min0%
pagesevery push to main; every pull request that changes its inputs; a schedule; dispatchTest the repo's own quality collector; Leak scan the built pages3.3 min95%
buildevery push to main; every pull request; a schedule; dispatchTest the repo's own quality collector; Leak scan the built pages––
secret-scanevery pull request; every push to main; dispatchSelf-test (the scan's range, with a planted fake key); Scan the commits this run answers for; Allow-marker self-test (throwaway repos, no network); The allow marker appears only where the allowlist says0.3 min100%
site-testsevery pull request; every push to main; skips its work when nothing it checks changedChange detector self-test (known-bad and known-clean paths); Export manifest check (every path classified); Runner check self-test (known-bad and known-clean labels); Content gate self-test (rules, samples, the private overlay); 12 more0.6 min80%
site-tests: changesevery pull request; every push to mainChange detector self-test (known-bad and known-clean paths); Export manifest check (every path classified); Runner check self-test (known-bad and known-clean labels); Content gate self-test (rules, samples, the private overlay); 4 more––
site-tests: testsevery pull request; every push to mainType check, unit, Worker and Communitas tests; Build the site; Lint the built HTML, .txt and .json; DOM tests over the built dist/; 1 more––

cloud-test check:push check test test:unit test:worker test:dom test:communitas test:e2e test:ai-visibility lint:selftest build

gh api graphql: HEAD:.github/workflows, HEAD:.githooks and HEAD:.github/cloud-test.json; each workflow's latest run timed, its pass rate over its last 20 runs read 2026-11-16 21:08 UTC