sync: multiple features from private repo

- quick-add-loading: fire-and-forget with loading placeholders, auto-open feed, SSE events, QuickAddInput redesign
- database-table-pane: TablePane + DatabaseTableView, countNodes(), event_date sort
- ui-polish-fixes: focus tab order, dim name editing, tab title sync, cost chip removal, custom sort drag-reorder, refresh button, dimension filter removal (~2,200 lines)
- node-creation-quality: description service prompt rewrite, title sanitization, extraction tool AI prompt rewrites
- feed-pane-ux: stripped kanban/grid/saved views, sort dropdown, AND dimension filtering, description preview

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
This commit is contained in:
“BeeRad”
2026-02-15 17:57:32 +11:00
co-authored by Claude Opus 4.6
parent 9954792b1d
commit 2f6518207d
25 changed files with 1590 additions and 2647 deletions
+14 -4
View File
@@ -28,11 +28,21 @@ When creating a node derived from existing content:
## Dimension Assignment
- New nodes should be assigned to relevant existing dimensions
- Check locked/priority dimensions — these auto-assign
- Check priority dimensions — assign these when relevant
- If no existing dimension fits, create a new one (but prefer existing)
## Description Field
- AI auto-generates a ~1 sentence description after creation
- Description is used for embeddings and search ranking (5x boost)
- Format: what is this node about, in plain language
The description is the most important field for AI context. It powers search (5x boost),
appears in system prompts, and determines how agents understand the node.
**Standard:** State WHAT this is + WHY it matters. Extremely concise, high-level. Max 280 characters.
**Rules:**
- NO weak verbs: "discusses", "explores", "examines", "talks about"
- State the actual claim, insight, or purpose directly
- Include significance or implication in 1 phrase
- If auto-generated (omitted), the system will generate one — but agent-written descriptions are always better
**Good:** "By Karpathy — Software is becoming fluid: agents can rip functionality from repos instead of taking dependencies."
**Bad:** "This article discusses the importance of software becoming more fluid."