bd sync: 2026-01-15 15:18:27

This commit is contained in:
dan 2026-01-15 15:18:27 -08:00
parent fedec9c46a
commit ec6c81b436
2 changed files with 2 additions and 2 deletions

View file

@ -204,7 +204,7 @@
{"id":"skills-m0e2","title":"Write developer docs for compiling/deployment workflow","status":"closed","priority":3,"issue_type":"task","created_at":"2026-01-10T23:14:36.685506396-08:00","created_by":"dan","updated_at":"2026-01-11T15:34:20.579336918-08:00","closed_at":"2026-01-11T15:34:20.579336918-08:00","close_reason":"Closed"}
{"id":"skills-m21","title":"Apply niri-window-capture code review recommendations","description":"CODE-REVIEW-niri-window-capture.md identifies action items: add dependency checks to scripts, improve error handling for niri failures, add screenshot directory validation, implement rate limiting. See High/Medium priority sections.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-11-30T11:58:24.648846875-08:00","updated_at":"2025-12-28T20:16:53.914141949-05:00","closed_at":"2025-12-28T20:16:53.914141949-05:00","close_reason":"Implemented all 4 high-priority recommendations from code review: dependency checks, directory validation, error handling, audit logging"}
{"id":"skills-mjf","title":"Design: Portable adversarial reviewer","description":"Design a reviewer agent/skill that can run on any capable model.\n\nalice is Claude Opus with specific tools. We need:\n- Model-agnostic reviewer prompt/instructions\n- Tool requirements (read-only: Read, Grep, Glob, Bash)\n- Integration with orch for multi-model consensus\n- Decision format (APPROVED/ISSUES)\n- Issue filing (beads or tissue)\n\nKey principles from alice:\n- Work for the USER, not the agent\n- Assume errors exist, find them\n- Steel-man then attack\n- Seek second opinions\n\nOutput: Reviewer skill spec that works across agents","status":"closed","priority":3,"issue_type":"task","created_at":"2026-01-09T17:14:20.778647076-08:00","created_by":"dan","updated_at":"2026-01-09T19:59:37.80146821-08:00","closed_at":"2026-01-09T19:59:37.80146821-08:00","close_reason":"Covered in architecture design doc - adversarial reviewer section"}
{"id":"skills-mlhe","title":"ui-query: extract shared find_elements() to common module","status":"open","priority":2,"issue_type":"task","owner":"dan@delpad","created_at":"2026-01-15T14:22:03.995612109-08:00","created_by":"dan","updated_at":"2026-01-15T14:22:03.995612109-08:00"}
{"id":"skills-mlhe","title":"ui-query: extract shared find_elements() to common module","status":"closed","priority":2,"issue_type":"task","owner":"dan@delpad","created_at":"2026-01-15T14:22:03.995612109-08:00","created_by":"dan","updated_at":"2026-01-15T15:18:23.469683869-08:00","closed_at":"2026-01-15T15:18:23.469683869-08:00","close_reason":"Extracted to common.py, imported in find-element.py and query-state.py"}
{"id":"skills-ms5","title":"Design: Local message passing layer","description":"Design: Local message passing layer\n\nImplementation: Nim (tiny_sqlite, channels)\nDesign doc: docs/design/message-passing-layer.md (v4)\n\nKey components:\n- SQLite WAL mode as source of truth\n- Heartbeat thread with own connection + channel control\n- Task claims with lease expiry\n- At-least-once delivery with explicit ack\n- JSONL export for debugging\n\nSee: skills-q40 for language decision","design":"docs/design/message-passing-layer.md","notes":"DESIGN UPDATED v2: SQLite as primary storage (not JSONL+flock). After orch consensus (3 models unanimous), aligned with Beads approach. Key change: SQLite with BEGIN IMMEDIATE for atomic writes, WAL mode for concurrency. JSONL becomes read-only export for debugging. See docs/design/message-passing-layer.md and message-passing-comparison.md.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-10T13:24:21.597509853-08:00","created_by":"dan","updated_at":"2026-01-11T21:23:19.067533522-08:00","closed_at":"2026-01-11T21:23:19.067533522-08:00","close_reason":"Solved by bd comments approach - orch consensus unanimously supported using existing bd comments instead of building separate JSONL layer","dependencies":[{"issue_id":"skills-ms5","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-10T13:24:36.033492407-08:00","created_by":"dan"}]}
{"id":"skills-mx3","title":"spec-review: Define consensus thresholds and decision rules","description":"'Use judgment' for mixed results leads to inconsistent decisions.\n\nDefine:\n- What constitutes consensus (2/3? unanimous?)\n- How to handle NEUTRAL votes\n- Tie-break rules\n- When human override is acceptable and how to document it","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-15T00:23:24.121175736-08:00","updated_at":"2025-12-15T13:58:04.339283238-08:00","closed_at":"2025-12-15T13:58:04.339283238-08:00"}
{"id":"skills-n3qp","title":"Use case-insensitive conflict detection in rebaseOnIntegration","description":"[SMELL] MED git.nim:70 - Checks 'CONFLICT' and 'conflict' separately with fragile string matching. Use output.toLowerAscii().contains(\"conflict\") for robustness.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-01-10T19:52:13.875954227-08:00","created_by":"dan","updated_at":"2026-01-10T20:55:02.354755642-08:00","closed_at":"2026-01-10T20:55:02.354755642-08:00","close_reason":"P2 bugs fixed"}

View file

