Bug type

Regression (worked before, now fails)

Beta release blocker

No

Summary

After upgrading OpenClaw from 2026.3.28 to 2026.3.31 on WSL2, the LINE provider stopped working and repeatedly restarted with Unable to resolve runtime module ./runtime-line.contract.

Steps to reproduce

1. Start from a working OpenClaw 2026.3.28 environment with LINE functioning normally.
2. Upgrade OpenClaw to 2026.3.31.
3. Restart the gateway or let the service restart.
4. Observe that the LINE provider exits and enters an auto-restart loop.
5. Check logs for Unable to resolve runtime module ./runtime-line.contract.

Expected behavior

Under the same environment and workflow, LINE works normally on 2026.3.28 and should continue working after upgrade.

Actual behavior

After upgrading to 2026.3.31, the LINE provider exits during startup and repeatedly restarts. Rolling back to 2026.3.28 restores LINE functionality.

OpenClaw version

2026.3.31

Operating system

Linux (WSL2)

Install method

Global install / update path showed pnpm / npm update

Model

openai-codex/gpt-5.4

Provider / routing chain

openclaw -> openai-codex

Additional provider/model setup details

Default model in the affected environment was openai-codex/gpt-5.4. The observed LINE failure occurred during provider startup and was not dependent on model generation behavior.

Logs, screenshots, and evidence

Relevant log lines:
Observed version comparison:
- Last known good: 2026.3.28
- First known bad: 2026.3.31

Observed recovery:
- Rolling back to 2026.3.28 restored LINE runtime behavior.

Additional incident note:
- A separate stale ngrok systemd override affected public webhook recovery after rollback, but that was a separate host issue and not the root cause of the LINE runtime failure itself.

Impact and severity

Affected users/systems/channels:

• LINE channel on a WSL2-based OpenClaw environment

Severity:

• High (LINE becomes unavailable after upgrade)

Frequency:

• Observed consistently after upgrade to 2026.3.31 in this environment

Consequence:

• LINE provider does not stay running, so LINE messaging stops working until rollback

Additional information

This appears to be a regression between:

• Last known good: 2026.3.28
• First known bad: 2026.3.31

The observed failure is a runtime/module resolution error during LINE provider startup, not a LINE token/secret misconfiguration. Rolling back to 2026.3.28 restored LINE functionality in the same environment.