Add OpenClaw V1R3C1 corrective release execution instructions

2026-07-08 14:31:24 +08:00
parent 75fd3c6274
commit 187dcc3554
1 changed files with 195 additions and 0 deletions
@@ -0,0 +1,195 @@
+# OpenClaw Execution Instructions: V1R3C1 Corrective Self-loop Release
+
+## Purpose
+
+Execute the corrective release path for `V1R3C1`.
+
+`V1R3C0` already exists, but it must be treated as an infrastructure-fix tag only. Do not promote `V1R3C0` as the self-loop autonomous engine baseline.
+
+The correct self-loop implementation target is this branch:
+
+```text
+patch/user-portal-rbac-ops-dashboard
+```
+
+The corrective release version is:
+
+```text
+V1R3C1
+```
+
+---
+
+## Required checks
+
+Use the Gitea bare repo:
+
+```bash
+GITEA_REPO="/data/aios-gitops/runtime/gitea-bin/data/repositories/aios/aios-v23.git"
+```
+
+Confirm the implementation branch exists:
+
+```bash
+git --git-dir="$GITEA_REPO" rev-parse patch/user-portal-rbac-ops-dashboard
+```
+
+Confirm the V1R3C1 proposal exists on the implementation branch:
+
+```bash
+git --git-dir="$GITEA_REPO" ls-tree -r patch/user-portal-rbac-ops-dashboard | grep 'versions/proposals/V1R3C1.json'
+```
+
+Confirm the implementation branch contains the self-loop files:
+
+```bash
+git --git-dir="$GITEA_REPO" ls-tree -r patch/user-portal-rbac-ops-dashboard | grep -E 'autonomous_self_loop|self_loop_executor|self_loop_orchestrator|self_loop_patch_executor|self_loop_scheduler|self_loop_runtime_api|self_loop_gitops_adapter|production_acceptance_gate|failure_memory|failure_memory_store|adaptive_policy|self_loop_event_hooks|self_loop_supervisor|self_loop_worker|self_evolution_report'
+```
+
+---
+
+## Do not promote V1R3C0
+
+Check `V1R3C0` only for reference:
+
+```bash
+git --git-dir="$GITEA_REPO" tag --list 'V1R3C0'
+git --git-dir="$GITEA_REPO" rev-list -n 1 V1R3C0 2>/dev/null || true
+```
+
+Do not delete, move, rewrite, or reuse `V1R3C0`.
+
+`V1R3C0` must remain an infrastructure-fix tag.
+
+---
+
+## Create or repair V1R3C1 approval request
+
+If the Actions endpoint `/api/tag-request` is broken, repair it first. The API should allow a tag request to be created for `V1R3C1`.
+
+Search the handler:
+
+```bash
+grep -R "tag-request\|createTagApprovalRequest\|requestOrCreateTag\|baseline/tag_requests" -n \
+  /data/aios-gitops/runtime \
+  /data/aios-gitops/workspace 2>/dev/null
+```
+
+Expected approval request branch:
+
+```text
+request/tag-V1R3C1-self-loop-corrective
+```
+
+Expected request file:
+
+```text
+baseline/tag_requests/V1R3C1.json
+```
+
+Expected promotion files:
+
+```text
+baseline/promotions/V1R3C1.release-manifest.json
+baseline/promotions/V1R3C1.acceptance-report.json
+```
+
+The approval request must state:
+
+```text
+V1R3C1 corrects the V1R3C0 release target.
+V1R3C0 is infrastructure fix only.
+V1R3C1 targets patch/user-portal-rbac-ops-dashboard.
+Owner approval required.
+```
+
+---
+
+## Create V1R3C1 tag at the correct commit
+
+Get the intended target commit:
+
+```bash
+PATCH_HEAD=$(git --git-dir="$GITEA_REPO" rev-parse patch/user-portal-rbac-ops-dashboard)
+echo "$PATCH_HEAD"
+```
+
+Verify no existing V1R3C1 tag:
+
+```bash
+git --git-dir="$GITEA_REPO" tag --list 'V1R3C1'
+```
+
+If the tag does not exist and owner approval is present, create the annotated tag at the implementation branch HEAD:
+
+```bash
+git --git-dir="$GITEA_REPO" tag -a V1R3C1 "$PATCH_HEAD" -m "release V1R3C1 self-loop autonomous engine corrective release"
+```
+
+If the tag already exists, verify it points to the same target commit. Do not move the tag without explicit owner approval.
+
+---
+
+## Verify V1R3C1 tag content
+
+```bash
+git --git-dir="$GITEA_REPO" tag --list 'V1R3C1'
+git --git-dir="$GITEA_REPO" rev-list -n 1 V1R3C1
+git --git-dir="$GITEA_REPO" ls-tree -r V1R3C1 | grep -E 'self_loop_supervisor|failure_memory|adaptive_policy|self_loop_worker|self_evolution_report'
+```
+
+The tag must include the self-loop files. If these files are missing, stop and report failure.
+
+---
+
+## Promotion rule
+
+Only after `V1R3C1` tag verification passes, promote baseline to:
+
+```text
+V1R3C1
+```
+
+Do not promote:
+
+```text
+V1R3C0
+```
+
+---
+
+## Forbidden actions
+
+- Do not delete or rewrite `V1R3C0`.
+- Do not promote `V1R3C0` as the self-loop release.
+- Do not push directly to `main`.
+- Do not write secrets to Git.
+- Do not modify Casdoor/SSO.
+- Do not modify Gitea branch index unless a new drift is found and owner approves.
+- Do not bypass owner gate except through an explicitly approved emergency path.
+
+---
+
+## Required final report
+
+Output this matrix:
+
+| Check | Result | Evidence |
+|---|---|---|
+| V1R3C0 treated as infrastructure fix only | YES/NO | tag/diff evidence |
+| V1R3C1 proposal exists | PASS/FAIL | file/SHA |
+| V1R3C1 approval request exists | PASS/FAIL | branch/file |
+| V1R3C1 tag exists | PASS/FAIL | tag/SHA |
+| V1R3C1 points to patch/user-portal-rbac-ops-dashboard HEAD | PASS/FAIL | SHA comparison |
+| V1R3C1 contains self-loop implementation files | PASS/FAIL | ls-tree output |
+| Baseline promotion to V1R3C1 completed | PASS/FAIL | baseline/current.json |
+| Runtime status after promotion | PASS/FAIL | runtime check |
+
+Final expected release path:
+
+```text
+V1R2C3
+  -> V1R3C1
+  -> baseline promotion
+  -> self-loop supervisor / failure memory / adaptive policy active
+```