Reliability Results Log

Timestamp: 20260310-115636

Session Goal

Validate the tool layer with the new local MCP harness.
Investigate whether the live external MCP transport can be reloaded safely in-session.

Added:
- research/experiments/local_mcp_tool_call.py
- research/experiments/calculator_verify_probe.py
- research/experiments/run_local_suite.py
Results:
- local_mcp_tool_call.py --tool Snapshot showed the new timestamp and informative text section in real tool output.
- calculator_verify_probe.py passed with Display is 15.
- run_local_suite.py passed end to end for:
  - Notepad typing
  - Calculator result verification
  - localized Notepad launch
  - Notepad switch

Process experiment:
- Killed the older uv.exe -> windows-mcp.exe -> python.exe tree.
- Verified that the in-session windows-mcp/* tools still worked, so that tree was not backing the active connection.
- Killed the remaining active tree.
- Immediate follow-up Clipboard call failed with Transport closed.
- Manually started a fresh uv.exe --directory C:\\Users\\Rufus\\src\\Windows-MCP run windows-mcp.
- Follow-up Clipboard call still failed with Transport closed.
Conclusion:
- The current host-side MCP client does not automatically reattach to a fresh windows-mcp process after transport closure.
- A manual reconnect from the host application is required.

Exact blocked step:
- resume live mcp__windows-mcp__* tool retests against the patched server from within the current session
Actual blocker:
- the external transport is closed and did not recover after manual server restart
Narrowest next human action:
- reconnect or reload the windows-mcp MCP server from the host application that owns the tool connection