@ -145,7 +145,7 @@
{"id":"skills-dtk","title":"Consolidate isStale() and staleLevel() logic","description":"[SMELL] MED state.nim:214-223,225-241 - Both compute heartbeat age with overlapping checks. Have isStale() call staleLevel() \\!= 'ok', or extract shared ageStatus() helper.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-10T19:49:51.730374503-08:00","created_by":"dan","updated_at":"2026-01-11T15:38:00.466085606-08:00","closed_at":"2026-01-11T15:38:00.466085606-08:00","close_reason":"Closed"}
{"id":"skills-du0a","title":"HQ: Structured communication templates","description":"**Raised by:** gpt (primary), gemini\n\n**Problem:**\nBD comments as message bus lacks structure. Questions/answers get buried. No threading. No way to signal \"requires HQ decision\" vs \"FYI\". No attachments/artifacts.\n\n**gpt:**\n> \"Require periodic worker 'state summaries' in a fixed schema (Summary / Risks / Next / Questions / Diffstat). Have HQ post a running 'Decision Log' comment for traceability.\"\n\n**Suggested templates:**\n\n**HQ kickoff comment:**\n- Scope (in/out)\n- Acceptance criteria bullets\n- Required checks (tests/lint/typecheck)\n- Risk areas / files\n- \"Ask before changing X\"\n\n**Worker update (every heartbeat):**\n- What changed\n- What's next\n- Blockers/questions\n- Commands run + results\n- Link to diff/commits\n\n**Suggested fixes:**\n1. Kickoff template posted by HQ\n2. Periodic state summary schema for workers\n3. Decision log comment (edited/superseding)\n4. \"Latest instruction\" pinning","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-12T09:23:26.910596266-08:00","created_by":"dan","updated_at":"2026-01-12T09:23:26.910596266-08:00"}
{"id":"skills-e8h","title":"Investigate waybar + niri integration improvements","description":"Look into waybar configuration and niri compositor integration.\n\nPotential areas:\n- Waybar modules for niri workspaces\n- Status indicators\n- Integration with existing niri-window-capture skill\n- Custom scripts in pkgs/waybar-scripts\n\nRelated: dotfiles has home/waybar.nix (196 lines) and pkgs/waybar-scripts/","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-28T20:11:23.115445797-05:00","created_by":"dan","updated_at":"2025-12-28T20:37:16.465731945-05:00","closed_at":"2025-12-28T20:37:16.465731945-05:00","close_reason":"Moved to dotfiles repo - waybar config lives there"}
{"id":"skills-e94u","title":"ui-query: extract shared find_windows() to common module","status":"open","priority":2,"issue_type":"task","owner":"dan@delpad","created_at":"2026-01-15T14:22:03.79081457-08:00","created_by":"dan","updated_at":"2026-01-15T14:22:03.79081457-08:00"}
{"id":"skills-e94u","title":"ui-query: extract shared find_windows() to common module","status":"closed","priority":2,"issue_type":"task","owner":"dan@delpad","created_at":"2026-01-15T14:22:03.79081457-08:00","created_by":"dan","updated_at":"2026-01-15T14:54:16.135426883-08:00","closed_at":"2026-01-15T14:54:16.135426883-08:00","close_reason":"Extracted to common.py, imported in get-text.py and find-element.py"}
{"id":"skills-e96","title":"skill: semantic-grep using LSP","description":"Use workspace/symbol, documentSymbol, and references instead of ripgrep.\n\nExample: 'Find all places where we handle User objects but only where we modify the email field directly'\n- LSP references finds all User usages\n- Filter by AST analysis for .email assignments\n- Return hit list for bead or further processing\n\nBetter than regex for Go interfaces, Rust traits, TS types.","status":"open","priority":3,"issue_type":"task","created_at":"2025-12-24T02:29:57.119983837-05:00","updated_at":"2025-12-24T02:29:57.119983837-05:00","dependencies":[{"issue_id":"skills-e96","depends_on_id":"skills-gga","type":"blocks","created_at":"2025-12-24T02:30:06.632906383-05:00","created_by":"daemon"}]}
{"id":"skills-ebh","title":"Compare bd-issue-tracking skill files with upstream","description":"Fetch upstream beads skill files and compare with our condensed versions to identify differences","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-03T20:14:07.886535859-08:00","updated_at":"2025-12-03T20:19:37.579815337-08:00","closed_at":"2025-12-03T20:19:37.579815337-08:00"}
{"id":"skills-ebl","title":"Benchmark vision model UI understanding","description":"## Goal\nMeasure how well vision models can answer UI questions from screenshots.\n\n## Test cases\n1. **Element location**: \"Where is the Save button?\" → coordinates\n2. **Element identification**: \"What buttons are visible?\" → list\n3. **State detection**: \"Is the checkbox checked?\" → boolean\n4. **Text extraction**: \"What does the error message say?\" → text\n5. **Layout understanding**: \"What's in the sidebar?\" → structure\n\n## Metrics\n- Accuracy: Does the answer match ground truth?\n- Precision: How close are coordinates to actual element centers?\n- Latency: Time from query to response\n- Cost: Tokens consumed per query\n\n## Prompt engineering questions\n- Does adding a grid overlay help coordinate precision?\n- What prompt format gives most actionable coordinates?\n- Can we get bounding boxes vs point coordinates?\n\n## Comparison baseline\n- Manual annotation of test screenshots\n- AT-SPI data (once enabled) as ground truth\n\n## Depends on\n- Test screenshots from real apps\n- Ground truth annotations","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-17T14:13:10.038933798-08:00","updated_at":"2025-12-29T15:26:19.822655148-05:00","closed_at":"2025-12-29T15:26:19.822655148-05:00","close_reason":"Benchmark complete. Vision models excellent for semantic understanding, approximate for coordinates. Recommend hybrid AT-SPI + vision. See docs/research/vision-ui-benchmark-2025-12-29.md"}