fix: /status shows stale thinking level after directive change

[cmfinlan]

Problem

When /think high /status (or any /think X /status combo) is sent as a directive-only message, the Think: field in the status reply shows the old thinking level rather than the just-applied one.

Root cause

In get-reply-directives-apply.ts, resolvedDefaultThinkLevel is computed before handleDirectiveOnly runs. handleDirectiveOnly mutates sessionEntry.thinkingLevel to the new value, but the status reply still receives the stale pre-directive value.

Fix

After handleDirectiveOnly returns, re-resolve all directive levels from sessionEntry before passing them to buildStatusReply. This ensures the status output reflects the just-applied changes.

The same pattern is applied to verbose, reasoning, and elevated levels for consistency.

Tests

Added two regression tests to status.test.ts:

• Verifies resolvedThink matching the updated sessionEntry.thinkingLevel shows correctly
• Verifies sessionEntry.thinkingLevel fallback works when resolvedThink is omitted

All 28 tests pass.

Closes #10867

Greptile Summary

Fixes a stale status display bug where /think high /status (or any /directive /status combo) showed the old thinking level instead of the just-applied one. The fix re-resolves all directive levels (thinkingLevel, verboseLevel, reasoningLevel, elevatedLevel) from sessionEntry after handleDirectiveOnly mutates them, ensuring the status output reflects the current state.

Key changes:

• get-reply-directives-apply.ts: Re-reads directive levels from sessionEntry after handleDirectiveOnly completes before passing to buildStatusReply
• status.ts: Updated fallback chain to check sessionEntry levels when resolved* params are omitted
• session-status-tool.ts: Now explicitly resolves and passes all directive levels to buildStatusMessage
• Added comprehensive regression tests covering fallback behavior and the specific bug scenario
• Unrelated fix: gateway-lock.test.ts switched from fake timers to real timers to avoid intermittent CI hangs

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The fix correctly addresses the root cause by re-resolving directive levels after mutation. The implementation follows existing patterns, includes comprehensive regression tests (8 new test cases covering fallback chains and the bug scenario), and all 28 tests pass. The logic is straightforward with no edge cases or security concerns.
• No files require special attention

_{Last reviewed commit: 1516698}

[greptile-apps]

_{4 files reviewed, 1 comment}

_{Edit Code Review Agent Settings | Greptile}

[greptile-apps]

Invalid ReasoningLevel value in test

ReasoningLevel is defined as "off" | "on" | "stream", but this test uses "medium" which is not a valid value. The test still passes because SessionEntry.reasoningLevel is typed as string | undefined, but using an invalid value here weakens the test's fidelity — it's testing a scenario that shouldn't occur in practice. Consider using "on" or "stream" instead.

Suggested change

	sessionScope: "per-sender",
	reasoningLevel: "on",

Prompt To Fix With AI

This is a comment left during a code review.
Path: src/auto-reply/status.test.ts
Line: 129:129

Comment:
**Invalid `ReasoningLevel` value in test**

`ReasoningLevel` is defined as `"off" | "on" | "stream"`, but this test uses `"medium"` which is not a valid value. The test still passes because `SessionEntry.reasoningLevel` is typed as `string | undefined`, but using an invalid value here weakens the test's fidelity — it's testing a scenario that shouldn't occur in practice. Consider using `"on"` or `"stream"` instead.

```suggestion
        reasoningLevel: "on",
```

How can I resolve this? If you propose a fix, please make it concise.