M7-Release: Prepare the v1.0.0 release PR with go/no-go evidence

.github/workflows/v1-acceptance.yml

@@ -12,10 +12,8 @@ concurrency:
   cancel-in-progress: true
 
 jobs:
-  #69: V1-AC1 (#63) and V1-AC2 (#64) have no marked tests yet, so the gate is expected to fail; remove continue-on-error before the v1.0.0 release PR (#72).
   v1-acceptance:
     runs-on: ubuntu-latest
-    continue-on-error: true
     steps:
       - uses: actions/checkout@v4
       - uses: astral-sh/setup-uv@v10.2.0

CHANGELOG.md

@@ -8,7 +8,9 @@ from git tags via hatch-vcs; see [docs/releasing.md](docs/releasing.md).
 
 ## [Unreleased]
 
-First release candidate (V1). Nothing has been tagged yet. Numbers are pull requests on
+## [1.0.0] - 2026-10-06
+
+First release (V1). Numbers are pull requests on
 <https://github.com/akurkar07/InvariantLab>.
 
 ### Added
@@ -67,7 +69,7 @@ First release candidate (V1). Nothing has been tagged yet. Numbers are pull requ
   status-first README (#151), docs index (#161), research-track roadmap (#162), Study 2
   corrections (#124, #128) and the documented evaluation protocol (#132).
 - Mutant catalogue and validation documentation, plus an acceptance test requiring package
-  mutant coverage for all ten mutation families or a documented infeasibility issue (issue #93).
+  mutant coverage for all ten mutation families or a documented infeasibility issue (#183).
 - This changelog and the [release procedure](docs/releasing.md).
 
 ### Changed
@@ -80,9 +82,10 @@ First release candidate (V1). Nothing has been tagged yet. Numbers are pull requ
 ### Known limitations
 
 See [docs/limitations.md](docs/limitations.md). In short: V1 runs from a source checkout, the
-Docker sandbox is single-machine, the repair-study harness evaluates the oscillator only until
-[#120](https://github.com/akurkar07/InvariantLab/issues/120), and the Study 1/2 results are not
+Docker sandbox is single-machine, the legacy oscillator `update-order` / `sign-error` study
+mutants are still graded by the oscillator study harness, and the Study 1/2 results are not
 yet reproducible from the repository
 ([#100](https://github.com/akurkar07/InvariantLab/issues/100)).
 
-[Unreleased]: https://github.com/akurkar07/InvariantLab/commits/main
+[Unreleased]: https://github.com/akurkar07/InvariantLab/compare/v1.0.0...HEAD
+[1.0.0]: https://github.com/akurkar07/InvariantLab/releases/tag/v1.0.0

CITATION.cff

@@ -7,7 +7,8 @@ authors:
     affiliation: University of Nottingham
 repository-code: "https://github.com/akurkar07/InvariantLab"
 license: MIT
-# version and date-released are added when the first release is tagged.
+version: 1.0.0
+date-released: 2026-10-06
 url: "https://github.com/akurkar07/InvariantLab"
 keywords:
   - AI evaluation

docs/releasing.md

@@ -39,7 +39,7 @@ through a normal PR (all required checks green) before tagging.
    `## [X.Y.Z] - YYYY-MM-DD`, add a fresh empty `## [Unreleased]` above it, and update the
    compare links at the bottom of the file.
 4. **Set the classifier.** Update the `Development Status :: ...` classifier in
-   `pyproject.toml` (currently `3 - Alpha`) to the maturity of this release.
+   `pyproject.toml` (`5 - Production/Stable` since 1.0.0) to the maturity of this release.
 5. **Tag.** After the release PR has merged, the maintainer pushes an annotated tag on `main`:
    `git tag -a vX.Y.Z -m "InvariantLab X.Y.Z" <merge-sha>` then `git push origin vX.Y.Z`.
    Only the maintainer creates tags; agents and contributors do not.

docs/v1-acceptance.md

@@ -16,8 +16,8 @@ when all eight criteria are `passed`; skipped, xfailed, failed and missing
 criteria — as well as tests marked with unknown acceptance ids — all fail the
 gate. The `V1 Acceptance` workflow (`.github/workflows/v1-acceptance.yml`, job
 `v1-acceptance`) runs the checker on every pull request to and push to `main`
-(plus manual dispatch) and uploads `v1-acceptance.json` as an artifact. Until
-V1-AC1..AC8 all pass, the job is `continue-on-error` (remove before #72); the
+(plus manual dispatch) and uploads `v1-acceptance.json` as an artifact. The job
+fails when any criterion is not `passed` (no `continue-on-error`); the
 maintainer should make the `v1-acceptance` check required in branch protection —
 agents cannot change repository settings.
 

pyproject.toml

@@ -21,7 +21,7 @@ keywords = [
     "coding-agents",
 ]
 classifiers = [
-    "Development Status :: 3 - Alpha",
+    "Development Status :: 5 - Production/Stable",
     "Intended Audience :: Science/Research",
     "License :: OSI Approved :: MIT License",
     "Programming Language :: Python :: 3",