fix: run work-metrics update on every transform pass

The initial work-metrics integration (commit fbfbc5a) gated the
computeOpenCodeWorkMetrics + setSessionWorkMetrics call on
workExecutedSuccessfully (OpenCode) and result.executedWorkThisPass (Pi).
That gate is overly conservative: the work-metrics update is a pure DB
read on the OpenCode message table plus a pure DB write to session_meta.
It does not mutate any tag state, does not rewrite message[0], and is
cache-stable.

Net effect of the bug: sessions sitting below the execute threshold
(default 65%) never see populated new_work_tokens / total_input_tokens
columns, so the TUI sidebar Stats section shows 0/0/0 for any session
that hasn't crossed threshold yet. For long-running but low-pressure
work this is essentially permanent.

Fix moves the work-metrics update out of the executedWorkSuccessfully
branch and runs it on every transform pass. Both OpenCode and Pi paths
updated symmetrically.

Verified:
- packages/plugin: typecheck clean, work-metrics.test.ts 6/6 pass
  (including live AFT smoke target)
- packages/pi-plugin: typecheck clean, work-metrics-pi.test.ts 1/1 pass
- Both dist bundles rebuilt

Author: ualtinok

packages/pi-plugin/src/context-handler.ts

@@ -1827,21 +1827,26 @@ export function registerPiContextHandler(
 				);
 			}
 
-			if (result.executedWorkThisPass) {
-				try {
-					const metrics = computePiWorkMetrics(outputMessages as unknown[]);
-					setSessionWorkMetrics(
-						options.db,
-						sessionId,
-						metrics.newWorkTokens,
-						metrics.totalInputTokens,
-					);
-				} catch (err) {
-					sessionLog(
-						sessionId,
-						`work-metrics update failed: ${err instanceof Error ? err.message : String(err)}`,
-					);
-				}
+			// Work-metrics update runs on EVERY transform pass (not just
+			// execute passes). The Pi compute helper is pure-read on
+			// outputMessages; setSessionWorkMetrics is a pure write to
+			// session_meta (no tag state, no message[0] mutation, no
+			// cache-busting). Gating on executedWorkThisPass would mean
+			// sessions sitting below execute threshold never see populated
+			// values, making Pi's status surface permanently zero.
+			try {
+				const metrics = computePiWorkMetrics(outputMessages as unknown[]);
+				setSessionWorkMetrics(
+					options.db,
+					sessionId,
+					metrics.newWorkTokens,
+					metrics.totalInputTokens,
+				);
+			} catch (err) {
+				sessionLog(
+					sessionId,
+					`work-metrics update failed: ${err instanceof Error ? err.message : String(err)}`,
+				);
 			}
 
 			logTransformTiming(sessionId, "postTransformPhase", tPostTransform);

packages/plugin/src/hooks/magic-context/transform-postprocess-phase.ts

@@ -960,21 +960,27 @@ export async function runPostTransformPhase(
         heuristicsRanSuccessfully ||
         pendingOpsRanSuccessfully;
 
-    if (workExecutedSuccessfully) {
-        try {
-            const metrics = withReadOnlySessionDb((openCodeDb) =>
-                computeOpenCodeWorkMetrics(openCodeDb, args.sessionId),
-            );
-            setSessionWorkMetrics(
-                args.db,
-                args.sessionId,
-                metrics.newWorkTokens,
-                metrics.totalInputTokens,
-            );
-        } catch (err) {
-            sessionLog(args.sessionId, "work-metrics update failed:", getErrorMessage(err));
-        }
+    // Work-metrics update runs on EVERY transform pass (not just execute passes).
+    // The SQL helper is pure-read on OpenCode's message table; setSessionWorkMetrics
+    // is a pure write to session_meta (no tag state, no message[0] mutation, no
+    // cache-busting). Gating on workExecutedSuccessfully would mean sessions
+    // sitting below execute threshold never see populated values, making the
+    // TUI Stats section permanently zero for low-pressure work.
+    try {
+        const metrics = withReadOnlySessionDb((openCodeDb) =>
+            computeOpenCodeWorkMetrics(openCodeDb, args.sessionId),
+        );
+        setSessionWorkMetrics(
+            args.db,
+            args.sessionId,
+            metrics.newWorkTokens,
+            metrics.totalInputTokens,
+        );
+    } catch (err) {
+        sessionLog(args.sessionId, "work-metrics update failed:", getErrorMessage(err));
+    }
 
+    if (workExecutedSuccessfully) {
         try {
             const currentFlag = peekDeferredExecutePending(args.db, args.sessionId);
             if (currentFlag !== null) {