feat: validate apply rollback flow / 驗證 apply rollback 流程

reports/phase4-acceptance-update.md

@@ -0,0 +1,53 @@
+# Phase 4 Acceptance Update
+
+- Date: 2026-05-13
+- Scope: pluginization path validation
+
+## What was validated
+
+The first version of the apply/rollback flow has now been validated against a pristine extracted `openclaw@2026.5.7` package.
+
+### Apply validation
+
+The apply script successfully injected the expected PoC markers into:
+
+- `send-sxDwUGaO.js`
+- `bot-Ce301bOE.js`
+
+Confirmed markers after apply included:
+
+- `rec:continue`
+- `A. 繼續`
+- `reply-end-controls.json`
+- `reply-end-debug.log`
+
+### Rollback validation
+
+The rollback script successfully restored the pristine files.
+
+Confirmed markers were gone again after rollback.
+
+## What this means
+
+This is not yet the final pluginized architecture, but it proves that the project now has a reproducible patch application path instead of depending entirely on undocumented manual edits.
+
+That is an important Phase 4 milestone because it reduces one of the biggest operational risks of the current PoC.
+
+## What is still missing
+
+- the live `openclawtest` runtime is still driven by direct patched OpenClaw runtime files
+- the runtime patches still need to be reduced and progressively replaced by cleaner repo-owned integration seams
+- callback behavior still needs more deterministic acceptance coverage in the live environment
+
+## Current judgment
+
+The project now has:
+
+- design documents
+- PoC success proof
+- reusable core/store/policy/callback modules
+- OpenClaw bridge helpers
+- unit tests
+- reproducible apply/rollback patch scripts
+
+That is enough to say the pluginization effort is materially underway, not just planned.