Fix archive (and every other mutation) not persisting to IndexedDB

[shashankbl]

The bug

Reported: "archive options does not seem to work correctly."

Cause: every mutation function in `lib/store.tsx` used this pattern:

```ts
let updated: Project | undefined;
setStore((s) => {
// …compute merged value
updated = merged;
return { ...s, projects: nextList };
});
if (updated) await writeProject(updated); // ❌ never runs
```

React's `useState` updater function is invoked during the next
render — not synchronously inside the `setStore` call. So
`updated` was still `undefined` when the `if` ran. The IDB write
was skipped entirely.

In-memory state flipped correctly (the UI showed archived banners,
items disappeared from lists, etc.), but nothing was persisted. On
the next page refresh / IDB rehydrate, the original un-archived
data came back.

This affected eight mutation paths:

• `updateProject` / `updateMember` / `updateCFP`
• `assignMemberToProject` / `unassignMemberFromProject`
• `assignProjectToCFP` / `updateCFPAssignment` / `unassignProjectFromCFP`

So: archive, restore, status changes, plan/setup edits, member
assignment toggles, CFP assignment toggles, CFP-status changes,
notes on CFP assignments, etc. — none of those edits survived a
refresh.

The fix

Wrap the updater in a Promise and resolve from inside it:

```ts
const updated = await new Promise<Project | undefined>((resolve) => {
setStore((s) => {
const target = s.projects.find((p) => p.id === id);
if (!target) { resolve(undefined); return s; }
const merged = { ...target, ...patch, updatedAt: new Date().toISOString() };
resolve(merged);
return { ...s, projects: s.projects.map((p) => p.id === id ? merged : p) };
});
});
if (updated) await writeProject(updated);
```

Same shape applied across all eight mutations. The Promise's
`resolve` fires from inside the updater, which React runs during
its render — so the `await` actually waits for the computed value.

Also `await` the update calls from the Archive button handlers on
`/projects/[id]`, `/members/[id]`, `/cfps/[id]` so the IDB write
completes before `router.push` navigates away (otherwise tab-close
during navigation could lose the write).

Test plan

• Create a project, archive it from the detail page, navigate to /projects — gone
• Visit /archives — shows the archived project. Reload the page — still shows it (this is the regression test; before this fix it would re-appear in /projects)
• Restore from /archives, reload — back in /projects, gone from /archives
• Permanent Delete from /archives, reload — fully gone
• Same flow for a member and a CFP
• Edit a project's plan / setup, reload — edit persists
• Assign a member to a project, reload — assignment persists
• Assign a CFP to a project, set status to `submitted`, reload — both persist

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
pi-hub	Ready	Preview, Comment	May 20, 2026 1:06am