aios/ops/openclaw/CMD-20260711-v1r4c6-run-to-owner-gate-wechat.md

CMD-20260711-v1r4c6-run-to-owner-gate-wechat

Execution Mode

Execute immediately using the existing V1R4C6 integration command:

ops/openclaw/CMD-20260711-v1r4c6-integrate-deploy-verify.md

Continue through actual merge, tests, deployment, and production verification.

Stop only at the owner gate for:

V1R4C6 Git tag creation
V1R4C6 baseline promotion

Do not ask the owner to perform routine engineering or deployment work.

Verified Starting State

Required before starting:

runtime = active
current_baseline = V1R4C5
previous_baseline = V1R4C3
baseline_git = a32c76a3c1baa49562e53fb8adce10a5ed0e6704
AIOS_GITOPS_BARE_REPO = /data/aios-gitops/runtime/gitea-bin/data/repositories/aios/aios.git
memory_search_enabled = false
force_push_allowed = false

If any starting condition differs, stop and send a WeChat blocker notification.

Required Work

Complete all phases in the referenced command:

1. Create/update the normal non-force-pushed integration execution branch.
2. Merge and validate Admin Workbench / Portal AIOS.
3. Merge and validate SR-03 Search Gateway real provider binding.
4. Merge and validate Agent Platform Integration.
5. Run component and full touched-scope test suites.
6. Deploy using the repository's existing deployment mechanism.
7. Verify production routes, RBAC, scope isolation, provenance, safe mode, and owner gates.
8. Update V1R4C6 release evidence and version metadata.
9. Push all normal commits to origin.
10. Keep V1R4C6 tag absent and baseline at V1R4C5 until owner approval.

Hard Constraints

AIOS_MEMORY_ENABLED=false
memory search remains disabled
no global memory/vector index
no force-push
no tag rewrite
no V1R4C5 tag movement
no Gitea DB mutation
no plaintext secrets in Git, logs, reports, or WeChat

Never bypass a failed security, isolation, RBAC, safe-mode, or owner gate.

WeChat Progress Notifications

Use the configured OpenClaw WeChat notification channel.

Send concise progress notifications at these milestones:

Notification 1 — Integration Started

V1R4C6 集成已启动。
范围：管理员工作台、SR-03 Search Gateway、Agent Platform。
当前基线：V1R4C5。
memory search 保持关闭。
下一步：完成合并、测试和部署验证。

Notification 2 — Gate A Complete

Include only:

Gate A result: PASS/FAIL
Admin task progress visibility: PASS/FAIL
Flow diagram visibility: PASS/FAIL
RBAC/isolation: PASS/FAIL
Blockers, if any

Do not include user records, tokens, cookies, or sensitive task content.

Notification 3 — Gate B Complete

Include only:

Gate B result: PASS/FAIL
Real provider binding: PASS/FAIL
Scope-before-ranking: PASS/FAIL
Provenance: PASS/FAIL
Safe fallback: PASS/FAIL
Memory search: disabled
Blockers, if any

Notification 4 — Gate C Complete

Include only:

Gate C result: PASS/FAIL
Event scope: PASS/FAIL
Message plane scope: PASS/FAIL
Safe-mode dispatch block: PASS/FAIL
Owner gate: PASS/FAIL
Blockers, if any

Final WeChat Owner Authorization Request

Send only after all mandatory gates and deployment verification pass.

Use this message:

V1R4C6 已完成实际合并、测试、部署和生产验证，现等待最终发布授权。

版本范围：
1. 管理员工作台 / Portal AIOS 上线
2. SR-03 Search Gateway Real Provider Binding
3. Agent Platform Integration

验收结果：
- Gate A（管理员工作台 / RBAC / 隔离）：PASS
- Gate B（Provider / scope / provenance / fallback）：PASS
- Gate C（Event Bus / Message Plane / Dispatch / Owner Gate）：PASS
- Runtime 写链路：PASS
- Gitea consistency sentinel：healthy
- memory search：仍为 disabled
- force-push：未使用
- 当前 active baseline：V1R4C5
- V1R4C6 tag：尚未创建

请明确回复以下其中一项：
A. 批准创建 V1R4C6 Git tag，并将 active baseline 从 V1R4C5 晋升至 V1R4C6。
B. 暂不批准，保持 V1R4C5，并说明需要处理的问题。

Authorization Rules

Do not treat reactions, emojis, acknowledgements, or ambiguous replies as approval.

Valid approval must explicitly authorize both:

create V1R4C6 Git tag
promote baseline V1R4C5 -> V1R4C6

If the owner approves only one operation, execute only the approved operation and stop before the other.

Before executing a consequential operation, record authorization in:

docs/releases/V1R4C6-owner-approval.md

Record only:

approved operation(s)
approved_at
approval channel = wechat
message/conversation identifier if available
owner identity reference without copying personal message content
memory search remains disabled

Do not store access tokens, cookies, phone numbers, or unrelated chat content.

WeChat Failure Handling

If the configured WeChat channel is unavailable:

1. Do not claim that a message was sent.
2. Stop before tag/promotion.
3. Write the exact final authorization request to:

/data/aios-gitops/runtime/state/V1R4C6-owner-confirmation-message.txt

4. Write notification failure details to:

/data/aios-gitops/runtime/state/V1R4C6-wechat-notification-failure.json

5. Report the failure through the active GitOps task/status channel.

Final Stop Condition

Before explicit owner authorization, final state must remain:

current_baseline = V1R4C5
V1R4C6 tag = absent
memory search = disabled

After owner authorization, follow the existing tag confirmation and baseline promotion controls. Do not bypass consequential-operation confirmation layers.