fix(lib): restore automatic hashtag creation for unknown tags

[antontranelis]

Summary

• Fix stale closure bug in useTags.tsx that prevented addTag from accessing current state
• Add missing useEffect in PopupView.tsx to persist newly detected hashtags to the database

Problem

Hashtags in item text that didn't exist in the database were not being automatically created. For example, #networking would appear as plain black text instead of being recognized as a hashtag with a color.

Root Causes

1. Stale Closure in addTag (useTags.tsx)

The addTag function used tags and api from the closure scope, which were stale when the function was called:

// Before: stale closure
const addTag = (tag: Tag) => {
  dispatch({ type: 'ADD', tag })
  if (!tags.some(...)) {  // ← tags is stale
    api.createItem && api.createItem(tag)  // ← api is stale
  }
}

2. Missing Persistence (PopupView.tsx)

New tags were detected and collected in newTagsToAdd state, but never actually persisted:

// Tags were added to local state...
setNewTagsToAdd((current) => [...current, newTag])
// ...but never sent to the database

Solution

useTags.tsx

• Use useRef for apiRef and tagsRef to always access current values
• Wrap addTag in useCallback with empty dependencies

PopupView.tsx

• Import useAddTag hook
• Add useEffect that calls addTag for each new tag when newTagsToAdd changes

Test plan

• Create an item with a new hashtag (e.g., #testnewtag)
• Verify the hashtag appears with a random color (not black)
• Refresh the page and verify the hashtag persists with its color
• Check the database to confirm the tag was created

🤖 Generated with Claude Code