* test(dolt): red — testdb_* leak onto production Dolt port when Docker absent (refs be-h2h25) * feat: green — Test suites create testdb_* on the PRODUCTION dolt server: harness fails open on the ambient port when Docker is absent (refs be-h2h25) * docs(release-gate): add be-napos gate — ambient Dolt port fail-open to fail-closed Deploy bead be-napos (build be-h2h25, review be-7fym1, verdict pass round 2). 7/7 gate criteria PASS; full independent evidence in the gate doc. refs be-napos, be-h2h25, be-7fym1 * docs(release-gate): record PR link for be-napos gate refs be-napos * test(testutil): make the fail-closed gate deterministic, not Docker-conditional The regression test skipped itself on every host that has Docker, by calling the real EnsureDoltContainerForTestMain and skipping when it succeeded. That asserted nothing on CI -- the only lane where it matters -- and on a Docker-having host it also started the shared singleton container purely to decide to skip, with no TestMain in internal/testutil to terminate it. Add checkDoltFn, a package-level seam over checkDolt, so the test can force a not-ready state without a Docker daemon and without starting a container. Only EnsureDoltContainerForTestMain routes through it; the neighbouring t.Skip call sites gate a skip rather than the fail-closed behaviour, so they keep calling checkDolt directly. The gate now covers all four not-ready states rather than the one the old test happened to hit, which also pins the intent that an explicit BEADS_TEST_SKIP=dolt opt-out must fail closed exactly as a Docker-less host does. Split into a platform-independent half (the helper's own contract, both variables cleared, idempotent) and a !windows half (the wiring, via the seam). Red/green: with the neutralizeAmbientDoltPort call removed from the not-ready branch, 4 of 4 subtests fail and 0 pass; restored, 4 of 4 pass in 0.06s with no Docker and no container. (refs be-napos) * fix(testutil): clear the ambient Dolt port on the Windows stub too The Windows EnsureDoltContainerForTestMain returned its error without touching BEADS_DOLT_SERVER_PORT / BEADS_DOLT_PORT, so the fail-open this branch fixes still shipped there -- unconditionally, since that stub never succeeds. Windows is a real lane: .github/workflows/pr.yml runs windows-latest on four jobs plus the cross-platform matrix. Gating it needed one pre-existing repair. testdoltserver_env_test.go has no build tag but calls checkDolt, which is !windows-only, so the internal/testutil test binary has never compiled for Windows -- reproduced identically on origin/main. Tagging that file !windows fixes the whole package's Windows test lane; without it a new Windows gate would compile nowhere and assert nothing, which is the same defect this branch is already correcting. Verified GOOS=windows go vet ./internal/testutil/ clean (it fails on origin/main), and GOOS=windows go build clean before and after. The Windows gate itself is compile-verified only -- no Windows host here to execute it. (refs be-napos) * docs(testing): state that ambient BEADS_DOLT_*_PORT is never honored The guard fires on every not-ready state, not only "Docker unavailable" -- a missing or wrong-version image and an explicit BEADS_TEST_SKIP=dolt opt-out clear the ambient port too. That is deliberate: the invariant is the absence of a test container, not the reason for it. Say so where the next person will look before investigating, and name the supported way to target a specific server. (refs be-napos) * chore: remove leaked internal release-gate doc from PR branch release-gates/be-napos-ambient-dolt-port-failclosed-gate.md Tracked our internal gc-management/beads-rig release-gate checklist and should never have been committed to this upstream branch -- it's process residue from our deploy tooling, not part of the change itself. Per maintainer bee-ghosttrack's request during review of PR #6571. The root cause (our deploy tooling auto-committing this file) is already fixed as of gm-qatxl1; this branch predates that fix, so this commit is cleanup only -- no other content on this branch is touched. Ref: be-lk7o3 * chore(bazel): enumerate the PR's new test files in BUILD.bazel Base added BUILD.bazel to internal/testutil and internal/storage/dolt after this PR was opened (#6881 made the Bazel lane real, and fork PRs always run it). The four new test files this PR adds were therefore absent from the go_test srcs lists, which the bazel lane's equivalence check reports as a missing target. Generated by 'make bazel-sync' (gazelle), not hand-edited, because the CI drift step diffs against exactly what gazelle emits. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> * fix(testutil): reconcile the shared-server harness with the fail-closed clear Review iterations 1-2 (adopt-pr, PR #5885): every gating finding from both review syntheses, plus their minors and nits. Iteration 1, Major 1 (Change Impact / Blast Radius). scripts/test.sh's BEADS_TEST_SHARED_SERVER=1 flow starts a dockerless `dolt sql-server` and exports BEADS_DOLT_PORT for every package to reuse. checkDolt() has no notion of an already-provisioned shared server, so on that flow's primary audience -- a host without Docker -- all 12 EnsureDoltContainerForTestMain callers erased the harness's own sanctioned port before m.Run(), turning green dockerless runs red, while engdocs/CI_TEST_SURFACE_AUDIT.md and the new TESTING.md paragraph advertised the two mechanisms unreconciled. Taken: a dedicated marker, BEADS_TEST_SHARED_DOLT_SERVER, exported by scripts/test.sh beside the port it allocated, which the helper's failure paths honor. Both docs state the reconciliation, including the precedence: a container, where one can be started, still overwrites both variables. Not taken: "skip the clear when BEADS_TEST_SHARED_SERVER=1 and a port var is already set". That flag is overloaded (cmd/bd/shared_server_integration_test.go reads it too), and the script starts no server when a port is already set, so the flag beside a port is exactly the case where the port is ambient. Iteration 2, blocker (Behavioral Correctness). Iteration 1 shipped that marker as a boolean ("1") which spared BOTH port variables, while the script vouched only for the BEADS_DOLT_PORT it exported and its entry guard never looked at BEADS_DOLT_SERVER_PORT -- the variable applyConfigDefaults resolves first. The runner's test environment (beads_test_env_enter) unsets both variables before the flow runs, so the hole needed that isolation skipped, e.g. with the documented BEADS_TEST_ENV_DISABLE=1; then an inherited BEADS_DOLT_SERVER_PORT reached `go test` beside the marker and outranked the shared server -- gm-2g3g5r, re-opened by its own fix. Measured with a fake `go` that prints its environment: SERVER_PORT=59999 PORT=<shared> MARKER=1 under the iteration-1 script. Now: - the marker's value is the port it vouches for, and the helper decides per variable (neutralizeUnvouchedDoltPorts): only a variable holding exactly that port survives, and says so on stderr; every other one is cleared, marker or not; - the flow starts only when neither port variable is set, and says on stderr when BEADS_TEST_SHARED_SERVER=1 is ignored for that reason. Not taken: also exporting BEADS_DOLT_SERVER_PORT from the flow. The widened guard means it is always unset there, so the export adds no safety, and five sites read that variable alone (internal/doltserver/doltserver.go:796, cmd/bd/init.go:773 and :1351, cmd/bd/bootstrap.go:857, internal/testutil/testdoltbranch.go:164) -- consumers the flow has never fed. Iteration 2, minor (Test Evidence Quality). The exception's second arm, a container that would not start, was reached by no test with its guard live. Both failure paths now share one clear, and the container start is a seam (startSharedContainerFn, pinned to startSharedContainer by identity) so tests reach that path without consuming doltServerOnce. TestEnsureDoltContainerForTestMain_KeepsHarnessProvisionedPort runs its whole table, marked_but_divergent_var included, through both paths. Iteration 2, minor (Contract & Interface Fidelity). The marker prose in TESTING.md, CI_TEST_SURFACE_AUDIT.md, test.sh and testdoltserver.go describes the per-port behavior the code now implements. Iteration 1, Major 2 (Contract & Interface Fidelity). neutralizeAmbientDoltPort's doc comment claimed "With no port resolvable, applyConfigDefaults' BEADS_TEST_MODE guard forces port 1". Clearing the env vars is not "no port resolvable": resolution falls through to the file chain and derives a directory from filepath.Dir(cfg.Path) when BeadsDir is empty (store.go:1661-1664), so a reachable .beads/dolt-server.port still yields a non-zero port and the ServerPort == 0 arm (store.go:1683-1687) never fires; production-port detection is strictly narrower than resolution. Narrowed to what the change actually guarantees -- no environment-named port is honored -- at all three sites carrying the claim: the helper doc, the TESTING.md paragraph, and TestApplyConfigDefaults_NoResolvablePortFailsClosed's own comment, whose fixture (an empty beadsDir) is what excludes the surviving path. The residual stays tracked in be-rl6tm. That test's stale cross-reference to a renamed test is corrected in the same pass. Iteration 1, minor (Test Evidence Quality). The Windows gate's comment claimed a CI lane it does not have; it now states the coverage exactly -- compile-checked, not CI-executed -- and lists the four windows-latest jobs' named selectors. Iteration 1, nits. doltServerErr is read under doltServerMu via sharedContainerErr(); TestCheckDoltFn_DefaultsToRealProbe pins function identity with reflect instead of asserting non-nil, which any leaked stub satisfied. Mutation ledger (scoped `go test ./internal/testutil/`, scrubbed env; every mutant restored from a copy and verified byte-identical): a set marker spares every marked_but_divergent_var, divergent_legacy_var, variable (the i2 blocker) marker_names_neither_var and boolean_marker red on BOTH failure paths the marker covers marked_but_divergent_var, marker_names_neither_var BEADS_DOLT_PORT only and boolean_marker red on both paths presence instead of value the same red set as the first row no clear after a failed the 5 container_start_failed cases that expect container start a clear red; every not_ready case stays green start attempted before the all four incumbent fail-closed subtests and probe every not_ready case red leak a wrapper into StartSharedContainerFn_DefaultsToRealStart red startSharedContainerFn delete the hermetic ClearsAmbientPortWhenNotReady red t.Setenv, marker ambient at the fixture's port Full package green with Docker, including the real-container EnsureDoltContainerForTestMain path (43 test and subtest passes, no skips); `go test ./scripts/`, which drives test.sh, green; `GOOS=windows go vet ./internal/testutil/` clean; `tools/bazel/go_srcs.py --check` clean, and no BUILD change is due (no new files, no new non-stdlib imports). Deferred deliberately: the iteration-1 synthesis's optional windows-latest step for ./internal/testutil/. It is newly feasible -- this branch is what made the package's Windows test binary compile -- but it would also newly execute four pre-existing test functions in this package that have never run on Windows, so it belongs in its own change. RequireDoltContainer's unsynchronized doltServerErr read is base-owned and left alone for the same reason. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com> --------- Co-authored-by: Julian Knutsen <julian@gastownhall.com> Co-authored-by: Claude Opus 5 <noreply@anthropic.com> Co-authored-by: Gas City Adopt-PR <adopt-pr@gascity.local>
16 KiB
Testing Guide
TESTING.md is the single authority for test commands, test selection, and
test design in this repository. Use the commands here for local work. For the
exact command behind a current CI check, inspect its workflow and corresponding
Makefile target; the CI audit and cleanup plan are dated maintainer context.
Choose the Smallest Useful Test
Test at the lowest seam that can fail for the user-visible reason. Add a higher tier only when it covers a distinct risk that the lower tier cannot show: integration wiring, a real persistence property, a process boundary, or an external contract.
This keeps feedback fast and failures readable. It does not mean every test is a unit test: use the real boundary when the defect could live there.
| Need | Run | When |
|---|---|---|
| Docs-only validation | git diff --check, go test -tags=gms_pure_go ./test/docsync, and ./scripts/check-doc-freshness.sh |
For prose-only changes; add any generated-doc or surface-specific link check the changed paths require. Do not run the full Go suite merely because a Markdown file changed. |
| Focused red/green loop | ./scripts/test.sh -run '^TestExactName$' ./path/to/package/... |
While writing or fixing one behavior. |
| Affected-package confidence | ./scripts/test.sh ./path/to/package/... |
After the focused test passes; include directly affected neighbors when their contract changed. |
| Final Go baseline | make test |
Once after focused work on Go code is green. It applies the normal local build flags, coverage, and local skip handling. |
| Named CI wrapper | make ci-pr-core, make ci-pr-policy, or make ci-pr-lint |
Run the wrapper whose risk or surface is affected, or use it to reproduce that CI check. Do not run all three routinely for every edit. |
| Hook shims against real timeout implementations | nix flake check -L (or nix build .#checks.<system>.hook-timeout-backends -L) |
After changing the hook generator in cmd/bd/hooks.go (then make githooks-regen) or anything under .githooks/. Runs the tracked managed sections against GNU coreutils, uutils, busybox and toybox timeout — the multicalls also installed as gtimeout alone — with and without Perl, under dash, bash and busybox ash. About one deadline of wall time; needs no Go build. |
Do not replace the focused loop with repeated full-suite runs. Run the final
make test once the affected Go tests are green. For docs-only changes, use
the docs, link, and diff checks instead.
Commands and Local Environment
./scripts/test.sh is the normal runner. It sources .buildflags, creates an
isolated test environment, applies .test-skip, and defaults to a 25m
per-package Go-test timeout. The timeout is a hang backstop, not a target
runtime. Override it only when diagnosing a legitimate slow path:
TEST_TIMEOUT=30m ./scripts/test.sh ./cmd/bd/...
TEST_VERBOSE=1 ./scripts/test.sh ./cmd/bd/...
TEST_RUN='^TestExactName$' ./scripts/test.sh ./cmd/bd/...
# Equivalent command-line options.
./scripts/test.sh -v -run '^TestExactName$' ./cmd/bd/...
./scripts/test.sh -timeout 30m ./cmd/bd/...
Use the opt-in ICU regex path only when the change requires it:
make test-icu-path
It is maintainer-only and not part of normal validation. make test-full-cgo
and ./scripts/test-cgo.sh remain deprecated compatibility aliases.
Use a named specialized target only when its risk is in scope:
make test-regression
make test-upgrade
make test-cross-version
make test-migration
For a failing GitHub Actions check, follow the current workflow and its
Makefile target when exact reproduction matters. The local runner and CI
intentionally have different contracts in some cases.
Test Environment and Readiness
The runner isolates HOME, Git configuration, and Dolt state. By default its
test environment adds dolt to BEADS_TEST_SKIP; set
BEADS_TEST_ENV_RUN_DOLT=1 only when deliberately exercising the Dolt path
and its prerequisites are available. Do not make ordinary tests depend on a
developer's database, daemon, global Git configuration, or filesystem state.
To skip an optional service explicitly, use the existing skip mechanism:
BEADS_TEST_SKIP=dolt ./scripts/test.sh ./...
Tests that need a Dolt SQL server get one from internal/testutil
(EnsureDoltContainerForTestMain, RequireDoltContainer,
StartIsolatedDoltContainer[Handle], NewContainerProvider). Two backends
sit behind that API, selected by BEADS_TEST_DOLT_SERVER:
container: thedolthub/dolt-sql-serverimage through testcontainers (needs docker and the pulled image). The default under plaingo test.local: adolt sql-serverstarted by the test process from the pinned dolt CLI (BEADS_TEST_DOLT_BINARY, elsedoltonPATH; it must be the image's version). No docker. Used only when explicitly selected, undergo testandbazel testalike (a Bazel target'senv, or--test_env=BEADS_TEST_DOLT_SERVER=local); unset meanscontainer, which in a Bazel action without docker keeps the usual skip.
BEADS_TEST_REQUIRE_DOLT_CONTAINER=1 turns an unavailable backend into a
failure (per test and in every TestMain) instead of a skip; lanes that
exist to run the Dolt suites set it.
Under Bazel, bazel test //... --config=doltserver runs the Dolt-backed
suites of pr.yml's "Test (storage domain + uow)" and "Contract corpus" jobs
on the local backend (the dolt-server targets); they need no docker and
execute remotely with --config=remote-exec. --config=docker runs the same
suites on the container backend (host docker) as the A/B control.
PR Risk's heavier server tiers have configs of their own, run by bazel.yml
only with remote execution, each in a job of its own (bazel-proxied,
bazel-server-storage): --config=doltserver-proxied is the
proxied-server cmd/bd tier ("Test (Proxied Dolt Cmd N/15)",
//cmd/bd:bd_proxied_test), and --config=doltserver-integration the
server-Dolt storage tier ("Test (Server Dolt Conformance)", "Test (Server
Dolt Full Suite N/16)", //internal/storage/dolt:dolt_server_*_test), which
builds with the integration tag like --config=integration. Each shard
runs its CI job's shard script, so Bazel shard k runs the tests of job k+1.
An ambient BEADS_DOLT_SERVER_PORT or BEADS_DOLT_PORT is never honored by
the suites that call testutil.EnsureDoltContainerForTestMain. When a test
container is started, that container's port overwrites both variables; when one
cannot be started -- for any reason, including BEADS_TEST_SKIP=dolt -- both
are cleared, so no environment-named server can be resolved. Point a test run
at a specific Dolt server by starting a container for it, not by exporting a
port.
The one sanctioned way to hand these suites a server you started yourself is
./scripts/test.sh with BEADS_TEST_SHARED_SERVER=1: it starts one
dolt sql-server, exports its port as BEADS_DOLT_PORT, and marks it by
exporting BEADS_TEST_SHARED_DOLT_SERVER set to that same port number. It
starts nothing if either port variable is still set when it gets there. The
runner's test environment clears both first, so that only happens when that
isolation is skipped (for example BEADS_TEST_ENV_DISABLE=1), and the script
then says so on stderr. The marker -- set only by that script, only for a
port it allocated -- is what the helper treats as container-equivalent, and
only for a variable holding exactly the port it names: that variable survives
the clearing above, and any other port variable is still cleared. A container
still wins where one can be started; the shared server is the Docker-less path.
Clearing the environment variables closes the channel the ambient port
travelled on; it does not make a port unresolvable in general. Resolution
continues into the file chain (.beads/dolt-server.port, config.yaml,
metadata.json), and internal/storage/dolt's production-port detection is
narrower than that resolution -- see be-rl6tm, which tracks the remaining
gap.
Tests that need a temporary repository or store should use t.TempDir() and
t.Cleanup(). Temporary repositories must set a repository-local hooks path;
do not inherit the developer's global hooks configuration.
In cmd/bd, fresh-workspace command fixtures should call
isolateBeadsDirForTest(t) before setup or dispatch. It clears inherited
BEADS_DIR and restores that variable exactly at cleanup, even after raw
command-dispatch mutations. The TestMain reset only isolates startup.
These fixtures must not use t.Parallel(). Tests intentionally selecting a
workspace should use t.Setenv("BEADS_DIR", ...); initConfigForTest and
ensureCleanGlobalState preserve that selection.
For manual CLI experiments, run both initialization and subsequent commands from a disposable working directory:
beads_manual_dir="$(mktemp -d)"
(
set -e
cd "$beads_manual_dir"
bd init --quiet --prefix test --skip-hooks --skip-agents
bd create "Test issue" -p 1
)
rm -rf -- "$beads_manual_dir"
BEADS_DB selects a database for database-opening commands, but it does not by
itself redirect bd init workspace setup. Never run a manual bd init from a
production workspace merely because BEADS_DB points elsewhere.
testing.Short() is for genuine runtime, stress, or large-fixture skips. It
is not a substitute for declaring an integration, end-to-end, API, Docker, or
external-dependency boundary. Keep new uses within the repository policy:
make check-testing-short
Dolt Container Tests (podman-rootless)
Anything that does not carry BEADS_TEST_SKIP=dolt — including
BEADS_TEST_ENV_RUN_DOLT=1 and a bare go test — reaches a real
dolt sql-server: by default through testcontainers-go where a container
runtime and the pinned image are present (otherwise those suites self-skip),
and from the local dolt CLI in the suites that use
testutil.RequireDoltBinary. Lanes that set
BEADS_TEST_REQUIRE_DOLT_CONTAINER=1 fail instead of skipping. Two limitations
of the containerized path are worth recognizing before reading a failure as a
product bug. Neither failure mode manifests in production or on GitHub Actions:
CI exercises this same containerized path green on every risk-tier PR, and
.github/workflows/pr-risk.yml pulls the pinned image precisely to defeat the
self-skip. A hang there is a real bug, not this section's subject.
Migration 0032 hangs over the wire protocol. Migration 0032
(drop_schema_migrations_applied_at) hangs indefinitely when applied through
the containerized sql-server. How it surfaces depends on the caller's context.
A go test ./internal/storage/uow/... -count=1 with no BEADS_TEST_SKIP
passes context.Background(), so it sits in initSchema until the package
timeout rather than failing — that is the shape you will normally see, with no
deadline to cut it short. A caller that does supply one gets the hang reported
by the server-mode store open (newServerMode in
internal/storage/dolt/store.go) instead:
failed to initialize schema: context deadline exceeded
The cause is the podman-rootless container port-forwarding path, not migration
0032's SQL: the identical statement completes normally through the embedded/CLI
engine, and against a bare-host-process dolt sql-server matching the deployed
shape. Evidence chain in be-j3szz. Use BEADS_TEST_SKIP=dolt unless the
container path is what you are testing.
Disabling Ryuk removes the container safety net. This repository sets no
TESTCONTAINERS_RYUK_DISABLED, so CI runs with Ryuk — testcontainers-go's
orphan-reaper sidecar — enabled. The podman-rootless flow generally requires
turning it off by hand (TESTCONTAINERS_RYUK_DISABLED=true), because under
rootless podman Ryuk frequently cannot start: it wants the runtime socket. See
be-w3n2m. With Ryuk off, nothing reaps a container whose test process exited
without running its cleanup — os.Exit reached before a deferred
TerminateDoltContainer, for instance. be-5kkk6 records the cost: 101 leaked
containers, and an exhausted swap. When running with Ryuk disabled, keep
teardown on the normal return path using the testMainInner pattern
(beads_test.go), and check for strays afterwards. Carry the rootless socket
this flow runs on — a bare docker ps talks to the CLI's default endpoint and
reports a false all-clear — and read the tag from the pin rather than copying
it, so the command cannot drift when the pin moves. An empty read would be the
same false all-clear (ancestor= matches nothing), so the command refuses to
run without a tag:
dolt_image=$(sed -n 's/.*DoltDockerImage = "\(.*\)".*/\1/p' \
"$(git rev-parse --show-toplevel)/internal/testutil/testdoltcommon.go")
DOCKER_HOST=unix:///run/user/$(id -u)/podman/podman.sock \
docker ps -a --filter "ancestor=${dolt_image:?could not read the Dolt image pin}"
Test Design
Seams, Scenarios, and Doubles
Write one scenario at the smallest seam that demonstrates the behavior. Cover the boundary or failure mode that changes the user result; use table-driven subtests when examples share setup. Do not repeat the same scenario through a helper, every caller, and the CLI merely because all are available.
A recording double or fake should be narrow: model only the calls, inputs, outputs, and failures the test needs. It should not recreate a storage engine, process manager, or another subsystem just to make a unit test look realistic.
A behavioral fake is different. If it stands in for a contract shared by multiple production implementations, give it the same semantic-conformance suite as those implementations. That shared suite defines observable behavior; it prevents the fake from teaching callers a contract production code does not honor.
Semantic conformance asks whether an implementation produces the promised results, errors, and state transitions for the same operation. Persistence conformance asks whether the real persistence boundary preserves its required durability, transaction, migration, and recovery properties. They answer different questions. Do not claim backend parity unless a stated contract and its conformance suite establish it.
Tier Admission
An integration test belongs above the unit seam only when it covers a distinct boundary that a narrow double cannot prove, such as configuration wiring, a real filesystem or Git interaction, a subprocess protocol, or persistence behavior.
An end-to-end test is admitted only when all of these are true:
- The failure would be user-visible.
- A real process, setup, or wiring boundary owns a distinct failure risk that no lower seam can prove.
- Lower-tier tests cover the underlying behavior where practical, leaving the end-to-end test focused on that boundary.
- No existing end-to-end test already covers the same boundary risk.
Lower-tier coverage of the same user journey does not disqualify the end-to-end test; duplicate coverage of the same boundary risk does. State that risk in the test name or nearby documentation.
Avoid Incidental Complexity
Avoid these patterns unless they are the behavior under test:
- Duplicate scenarios at several layers.
- Global-state reset choreography. Prefer per-test state and cleanup.
- Subprocesses, listeners, sleeps, or real-store setup for a unit-level claim.
- Assertions on private implementation shape when observable behavior is the contract.
- Performance claims without a repeatable measurement and stated workload.
Sleeps, listeners, and real stores are appropriate when the test is specifically about timing, lifecycle, protocol, or persistence. Keep the setup scoped and make that reason apparent.
Failures, Skips, and Review
.test-skip is a local, temporary exception list. If an unrelated failure is
already listed, report it rather than silently broadening the skip. Before
adding a new skip, record the issue it tracks and remove the skip when the
underlying failure is fixed.
Before opening a PR:
- For docs-only changes, run the applicable docs, link, freshness, and diff checks; do not run the full Go suite by default.
- For Go code, keep the focused and affected-package tests green, then run one
final
make test. - Run only the named CI wrapper, specialized target, or risk gate required by the changed surface, or the one needed to reproduce a CI result.
For historical CI inventory and maintainer planning context, consult
CI_TEST_SURFACE_AUDIT.md and
CI_CLEANUP_PLAN.md. For current commands, use the
workflow files and Makefile; these context documents are not a second testing
guide or a live CI inventory.