Skip to content

Run only the CI suites a pull request or push can affect #563

Open

Description

@HMarzban

Part of #554, Set C: change-aware gating, except the extension filter. #562 owns the filter. Work on main. Rulings: #554 rulings 1, 5, 6, 7, 8, 9, 10, 15, 16.

Status, 2026-11-11. Built in abd852f, deployed 2026-11-03. Done: both Verification dispatches (42778681880, 42781445956), the (build): deploy job set (41608014517, 41626334830, 41636667896), the cron (42443026527) and the first docs-only push (42663827704). Left: the docs-only and admin-only draft PRs, 5 runs each (maintainer, due 2026-11-18). Then the SP3 record (agent in the repo, within 7 days of the last sample).

Status, 2026-11-16. The claim basis was ruled on 2026-11-16. The docs-only draft PR stays at 5 runs, as ruled. It now edits one root .md line and one comment line in one .agents/skills/ script, so its logs also give #759 (b) and (c). The admin-only draft PR drops to 1 run, judged on the job count only (review, 2026-11-16).

Summary

  • Today. Every pull request and every push without (build): runs Type Check, Webapp Unit Tests and Build Verification, whatever it changed. Every pull request also runs Backend Validation.
  • After. 🔎 Detect Changes also emits webapp, admin, backend and docs_only. A new script, .github/scripts/detect-change-scopes.sh, computes them from the changed files.
    • Type Check, Backend Validation, Webapp Unit Tests and Build Verification gate on them.
    • A docs-only change also skips the Ext suites. Lint and security always run.
  • Every scope is on for a (build): push, including (build): back no-deploy. The same holds for workflow_dispatch, the weekly cron and a missing diff base. Those keep today's gate set.
  • If a skip is not provable, every scope turns on. That covers a shared file, an unmatched path, an empty list and more than 500 files. It also covers .github/, except Markdown files and issue templates.

Gain. Docs-only push run 38364279436 (docs(contributing)) changed AGENTS.md, CONTRIBUTING.md, README.md and apps/webapp/README.md. It took 217 s.

  • Build Verification alone took 128 s (run 38364279436, +89 s to +217 s). Lint ended at +85 s (run 38364279436).
  • After this issue, that push ends when lint ends, at about 85–95 s. Single-area pull requests skip the suites of the other areas.
  • Measured: docs-only push run 42663827704 (2026-11-09) logged docs_only=true and took 81 s (n = 1).

No gain:

New cost on deploys. Type Check and Backend Validation gain a needs: changes edge.

  • In deploy run 39398067267, 🔎 Detect Changes ended at +19 s. Type Check started at +12 s, and Backend E2E ended at +138 s.
  • So both jobs start about 10 s later on every (build): deploy. On a deploy with no Ext suite, Backend E2E is the longest gate, so M2g can grow by about 10 s.
  • Since Build the deploy images while the quality gates run #565, the image path is the critical path, so the cost to M1 is about 0 s.

Benchmark

