keep whether agents' feedback has been handled, and how

packages/db/prisma/migrations/v038_add_agent_feedback_resolution/migration.sql

@@ -0,0 +1,5 @@
+-- Whether we have handled an agent's feedback: when we marked it, and a short note on how, such as
+-- the pull request that fixed it. Both null while it is open, as all of it is so far.
+-- AlterTable
+ALTER TABLE "AgentFeedback" ADD COLUMN     "resolution" TEXT,
+ADD COLUMN     "resolvedAt" TIMESTAMP(3);

packages/db/prisma/schema.prisma

@@ -443,9 +443,10 @@ model AgentTask {
 // What an agent told the makers of Personal Agent Proxy, such as a tool that didn't work as it
 // expected: sent with the MCP server's send_feedback or the agent pages' feedback form, and read
 // by us, never shown in the app. Plain ids, like the activity log, so it stays when the agent or
-// the connection is gone; it goes with the organization.
+// the connection is gone; it goes with the organization. We mark what we have handled from our
+// own admin (resolvedAt, resolution); nothing here writes them.
 model AgentFeedback {
-  id           String   @id @default(cuid())
+  id           String    @id @default(cuid())
   orgId        String
   agentId      String
   // The agent's AGENT_PROVIDERS id, such as `claude`, kept beside the login it came from.
@@ -457,6 +458,10 @@ model AgentFeedback {
   via          AuditVia
   // The task the agent was on, where it named one.
   taskId       String?
+  // When we marked it handled, null while it is open, and a short note on how, such as the pull
+  // request that fixed it (`#151`) or `upstream`, where we gave one.
+  resolvedAt   DateTime?
+  resolution   String?
 
   createdAt DateTime @default(now())