From b3b53cf669b25cab20dc2f237b078e60616bdf1f Mon Sep 17 00:00:00 2001 From: CoderDeltaLAN Date: Tue, 16 Jun 2026 04:07:17 +0100 Subject: [PATCH] docs: clarify v0.2 release maturity history --- CHANGELOG.md | 2 +- README.md | 2 +- docs/V0.2-GOVERNANCE-RULES-SPEC.md | 16 ++++++++-------- docs/V0.2-PACKAGING-DRY-RUN.md | 8 ++++---- docs/V0.2-RELEASE-READINESS.md | 12 ++++++------ 5 files changed, 20 insertions(+), 20 deletions(-) diff --git a/CHANGELOG.md b/CHANGELOG.md index f0c3825..054337b 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -2,7 +2,7 @@ All notable changes to agent-rules-kit will be documented in this file. -This project has no stable public release yet. +This project has a published GitHub Release line, but no stable support or API guarantee yet. ## [Unreleased] diff --git a/README.md b/README.md index d8b5293..cf661b9 100644 --- a/README.md +++ b/README.md @@ -359,7 +359,7 @@ The required status check for `main` is: Current status: - `v0.2.0` is published as a GitHub Release; -- no public stable release yet; +- no stable support or API guarantee yet; - release tag `v0.2.0` points to the verified release SHA; - wheel and sdist artifacts are attached to the `v0.2.0` GitHub Release; - release assets were downloaded, checksum-verified, installed, and smoke-tested; diff --git a/docs/V0.2-GOVERNANCE-RULES-SPEC.md b/docs/V0.2-GOVERNANCE-RULES-SPEC.md index e0d9f5f..a7a3c34 100644 --- a/docs/V0.2-GOVERNANCE-RULES-SPEC.md +++ b/docs/V0.2-GOVERNANCE-RULES-SPEC.md @@ -2,9 +2,9 @@ This document defines the v0.2 governance rules specification for agent-rules-kit after the v0.1.0 pre-release. -It originally described candidate rules. Current `main` now contains unreleased v0.2 governance diagnostics based on this specification, including structured finding evidence and supported redaction for finding message, path, and evidence payload fields. +This is a historical rules specification. The rules described here were implemented and published in the `v0.2.0` GitHub Release. -This document must not be used to claim that v0.2 has been published as a versioned release. +For current release state, use `README.md`, `CHANGELOG.md`, `SECURITY.md`, `docs/V0.2.0-RELEASE-NOTES.md`, and the GitHub Release. ## Purpose @@ -39,7 +39,7 @@ The published v0.1.0 pre-release supports: * pattern-based redaction helpers; * a Finding model with rule id, severity, message, and optional location fields. -Current `main` additionally includes unreleased v0.2 governance diagnostics: +`v0.2.0` includes these governance diagnostics: * AIRK-GOV006 unsupported security or maturity claim; * AIRK-GOV003 review or CI bypass guidance; @@ -50,7 +50,7 @@ Current `main` additionally includes unreleased v0.2 governance diagnostics: * structured finding evidence for line-based governance findings; * supported redaction for finding message, path, and evidence payload fields. -This unreleased v0.2 behavior builds on the v0.1.0 boundary. It does not introduce a new product category, and it has not been published as a versioned release yet. +The published `v0.2.0` governance behavior builds on the v0.1.0 boundary. It does not introduce a new product category. ## v0.2 goal @@ -295,7 +295,7 @@ Non-goals: ## Implemented rule ordering on current main -Current `main` evaluates unreleased governance findings in this stable order: +`v0.2.0` evaluates governance findings in this stable order: 1. AIRK-GOV006 unsupported security or maturity claim. 2. AIRK-GOV003 review or CI bypass guidance. @@ -304,7 +304,7 @@ Current `main` evaluates unreleased governance findings in this stable order: 5. AIRK-GOV002 missing secret-handling boundary. 6. AIRK-GOV001 missing instruction scope or authority. -This order documents current `main` behavior. It is not proof of a published v0.2 release. +This order documents the published `v0.2.0` behavior. Future rule-order changes must remain deterministic, documented, fixture-backed, and conservative. @@ -378,7 +378,7 @@ Forbidden: ## Release gate -Before publishing a versioned v0.2 release, the maintainer must verify this specification against: +For future `v0.2.x` releases, the maintainer must verify this specification against: * docs/PRODUCT-STRATEGY.md; * docs/THREAT-MODEL.md; @@ -402,7 +402,7 @@ The release review must confirm that: The `test/add-governance-golden-output-coverage` phase has been completed on current `main`. -The next follow-up should be a release-readiness audit before any v0.2 version, tag, or release decision. +This follow-up was completed by the `v0.2.0` release train; keep this section as historical implementation guidance. That audit should verify: diff --git a/docs/V0.2-PACKAGING-DRY-RUN.md b/docs/V0.2-PACKAGING-DRY-RUN.md index 6cd2539..2ade44c 100644 --- a/docs/V0.2-PACKAGING-DRY-RUN.md +++ b/docs/V0.2-PACKAGING-DRY-RUN.md @@ -1,6 +1,6 @@ # v0.2 Packaging Dry-Run Report -Status: packaging path verified for current main; final v0.2.0 artifacts still pending. +Status: historical packaging dry-run; superseded by final `v0.2.0` release artifacts. Date: 2026-06-15. @@ -10,7 +10,7 @@ CI run reviewed before dry-run: 27547533879. This report records a packaging and install dry-run for the current `main` state before any v0.2.0 version bump, tag, GitHub Release, or artifact upload. -It is not a v0.2.0 release approval. +It is not a v0.2.0 release approval. It is retained as historical pre-release evidence; the final `v0.2.0` artifacts were later built, attached to the GitHub Release, downloaded, installed, and smoke-tested. ## Scope @@ -146,8 +146,8 @@ Packaging path status: - wheel install path: verified; - sdist install path: verified; - installed CLI smoke behavior: verified; -- final v0.2.0 artifacts: pending; -- final v0.2.0 release decision: still blocked. +- final v0.2.0 artifacts: superseded by published release artifacts; +- final v0.2.0 release decision: superseded by the published GitHub Release. Recommended next phase: diff --git a/docs/V0.2-RELEASE-READINESS.md b/docs/V0.2-RELEASE-READINESS.md index 9ce0e1c..eeeadd5 100644 --- a/docs/V0.2-RELEASE-READINESS.md +++ b/docs/V0.2-RELEASE-READINESS.md @@ -8,7 +8,7 @@ Base commit reviewed: 7594346ebeb674a7e471197250bccbca8b4c36bf. CI run reviewed: 27545634227. -This report records the release-readiness state after the unreleased v0.2 governance baseline landed on `main`. +This historical report records the release-readiness state from before the `v0.2.0` release was cut. It is not a release note, tag decision, version bump, or stability claim. @@ -74,7 +74,7 @@ The current package version is still: That is correct for this phase and blocks any `v0.2.0` release until a dedicated version-cut phase. -## Current unreleased v0.2 behavior on main +## Historical pre-release v0.2 behavior on main Current `main` contains unreleased governance diagnostics for AI agent instruction files. @@ -101,8 +101,8 @@ Golden contract coverage exists for current governance console, JSON, and Markdo README.md distinguishes: - the published `v0.1.0` GitHub pre-release; -- current unreleased v0.2 governance behavior on `main`; -- absence of a stable public release. +- historical pre-release v0.2 governance behavior on `main`; +- absence of a stable support or API guarantee at that time. README.md no longer pins a fragile unit test count. It points to `./scripts/check.sh` and the matching GitHub Actions run as the source of truth. @@ -114,7 +114,7 @@ SECURITY.md preserves the security boundary: - no security guarantees; - best-effort pre-release support; - private reporting path preferred when available; -- stable support policy still required before a stable release. +- stable support policy still required before any stable-support claim. docs/V0.2-GOVERNANCE-RULES-SPEC.md requires a release-readiness audit before any v0.2 version, tag, or release decision. @@ -150,7 +150,7 @@ A dedicated packaging dry-run phase must verify: - `python -m agent_rules_kit.cli` execution; - no unexpected runtime dependencies. -### Blocker 4: v0.2 tag and GitHub Release do not exist +### Historical blocker 4: v0.2 tag and GitHub Release did not exist at that reviewed commit Historical state at the reviewed commit: no `v0.2.0` tag or GitHub Release existed yet.