Rename refresh menu label

packages/app/src/app/agent/[id].tsx

@@ -292,7 +292,7 @@ export default function AgentScreen() {
               >
                 <RotateCcw size={20} color={theme.colors.foreground} />
                 <Text style={styles.menuItemText}>
-                  {isInitializing ? "Refreshing..." : "Refresh from disk"}
+                  {isInitializing ? "Refreshing..." : "Refresh"}
                 </Text>
                 {isInitializing && (
                   <ActivityIndicator

plan.md

@@ -13,6 +13,8 @@
   - Added shared tool-call parsers plus a reusable diff viewer, then upgraded the permission cards to render plan markdown (ExitPlanMode), shell metadata, diffs, read content, and the raw payload directly inside the stream. Ran `npm run typecheck --workspace=@voice-dev/app`; please test across providers on-device once agents are hooked up.
 - [x] Investigate how each agent provider handles todo lists, we should have first class support for rendering those in the agent stream. I believe the Codex calls them plan and Claude uses TodoWrite tool calls. You can search the web, look at their node modules or just experiment via testing, which is a good diea anyways becaue we want tests for this, you just have to thinka bout how to trigger the agent to do plans / todo lists. Maybe just ask directly.
   - Normalized `todo` timeline entries into a dedicated `todo_list` stream item, rendered them with a new plan card in the agent stream (provider badge, completion status, checkboxes), and added consolidation logic plus regression coverage in `test-idempotent-stream.ts`. Ran `npm run typecheck --workspace=@voice-dev/app`.
-- [ ] Change "Refresh from disk" to "Refresh" in the agent three dot menu
+- [x] Change "Refresh from disk" to "Refresh" in the agent three dot menu
+  - Updated the agent overflow menu label in `packages/app/src/app/agent/[id].tsx` so the refresh action now matches the desired wording while keeping the busy state text untouched; no additional changes were required.
 - [ ] Are we filtering our own shats (already present in agents storage) from the resume agent list? We should if not.
 - [ ] Getting "two children with the same key" for "thoughts" and "assistant" review our keying strategy, and make it more robust and performant, and stable.
+- [ ] Hydrated session show previous tool calls as loading. At least for claude we're not loading the output Chekc Codex too.