bao/nexus
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs: record v0.2.60 production acceptance [skip ci]

Browse Source
This commit is contained in:
AzuTear
2026-08-01 02:24:37 +02:00
parent f87b9ef298
commit a83de81031
5 changed files with 105 additions and 65 deletions
Download Patch File Download Diff File Expand all files Collapse all files
README.md
+7 -4
View File
@@ -39,18 +39,21 @@ isolated from the frontend and the Nexus domain model.
> **Structured operation results checkpoint (2026-07-31):**
> [implementation and acceptance](docs/audits/2026-07-31/operation-results-deep-links/IMPLEMENTATION_AND_ACCEPTANCE.md).
>
> **Production release v0.2.59 (2026-07-31):**
> **Previous production checkpoint v0.2.59 (2026-07-31):**
> [production validation, route matrix and next plan](docs/audits/2026-07-31/production-release-v0.2.59/PRODUCTION_VALIDATION_AND_NEXT_PLAN.md).
> Gitea run 362 deployed commit `144edf58fe5928a3e04816f4435ea574d64211a1`;
> PostgreSQL and the OpenClaw HTTP runtime are healthy. Productive Protocol-v4
> management remains intentionally blocked by the external Client-ID gate.
>
> **Stability and recovery v0.2.60 candidate (2026-07-31):**
> **Production release v0.2.60 — stability and recovery (2026-07-31):**
> [implementation and acceptance](docs/audits/2026-07-31/stability-v0.2.60/IMPLEMENTATION_AND_ACCEPTANCE.md).
> Readiness, browser-origin protection, generated ProblemDetails metadata,
> shared UI recovery states, version provenance and mandatory container-backed
> CI are implemented. The audit separates locally proven behavior from the
> Linux/Docker, deployment, credentialed-production and OpenClaw-write gates.
> CI are deployed from commit `f87b9ef298f8a13ed7e044f9850024aa50fbbed0`
> through Gitea run 372. All 386 regular backend tests, all five PostgreSQL/
> Toxiproxy tests, 42 frontend tests, 26 Playwright tests and the pinned
> full-history Gitleaks scan passed. Credentialed production, Task Board load
> evidence and productive OpenClaw writes remain separate acceptance gates.
> 📋 **Architektur-Review** (2026-06-22): Board-first Orchestrierung, sichere
> Backend-Brücke und Gateway-Integration geprüft. Siehe