Field Value
Metric 1. App jobs run on a docs-only change: Type Check, Webapp Unit Tests, Build Verification (count, exact).
2. M6 (#569) of a docs-only change (s).
3. Gate jobs on an admin-only draft PR (count, exact).
4. Cost check: Type Check start offset on a (build): deploy (s).
Before 1. 3 of 3 (run 38364279436, 2026-10-13).
2. 217 s on the pure docs-only push 38364279436 (n = 1). Same job set, n = 7 non-deploy pushes with 0 Ext suites: median 278 s, range 217–927 s (33487894862, 34224526419, 35244236059, 38364279436, 38869200675, 39586910947, 39747939586).
3. 4 gate jobs: Type Check, Backend Validation, Webapp Unit Tests, Build Verification. PR M6 median 519 s (n = 10, 2026-09-20 to 2026-10-20, all Shared, context only).
4. +12 s, n = 1 (run 39398067267).
After 1. 0 of 3 (push run 42663827704, 2026-11-09, docs_only=true).
2. 81 s on push run 42663827704 (n = 1). Draft PR, n = 5: not measured yet.
3. Not measured yet.
4. Median +21.5 s, range +18 to +26 s, n = 9 deploys, 2026-11-04 to 2026-11-11 (review read of 2026-11-11). One queued outlier, 42643542728, at +258 s.
Condition GitHub-hosted ubuntu-latest. prod.docs.plus.yml at abd852f or later. Each draft PR holds one fixed change set. The docs-only PR gives 5 runs: the first push plus 4 empty commits, pushed one at a time. It edits one root .md line and one comment line in one .agents/skills/ script. The admin-only PR gives 1 run. State the date and the head SHA.
How to run gh run view <id> --repo docs-plus/docs.plus --json createdAt,jobs, and the scopes lines in the 🔎 Detect Changes log. M6 = run createdAt to the last successful non-report job completedAt (#569). Never gh run rerun: a rerun keeps the run createdAt.
Pass rule 1. 0 of 3 in each docs-only run.
2. Median 120 s or less, n = 5.
3. Exactly 2 gate jobs (Type Check, Build Verification) and 0 Ext suites, in the one admin-only run.
4. M1 cost about 0 s, because images end last.
Revert: any Accountability stop condition.
Guard Each (build): deploy still runs every gate (reason=forced). The weekly cron still runs every Ext suite.
Owner Maintainer: opens both draft PRs, pushes the docs-only PR's empty commits and closes both unmerged, by 2026-11-18. Agent in the repo: posts SP3 within 7 days of the fifth sample.
Claim Ruled 2026-11-16: "A docs-only change now passes CI in s (n = 5 draft-PR runs), down from a 278 s median (217–927 s, n = 7 non-deploy pushes with mixed changes). It runs 0 build or test jobs, down from 3."

Depends on / Blocks

Current behaviour

Links are pinned to d0a53756f8676556358b6adc6c2397d2ed7c64c8. All paths are in .github/workflows/prod.docs.plus.yml unless named.

  1. Triage emits triggered. It is true only for a (build): subject (prod.docs.plus.yml:97-105). Any other subject emits triggered=false (parse-build-trigger.sh:30-34). On pull_request, head_commit is empty, so triggered is false (:111).
  2. 🔎 Detect Changes emits only the extension list (:124-176).
    • Outputs: changed_extensions only (:140-141).
    • The fallback expression is at :157: FORCE_ALL: ${{ github.event_name == 'workflow_dispatch' || github.event_name == 'schedule' || github.event.before == '0000000000000000000000000000000000000000' }}.
    • The header comment says "lint/typecheck/security stay always-on because they are fast and repo-global" (:120-122). That sentence becomes false.
  3. Type Check runs on every non-cron event (:189-197): needs: [triage], if: github.event_name != 'schedule' && needs.triage.outputs.skip_app_ci != 'true'.
  4. Backend Validation runs on every pull request (:260-270): if: github.event_name == 'pull_request' || needs.triage.outputs.has_back == 'true' || needs.triage.outputs.app_deploy == 'true'.
    • A push without (build): never runs it.
    • run_e2e is github.event_name != 'pull_request' (:270), so any non-PR run of it also runs Backend E2E (backend-ci.yml:44-46).
  5. The Ext suites follow the extension filter only (:272-281). A change to extensions/<ext>/docs/*.md starts that suite today, about 194 s for mermaid.
  6. Webapp Unit Tests run on every pull request and every push without (build): (:308-318). The last clause is (needs.triage.outputs.has_front == 'true' || needs.triage.outputs.triggered != 'true' || github.event_name == 'pull_request').
  7. Build Verification runs whenever its gates pass (:351-376). It accepts a skipped Backend Validation, Ext suite or Webapp Unit Tests result (:374-376). It demands success from lint, typecheck and security (:371-373).
  8. Lint and security stay as they are (:181-187, :214-222). Lint runs prettier --check ., which checks Markdown (quality-lint.yml:23-27).
  9. The deploy gate stays as it is (:431-435). It needs build to succeed. Every scope is on for a (build): push, so build still runs before every deploy.
  10. No branch protection and no required status check exist. gh api repos/docs-plus/docs.plus/branches/main/protection returns 404 Branch not protected. The only ruleset, main safety (id 21301824), holds non_fast_forward and deletion rules. So a skipped job blocks no merge.
  11. The import graph, checked at the pin:
    • The webapp depends on all six extensions and @docs.plus/floating-popover (apps/webapp/package.json:27-33). @docs.plus/playground is a dev dependency (:103). packages/playground/** stays Unmatched, which turns every scope on.
    • The backend depends on @docs.plus/email-templates and three extensions: hyperlink, hypermultimedia and inline-code (apps/hocuspocus.server/package.json:45-48).
    • apps/admin-dashboard has no workspace dependency.
    • A webapp unit test reads packages/supabase SQL files (chatMediaMime.test.ts:17-20). So packages/supabase/** is in the webapp scope.
    • The extension preflight reads only the extension README (check-quickstart-example.ts:20). No app build or test reads a file under docs/.
    • One Markdown file outside apps/*/src/ is read by code: packages/document-swarm/src/fixtures/academy.md (academy.ts:30). So .md under any src/ folder counts as code.
  12. dorny/paths-filter v4.0.3 (ceb8a2b8f2d89434be7ff52d3de7ec3738c5cc9d):
    • dot: true makes globs match .github/ (src/filter.ts:16). Git diffs use --no-renames, so a rename is a delete and an add (src/git.ts:65).
    • On a pull request, the API path splits a rename into the new name and previous_filename (src/main.ts:230-240).
    • list-files: json writes JSON.stringify of the file names (src/main.ts:296-297) and <key>_count (src/main.ts:274).
  13. The docs describe today's rule. .github/WORKFLOWS.md says a normal commit runs "gates only" and a pull request runs "gates + build verification" (WORKFLOWS.md:88-89). AGENTS.md warns that only the extension suites are path-gated (AGENTS.md:222).
  14. parse-build-trigger.test.sh runs in no workflow, only by hand. The new test runs the same way.

Target behaviour

This issue builds the two .github/ exceptions to the tracker's "run everything" rule: .github/ISSUE_TEMPLATE/** and .md files under .github/. No CI job reads them, except lint, which always runs.

The scope map. The script classes each changed path by the first row that matches.

Order Class Paths Effect
1 Never docs extensions/*/README.md, extensions/*/CHANGELOG.md, any path under a src/ folder, apps/webapp/public/** Skips row 2. Row 3 still applies, so anything under extensions/<ext>/assets/ is media, as in #562.
2 Docs **/*.md, docs/**, .github/ISSUE_TEMPLATE/**, root LICENSE No scope. Counts toward docs_only.
3 Extension README media extensions/<ext>/assets/**, and a .gif, .png, .jpg, .jpeg, .webp or .mp4 file at an extension root No scope
4 Shared Root package.json, bun.lock, bunfig.toml, tsconfig*.json, tsup.base.ts, .prettierrc*, .prettierignore, eslint.config.*, .stylelintrc*, docker-compose*.yml; .github/**; scripts/**; packages/eslint-config/** Every scope on
5 webapp apps/webapp/**, extensions/**, packages/floating-*/**, packages/supabase/**, packages/pad-url/** (6f74d89) webapp on
5 admin apps/admin-dashboard/** admin on
5 backend apps/hocuspocus.server/**, packages/email-templates/**, packages/pad-url/** (6f74d89), packages/supabase/**, packages/floating-*/**, extensions/extension-hyperlink/**, extensions/extension-hypermultimedia/**, extensions/extension-inline-code/** backend on
6 Unmatched Any other path, for example packages/document-swarm/**, packages/playground/**, packages/release-tooling/**, Makefile, .cursor/rules/*.mdc Every scope on
  • docs_only is true only when every path is in row 2.
  • .github/WORKFLOWS.md and .github/PULL_REQUEST_TEMPLATE.md are in row 2, because row 2 comes before row 4.
  • Every scope turns on, and docs_only is false, in these cases:
    • the event is workflow_dispatch or schedule;
    • github.event.before is all zeros;
    • the event is a push with triggered == 'true';
    • the file count is missing or above 500;
    • the list is empty, or its length differs from the count.

Which jobs run on a pull request, or a push without (build)::

Job Runs when
triage, Detect Changes, lint, security Always, as today
Type Check webapp, admin or backend is on
Backend Validation Pull request: backend is on. Push without (build):: never, as today.
Ext suites The extension filter selects the suite, and docs_only is not true
Webapp Unit Tests webapp is on
Build Verification webapp or admin is on, and every gate passed or was skipped
deploy, observability, Uptime Kuma Unchanged

On a (build): push, a dispatch and the cron, every job runs or skips exactly as today.

Every run explains itself. The scopes step logs one line per path (docs, media, shared, scoped or unmatched) and the five outputs, including reason.

Implementation steps

Read every file in Read first before Step 0. "Comment here" means a comment on this GitHub issue, never a code comment.

Step 0. Read and check the base

  1. Confirm you are on an up-to-date main with git status and git log -1 --format=%H.
  2. Diff the pinned files against main:
    git diff d0a53756f8676556358b6adc6c2397d2ed7c64c8 HEAD -- .github/workflows/prod.docs.plus.yml .github/filters/extensions.yaml .github/WORKFLOWS.md AGENTS.md scripts/check-ci.ts
  3. Confirm Stop extension README media from triggering extension test suites #562 is merged:
    grep -n "predicate-quantifier" .github/workflows/prod.docs.plus.yml
    grep -n "_readme_media" .github/filters/extensions.yaml
    • Both must print a line. If not, stop and comment here. Since df1a9d4, scripts/check-ci.ts holds no README_MEDIA; it reads the filter file.
    • Compare the _readme_media globs with the regex in Step 1. They must select the same files. If they differ, change the Step 1 regex to match. Then run Step 2.
    • If nested-assets fails because a nested assets/ file now reaches row 5, change that line to expect true false true false nested-assets. Any other failure: stop and comment here.
  4. Confirm the dorny/paths-filter pin and its four facts (Current behaviour item 12):
    R=ceb8a2b8f2d89434be7ff52d3de7ec3738c5cc9d
    gh api "repos/dorny/paths-filter/contents/src/filter.ts?ref=$R" -q .content | base64 -d | sed -n '14,18p'
    gh api "repos/dorny/paths-filter/contents/src/git.ts?ref=$R" -q .content | base64 -d | sed -n '65p'
    gh api "repos/dorny/paths-filter/contents/src/main.ts?ref=$R" -q .content | base64 -d | sed -n '230,240p;274p;296,297p'
    • Expect dot: true, --no-renames, the previous_filename push, _count, and JSON.stringify(fileNames).
    • If the workflow pins another SHA now, run the same reads at that SHA. If a fact fails, stop and comment here.
  5. Confirm no required status check exists:
    gh api repos/docs-plus/docs.plus/branches/main/protection
    gh api repos/docs-plus/docs.plus/rulesets/21301824 -q '[.rules[].type] | join(",")'
    • Expect 404 Branch not protected, and no required_status_checks in the rule list. Restrict the production self-hosted runner to main deploys #552 may add another rule to main safety; that is fine.
    • If a required check exists, stop and comment here. A skipped job counts as passed, but a matrix that never starts reports nothing.

Step 1. The scope script

Create .github/scripts/detect-change-scopes.sh. It is shell, not TypeScript: the changes job has no Bun, and setup-bun there would delay every gate. It runs on Bash 3.2 too, so it works on a stock macOS shell.

#!/usr/bin/env bash
# Maps changed paths (one per line on stdin) to the CI scopes a change can
# affect. If a skip is not provable, every scope turns on.
# Keep the patterns in step with the scope table in .github/WORKFLOWS.md.
set -uo pipefail

MAX_FILES=500

emit() { # key value
  [ -n "${GITHUB_OUTPUT:-}" ] && printf '%s=%s\n' "$1" "$2" >> "${GITHUB_OUTPUT}"
  printf '%s=%s\n' "$1" "$2"
}
emit_all() { # webapp admin backend docs_only reason
  emit webapp "$1"; emit admin "$2"; emit backend "$3"; emit docs_only "$4"; emit reason "$5"
}
# Drain stdin first, so the writer upstream never dies of SIGPIPE under pipefail.
everything() { cat > /dev/null; emit_all true true true false "$1"; exit 0; }

[ "${ALL_SCOPES:-false}" = true ] && everything forced
case "${FILE_COUNT:-}" in ''|*[!0-9]*) everything no-file-count ;; esac
[ "${FILE_COUNT}" -gt "${MAX_FILES}" ] && everything too-many-files

webapp=false; admin=false; backend=false; total=0; docs=0
while IFS= read -r f; do
  [ -n "${f}" ] || continue
  total=$((total + 1))

  # Docs are neutral, except preflight inputs and anything under a src/ or the
  # served public/ folder. A case `*` also matches `/`, which only widens these.
  case "${f}" in
    extensions/*/README.md|extensions/*/CHANGELOG.md|src/*|*/src/*|apps/webapp/public/*) : ;;
    *.md|docs/*|.github/ISSUE_TEMPLATE/*|LICENSE) docs=$((docs + 1)); echo "docs      ${f}" >&2; continue ;;
  esac
  # Extension README media is neutral. Same set as `_readme_media` in .github/filters/extensions.yaml.
  if [[ "${f}" =~ ^extensions/[^/]+/(assets/|[^/]+\.(gif|png|jpe?g|webp|mp4)$) ]]; then
    echo "media     ${f}" >&2; continue
  fi

  case "${f}" in
    package.json|bun.lock|bunfig.toml|tsconfig*.json|tsup.base.ts|.github/*|scripts/*|packages/eslint-config/*|.prettierrc*|.prettierignore|eslint.config.*|.stylelintrc*|docker-compose*.yml)
      webapp=true; admin=true; backend=true; echo "shared    ${f}" >&2; continue ;;
  esac

  hit=false
  case "${f}" in apps/webapp/*|extensions/*|packages/floating-*|packages/supabase/*|packages/pad-url/*) webapp=true; hit=true ;; esac
  case "${f}" in apps/admin-dashboard/*) admin=true; hit=true ;; esac
  case "${f}" in
    apps/hocuspocus.server/*|packages/email-templates/*|packages/pad-url/*|packages/supabase/*|packages/floating-*|extensions/extension-hyperlink/*|extensions/extension-hypermultimedia/*|extensions/extension-inline-code/*)
      backend=true; hit=true ;;
  esac
  if [ "${hit}" = true ]; then
    echo "scoped    ${f}" >&2
  else
    webapp=true; admin=true; backend=true; echo "unmatched ${f}" >&2
  fi
done

[ "${total}" -gt 0 ] || everything no-files
[ "${total}" -eq "${FILE_COUNT}" ] || everything count-mismatch
docs_only=false
[ "${docs}" -eq "${total}" ] && docs_only=true
emit_all "${webapp}" "${admin}" "${backend}" "${docs_only}" "files=${total}"
  • A case pattern anchors at the start of the path, so package.json and tsconfig*.json match only root files.
  • In a case pattern, * also matches /. That only widens rows 1, 4 and 5, which makes more suites run. Row 3 uses a regex, because a wider match there would skip suites.
  • Check: shellcheck .github/scripts/detect-change-scopes.sh prints nothing, if shellcheck is installed.

Step 2. The test, and prove it by sabotage

AGENTS.md §Test Policy case (c) applies. The failure mode is a parsing bug: a path classed as docs or media silently skips a suite that its change can affect.

Create .github/scripts/detect-change-scopes.test.sh, in the same shape as parse-build-trigger.test.sh:

#!/usr/bin/env bash
# Self-contained test harness for detect-change-scopes.sh (no bats dependency).
set -uo pipefail
HERE="$(cd "$(dirname "${BASH_SOURCE[0]}")" && pwd)"
SCRIPT="${HERE}/detect-change-scopes.sh"
PASS=0; FAIL=0

# run <files, one per line> [ALL_SCOPES] [FILE_COUNT, default: the line count] -> sets OUT
run() {
  local count="${3-auto}"
  [ "${count}" != auto ] || count="$(printf '%s' "$1" | grep -c . || true)"
  OUT="$(printf '%s\n' "$1" | ALL_SCOPES="${2:-false}" FILE_COUNT="${count}" GITHUB_OUTPUT='' bash "${SCRIPT}" 2>/dev/null)"
}
# expect <webapp> <admin> <backend> <docs_only> <label>
expect() {
  local got; got="$(printf '%s\n' "${OUT}" | grep -E '^(webapp|admin|backend|docs_only)=' | cut -d= -f2 | tr '\n' ' ')"
  if [ "${got}" = "$1 $2 $3 $4 " ]; then PASS=$((PASS+1)); else FAIL=$((FAIL+1)); echo "FAIL [$5]: expected '$1 $2 $3 $4' got '${got}'"; fi
}

run $'README.md\ndocs/api/README.md\ndocs/assets/flow.png\n.github/ISSUE_TEMPLATE/bug_report.md\nLICENSE\n.github/WORKFLOWS.md'
expect false false false true docs-only
run 'apps/webapp/src/utils/titleWrite.ts';                   expect true false false false webapp-only
run 'extensions/extension-mermaid/assets/demo-dark.gif';     expect false false false false gif-only
run 'bun.lock';                                              expect true true true false lockfile
run 'extensions/extension-mermaid/README.md';                expect true false false false ext-readme
run 'extensions/extension-hyperlink/CHANGELOG.md';           expect true false true false backend-ext-changelog
run 'extensions/extension-mermaid/src/assets/icon.svg';      expect true false false false src-assets-not-media
run 'apps/webapp/src/notes.md';                              expect true false false false md-under-src
run 'apps/webapp/public/robots.md';                          expect true false false false md-under-public
run 'apps/admin-dashboard/src/app/page.tsx';                 expect false true false false admin-only
run 'apps/hocuspocus.server/src/index.ts';                   expect false false true false backend-only
run 'packages/supabase/scripts/12-buckets.sql';              expect true false true false supabase
run 'packages/floating-popover/src/index.ts';                expect true false true false floating
run 'packages/email-templates/src/index.ts';                 expect false false true false email-templates
run 'packages/pad-url/src/padUrlCore.ts';                    expect true false true false pad-url
run '.github/workflows/prod.docs.plus.yml';                  expect true true true false workflow-file
run 'tsconfig.base.json';                                    expect true true true false root-tsconfig
run 'apps/webapp/tsconfig.json';                             expect true false false false app-tsconfig
run 'packages/document-swarm/src/run.ts';                    expect true true true false unmatched
run $'README.md\napps/webapp/src/a.ts';                      expect true false false false docs-plus-code
run '' false 0;                                              expect true true true false no-files
run 'README.md' true;                                        expect true true true false forced
run 'packages/document-swarm/src/fixtures/academy.md';       expect true true true false md-under-package-src
run 'extensions/extension-mermaid/docs/guide.md';            expect false false false true ext-docs-folder
run 'extensions/extension-hypermultimedia/assets/readme-media/sample.mp4'; expect false false false false nested-assets
run 'extensions/extension-mermaid/demo.webp';                expect false false false false ext-root-media
run 'extensions/extension-hypermultimedia/cypress/fixtures/x.png'; expect true false true false media-outside-assets
run '.github/assets/social-preview.png';                     expect true true true false github-assets
run 'README.md' false 501;                                   expect true true true false too-many-files
run 'README.md' false 2;                                     expect true true true false count-mismatch
run 'README.md' false '';                                    expect true true true false no-file-count

echo "PASS=${PASS} FAIL=${FAIL}"
[ "${FAIL}" -eq 0 ]
  1. Run bash .github/scripts/detect-change-scopes.test.sh. Expect PASS=32 FAIL=0 and exit 0. (6f74d89 added the pad-url case on 2026-10-31. 98b9b00 added the .agents case.)
  2. Sabotage. In the script, delete extensions/*/README.md| from the row 1 pattern. Run the test again. Expect FAIL [ext-readme] and exit 1.
  3. Restore the line. Run the test again and expect PASS=32 FAIL=0. Paste both outputs in the review.
  4. Do not sabotage with bun.lock. Removing it from row 4 sends it to row 6, which also turns every scope on, so the test cannot see it.

Step 3. The changes job

  1. The header comment at :120-122: replace only the sentence that says Type Check stays always-on. Leave the "~14 min" text to Make CI failures reach Telegram: set the watchdog secrets, alert on red E2E pushes #557.
      # extension-tests job keys off. It also emits the webapp, admin, backend and
      # docs_only scopes from detect-change-scopes.sh. Lint and security always
      # run. On a PR or a push without `(build):`, typecheck, backend validation,
      # webapp unit tests and Build Verification run only for scopes that are on.
  2. The outputs at :140-141:
        outputs:
          changed_extensions: ${{ steps.assemble.outputs.list }}
          webapp: ${{ steps.scopes.outputs.webapp }}
          admin: ${{ steps.scopes.outputs.admin }}
          backend: ${{ steps.scopes.outputs.backend }}
          docs_only: ${{ steps.scopes.outputs.docs_only }}
  3. Two new steps after the assemble step (after :176). Do not change filter or assemble.
          # Every changed path, for the scope map. Its own step: the extension filter
          # above has its own predicate quantifier. A `(build):` push needs no list.
          - id: files
            if: github.event_name == 'pull_request' || (github.event_name == 'push' && needs.triage.outputs.triggered != 'true')
            uses: dorny/paths-filter@ceb8a2b8f2d89434be7ff52d3de7ec3738c5cc9d # v4.0.3
            with:
              list-files: json
              filters: |
                all:
                  - '**'
    
          - id: scopes
            env:
              # The `assemble` fallback, plus every `(build):` push: scopes never
              # narrow a deploy push's gate set.
              ALL_SCOPES: ${{ github.event_name == 'workflow_dispatch' || github.event_name == 'schedule' || github.event.before == '0000000000000000000000000000000000000000' || (github.event_name == 'push' && needs.triage.outputs.triggered == 'true') }}
              FILE_COUNT: ${{ steps.files.outputs.all_count }}
              # Over 500 paths the list could pass the env size limit; the script turns every scope on.
              FILES_JSON: ${{ fromJSON(steps.files.outputs.all_count || '0') <= 500 && steps.files.outputs.all_files || '[]' }}
            run: |
              set -euo pipefail
              printf '%s' "${FILES_JSON}" | jq -r '.[]' | bash .github/scripts/detect-change-scopes.sh
    • Use the same dorny/paths-filter SHA as the filter step. If Step 0 found a new pin, use it.
    • Do not name the filter key changes. That name is a reserved output of the action.
    • The file list goes through env, never into the script text. File names in a pull request are untrusted input.
    • Why 500: the longest repo path is 144 characters. 500 paths are about 74 KB, under the 128 KB limit for one environment value.
    • jq is preinstalled on ubuntu-latest.

Step 4. Type Check

At :193-197:

    needs: [triage, changes]
    # Skip on infra-only commits (skip_app_ci=true), schedule, or no code scope.
    if: |
      github.event_name != 'schedule' &&
      needs.triage.outputs.skip_app_ci != 'true' &&
      (needs.changes.outputs.webapp == 'true' || needs.changes.outputs.admin == 'true' || needs.changes.outputs.backend == 'true')
  • With no status function, the if also needs triage and changes to succeed. If changes fails, Type Check skips, and Build Verification then blocks the deploy. Today a failed changes blocks Build Verification too.

Step 5. Backend Validation

At :262-267. Keep the four comment lines and add one:

    needs: [triage, changes]
    # `app_deploy` is the value the deploy job gates on, and the deploy always
    # runs the Prisma migration and rolls all three backend services. Gating on
    # `has_back` alone let a `(build): front` push deploy backend code no test
    # had ever touched. `has_back` stays so `(build): back no-deploy` still runs.
    # A PR runs it only for the backend scope; a `(build):` push turns every scope on.
    if: |
      (github.event_name == 'pull_request' || needs.triage.outputs.has_back == 'true' || needs.triage.outputs.app_deploy == 'true') &&
      needs.changes.outputs.backend == 'true'
  • Do not change run_e2e. A push without (build): stays without Backend Validation, so it never runs Backend E2E.

Step 6. Ext suites skip docs-only changes

In the extension-tests if (:276-281 at the pin), add one line after the changed_extensions line:

      needs.changes.outputs.changed_extensions != '[]' &&
      needs.changes.outputs.docs_only != 'true' &&

Step 7. Webapp Unit Tests

At :312-318. #558 has removed the back-validation wait. Add changes to needs and one clause:

    needs: [triage, changes]
    if: |
      always() &&
      github.event_name != 'schedule' &&
      needs.triage.outputs.skip_app_ci != 'true' &&
      needs.changes.outputs.webapp == 'true' &&
      (needs.triage.outputs.has_front == 'true' || needs.triage.outputs.triggered != 'true' || github.event_name == 'pull_request')
  • Keep back-validation out of needs and keep no needs.back-validation.result line.
  • A (build): back push still skips this job. Its has_front is false and triggered is true, as today.

Step 8. Build Verification

In the build if (:366-376), add one line after needs.changes.result == 'success' &&:

      needs.changes.result == 'success' &&
      (needs.changes.outputs.webapp == 'true' || needs.changes.outputs.admin == 'true') &&
  • Do not touch the typecheck clause. When webapp or admin is on, Type Check runs, so its success demand stays right.

Step 9. Docs

  1. .github/WORKFLOWS.md:88-89. Replace the two rows:
    | `fix: …` (normal commit)                        | typecheck by scope, no backend-ci | ⏭️         | ⏭️  | ⏭️  | gates for changed scopes, no deploy |
    | PR to `main`                                    | changed scopes | ⏭️         | ⏭️  | ⏭️  | gates + build verification for changed scopes |
  2. .github/WORKFLOWS.md, new section between the truth table and ## Related files:
    ## Change scopes (PRs and pushes without `(build):`)
    
    `🔎 Detect Changes` runs `.github/scripts/detect-change-scopes.sh` on the changed files. It emits `webapp`, `admin`, `backend` and `docs_only`. Lint and security always run.
    
    <the scope-map table and the job table from this issue's Target behaviour>
    
    Every scope is on for a `(build):` push, a `workflow_dispatch`, the weekly cron, a missing diff base, more than 500 files, or an empty list.
    Paste both tables from Target behaviour in place of the angle-bracket line.
  3. .github/WORKFLOWS.md §Related files. Add - Change-scope classifier: .github/scripts/detect-change-scopes.sh (test: detect-change-scopes.test.sh).
  4. AGENTS.md:222. Find the sentence "Confirm the job actually executed in the run you cite before calling a suite healthy." Add these two sentences after it:

    On a PR or a push without (build):, Type Check, Backend Validation, Webapp Unit Tests and Build Verification also skip by changed path (.github/scripts/detect-change-scopes.sh). A green PR therefore does not prove that those jobs ran.

  5. Format the touched files: bunx prettier --write .github/WORKFLOWS.md AGENTS.md .github/workflows/prod.docs.plus.yml.

Step 10. Local checks

  1. actionlint -config-file .github/actionlint.yaml .github/workflows/prod.docs.plus.yml prints nothing.
  2. bash .github/scripts/detect-change-scopes.test.sh prints PASS=32 FAIL=0.
  3. bash .github/scripts/parse-build-trigger.test.sh still prints FAIL=0. Triage does not change, so this is a guard.
  4. Replay four real file lists through the script. A dry_run_subject dispatch cannot test scopes, because a dispatch turns every scope on.
    replay() { FILE_COUNT=$(printf '%s\n' "$1" | grep -c .) bash .github/scripts/detect-change-scopes.sh <<< "$1"; }
    replay "$(git diff --name-only --no-renames 1abb90a62^ 1abb90a62)"
    replay "$(git diff --name-only --no-renames 0918031d0^ 0918031d0)"
    replay $'extensions/extension-mermaid/assets/demo-dark.gif\nextensions/extension-mermaid/assets/demo-light.gif'
    replay "$(gh api repos/docs-plus/docs.plus/pulls/540/files -q '.[].filename')"
    Replay Files Expected output Jobs that then run
    Docs-only, 1abb90a62 (run 38364279436) AGENTS.md, CONTRIBUTING.md, README.md, apps/webapp/README.md webapp=false admin=false backend=false docs_only=true triage, Detect Changes, lint, security
    Webapp-only, 0918031d0 7 files under apps/webapp/src/, plus .cursor/docs/design-system.md webapp=true admin=false backend=false docs_only=false the above, plus Type Check, Webapp Unit Tests, Build Verification
    GIF-only, synthetic two extensions/extension-mermaid/assets/demo-*.gif files webapp=false admin=false backend=false docs_only=false triage, Detect Changes, lint, security. Stop extension README media from triggering extension test suites #562 skips the mermaid suite.
    bun.lock, PR chore(deps): bump cypress from 15.21.1 to 16.2.0 #540 apps/webapp/package.json, bun.lock, package.json webapp=true admin=true backend=true docs_only=false every gate and all six Ext suites, as today
  5. bun run format passes.
  6. bun run check:agent-docs passes.

Review checkpoint

Show git diff --stat and the full diff of .github/workflows/prod.docs.plus.yml. Paste the outputs of Steps 2 and 10. Then stop. Do not run git add, git commit, git push or git stash. Do not create a branch.

The maintainer reviews the change set, then commits and pushes it per SP2 (#554), with a subject that does not start with (build):.

Acceptance criteria

  • .github/scripts/detect-change-scopes.sh and .github/scripts/detect-change-scopes.test.sh exist. The test prints PASS=32 FAIL=0 and failed once under the Step 2 sabotage.
  • 🔎 Detect Changes outputs webapp, admin, backend and docs_only. The scopes step log shows one class line per path and a reason line.
  • ALL_SCOPES is true for workflow_dispatch, schedule, an all-zeros before and every push with triggered == 'true'.
  • Type Check, Backend Validation, Webapp Unit Tests and Build Verification gate on the scopes as in Steps 4–8. Ext suites skip when docs_only is true.
  • actionlint prints nothing for prod.docs.plus.yml.
  • The four Step 10 replays print the expected outputs.
  • The two Verification dispatches run and skip the jobs that Verification lists. In the (build): front dispatch, lint and security also run. (42778681880, 42781445956, 2026-11-10.)
  • The next docs-only push runs only triage, Detect Changes, lint and security, and its M6 is 120 s or less. Amended, maintainer ruling 2026-11-06: a docs-only draft PR run counts in place of a push. (42663827704, 81 s, Measured, 2026-11-11.)
  • The next (build): deploy runs lint, security, Type Check, Backend Validation and Build Verification. It runs Webapp Unit Tests when has_front is true. Its Ext matrix equals the changed_extensions list in its assemble log. (41608014517, 41626334830, 41636667896, comment of 2026-11-03.)
  • The next weekly cron runs 🔒 Security Audit and one Ext suite for each name in the all list of the assemble step. Type Check, Webapp Unit Tests and Build Verification skip, as in run 39089384453. (42443026527, 2026-11-08.)
  • .github/WORKFLOWS.md and AGENTS.md:222 say what Step 9 says.
  • The result is recorded per SP3 ([Tracking] Faster, change-aware CI/CD pipeline #554), as in Accountability.

Verification

Before the push (the builder):

actionlint -config-file .github/actionlint.yaml .github/workflows/prod.docs.plus.yml
bash .github/scripts/detect-change-scopes.test.sh
bash .github/scripts/parse-build-trigger.test.sh
bun run format
bun run check:agent-docs

Then the four replays in Step 10.

After the push (the maintainer). A dispatch turns every scope on, so these two dispatches prove the unchanged paths only.

  1. Run SP1 ([Tracking] Faster, change-aware CI/CD pipeline #554) before each dispatch. The deploy job comment at prod.docs.plus.yml:415-418 says a push also cancels a running roll. Build the deploy images while the quality gates run #565 shows that a running deploy survives (run 34223310158).
  2. Run one dispatch at a time. Wait for it with gh run watch <id> --repo docs-plus/docs.plus before you start the next one.
  3. Nobody pushes to main while a dispatch runs.
gh workflow run prod.docs.plus.yml --repo docs-plus/docs.plus --ref main -f dry_run_subject='(build): front'
# wait for it to end, repeat check 1, then:
gh workflow run prod.docs.plus.yml --repo docs-plus/docs.plus --ref main -f dry_run_subject='fix: scope check'
  • (build): front. The scopes log shows reason=forced. Type Check, Backend Validation, every Ext suite, Webapp Unit Tests and Build Verification run. 🚀 Deploy Production skips, because force_deploy is false.
  • fix: scope check. The scopes log shows reason=forced. Type Check, every Ext suite, Webapp Unit Tests and Build Verification run. Backend Validation skips, as today.

Accountability

  • Owner: the person who pushes this change set: the maintainer, or a builder the maintainer names.

  • Record per SP3 ([Tracking] Faster, change-aware CI/CD pipeline #554) within 7 days of the push. If a run type has not happened by then, say so and add it later.

    • The first due date, 2026-11-10, passed with no SP3 record. New due date: within 7 days of the fifth draft-PR sample (agent in the repo).
    • Also record these items. SP3 has no slot for them.
      • Both dispatch runs: the run ids and the job list with results.
      • The docs-only draft PR: each run id, M6 and the skipped jobs. The admin-only draft PR (a single-area pull request): its run id and the skipped jobs.
      • The next (build): deploy: the run id and the Type Check start offset.
      • The next weekly cron: the run id.
    • For the deploy, confirm the job set in the acceptance criteria. For the next weekly cron, confirm Security and one Ext suite per name in the assemble all list.
  • Metric rows. Measure CI/CD time to live after the v2.3 work: 1090 s median before #569 defines every metric and holds the full baseline table. Read each with gh run view <id> --repo docs-plus/docs.plus --json createdAt,jobs.

    Metric Run to read Baseline Expected
    M6, docs-only change 42663827704, plus one docs-only draft PR (one line in a root .md file and one comment line in one .agents/skills/ script): the first push and 4 empty commits, one at a time 217 s, run 38364279436 (n = 1). Same job set, n = 7: median 278 s, range 217–927 s median 120 s or less, n = 5
    Gate jobs, admin-only draft PR A draft PR with a one-line comment edit in one apps/admin-dashboard/src/ file: 1 run, closed unmerged. Maintainer, by 2026-11-18. 4 gate jobs (Type Check, Backend Validation, Webapp Unit Tests, Build Verification) 2 gate jobs (Type Check, Build Verification)
    Type Check start offset, (build): deploy The next (build): deploy +12 s; changes ended at +19 s (run 39398067267) About +20 s. Read: median +21.5 s, range +18 to +26 s, 9 deploys from 2026-11-04 to 2026-11-11 (review read of 2026-11-11); one queued outlier, 42643542728, at +258 s.
    M1 The next (build): deploy Median 1090 s, p90 1386 s, range 777–1510 s, over 14 runs (before Build the deploy images while the quality gates run #565): 35723691814, 36473904247, 36550492709, 37440315600, 37976785981, 38068638114, 38239392350, 38392614215, 39275929831, 36324777594, 36437965916, 37431581531, 39297468969, 39398067267 Unchanged; images are the critical path since Build the deploy images while the quality gates run #565. M1 after: see Measure CI/CD time to live after the v2.3 work: 1090 s median before #569 Measured 6812443811.
    W, M2i, M3, M4, M5 — — Not touched by this issue. No read needed.
  • Stop condition, meaning revert (see Rollback):

    • A (build): push or a dispatch skips a job that runs there today. Check lint, security, Type Check, Backend Validation and Build Verification, and Webapp Unit Tests when has_front is true. The Ext matrix must equal the changed_extensions list in the assemble log.
    • A pull request or push skips a suite in the scope of one of its changed files, per the scope map.
    • 🔎 Detect Changes fails on a valid pull request or push.
  • Not a revert: M1 grows by more than 20 s on two deploys in a row while M2i does not. Comment here instead, to reopen the needs: changes edge.

Rollback

  1. Revert per SP4 ([Tracking] Faster, change-aware CI/CD pipeline #554), with git revert --no-edit <commit>. If this issue landed as several commits, revert all of them, newest first. Do not revert Stop extension README media from triggering extension test suites #562, and do not revert part of this issue.
  2. Push the revert with its default Revert "…" subject. This change touches CI files only, so no (build): deploy is needed.
  3. Check the revert. grep -c 'steps.scopes' .github/workflows/prod.docs.plus.yml prints 0. In the revert run (gh run view <id> --repo docs-plus/docs.plus --json jobs), Type Check, Webapp Unit Tests and Build Verification run and pass.
  4. There is no host step, secret or GitHub setting to undo.

Known gap, not a revert. Scopes read before..after. A cancelled run's files are checked only by the next (build): push or the cron. #759 owns the fix.

Docs to update

  • .github/WORKFLOWS.md:88-89, a new §Change scopes section, and §Related files (Step 9).
  • AGENTS.md:222: one sentence (Step 9).
  • The changes job header comment in prod.docs.plus.yml (Step 3).
  • No CHANGELOG. This is a CI-only change.

Out of scope

Read first

Activity

  1. added this to the v2.3.0 milestone on Oct 20, 2026
  2. HMarzban commented on Oct 26, 2026

    @HMarzban
    CollaboratorAuthor

    Built and committed on local main. Awaits the maintainer's final push.

    Remaining gate: the push, then the two dry_run_subject dispatches one at a time, and the SP3 record.

  3. HMarzban commented on Nov 3, 2026

    @HMarzban
    CollaboratorAuthor

    Status, 2026-11-03. abd852f92 is pushed and deployed on 2026-11-03. On (build): run 41608014517, every scope was on, and every gate and all six Ext suites ran.

    Left:

    • Maintainer: the two dry_run_subject dispatches, one at a time.
    • Builder: read the next docs-only push (M6 120 s or less), the next single-area PR and the weekly cron.
    • Builder: post the SP3 record by 2026-11-10.
  4. HMarzban commented on Nov 3, 2026

    @HMarzban
    CollaboratorAuthor

    Measured, 2026-11-03.
    Run: 41608014517, attempt 1, then deploys 41626334830 and 41636667896.
    On main: #555–#565. #566 has only its temporary backend_no_cache input (a9688f0). #568 has only its trace tooling (d9b6222).
    M1 598 | M2g 496 | M2i 509 | M3 445 | M4 7 | M5 59 | W 9 | free_gb 60 | cached_installs 0
    Expected: every scope on for a (build): push. Type Check starts at about +20 s. M1 within the normal range.
    Verdict: keep.

    The (build): deploy job set is proven on all three deploys:

    • scopes logs webapp=true, admin=true, backend=true, docs_only=false, reason=forced.
    • Triage logs has_front=true, has_back=true, triggered=true.
    • Lint, security, Type Check, Backend Tests, Backend E2E, Webapp Unit Tests and Build Verification ran and passed.
    • The assemble step had FORCE_ALL: false and all six R_… values true. The Ext matrix ran those six names.
    Run Detect Changes ends Type Check job Type Check starts
    41608014517 +27 s 125822788135 +29 s
    41626334830 +16 s 125884636913 +19 s
    41636667896 +17 s 125919620790 +19 s

    M1: 598 s, 633 s and 670 s. Each is below the 777 s baseline minimum.

    The bun.lock PR rows (Dependabot #674):

    • Run 41626692066: scopes logs reason=files=2 and every scope true. All six Ext suites ran. M6 is 192 s (📊 Run Report, job 125887166572).
    • Run 41637030759: the same scopes. M6 is 257 s (📊 Run Report, job 125922723808).
    • Both runs failed at 📝 Type Check (jobs 125885865695, 125920876905), so 🏗️ Build Verification skipped. Backend E2E skips on every PR (run_e2e is false on pull_request). M6 is not judged, because the runs failed.

    Not read yet:

    • The two dry_run_subject dispatches have not run.
    • No docs-only push has run.
    • No single-area pull request has run.
    • No (build): deploy without an Ext suite has run, so the M2g row stays open.
    • The next weekly cron is due on 2026-11-08.

    Can close now: no — the two dispatches (maintainer), a docs-only push with M6 of 120 s or less, a single-area pull request, the weekly cron, and SP3 by 2026-11-10.

  5. HMarzban commented on Nov 6, 2026

    @HMarzban
    CollaboratorAuthor

    Maintainer ruling, 2026-11-06

    The acceptance list is amended in the issue body. Each changed line is marked with this date.

  6. modified the milestones: v2.3.0, v2.3.6 on Nov 9, 2026
  7. HMarzban commented on Nov 10, 2026

    @HMarzban
    CollaboratorAuthor

    Result, 2026-11-10: the first of the two Verification dispatches. Dry-run dispatch 42778681880, dry_run_subject='(build): front', force_deploy false, on 24f302ae0. Run SP1 printed 0 first. The run ended success.

    • The scopes log shows webapp=true, docs_only=false and reason=forced.
    • Lint and security ran. Type Check, Backend Tests, Backend E2E, all six Ext suites, Webapp Unit Tests and Build Verification ran and passed.
    • 🚀 Deploy Production was skipped, because force_deploy is false.

    Left: the second dispatch, dry_run_subject='fix: scope check', where Backend Validation must skip. Also the docs-only draft PR, a single-area pull request, and a (build): deploy with no Ext suite. The 2026-11-08 cron (run 42443026527) ran all six Ext suites.

  8. HMarzban commented on Nov 10, 2026

    @HMarzban
    CollaboratorAuthor

    Result, 2026-11-10: the second Verification dispatch. Dry-run dispatch 42781445956, dry_run_subject='fix: scope check', on 24f302ae0. Run SP1 printed 0 first. The run ended success.

    • The scopes log shows webapp=true, backend=true, docs_only=false and reason=forced.
    • Type Check, all six Ext suites, Webapp Unit Tests and Build Verification ran and passed.
    • 🔧 Backend Validation was skipped, as today. 🚀 Deploy Production was skipped.

    Both Verification dispatches now pass. Left: the docs-only draft PR (M6 of 120 s or less), a single-area pull request, and a (build): deploy with no Ext suite.

  9. HMarzban commented on Nov 11, 2026

    @HMarzban
    CollaboratorAuthor

    Measured, 2026-11-11. Read with gh run view <id> --repo docs-plus/docs.plus --json createdAt,jobs and the 🔎 Detect Changes logs.

    1. The first docs-only push. Run 42663827704, push of 5ecc99739 (2026-11-09), attempt 1. The run ended success.
    Expected: only triage, Detect Changes, lint and security run, and M6 is 120 s or less.
    Verdict: keep. This is sample 1 of the docs-only row.

    • 🔎 Detect Changes: Changes will be detected between 389860983… and main, Detected 2 changed files.
    • Class lines: docs .agents/skills/release-extensions/SKILL.md and docs CHANGELOG.md.
    • Scope outputs: webapp=false, admin=false, backend=false, docs_only=true, reason=files=2.
    • Ran: triage, Security Audit, Detect Changes, lint, Run Report.
    • Skipped: Type Check, Backend Validation, every Ext suite, Webapp Unit Tests, Build Images, Build Verification and Deploy Production.
    • M6 = 81 s: createdAt 17:21:34Z to lint completedAt 17:22:55Z. The report job is left out (Measure CI/CD time to live after the v2.3 work: 1090 s median before #569).
    • Before: 217 s on docs-only push 38364279436 (n = 1). Each side is n = 1, so the draft PR adds n = 5.

    2. The weekly cron. Run 42443026527, schedule (2026-11-08), head d31ed9033. The run ended success.

    • Ran: Security Audit, Detect Changes and all six Ext suites, all success.
    • Skipped: lint, triage, Type Check, Webapp Unit Tests, Backend Validation, Build Verification and Deploy Production.
    • That matches the cron acceptance box.

    3. M2g on (build): deploys with no Ext suite. Review read of 2026-11-11: 314 s (42603950298) and 291 s (43008200172). 42643542728 is excluded, because Type Check queued to +258 s. Since #565, images end after the gates, so M2g is context only.

    4. Push run 42671777126 failed. Push of fef27c1e7 (2026-11-09), attempt 1. I read its jobs, check runs and annotations.

    • The API holds 5 job records. Run 42663827704, one push earlier, holds 15. Triage, Security Audit, Type Check, the Ext suites, Build Verification and Run Report have no record.
    • No record shows a failure. Detect Changes and Webapp Unit Tests ended success; the other three were skipped.
    • The only annotations are two notice lines about the ubuntu-latest label move. No error annotation exists.
    • Webapp Unit Tests needs triage and changes, and it ran. So the needs: changes edge did not skip it. This is not a Rollback stop condition.
    • The Discord repo-activity run on the same push (42671776969) also ended failure, with 0 jobs.
    • I found no cause in the run data. The missing records point to a GitHub-side start failure. No action needed here.
    • Next good run: 42689997917, (build): back front on 24f302ae0 (2026-11-09). It contains fef27c1e7. Every scope was on, and 13 jobs ended success.
    • The Detect Changes log of 42671777126 shows 4 files. One is unmatched .agents/skills/release-product/scripts/note-coverage.ts, so every scope was on. That is the .agents/ follow-up named under "No gain".

    Body edits, 2026-11-11:

    • A status block and one Benchmark section, under the Summary.
    • PASS=31 FAIL=0: 6f74d89 (2026-10-31) added packages/pad-url/** to the webapp and backend scopes and one test case. Steps 1 and 2 now match the merged files.
    • Step 0.3 greps _readme_media in .github/filters/extensions.yaml, because df1a9d4 removed README_MEDIA from scripts/check-ci.ts.
    • The single-area row is now an admin-only draft PR. Both draft PRs take 5 runs: the first push plus 4 empty commits, one at a time. A rerun keeps the run createdAt, so it does not count.
    • The M1 row keeps the 1090 s baseline (before Build the deploy images while the quality gates run #565). Measure CI/CD time to live after the v2.3 work: 1090 s median before #569 posts the after value from its stats script.
    • Rollback names the cancelled-run gap.

    Left: the docs-only draft PR and the admin-only draft PR (maintainer, by 2026-11-18). Then SP3 within 7 days of the fifth sample (agent in the repo).

  10. HMarzban commented on Nov 14, 2026

    @HMarzban
    CollaboratorAuthor

    Moved to v2.3.7 at the v2.3.6 release audit. The docs-only and admin-only draft PR runs are not measured yet. The SP3 record follows them.

  11. modified the milestones: v2.3.6, v2.3.7 on Nov 14, 2026
  12. HMarzban commented on Nov 16, 2026

    @HMarzban
    CollaboratorAuthor

    Maintainer ruling, 2026-11-16

    Answered by the maintainer in the 2026-11-16 working session; posted by the agent.

    • Claim basis: the recommended sentence: "A docs-only change now passes CI in s (n = 5 draft-PR runs), down from a 278 s median (217–927 s, n = 7 non-deploy pushes with mixed changes). It runs 0 build or test jobs, down from 3."
  13. HMarzban commented on Nov 16, 2026

    @HMarzban
    CollaboratorAuthor

    Review, 2026-11-16 (maintainer approved).

    • The docs-only draft PR stays at n = 5, as ruled. It now also edits one comment line in one .agents/skills/ script. Its logs then give Path-test the files of a cancelled push, and class .agents/** changes as docs only #759 (b) and (c), so Path-test the files of a cancelled push, and class .agents/** changes as docs only #759 needs no PR of its own.
    • The admin-only draft PR drops to 1 run, judged on the job count only. The diff fixes that count, and no claim uses its M6.
    • The bun.lock M6 row and the M2g row are cut. Both were context only. The M1 row now lists its 14 runs in full.
    • PASS=31 now reads PASS=32, because 98b9b002c added the .agents case. The test prints PASS=32 FAIL=0 at 5aa56e1d1.
    • Boxes 2-5 are ticked. actionlint printed nothing today, and the recorded runs prove the scope outputs and gating. Boxes 1 and 6 stay open: no comment records the sabotage run or the four replays.
    • The Claim row now holds the 2026-11-16 ruled sentence.
  14. HMarzban commented on Nov 17, 2026

    @HMarzban
    CollaboratorAuthor

    Rollback note, 2026-11-17 (#759 step 5). Scopes read before..after. Since #759 (58f22a844), a run after a cancelled push forces every scope.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions