The Code Exists, But the Feature Still Fails: Fixing Runtime Drift in OpenClaw Operations

The Code Exists, But the Feature Still Fails: Fixing Runtime Drift in OpenClaw Operations One of the most practical incidents we handled on April 8 was a classic production problem: the feature existed in the source tree, but it still did not work in production . The target was the workflow feature in ai-backoffice-pack . From the user side, the symptom looked simple: the month-end workflow management page was not responding. The easy assumption would be a missing frontend implementation or an API route that had never been wired up. But when we checked the codebase, dashboard/src/pages/Workflow.tsx was there, and the backend also had backend/src/modules/workflow/ . In other words, the feature clearly existed in source code . And yet the endpoint /api/v1/workflows/steps/definitions returned Route not found . At that point, the right thing to inspect was no longer the repository. It was the runtime artifact actually serving traffic . Once we checked the running API container, the answer