Reconcile portable Hop prompt records with the latest accepted repository state

Hop-State: A_06FN6X5SEFS9VB6A92K2JE0
Hop-Proposal: R_06FN6X45KVCRM0P2G9SF9N0
Hop-Task: T_06FN6Q6CPY9NYPA25F6DKS8
Hop-Attempt: AT_06FN6WXQF509ZK786R6N7Z0

.hop/records/prompts/P_06FN3ZWPQTSC848DMGNM700.json

@@ -0,0 +1,16 @@
+{
+  "id": "P_06FN3ZWPQTSC848DMGNM700",
+  "task_id": "T_06FN3ZWPQS1937BKCB06S9G",
+  "attempt_id": "AT_06FN3ZWPQV0984HA5C79DY8",
+  "state_id": "P_06FN3ZWPQTSC848DMGNM700",
+  "prompt": "Hop currently treats the selected folder as a controller/canonical-state anchor:\nhop begin creates an isolated workspace under .hop/workspaces/.\nThe agent edits and tests there.\nhop propose freezes that workspace.\nhop accept advances Hop’s internal accepted Git tree.\nBut it does not check that accepted tree out into the visible project root.\nSo the work is stored and accepted, but the folder you selected still appears empty. Codex also hides .hop, making this especially confusing.\nFor desktop use, I think the correct behavior is:\nAgents continue working in isolated Hop workspaces.\nAcceptance updates Hop’s internal state.\nHop then safely materializes the accepted tree into /Users/christopher/Dev/HopWeb.\nIf that visible folder contains uncommitted user changes, Hop blocks synchronization instead of overwriting them.\nThat gives isolation during work while ensuring the selected project folder always displays the accepted result. The current behavior is effectively “bare controller mode,” and it’s wrong for the UX you expected.",
+  "agent_name": "codex",
+  "status": "active",
+  "created_at": "2026-07-11T16:25:32.606093Z",
+  "metadata": {
+    "source_tree": "1efea9a3d94dac0a5fbfc48dbe98cc4dc0a19ab8",
+    "git_commit": "d9544b435bd59c746909cb5103217bd6c86aad01",
+    "attempt_head": "P_06FN3ZWPQTSC848DMGNM700",
+    "attempt_head_kind": "prompt"
+  }
+}