persona-harness 0.8.25 → 0.8.26

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md CHANGED
@@ -8,6 +8,9 @@ preparation alone does not establish stable support or channel state.
8
8
 
9
9
  ## Unreleased
10
10
 
11
+ - Replace static live-release snapshots in package-visible current documents
12
+ with npm and GitHub lookup links, so a newly published package cannot become
13
+ stale at the instant its governed publish completes.
11
14
  - Add a release-truth contract: stable GitHub Release generation rejects
12
15
  source-candidate language, distinguishes the GitHub Release from the later
13
16
  npm/provenance completion step, and keeps public maintainer command scopes
@@ -16,6 +19,12 @@ preparation alone does not establish stable support or channel state.
16
19
  the single-worker resource-sensitive lane for fixtures that own mutable
17
20
  package, Gradle, staged-consumer, workflow-loop, or producer runtime state.
18
21
 
22
+ ## [0.8.25] - 2026-08-22
23
+
24
+ - Publish the release-truth contract through protected integration, immutable
25
+ tag, stable GitHub Release, npm `latest`, canonical tar reconciliation, and
26
+ provenance readback.
27
+
19
28
  ## [0.8.24] - 2026-08-22
20
29
 
21
30
  - Publish the exact packed-package Java/Spring Gradle/JUnit cooperative Finish
@@ -16,19 +16,20 @@ find the record; it is not a ledger of every historical release decision.
16
16
  - [Release operations history](history.md) retains old readiness decisions,
17
17
  beta evidence, and the full release-note index without making them current.
18
18
 
19
- ## Recorded Release State
19
+ ## Live Release State
20
20
 
21
- At the recorded 2026-08-22 release state:
21
+ The package version in this checkout is a source input. npm dist-tags and
22
+ GitHub Releases can change only later in the governed lifecycle, so
23
+ package-visible current docs do not freeze a live channel snapshot.
22
24
 
23
- | Channel or record | Value | Source |
24
- | --- | --- | --- |
25
- | npm `latest` | `0.8.24` | [`v0.8.24` release notes](v0.8.24-release-notes.md) |
26
- | GitHub latest release | `v0.8.24` | [GitHub releases](https://github.com/jyt6640/persona-harness/releases) |
27
- | Historical prerelease channels | recorded separately | [Package/version index](../../releases/package-index.md) |
25
+ - Read [live npm versions and dist-tags](https://www.npmjs.com/package/persona-harness?activeTab=versions).
26
+ - Read [live GitHub Releases](https://github.com/jyt6640/persona-harness/releases).
27
+ - Read immutable historical version facts in the
28
+ [package/version index](../../releases/package-index.md).
28
29
 
29
- These are recorded facts, not a standing authorization to publish, promote a
30
- channel, consume Finish authority, or create a release. Before a release
31
- decision, read the live registry and the protected workflow state again.
30
+ Those sources are not a standing authorization to publish, promote a channel,
31
+ consume Finish authority, or create a release. Before a release decision, read
32
+ the live registry and the protected workflow state again.
32
33
 
33
34
  ## Current Workflow Lifecycle Boundary
34
35