mirror of https://github.com/rustfs/rustfs.git synced 2026-10-27 14:27:10 +00:00

Files

T

Chris ea596b2e2d fix(decommission): adopt target intents left by a killed leader (#8710 )

* fix(decommission): adopt target intents left by a killed leader

A decommission leader killed after persisting a target capacity intent and
before finalizing it left that intent in the exclusive pending slot of the
still-active reservation. The resumed routine derives the same reservation
identity, but every other mutation on that target was rejected as "another
mutation" until the interrupted object happened to be retried on the same
target, so the resumed decommission exhausted its retries and stalled.

At routine start, before any worker runs, the resumed routine now adopts the
reservation's pending intents: under the target fence (or the legacy pool
metadata fence) it moves each one into a mutation-scoped inflight marker that
keeps its identity and bytes. The interrupted mutation's retry settles the
marker through the existing commit, temporary-release and equivalent-target
paths, and an equivalent committed target now settles a mutation's own marker
when no pending intent remains. Adoption is pinned to the persisted
decommission start time and reservation identity, never runs mid-incarnation,
and a failure pauses the routine instead of marking the decommission failed.

* fix(decommission): keep adopted intents within budget and settle them once

Address the adversarial review of the leftover intent adoption.

- Merge an adopted intent into its mutation's staged marker by summing only
  while the target's temporary-copy budget allows, never below the larger of
  the two. A multipart completion moves its staged parts into the object, so
  summing them could exceed the budget and pause every later routine start;
  the adopted marker now exceeds the budget only where the completion's own
  finalize would have. Reuse resolve and record_inflight for the move.
- Distinguish a temporary release that proved the exact committed target from
  one that could not prove the target identity. When the committed mutation no
  longer has a pending intent, release only the bytes the cleanup freed and
  keep the adopted completion for the equivalent-target reconciliation.
- Let an equivalent target settle a mutation's own marker while another
  mutation holds the pending slot, instead of failing on that unrelated intent.
- Cover real leader kills before and after the target commit at routine level
  for both lock models, an injected adoption failure that pauses and then
  completes, an adopted multipart completion surviving a background abort, and
  a live legacy intent. Routine tests reuse the large-stack test helper.

* fix(decommission): pause instead of failing on target slot contention

The S00 leader-kill run with the null-version fix merged ended the resumed
decommission as failed. A re-run of a versioned key reconciled its delete
marker against an already charged target copy while another worker of the
same incarnation held the target's pending slot between a failed write and
its retry. The reconciliation rejected that unrelated intent, the entry
context wrapper flattened the error to a string the intent-conflict retry
could not recognize, and the bucket runner reported a sibling bucket's
OperationCanceled instead of the capacity block, so the routine marked the
decommission failed.

- An equivalent-target reconciliation, including the temporary checkpoint
  variant, no longer depends on another mutation's pending intent: a target
  holds one pending intent at a time, so this mutation has none to settle.
- The entry context keeps the typed cause, and the capacity-block and
  intent-conflict classifiers also recognize the rendered message that an
  error clone keeps.
- Concurrent bucket and listing failures keep the root cause over sibling
  cancellations, so a capacity block pauses the routine.

* test(decommission): delete marker copy waits for a busy target gate

The Linux run of the S00 matrix showed the delete marker copy meeting a busy
target capacity gate without any leader kill. The copy already waits on that
gate like an ordinary object copy; pin it with an entry-level test that holds
the gate, checks the entry keeps waiting, and expects the key to migrate once
the gate is released. Share the versioned delete marker fixture with the
foreign pending slot test.

* fix(decommission): keep an adopted completion unless the target is absent

Close the remaining path where an adopted completion could lose its record
before being charged. A multipart cleanup that found a target it could not
prove as the exact owned copy still dropped the whole marker of a mutation
without a pending intent, after which the equivalent-target reconciliation
would treat the commit as already charged.

Any cleanup that did not prove the exact target absent now releases only the
bytes it freed when the mutation has no pending intent, and leaves the rest
for the reconciliation. This makes the three-state release unnecessary, so
the release proof goes back to the existing clear-pending flag.

* chore(ci): shrink the error format ratchet baseline for pools.rs

9eae47ce8 removed one Error::other(format!) call site from crates/ecstore/src/core/pools.rs, so the ratchet requires the baseline to drop from 178 to 177.

* fix(decommission): keep adopted completions in their own capacity marker

