bd sync: 2026-01-18 08:27:06
This commit is contained in:
dan
parent
5b8dbfde45
commit
fb43fbb0fc
|
|
@ -7,7 +7,7 @@
|
|||
{"id":"skills-0u9","title":"Consolidate: Merge overlapping cross-agent design tasks","description":"Merge overlapping research/design tasks into coherent work items.\n\n## Current Overlap\n- skills-3gk: Research: Cross-agent hook alternatives\n- skills-3ja: Design: Cross-agent quality gate architecture \n- skills-thk: Design: Hybrid hook + gate architecture\n- skills-6fu: Research: State management for cross-agent workflows\n\nThese all touch the same problem space.\n\n## Proposed Consolidation\n1. Close overlapping tasks with \"consolidated\" reason\n2. Create single \"Design: Cross-agent enforcement architecture\" task\n3. Update epic description to reference consolidated task\n\n## Deliverable\nClean task list with no duplication","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-09T19:32:57.364887317-08:00","created_by":"dan","updated_at":"2026-01-09T19:33:42.464968954-08:00","closed_at":"2026-01-09T19:33:42.464968954-08:00","close_reason":"Created skills-8sj, closed 4 overlapping tasks"}
|
||||
{"id":"skills-0vec","title":"ui-query: consider extracting state extraction helper","status":"open","priority":4,"issue_type":"task","owner":"dan@delpad","created_at":"2026-01-15T14:22:04.663482444-08:00","created_by":"dan","updated_at":"2026-01-15T14:22:04.663482444-08:00"}
|
||||
{"id":"skills-0wk","title":"Fix predictable ID generation in genOid()","description":"[SECURITY] HIGH db.nim:14-18 - genOid() uses rand(25) without randomize() call. IDs are predictable/deterministic. Add randomize() at module init or use std/sysrand for crypto-safe IDs.","status":"closed","priority":1,"issue_type":"bug","created_at":"2026-01-10T18:52:35.120227893-08:00","created_by":"dan","updated_at":"2026-01-10T20:24:36.546618405-08:00","closed_at":"2026-01-10T20:24:36.546618405-08:00","close_reason":"Fixed: genOid() now uses std/sysrand for cryptographically secure random IDs"}
|
||||
{"id":"skills-0y9","title":"Design: Structured task specs (requirements/design/tasks)","description":"Adopt spec-driven development pattern from Kiro/Tessl/GitHub Spec Kit. Each task should have: requirements.md (what), design.md (how), tasks.md (decomposed steps). Agents work from specs not vague prompts. Specs are versioned; agents echo which version they used. Prevents state divergence and 'different reality' footgun.","status":"open","priority":2,"issue_type":"task","created_at":"2026-01-10T15:40:59.99198595-08:00","created_by":"dan","updated_at":"2026-01-10T15:40:59.99198595-08:00","dependencies":[{"issue_id":"skills-0y9","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-10T15:41:00.005934153-08:00","created_by":"dan"}]}
|
||||
{"id":"skills-0y9","title":"Design: Structured task specs (requirements/design/tasks)","description":"Adopt spec-driven development pattern from Kiro/Tessl/GitHub Spec Kit. Each task should have: requirements.md (what), design.md (how), tasks.md (decomposed steps). Agents work from specs not vague prompts. Specs are versioned; agents echo which version they used. Prevents state divergence and 'different reality' footgun.","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-10T15:40:59.99198595-08:00","created_by":"dan","updated_at":"2026-01-18T08:27:05.922090984-08:00","closed_at":"2026-01-18T08:27:05.922090984-08:00","close_reason":"Superseded by skills-oh8m (simplified design/plan/tasks approach)","dependencies":[{"issue_id":"skills-0y9","depends_on_id":"skills-s6y","type":"blocks","created_at":"2026-01-10T15:41:00.005934153-08:00","created_by":"dan"}]}
|
||||
{"id":"skills-16zf","title":"Check for symlinks before reading context file","description":"[SECURITY] MED context.nim:21,31 - readFile follows symlinks, could read arbitrary files if .worker-ctx.json is symlinked. Check that path is regular file before reading.","status":"closed","priority":2,"issue_type":"bug","created_at":"2026-01-10T20:10:03.403878355-08:00","created_by":"dan","updated_at":"2026-01-10T20:55:02.344845949-08:00","closed_at":"2026-01-10T20:55:02.344845949-08:00","close_reason":"P2 bugs fixed"}
|
||||
{"id":"skills-17f","title":"Ensure git access to both local Forgejo and ops-jrz1 Forgejo","description":"Need reliable access to both git servers for plugin development and deployment:\n\n**Local Forgejo (home):**\n- URL: http://192.168.1.108:3000\n- Currently down/unreachable at times\n- Used for skills repo remote\n\n**ops-jrz1 Forgejo (VPS):**\n- URL: https://git.clarun.xyz\n- Production server\n- Target for emes plugin deployment\n\n**Tasks:**\n- Verify local Forgejo is running (systemctl status)\n- Add ops-jrz1 as additional remote for skills repo\n- Consider mirroring skills repo to both\n- Document which forge is source of truth","status":"closed","priority":2,"issue_type":"task","created_at":"2026-01-09T11:14:52.639492685-08:00","created_by":"dan","updated_at":"2026-01-09T16:57:16.417563927-08:00","closed_at":"2026-01-09T16:57:16.417563927-08:00","close_reason":"Multi-push configured: origin pushes to both local and clarun Forgejos"}
|
||||
{"id":"skills-1ig","title":"Brainstorm agent-friendly doc conventions","description":"# Agent-Friendly Doc Conventions - Hybrid Architecture\n\n## FINAL ARCHITECTURE: Vale + LLM Hybrid\n\n### Insight\n\u003e \"Good old deterministic testing (dumb robots) is the best way to keep in check LLMs (smart robots) at volume.\"\n\n### Split by Tool\n\n| Category | Rubrics | Tool |\n|----------|---------|------|\n| Vale-only | Format Integrity, Deterministic Instructions, Terminology Strictness, Token Efficiency | Fast, deterministic, CI-friendly |\n| Vale + LLM | Semantic Headings, Configuration Precision, Security Boundaries | Vale flags, LLM suggests fixes |\n| LLM-only | Contextual Independence, Code Executability, Execution Verification | Semantic understanding required |\n\n### Pipeline\n\n```\n┌─────────────────────────────────────────────────────────────┐\n│ Stage 1: Vale (deterministic, fast, free) │\n│ - Runs in CI on every commit │\n│ - Catches 40% of issues instantly │\n│ - No LLM cost for clean docs │\n└─────────────────────┬───────────────────────────────────────┘\n │ only if Vale passes\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ Stage 2: LLM Triage (cheap model) │\n│ - Evaluates 3 semantic rubrics │\n│ - Identifies which need patches │\n└─────────────────────┬───────────────────────────────────────┘\n │ only if issues found\n ▼\n┌─────────────────────────────────────────────────────────────┐\n│ Stage 3: LLM Specialists (capable model) │\n│ - One agent per failed rubric │\n│ - Generates patches │\n└─────────────────────────────────────────────────────────────┘\n```\n\n### Why This Works\n- Vale is battle-tested, fast, CI-native\n- LLM only fires when needed (adaptive cost)\n- Deterministic rules catch predictable issues\n- LLM handles semantic/contextual issues\n\n---\n\n## Vale Rules Needed\n\n### Format Integrity\n- Existence: code blocks without language tags\n- Regex for unclosed fences\n\n### Deterministic Instructions \n- Existence: hedging words (\"might\", \"may want to\", \"consider\", \"you could\")\n\n### Terminology Strictness\n- Consistency: flag term variations\n\n### Token Efficiency\n- Existence: filler phrases (\"In this section we will...\", \"As you may know...\")\n\n### Semantic Headings (partial)\n- Existence: banned headings (\"Overview\", \"Introduction\", \"Getting Started\")\n\n### Configuration Precision (partial)\n- Existence: vague versions (\"Python 3.x\", \"recent version\")\n\n### Security Boundaries (partial)\n- Existence: hardcoded API key patterns\n\n---\n\n## NEXT STEPS\n\n1. Create Vale style for doc-review rubrics\n2. Test Vale on sample docs\n3. Design LLM prompts for semantic rubrics only\n4. Wire into orch or standalone","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-04T14:02:04.898026177-08:00","updated_at":"2025-12-04T16:43:53.0608948-08:00","closed_at":"2025-12-04T16:43:53.0608948-08:00"}
|
||||
|
|
|
|||
Loading…
Reference in a new issue