v0.23.0

SCPN Control v0.23.0

Minor release: modularisation of several god-modules plus integrity/honesty
hardening of the shipped control path (fail-closed guards, backend=z3
rejection, SCPN/PID/MPC benchmark un-rig). See CHANGELOG.md and
docs/release_notes_v0.23.0.md.

v0.22.1

Authored by Anulum Fortis & Arcane Sapience (protoscience@anulum.li)

v0.22.0

chore: prepare v0.22.0 release

Authored by Anulum Fortis & Arcane Sapience (protoscience@anulum.li)

v0.21.0

SCPN Control v0.21.0 — closed-form validation campaign and coverage

v0.20.7

SCPN Control v0.20.7

SCPN Control v0.20.6

SCPN Control v0.20.6 Release Notes

v0.20.6 is a CI, dependency, and repository-hygiene patch on top of v0.20.5.
It restores the remote coverage margin with module-specific tests, merges the
pending dependency-maintenance pull requests after fresh green checks, and
reconfirms that public security-alert surfaces are clear.

What changed

• Added focused rust_engine coverage for native PyO3 handoff policy
  forwarding, fail-closed hardware-loop behaviour, ITPA gyro-Bohm coefficient
  loading, transport-network bounds, heartbeat timeout handling, and hybrid-loop
  telemetry accounting.
• Added focused quantum disruption bridge coverage for contract tamper
  detection, backend attestation, kernel/certificate evidence, feature mapping,
  and advisory decision validation.
• Merged the green Dependabot updates for click, z3-solver, and
  hypothesis.
• Refreshed and merged the stale Dependabot updates for pinned GitHub Actions
  and Rust log after their updated branches produced fresh green checks.
• Rechecked code scanning, Dependabot alerts, and secret scanning after the
  dependency lane; all three reported zero open alerts.
• Bumped package, citation, API, README capability, release-note, and public
  changelog metadata to 0.20.6.

Evidence boundary

This patch does not upgrade local-regression benchmark reports to production
benchmark evidence. It also does not change the blocked facility,
target-hardware, EFIT/P-EFIT, external-code, independent security-audit, or
PREEMPT_RT production-claim boundaries declared for the previous release line.

Release checklist

Do not treat v0.20.6 as published until all items are true:

• Version metadata and documentation updates are committed.
• CI, CodeQL, Pre-commit, OpenSSF Scorecard, Docs Pages, release, and publish
  workflows are green for the v0.20.6 commit/tag.
• Pull requests and security alerts remain clear.
• Failed or cancelled Actions/deployment records are deleted only when safe and
  only after replacement evidence is green.
• The GitHub release is created from the v0.20.6 tag.

v0.20.5

SCPN Control v0.20.5

v0.20.4

SCPN Control v0.20.4

SCPN Control v0.20.3

SCPN Control v0.20.3 Release Notes

v0.20.3 is a patch release for Lean formal-evidence admission security. It
keeps the v0.20.2 documentation and evidence-bound claim posture, then adds
the CodeQL ReDoS remediation to the release tag.

What changed

• Replaced regex-based Lean theorem, Lean module, and safety-case identifier
  checks with linear-time validators.
• Reused the same validators in both Lean report admission and controller
  artifact admission so the security boundary stays single-source.
• Preserved duplicate rejection, non-empty list checks, proof-assumption
  digests, required Lean contract coverage, and manifest/report consistency
  checks.
• Bumped package, citation, archive, API, README capability, and release-note
  metadata to 0.20.3.

Evidence boundary

This release does not change the public physics or deployment claim boundary.
Predictive EFIT/P-EFIT, external-code gyrokinetic agreement, saturated nonlinear
Cyclone Base Case agreement, target-hardware/HIL real-time PCS-cycle operation,
commissioned plant deployment, and independent security-audit completion remain
blocked until their strict admission artefacts exist.

Release checklist

Do not treat v0.20.3 as published until all items are true:

• Version metadata and documentation updates are committed.
• Documentation builds successfully.
• Release-evidence and version-sync gates pass.
• The branch is pushed and GitHub Actions for main are green.
• CodeQL no longer reports the Lean identifier ReDoS alert on the release tag.
• Pull requests and security alerts are triaged.
• Failed or cancelled Actions/deployment records are deleted only when safe and
  only after replacement evidence is green.
• The GitHub release is created from the v0.20.3 tag.

SCPN Control v0.20.2

SCPN Control v0.20.2 Release Notes

v0.20.2 is a documentation, release-readiness, security-boundary, and
evidence-admission polish release. It makes the public surface easier to read
while keeping quantitative physics, hardware, and deployment claims bounded by
the validators.

What changed

• Reworked the README into clearer product, workflow, evidence, quick-start,
  and limitation sections so new readers can understand what SCPN Control is
  and what it is not.
• Added a public benchmark-regression admission gate for persisted latency
  evidence. The gate checks report digests, metric paths, thresholds, sample
  counts, hardware context, and claim-boundary text without generating new
  timing data.
• Hardened optional native C++ solver compilation with compiler admission,
  minimal build environment, symlink rejection, temporary build output, and
  atomic publication of regular shared-library files.
• Expanded the documentation around native-build security, benchmark admission,
  release boundaries, and collaboration value.
• Tightened public wording for gyrokinetic, real-time, disruption, and
  equilibrium claims where external-code, measured-shot, target-hardware, or
  peer-reviewed evidence remains missing.

Evidence boundary

This release does not claim:

• commissioned plant PCS deployment;
• predictive EFIT/P-EFIT admission;
• external-code gyrokinetic agreement on identical inputs;
• saturated nonlinear Cyclone Base Case heat-flux agreement;
• target-hardware or HIL real-time PCS-cycle readiness;
• independent security audit completion.

Those claims require strict artefact admission before public promotion.

Recommended reading order

1. README for the concise product
   overview and quick-start path.
2. Onboarding for first-hour and first-day workflows.
3. Use Cases and Market Value for who benefits and why.
4. Production Readiness for claim levels.
5. Validation and QA, Benchmarks, and
   Validation Summary for current evidence.
6. Compute Validation Funding for the open
   support and financing needs.

Release checklist

Do not treat v0.20.2 as published until all items are true:

• Version metadata and documentation updates are committed.
• Documentation builds successfully.
• Release-evidence and version-sync gates pass.
• The branch is pushed and GitHub Actions for main are green.
• Pull requests and security alerts are triaged.
• Failed or cancelled Actions/deployment records are deleted only when safe and
  only after replacement evidence is green.
• The GitHub release is created from the v0.20.2 tag.