An adopted completion shared the mutation's staged marker, so whether
it survived a cleanup depended on the pool-wide free-space delta, and a
cleanup that freed little space left staged bytes behind and repeated
forever.

Record each adopted intent under a mutation id derived from the
interrupted mutation (decommission_adopted_intent_mutation_id) as a
separate temporaryMutations entry. A commit or an equivalent-target
reconciliation settles both markers, a temporary cleanup releases the
staged marker as before, and only a cleanup that proved the exact
target absent drops the adopted one. While the target holds only that
adopted completion, a cleanup keeps the delayed-release exemption of
the published pending intent it replaced. Older nodes see an ordinary
temporary mutation they never release, which only over-reserves.

Also log capacity_intents_adopted as soon as the adopted ledger is
durable, merge the root-cause helpers into decommission_root_cause,
drop the decommission_capacity_blocked: prefix fallback, and log the
already-charged equivalent-target branch at debug level.

Refs rustfs/backlog#2873, rustfs/backlog#2872

* fix(decommission): return uncommitted retries to their adopted target

A retry that had not committed yet went to the reserved target with the
most remaining allocation. When that was not the target holding the
mutation's adopted completion, the commit settled only its own target
and the adopted marker stayed inflight until the reservation was
released.

Prefer a reserved target that holds the mutation's adopted marker while
it still fits the object (decommission_reserved_target_choice).

Also cover the remaining settlement paths of the derived marker
(non-growing replacement, equivalent temporary reconciliation and its
discovery gate, scanner backlog retirement), repeated adoption of one
mutation and the zero-byte staging record in both lock models, drop two
conditions that always equal another one, and correct the adopted-id
doc comment about nodes without adoption.

Refs rustfs/backlog#2873, rustfs/backlog#2872

* fix(decommission): count a completion adopted twice only once

A mutation killed twice leaves an adopted completion and then a new
intent for the same object version. Adoption added the two, so an
11-byte object counted 22 inflight bytes and could trip the capacity
check once later commits shrank the budget. Both reserve the same
completion, so merge them by their maximum before adding staged parts;
a single adoption is unchanged.

Also assert in the three-pool sticky test that no entry failed, the
retry is charged on its adopted target and the source is cleaned, run
it for the legacy lock model too, stop saying operators rely on the
adoption log before rollback, and document that the selection fallback
cannot help an adopted completion.

Refs rustfs/backlog#2873, rustfs/backlog#2872

* fix(decommission): log where an adopted retry is placed

An e2e run could not show whether a resumed retry went back to the
target holding its adopted completion. Target selection now logs
adopted_target_reused when it does, and adopted_target_bypassed with
the adopted target pools when the object no longer fits there and the
adopted marker stays behind. Both carry the mutation id and the source
and target pools.

Refs rustfs/backlog#2873, rustfs/backlog#2872

2026-10-20 11:28:22 +09:00

README.md

scripts/ index

