docs(phase970): roadmap, release notes, and testing docs for v0.8.937
Mark Phase 970 complete in PLATFORM_ROADMAP, add release notes and AUTOMATED_TESTING/PRODUCTION_MESH/MESH_STABILITY/MODULES updates for stability e2e validate smoke harness. Co-authored-by: Cursor <[email protected]>
This commit is contained in:
@@ -0,0 +1,39 @@
|
||||
# Release v0.8.937 — Phase 970: Guild Mesh Stability E2E Validate Smoke Harness
|
||||
|
||||
**Date:** 2026-06-05
|
||||
**Type:** Non-breaking refactor — Guild mesh production hardening
|
||||
|
||||
## Summary
|
||||
|
||||
Phase 970 adds an end-to-end validate harness for guild mesh stability stats field keys
|
||||
and builder alignment (`guild-mesh-stability-validate-e2e.js`). The validate chain
|
||||
confirms `listMeshStabilityStatsFieldKeys` matches the canonical registry and that
|
||||
`buildMeshStabilityStatsSnapshot` produces all 29 keys. Zero externally visible behavior changes.
|
||||
|
||||
## New Module
|
||||
|
||||
### `pearcord-platform/guild-mesh-stability-validate-e2e`
|
||||
|
||||
Exports:
|
||||
|
||||
- **Validators**: `validateMeshStabilityStatsFieldKeyAlignment`, `validateMeshStabilityStatsBuilderAlignment`
|
||||
- **Runner**: `runGuildMeshStabilityValidateE2e`
|
||||
|
||||
## Agentctl Journey
|
||||
|
||||
| Journey | Role |
|
||||
|---------|------|
|
||||
| `runGuildMeshStabilityValidateE2eJourney` | Runs validate chain + live `getMeshStabilityStats` |
|
||||
|
||||
## Test Coverage
|
||||
|
||||
- `smoke-guild-mesh-stability-validate-e2e.cjs` — validate chain unit smoke
|
||||
- `smoke-phase970-boot-gate.cjs` — structural verification + version check (0.8.937)
|
||||
- `smoke-agentctl-guild-mesh-stability-validate-e2e-journey-stub.cjs` — agentctl integration stub
|
||||
- `test:mesh-stability-stats` — extended with validate e2e chain assertion
|
||||
- `test:gossip-rpc-pull-unit` — extended with validate e2e runner assertion
|
||||
- `test:ci-phase970` — full CI bundle
|
||||
|
||||
## Version
|
||||
|
||||
`0.8.936` → `0.8.937`
|
||||
Reference in New Issue
Block a user