V1R4C6 merge candidate (squashed). Contains 10 files, ~1440 lines added across: - docs/releases/ (6 files: checklist, evidence, blocker, resume, merge-matrix, gate-status) - ops/openclaw/ (2 files: integrate-deploy-verify, run-to-owner-gate-wechat) - patches/ (1 file: branch patch) - versions/ (1 file: V1R4C6.json) Task: admin workbench, SR-03 Search Gateway, Agent Platform Integration Baseline: V1R4C5 V1R4C5 tag semantics: - tag refs/tags/V1R4C5 targetd457ac3: immutable release snapshot - baseline gita32c76a: runtime baseline promotion commit No tag creation, baseline promotion, or memory search activation in this merge.
2.1 KiB
V1R4C6 Context Isolation Recovery and Resume Decision
Date: 2026-07-11
Status: approved to resume merge/deploy/verification; stop before tag/promotion
Recovery Evidence
The unrelated OpenClaw/WeChat report was traced to notification/task isolation weaknesses rather than GitOps baseline corruption.
Actions completed:
- The legacy
AIOS每日自治报告cron was disabled and retained for forensic review. - The expired
2026-07-06-remindercron was archived and deleted after confirming no pending dependency. - Pending notification queue depth was verified as zero.
- Unknown/unscoped queued message count was verified as zero.
- A scoped V1R4C6 WeChat test notification was sent successfully.
The test notification included:
task_id = V1R4C6-integration
release_id = V1R4C6
branch = release/v1r4c6-admin-search-agent-integration-20260711
baseline = V1R4C5
correlation_id = 70308f5e243ab81d
No recipient identifier, token, cookie, or unrelated message content is stored in this release record.
Resume Decision
V1R4C6 may resume:
merge
component tests
security/isolation tests
deployment
production verification
release evidence updates
V1R4C6 must still stop before:
Git tag creation
baseline promotion
memory search activation
Required Execution Context
Before every OpenClaw execution or WeChat notification, assert:
task_id = V1R4C6-integration
release_id = V1R4C6
branch = release/v1r4c6-admin-search-agent-integration-20260711
baseline = V1R4C5
memory_search_enabled = false
Any mismatch re-enters safe mode and blocks execution/notification.
Hard Constraints
no force-push
no Gitea DB mutation
no V1R4C5 tag movement
no global memory/vector index
no cross-user/project/session notification or task data
Owner Gate
After Gate A, Gate B, Gate C, deployment verification, runtime acceptance, and Gitea sentinel checks pass, OpenClaw must request explicit owner approval through the scoped WeChat channel for both:
- Create V1R4C6 Git tag.
- Promote active baseline from V1R4C5 to V1R4C6.
Ambiguous acknowledgements do not count as approval.