Authoritative inventory of everything under scripts/ (backlog#1153 infra-13). One row per top-level entry; subdirectories get one row each and keep their own READMEs. The test-layer map that ties the major runners together lives in docs/testing/README.md.

Statuses

ci-gate — wired into CI, release, or image-build pipelines. Do not move, rename, or change flags without updating the wiring listed in the last column.
dev-tool — run by humans: local dev loops, runbooks, validation harnesses. Kept working, not wired into CI.
archived — one-shot scripts whose investigation/issue is finished, moved to scripts/archive/. Unmaintained reference material: never wire into CI, and expect bit-rot. To resurrect one, move it back and give it an index row here.

Adding a script? Add an index row in the same PR. Issue-scoped scripts (run_issueNNN_*, validate_issue_NNN_*) are expected to be archived when their issue closes.

Repository & CI gates

Entry	Status	Purpose	Wiring / docs
`check_architecture_migration_rules.sh`	ci-gate	Architecture-boundary anti-regression guard	ci.yml Quick Checks; `make pre-commit`
`check_body_cache_whitelist.sh`	ci-gate	Keeps the app-layer body-cache eligibility gate fail-closed	ci.yml Quick Checks
`check_doc_paths.sh`	ci-gate	Fails when instruction/architecture docs reference repo paths that no longer exist	`make pre-commit` / `pre-pr`
`check_embedded_secrets.sh`	ci-gate	Repo-wide scan blocking committed private key material and provider credential literals	ci.yml Quick Checks; `make pre-commit` / `pre-pr`
`check_extension_schema_boundaries.sh`	ci-gate	Extension-schema crate boundary guard	ci.yml Quick Checks; `make pre-commit`
`check_layer_dependencies.sh`	ci-gate	Crate-layering DAG guard (reads `layer-dependency-baseline.txt`)	ci.yml Quick Checks
`check_logging_guardrails.sh`	ci-gate	Blocks legacy logging patterns from returning	`make pre-commit` / `pre-pr`
`check_migration_gate_count.sh`	ci-gate	Migration-critical test gate with committed count floor (`.config/migration-gate-floor.txt`)	ci.yml Test and Lint; `docs/testing/README.md`
`check_no_planning_docs.sh`	ci-gate	Blocks committed planning-type documents	ci.yml Quick Checks; `make pre-commit`
`check_no_tokio_io_uring.sh`	ci-gate	Keeps tokio's io-uring backend disabled	ci.yml Quick Checks
`check_s3s_footprint.sh`	ci-gate	Lower-only ratchet freezing the direct s3s surface ahead of the s3gate migration	ci.yml Quick Checks; `make pre-commit`
`check_unsafe_code_allowances.sh`	ci-gate	Unsafe-code allowance ledger guard	ci.yml Quick Checks
`layer-dependency-baseline.txt`	ci-gate (data)	Committed baseline consumed by `check_layer_dependencies.sh`	Architecture guard troubleshooting
`static.sh`	ci-gate	Static-build helper executed inside image builds	`Dockerfile.source`, `Dockerfile.decommission-local`
`helm_chart_version.sh`	ci-gate	Keeps the Helm chart version in sync with the release	helm-package.yml
`test_helm_templates.sh`	ci-gate	Helm template rendering test	helm-package.yml

Test & e2e runners

Entry	Status	Purpose	Wiring / docs
`diagnose_scanner_enumeration_restart.py`	dev-tool	Strict fixed raw-entry-budget scanner-worker restart diagnostic	Checkpoint fixture
`prepare_replacement_migration.py`	dev-tool	Prepares digest-bound schema 5/6 replacement maintenance approvals	Replacement recovery
`test_prepare_replacement_migration.py`	dev-tool	Verifies maintenance approval scope, publication, and stopped-writer assertion	Python unittest; same runbook
`test_diagnose_scanner_enumeration_restart.py`	dev-tool	Driver report validation and positive convergence oracle tests	Python unittest; same guide
`test_object_generation_protocol_model.py`	dev-tool	Bounded single-slot, four-voter promise/accept design model and recovery/retirement examples; no production runtime evidence	`python3 scripts/test_object_generation_protocol_model.py`; Generation contract
`e2e-run.sh`	ci-gate	Boots a rustfs server and runs the `s3s-e2e` black-box conformance tool against it	ci.yml `e2e-tests` jobs; `docs/testing/README.md`
`run_ecstore_validation_suite.sh`	dev-tool	ecstore black-box validation suite (`quick`/`full`/`destructive`/`fuzz` profiles)	`docs/testing/README.md`, `docs/testing/ecstore-validation-suite-design.md`
`run_e2e_tests.sh`	dev-tool	Local `e2e_test` crate runner (starts a server, applies filters, cleans up)	`crates/e2e_test/README.md`
`run.sh`	dev-tool	Local rustfs startup wrapper	`make e2e-server`; Justfile
`run.ps1`	dev-tool	Windows counterpart of `run.sh`	—
`probe.sh`	dev-tool	Probe-style e2e run	`make probe-e2e`
`run_scanner_validation_harness.sh`	dev-tool	Scanner validation harness	`docs/operations/scanner-benchmark-runbook.md`
`check_test_wiring.py`	dev-tool	Validates test wiring and assembles one or more measured Scanner/Heal release descriptors into a single release evidence bundle	`.config/scanner-heal-required-tests.json`; `check_test_wiring.py --self-test`
`run_scanner_heal_evidence_case.sh`	dev-tool	Runs one Scanner/Heal release-evidence registry case and checks the produced receipt/oracle	`.config/scanner-heal-required-tests.json`; `check_test_wiring.py --check-scanner-heal`
`run_scanner_heal_authority_evidence.py`	dev-tool	Assembles measured Scanner/Heal G01 root/quota authority release descriptors from operator-collected authority artifacts	`.config/scanner-heal-required-tests.json`; `test_scanner_heal_authority_evidence.sh`
`run_scanner_heal_checkpoint_crash_evidence.py`	dev-tool	Assembles measured Scanner/Heal G02/R-E checkpoint and restart release descriptors from scanner restart diagnostic reports	`diagnose_scanner_enumeration_restart.py`; `test_scanner_heal_checkpoint_crash_evidence.sh`
`run_scanner_heal_g14_multiset_evidence.py`	dev-tool	Assembles measured Scanner/Heal G14 same-window EC8+4 multi-set/multi-pool release descriptors from e2e case directories or an operator-collected proof	`.config/scanner-heal-required-tests.json`; `test_scanner_heal_g14_multiset_evidence.sh`
`run_scanner_heal_g09_upgrade_evidence.sh`	dev-tool	Runs the G09 mixed-version and rollback upgrade E2E lanes against a pinned previous release and verifies the raw evidence artifacts	`docs/testing/ci-gates.md`; `.github/workflows/e2e-upgrade.yml`; `test_scanner_heal_g09_upgrade_evidence.sh`
`run_scanner_heal_linux_evidence_plan.py`	dev-tool	Writes the unified Scanner/Heal Linux release-evidence execution manifest and can run lightweight preflight checks without producing measured evidence	`docs/testing/ci-gates.md`; `test_scanner_heal_linux_evidence_plan.sh`
`run_scanner_heal_scoped_ack_evidence.py`	dev-tool	Assembles measured Scanner/Heal G03 scoped ACK publication and mixed-peer fallback release descriptors	`.config/scanner-heal-required-tests.json`; `test_scanner_heal_scoped_ack_evidence.sh`
`run_scanner_heal_legacy_rollback_evidence.py`	dev-tool	Assembles measured Scanner/Heal R-L legacy source-conflict, migration-gap, and source-retirement release descriptors	`.config/scanner-heal-required-tests.json`; `test_scanner_heal_legacy_rollback_evidence.sh`
`run_scanner_heal_mrf_evidence.py`	dev-tool	Assembles measured Scanner/Heal G07/G08/P4 MRF release descriptors from W13 raw artifacts	`.config/scanner-heal-required-tests.json`; `test_scanner_heal_w13_mrf_evidence.sh`
`run_scanner_heal_scheduler_pressure_evidence.py`	dev-tool	Assembles measured Scanner/Heal G10/P1/P3 scheduler-pressure release descriptors from a completed measured ABBA run, recovery-window proof, and profile artifacts	`docs/operations/scanner-benchmark-runbook.md`; `test_scanner_heal_scheduler_pressure_evidence.sh`
`run_scanner_heal_status_outcome_probe.py`	dev-tool	Normalizes live Scanner/Heal status/outcome observations into the measured G05/G06/R-D raw artifacts consumed by the descriptor producer	`.config/scanner-heal-required-tests.json`; `test_scanner_heal_status_outcome_evidence.sh`
`run_scanner_heal_status_outcome_evidence.py`	dev-tool	Assembles measured Scanner/Heal G05/G06/R-D status-and-outcome release descriptors from same-run status, compatibility, and disposition artifacts	`.config/scanner-heal-required-tests.json`; `test_scanner_heal_status_outcome_evidence.sh`
`run_scanner_heal_maintenance_evidence.py`	dev-tool	Assembles measured Scanner/Heal G11/G13 maintenance-producer release descriptors from operator-collected proof JSON	`.config/scanner-heal-required-tests.json`; `test_scanner_heal_maintenance_evidence.sh`
`run_scanner_heal_w13_mrf_evidence.sh`	dev-tool	Runs the W13 durable MRF replay lanes and writes G07/G08/P4 bundle-ready evidence descriptors	`docs/testing/ci-gates.md`; `test_scanner_heal_w13_mrf_evidence.sh`
`run_scanner_heal_w16_recovery_evidence.sh`	dev-tool	Runs the W16 recovery-intent and quota authority lanes and writes G04/G12 bundle-ready evidence descriptors	`docs/testing/ci-gates.md`; `test_scanner_heal_w16_recovery_evidence.sh`
`test_scanner_validation_harness.sh`	dev-tool	Self-test for the scanner validation harness	—
`test_scanner_heal_checkpoint_crash_evidence.sh`	dev-tool	Shell self-test for the Scanner/Heal checkpoint/crash evidence assembler	—
`test_scanner_heal_authority_evidence.sh`	dev-tool	Shell self-test for the Scanner/Heal G01 authority evidence assembler	—
`test_scanner_heal_scoped_ack_evidence.sh`	dev-tool	Shell self-test for the Scanner/Heal G03 scoped ACK evidence assembler	—
`test_scanner_heal_legacy_rollback_evidence.sh`	dev-tool	Shell self-test for the Scanner/Heal R-L legacy rollback evidence assembler	—
`test_scanner_heal_g14_multiset_evidence.sh`	dev-tool	Shell self-test for the Scanner/Heal G14 multi-set/multi-pool evidence assembler	—
`test_scanner_heal_scheduler_pressure_evidence.sh`	dev-tool	Shell self-test for the Scanner/Heal scheduler-pressure evidence assembler	—
`test_scanner_heal_status_outcome_evidence.sh`	dev-tool	Shell self-test for the Scanner/Heal status-and-outcome evidence assembler	—
`test_scanner_heal_maintenance_evidence.sh`	dev-tool	Shell self-test for the Scanner/Heal G11/G13 maintenance evidence assembler	—
`test_scanner_heal_g09_upgrade_evidence.sh`	dev-tool	Shell self-test for the Scanner/Heal G09 upgrade evidence runner	—
`test_scanner_heal_w16_recovery_evidence.sh`	dev-tool	Shell self-test for the Scanner/Heal W16 recovery evidence runner	—
`test_scanner_heal_w13_mrf_evidence.sh`	dev-tool	Shell self-test for the Scanner/Heal W13 MRF evidence runner	—
`scanner_abba.py`	dev-tool	Scanner/heal ABBA orchestration and evidence gates via `run_scanner_validation_harness.sh --abba`	`docs/operations/scanner-benchmark-runbook.md`
`test_scanner_abba.py`	dev-tool	Synthetic ABBA adapter and failure-path tests	`test_scanner_validation_harness.sh`
`test_build_rustfs_options.sh`	dev-tool	Shell test for rustfs build-option wiring	`make test` (script-tests)
`test_entrypoint_credentials.sh`	dev-tool	Container entrypoint credential-handling test	`make test` (script-tests)
`test_helm_chart_version.sh`	dev-tool	Test for `helm_chart_version.sh`	—
`test_package_service_scripts.sh`	ci-gate	Verifies DEB/RPM install, upgrade, removal, and service restart scriptlets	audit.yml `workflow-pin-report`
`test_package_versions.sh`	ci-gate	Exact-output and fail-closed tests for DEB/RPM package version normalization	audit.yml `workflow-pin-report`; package.yml RPM build
`windows-sftp-listener-smoke.sh`	dev-tool	Confirms `rustfs.exe --features sftp` binds an SFTP listener on Windows	—

Benchmark & performance harnesses

Entry	Status	Purpose	Wiring / docs
`run_hotpath_warp_ab.sh`	dev-tool	Linux warp A/B rig for the hotpath series (quick local A/B)	`docs/operations/hotpath-warp-ab-runbook.md`
`run_hotpath_warp_abba.sh`	ci-gate	Formal ABBA warp runner (baseline/candidate interleaved, `--rounds >= 3`); the runner performance-ab.yml executes	performance-ab.yml (scheduled); `docs/operations/hotpath-warp-ab-runbook.md`
`hotpath_warp_ab_gate.sh`	dev-tool	Relative-budget gate evaluated over the warp A/B results	used by `run_hotpath_warp_ab.sh`; hotpath runbook
`run_internode_grpc_ab_bench.sh`	dev-tool	One-click A/B driver for the internode gRPC optimization stages	`docs/operations/internode-grpc-benchmark-runbook.md`
`run_internode_transport_baseline.sh`	dev-tool	Internode transport baseline runner	internode runbook; `crates/io-metrics/README.md`
`run_four_node_cluster_failover_bench.sh`	dev-tool	Four-node cluster failover benchmark	`docker/compose/README.md`; internode runbook
`run_object_batch_bench.sh`	dev-tool	Batch object benchmark runner (warp/s3bench)	internode + scanner runbooks
`run_object_batch_bench_enhanced.sh`	dev-tool	Enhanced batch benchmark runner; hub used by the smoke rigs	hotpath runbook
`run_pinned_paired_abba_bench.sh`	dev-tool	Pinned RustFS/MinIO paired ABBA benchmark orchestrator for backlog#1432	`test_pinned_paired_abba_bench.sh`
`prepare_conditional_read_baseline.py`	dev-tool	Installs only the matching conditional-read benchmark harness in a clean detached baseline	`docs/testing/conditional-read-benchmark.md`
`run_conditional_read_abba.py`	dev-tool	Serial ordinary/hit/miss GET ABBA with cache/slow-disk controls and drift/regression gates	`docs/testing/conditional-read-benchmark.md`
`test_conditional_read_abba.py`	dev-tool	Parser, drift rejection, and throughput/lock regression tests for conditional-read evidence	`run_conditional_read_abba.py`
`run_get_codec_streaming_smoke.sh`	dev-tool	Local GET benchmark harness for the codec streaming read path	`docs/testing/ecstore-validation-suite-design.md`
`run_get_1mib_abba_stage_metrics.sh`	dev-tool	Exact-1MiB isolated-host GET ABBA/stage-metrics harness for backlog#1434	`test_get_1mib_abba_stage_metrics.sh`
`issue_2007_coalescer_prometheus_report.py`	dev-tool	Read-only Prometheus report for GET metadata coalescer delay cost validation; usage in the module docstring	`test_issue_2007_coalescer_prometheus_report.sh`
`prometheus_metrics_1649_smoke.py`	dev-tool	Read-only Prometheus instant-query smoke check for the backlog#1649 metric dimensions, required labels, and retired series; usage in the module docstring	`--self-test`
`run_gt1g_get_http_matrix.sh`	dev-tool	>1 GiB GET HTTP matrix	`docs/testing/ecstore-validation-suite-design.md`
`run_gt1g_multipart_put_matrix.sh`	dev-tool	>1 GiB multipart PUT matrix	`docs/testing/ecstore-validation-suite-design.md`
`sample_remote_rustfs_rss.sh`	dev-tool	Remote RustFS PID CPU/RSS TSV sampler for hotpath profiling runs	`test_sample_remote_rustfs_rss.sh`; backlog#1647
`summarize_samply_profile_symbols.py`	dev-tool	Offline samply `profile.json.gz` + `.syms.json` function-level hotpath summarizer	`test_summarize_samply_profile_symbols.py`; backlog#1647
`run_scanner_benchmarks.sh`	dev-tool (disposition pending)	Scanner performance benchmark runner. Contains a hardcoded stale path; disposition owned by backlog perf-10 — do not fix, move, or delete it here	—

Local development & operations

Entry	Status	Purpose	Wiring / docs
`dev_clear.sh`	dev-tool	Local dev cleanup. `scripts/dev_*.sh` is a CI paths-filter glob — keep the naming	ci.yml/build.yml paths filters
`dev_deploy.sh`	dev-tool	Copy a built binary to dev servers	`make deploy` (`.config/make/deploy.mak`); Justfile
`dev_rustfs.sh`	dev-tool	Local dev run loop	—
`dev_rustfs.env`	dev-tool (data)	Env presets for the dev scripts	—
`restart_local_single_node_multidisk_rustfs.sh`	dev-tool	Restart a local single-node multi-disk instance	—
`inspect_dashboard.sh`	dev-tool	Sanity-checks the Grafana dashboard JSON	`.docker/observability`
`notify.sh`	dev-tool	Starts a local webhook receiver for notify-target development	—
`manual_transition_debug.sh`	dev-tool	Log/metrics helper for manual transition troubleshooting	—
`manual_transition_journal_audit.sh`	dev-tool	Journal + metrics + log audit for manual transition jobs	—
`manual_transition_mixed_rollout_matrix.sh`	dev-tool	Matrix generator for mixed-version rollout phases	—
`manual_transition_mixed_rollout_runbook.sh`	dev-tool	Reusable mixed-version rollout runbook generator (external run)	—
`manual_transition_mixed_version_docker_harness.sh`	dev-tool	Dedicated #1508 Docker harness for old/new manual-transition rollout evidence with strict/baseline/blocked result classification	`test_manual_transition_runbooks.sh`
`monitor_manual_transition_ci.sh`	dev-tool	CI workflow/status watcher for manual transition follow-up monitoring	—
`manual_transition_soak_matrix.sh`	dev-tool	Matrix generator for nightly stress windows	—
`manual_transition_nightly_stress_runbook.sh`	dev-tool	Nightly stress entrypoint with failure snapshot templates	—
`install-flatc.sh`	dev-tool	Local flatc installer (macOS)	—
`install-protoc.sh`	dev-tool	Local protoc installer (macOS/Linux)	—
`cargo_publish_workspace.sh`	dev-tool	Generates the workspace crate publish order, checks existing registry versions, and optionally runs ordered `cargo publish` dry-runs or publication	`docs/operations/cargo-publish-workspace.md`
`makefile-header.sh`	dev-tool	Generates the `## —— section ——` header lines used in `.config/make/*.mak`	—
`tls_gen.md`	dev-tool (doc)	Notes on generating local TLS certificates	—

Subdirectories

Entry	Status	Purpose	Wiring / docs
`fuzz/`	ci-gate	Unified cargo-fuzz runner and helpers for the `fuzz/` sub-workspace	fuzz.yml; `fuzz/README.md`
`release/`	ci-gate	Release creation and DEB/RPM version-normalization helpers	build.yml; package.yml
`s3-tests/`	ci-gate	ceph/s3-tests compatibility harness (allow-lists, patches, report tooling)	ci.yml; e2e-s3tests.yml; `scripts/s3-tests/README.md`
`security/`	ci-gate	Workflow-pin enforcement and release supply-chain asset generation	audit.yml; build.yml
`table-catalog/`	dev-tool	S3-Tables / pyiceberg validation suite	`docs/architecture/s3-tables-support-matrix.md`
`test/`	dev-tool	Manual operational validation runbooks (decommission, tier lifecycle), paired `.sh` + `.md`	—
`archive/`	archived	Retired one-shot scripts (see below)	—

Archived (scripts/archive/)

Moved 2026-07 (backlog#1153 infra-13) after a whole-tree reference census: each entry had zero references from CI, Makefiles, docs, or code — or was referenced only by other scripts in this same archived set. Reasons:

Entry	Was
`validate_issue_785_list_objects.sh`	One-shot issue validation (list-objects series)
`validate_issue_786_list_objects.sh`	One-shot issue validation (list-objects series)
`validate_issue_787_list_quorum.sh`	One-shot issue validation (list-quorum)
`validate_issue_841_list_objects_observability.sh`	One-shot issue validation (list observability)
`validate_issue_1365_docker.sh`	One-shot issue validation (docker repro)
`validate_issue_2723_site_replication.sh`	One-shot issue validation (site replication)
`validate_issue_3031_docker.sh`	One-shot issue validation (docker repro)
`run_issue712_deeper_zero_copy_put_with_capture.sh`	One-shot perf capture for backlog#712
`run_issue797_local_4node_16disk_ab.sh`	One-shot 4-node/16-disk A/B for backlog#797
`run_issue_2573_acceptance.sh`	One-shot acceptance run for issue #2573
`run_issue_2941_perf_capture.sh`	One-shot perf capture for issue #2941
`run_put_large_stage_breakdown.sh`	backlog#706 large-PUT stage breakdown (family)
`run_put_large_stage_breakdown_with_capture.sh`	backlog#706 one-shot wrapper (family)
`run_put_large_tuning_matrix.sh`	backlog#706 tuning matrix (family)
`collect_put_large_stage_breakdown_artifacts.sh`	backlog#706 artifact collector (family)
`analyze_put_service_metrics_deltas.py`	backlog#706 metrics-delta analyzer (family)
`README-stress-test.md`	GET-optimization one-shot suite doc
`stress-test-get-optimization.sh`	GET-optimization one-shot stress test
`quick-validate-get-optimization.sh`	GET-optimization one-shot validation
`benchmark-sf-optimization.sh`	GET-optimization one-shot benchmark
`prepare_gt1g_get_test_objects.sh`	>1 GiB GET investigation one-shot fixture prep
`run_gt1g_multipart_put_server_path_focus.sh`	>1 GiB PUT investigation one-shot focus run
`run_get_metrics_gate_smoke.sh`	One-shot GET metrics-gate smoke
`run_listobjects_verified_bench.sh`	One-shot verified list-objects bench
`run_object_batch_bench_abc.sh`	One-shot capacity/object profile A/B/C controller
`run_object_data_cache_bench.sh`	One-shot GET bench for the object-data-cache rollout gate
`setup-test-binaries.sh`	One-shot Docker-build test binary fixture
`test.sh`	Ancient manual `mc` bucket smoke scratchpad
`test_policy.json`	Orphaned IAM policy fixture (hardcoded test bucket)