# 1.0.0-beta.14 Benchmark Suite Catalog And Metadata Gate

Status: release scope for `1.0.0-beta.14`.

`1.0.0-beta.14` is a docs/tooling metadata slice for the existing benchmark
suite. It keeps the `1.0.0-beta` source language, typed core, runtime,
standard library, API surface, compiler diagnostics, diagnostic output shape,
ABI/layout behavior, and compiler-known runtime names unchanged.

## Scope

- Add `benchmarks/README.md` as the top-level benchmark suite catalog.
- Document `python3 benchmarks/runner.py --suite-list` as the non-JSON suite
  inventory command.
- Document `python3 benchmarks/runner.py --suite-list --json` as the beta
  tooling metadata form for the same inventory.
- Record the current suite inventory:
  `math-loop`, `branch-loop`, `parse-loop`, `array-index-loop`,
  `string-eq-loop`, `array-struct-field-loop`,
  `enum-struct-payload-loop`, `vec-i32-index-loop`,
  `vec-string-eq-loop`, and `json-quote-loop`.
- Document that benchmark timings are local-machine evidence only.
- Update README, language roadmap, language spec, release notes, post-beta
  roadmap, and this release contract to introduce beta14.

## Acceptance

- Public docs name current release/stage `1.0.0-beta.14`.
- `benchmarks/README.md` explains both root suite-list commands:
  `python3 benchmarks/runner.py --suite-list` and
  `python3 benchmarks/runner.py --suite-list --json`.
- The suite catalog lists the current benchmark suite inventory without adding
  or removing benchmark kernels.
- The suite catalog verifies required scaffold files for each suite:
  `benchmark.json`, `run.py`, `slovo.toml`, and `src/main.slo`.
- The docs say timing output is local-machine evidence only and do not publish
  timing numbers.
- The JSON suite listing is described as beta tooling metadata, not a stable
  public schema.
- Explicit exclusions include no new benchmark kernels, no timing publication,
  no performance thresholds, no stable JSON schema, no source-language change,
  no runtime change, no stdlib/API change, no diagnostic-output change, and no
  ABI/layout change.

## Explicit Non-Scope

- no new benchmark kernels or implementation language slots
- no benchmark timing publication
- no release performance threshold
- no stable JSON schema or stable benchmark metadata compatibility promise
- no source-language syntax, typed-core, lowering, runtime, stdlib, or API
  change
- no compiler diagnostic or diagnostic-output shape change
- no ABI/layout or optimizer guarantee
- no worker-owned release publication work before controller review and gates

## Expected Controller Verification

- Run lightweight docs checks:
  - `git diff --check -- README.md benchmarks/README.md docs/POST_BETA_ROADMAP.md docs/language/SPEC-v1.md docs/language/ROADMAP.md docs/language/RELEASE_NOTES.md .llm/BETA_14_BENCHMARK_SUITE_CATALOG_AND_METADATA_GATE.md`
  - run an `rg` check for stale beta13-only current-stage phrasing across the
    same touched docs
- Smoke the metadata commands:
  - `python3 benchmarks/runner.py --suite-list`
  - `python3 benchmarks/runner.py --suite-list --json`
- Run focused compiler/tooling checks:
  - `cargo test --test benchmark_suite_catalog_beta14`
  - `cargo test --test benchmark_math_loop_scaffold`
- Do not commit, tag, push, or run release publication from this worker scope.
