add e2e test under tests/ut/e2e

[huangxun375-stack]

Description

Add 2 end-to-end (E2E) test scripts for the OpenClaw + OpenViking integration, covering memory chain lifecycle and tool call capture. Each script includes detailed usage documentation, design rationale, and known limitations.

Related Issue

Type of Change

• Bug fix (non-breaking change that fixes an issue)
• New feature (non-breaking change that adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)
• Documentation update
• Refactoring (no functional changes)
• Performance improvement
• Test update

Changes Made

• Add tests/e2e/test-memory-chain.py: Full memory pipeline E2E test — covers afterTurn write → commit → assemble context → budget trimming → sessionId consistency → new-user memory recall (29 assertions, 6 phases)
• Add tests/e2e/test-tool-capture.py: E2E test for extractNewTurnTexts — verifies that toolUse/toolResult content is correctly captured and stored in OV session (15 assertions, 4 phases)
• Each script includes: detailed docstring (design rationale, usage, prerequisites, known limitations, expected results), --phase support for individual phase execution, rich formatted output with assertion tables

Testing

• I have added tests that prove my fix is effective or that my feature works
• New and existing unit tests pass locally with my changes
• I have tested this on the following platforms:
  • Linux
  • macOS
  • Windows

Test Results (Windows, 2026-04-01)

Test	Pass Rate	Duration
test-memory-chain.py	29/29 (100%)	~11 min
test-tool-capture.py	15/15 (100%)	~2 min
Key validations:

• Memory pipeline: 24 memories extracted, 5 commits, sessionId consistency verified (no sessionKey remnants), archive overview + budget trimming working correctly
• Tool capture: toolResult markers correctly stored in OV session, keyword traceability confirmed across Gateway response and OV storage

Checklist

• My code follows the project's coding style
• I have performed a self-review of my code
• I have commented my code, particularly in hard-to-understand areas
• I have made corresponding changes to the documentation
• My changes generate no new warnings
• Any dependent changes have been merged and published

Additional Notes

• These E2E tests require a running OpenClaw Gateway + OpenViking environment with LLM backend access
• Test stability depends on LLM behavior (keyword hit rate threshold is set to >= 50% to absorb response variability)
• Run with pip install requests rich as the only Python dependencies
• Each script supports --phase for individual phase execution and --verbose for detailed output

[CLAassistant]

All committers have signed the CLA.

[github-actions]

Failed to generate code suggestions for PR