# Beta.1 Tooling Hardening Scope

This file tracks the first post-`1.0.0-beta` tooling bundle. It is committed on
`main` but must not be tagged as `1.0.0-beta.1` until the connected bundle is
complete and the full release gate passes near publication.

## Implemented In This Slice

- `glagol run <file.slo|project>` builds through the existing native hosted
  path, executes the result, forwards stdout/stderr, and exits with the program
  status.
- `glagol run` writes to `.slovo/build/<name>` by default and supports `-o
  <binary>` for an explicit executable path.
- `glagol run ... -- <args>` forwards program arguments to the produced
  executable.
- `glagol clean <file.slo|project>` removes generated `.slovo/build` artifacts.
- `glagol new --template binary|library|workspace` supports the existing
  binary scaffold plus checkable/testable library and local workspace
  scaffolds.
- `scripts/install.sh` installs `bin/glagol`, `share/slovo/std/*.slo`, and
  `share/slovo/runtime/runtime.c` under a configurable prefix.
- Installed `glagol` discovers both standard-library source modules and the
  runtime C input relative to the executable, with `SLOVO_STD_PATH`,
  `SLOVO_RUNTIME_C`, `GLAGOL_RUNTIME_C`, and `GLAGOL_CLANG` override paths.
- The release gate prints a concise success line after docs, formatting, tests,
  promotion, binary, and LLVM smoke checks pass.

## Explicitly Out Of Scope

- no source-language syntax change
- no networking or runtime resource model
- no package registry behavior
- no stable ABI/layout promise
- no operating-system package-manager integration
- no stable install layout promise beyond this beta toolchain layout

## Remaining Before Tagging `1.0.0-beta.1`

- rerender publication PDFs only if documentation release text changes
- run the full release gate from a clean checkout state
- decide whether this tooling bundle is sufficient for the `1.0.0-beta.1` tag