# 1.0.0-beta.25 User Project Conformance Matrix

## Scope

`1.0.0-beta.25` is a tooling/conformance evidence slice for ordinary
project and workspace usage. It adds a deterministic user-project conformance
matrix over the existing checked examples under `examples/projects/` and
`examples/workspaces/`.

The matrix is stable-readiness evidence for the beta toolchain. It records
which existing user-shaped example projects and workspaces are expected to
pass `glagol check`, `glagol test --list`, and stable `glagol test` execution
through ordinary Glagol entry points.

At release time the matrix covers all 43 top-level fixture roots with
`slovo.toml` under those inventories and 655 discovered tests. Environment
fixtures run with deterministic in-test environment values so host shell state
does not decide the result.

This release changes tooling evidence only. It does not change the Slovo
source language, typed core, runtime behavior, standard-library helper
surface, compiler-known runtime names, package-manager behavior, package graph
semantics, registry behavior, lockfile behavior, semver behavior, ABI/layout
policy, stable schema policy, or performance policy.

## Contract

The conformance matrix is deterministic and repository-local:

- inputs are every top-level `slovo.toml` fixture under the existing
  `examples/projects/` and `examples/workspaces/` directories
- entries are sorted by stable repository-relative path
- each entry names the example kind, path, and ordinary project/workspace
  test count covered by the matrix
- fixture inventory drift must fail the focused matrix test until the matrix
  and release evidence are updated deliberately
- generated evidence must not depend on wall-clock time, host-specific
  absolute paths, random ordering, or network access
- matrix output is beta readiness evidence, not a frozen public schema

The matrix is intended to answer whether normal beta users can exercise the
current example projects and workspaces through the documented toolchain. It
does not promote new language forms, new standard-library helpers, new runtime
capabilities, new package manager behavior, or new compatibility guarantees.

## Non-Scope

This scope does not add:

- source-language syntax or semantics
- typed-core changes
- standard-library helpers or stdlib behavior changes
- compiler-known `std.*` runtime names
- runtime behavior or runtime C capabilities
- package manager behavior
- remote registry behavior
- lockfiles
- semantic-version solving
- package publishing
- optional, dev, target, or feature-gated dependencies
- stable package ABI/layout
- stable artifact-manifest, Markdown, JSON, or conformance-matrix schema
  guarantees
- performance thresholds, performance claims, or timing publication
- LSP/watch, SARIF, daemon, coverage, retry, tag/group, or event-stream
  protocols

## Acceptance Criteria

- README names `1.0.0-beta.25` as the current release and describes the
  user-project conformance matrix as tooling/readiness evidence only.
- Language and compiler release notes describe beta25 as a
  tooling/conformance evidence slice over existing `examples/projects/` and
  `examples/workspaces/`.
- Language and compiler roadmaps record beta25 as the current
  stable-readiness evidence slice while keeping language, stdlib, runtime,
  package-manager, stable-schema, and performance work deferred.
- The post-beta roadmap records beta25 under tooling/release hardening.
- Glagol is versioned as `1.0.0-beta.25`.
- `compiler/tests/user_project_conformance_beta25.rs` covers all 43 top-level
  project/workspace fixture roots and 655 discovered tests.
- Fixture inventory drift is checked against discovered top-level
  `slovo.toml` roots.
- `scripts/release-gate.sh` runs the focused beta25 matrix test.
- No compiler, runtime, standard-library, package-manager, registry, lockfile,
  semver, ABI/layout, stable-schema, or performance claim is introduced by
  the documentation.

## Suggested Gates

```bash
git diff --check
cargo fmt --check
cargo test --test user_project_conformance_beta25
```