johno/beads
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

bd sync: 2025-12-24 19:31:04

Browse Source
This commit is contained in:
Steve Yegge
2025-12-24 19:31:04 -08:00
parent 4668240495
commit fbae7711bc
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
.beads/issues.jsonl
View File

@@ -502,7 +502,7 @@
{"id":"bd-ucgz","title":"Migration invariants should exclude external dependencies from orphan check","description":"## Summary\n\nThe `checkForeignKeys` function in `migration_invariants.go` flags external dependencies as orphaned because they dont exist in the local issues table.\n\n## Location\n\n`internal/storage/sqlite/migration_invariants.go` around line 150-162\n\n## Current Code (buggy)\n\n```go\n// Check for orphaned dependencies\nvar orphanCount int\nerr = db.QueryRowContext(ctx, \\`\n SELECT COUNT(*)\n FROM dependencies d\n WHERE NOT EXISTS (SELECT 1 FROM issues WHERE id = d.depends_on_id)\n\\`).Scan(\u0026orphanCount)\n```\n\n## Fix\n\nExclude external references (format: `external:\u003cproject\u003e:\u003ccapability\u003e`):\n\n```go\n// Check for orphaned dependencies (excluding external refs)\nvar orphanCount int\nerr = db.QueryRowContext(ctx, \\`\n SELECT COUNT(*)\n FROM dependencies d\n WHERE NOT EXISTS (SELECT 1 FROM issues WHERE id = d.depends_on_id)\n AND d.depends_on_id NOT LIKE 'external:%'\n\\`).Scan(\u0026orphanCount)\n```\n\n## Reproduction\n\n```bash\n# Add external dependency\nbd dep add bd-xxx external:other-project:some-capability\n\n# Try to sync - fails\nbd sync\n# Error: found 1 orphaned dependencies\n```\n\n## Files to Modify\n\n1. **internal/storage/sqlite/migration_invariants.go** - Add WHERE clause\n\n## Testing\n\n```bash\n# Create issue with external dep\nbd create \"Test external deps\" -t task\nbd dep add bd-xxx external:beads:release-workflow\n\n# Sync should succeed\nbd sync\n\n# Verify dep exists\nbd show bd-xxx --json | jq .dependencies\n```\n\n## Success Criteria\n- External dependencies dont trigger orphan check\n- `bd sync` succeeds with external deps\n- Regular orphan detection still works for internal deps","status":"closed","priority":2,"issue_type":"bug","created_at":"2025-12-23T12:37:08.99387-08:00","updated_at":"2025-12-23T12:42:03.722691-08:00","closed_at":"2025-12-23T12:42:03.722691-08:00","close_reason":"Fixed in commit 90196eca - added NOT LIKE 'external:%' exclusion"}
{"id":"bd-udsi","title":"Async Gates for Agent Coordination","description":"Agents need an async primitive for waiting on external events (CI completion, API responses, human approval). Gates are wisp issues that block until external conditions are met, managed by the Deacon.\n\n## Core Concepts\n\n**Gate** = wisp issue that blocks until external condition is met\n- Type: gate\n- Phase: wisp (never synced, ephemeral)\n- Assignee: deacon/ (Deacon monitors it)\n- Fields: await_type, await_id, timeout, waiters[]\n\n**Await Types:**\n- gh:run:\u003cid\u003e - GitHub Actions run completion\n- gh:pr:\u003cid\u003e - PR merged/closed\n- timer:\u003cduration\u003e - Simple delay\n- human:\u003cprompt\u003e - Human approval required\n- mail:\u003cpattern\u003e - Wait for mail matching pattern\n\n## Open Questions\n- Should gates live in wisp storage or main storage with wisp flag?\n- Do we need a gate catalog (like molecule catalog)?\n- Should waits-for dep type work with gates?","status":"closed","priority":1,"issue_type":"epic","created_at":"2025-12-23T11:44:02.711062-08:00","updated_at":"2025-12-23T12:24:43.537615-08:00","closed_at":"2025-12-23T12:24:43.537615-08:00","close_reason":"Core beads implementation complete (types, migration, CLI). Remaining Deacon integration work moved to gastown (gt-dh65, gt-ng6g, gt-fqcz, gt-gswn)."}
{"id":"bd-ujz5","title":"Explore wiki-style documentation structure","description":"Our docs are growing into a book. Evaluate options for wiki-like structure:\n\n**Options to evaluate:**\n- GitHub Wiki (built-in, limited features)\n- mdBook (Rust, CLI-friendly, produces HTML/PDF/ePub)\n- MkDocs / Material for MkDocs (Python, beautiful themes)\n- Docusaurus (React, powerful but complex)\n- Plain markdown with good structure (current approach)\n\n**Requirements:**\n- Git-backed (version control)\n- Markdown-native (agents can edit)\n- Table of contents / navigation\n- Cross-linking between pages\n- Searchable\n- Can be hosted on GitHub Pages\n\n**Deliverables:**\n- Recommendation with pros/cons\n- If switching: migration plan\n- If staying with markdown: structure guidelines for wiki-like organization\n\nReferences:\n- https://squidfunk.github.io/mkdocs-material/alternatives/\n- https://www.archbee.com/blog/gitbook-alternatives","status":"open","priority":3,"issue_type":"task","created_at":"2025-12-24T18:23:23.665509-08:00","updated_at":"2025-12-24T18:23:23.665509-08:00"}
{"id":"bd-ul59","title":"Update molecular chemistry docs with discoveries","description":"Document recent discoveries about molecule/epic relationship and lifecycle:\n\n**Layer Cake (corrected order):**\n```\nFormulas (YAML compile-time macros)\n ↓\nProtos (template label, read-only)\n ↓\nMolecules (pour, bond, squash, burn)\n ↓\nEpics (parent-child, dependencies) ← DATA PLANE\n ↓\nIssues (JSONL, git-backed) ← STORAGE\n```\n\n**Key insight:** Molecules work without protos - you can create ad-hoc molecules.\nProtos are templates FOR molecules, not the other way around.\n\n**New concepts to document:**\n1. Orphan vs Stale matrix (blocking × assigned dimensions)\n2. Graph pressure as staleness indicator (not time)\n3. Parallelism via absence of depends_on (default parallel, opt-in sequential)\n4. progress.Completed/Total are computed, not stored\n5. WaitsFor: all-children for dynamic fanout gates\n\n**Common pitfalls for agents:**\n- Thinking phases/steps imply sequence (NO - deps do)\n- Confusing protos with molecules\n- Temporal language inverting dependencies\n- Forgetting to squash/burn wisps\n\n**Consider splitting docs:**\n- molecules.md → conceptual overview\n- formulas.md → YAML syntax reference\n- lifecycle.md → pour/squash/burn/bond operations\n- patterns.md → Christmas Ornament, factory assembly, etc.","status":"open","priority":2,"issue_type":"task","assignee":"dave","created_at":"2025-12-24T18:23:23.968937-08:00","updated_at":"2025-12-24T18:30:11.045152-08:00"}
{"id":"bd-ul59","title":"Update molecular chemistry docs with discoveries","description":"Document recent discoveries about molecule/epic relationship and lifecycle:\n\n**Layer Cake (corrected order):**\n```\nFormulas (YAML compile-time macros)\n ↓\nProtos (template label, read-only)\n ↓\nMolecules (pour, bond, squash, burn)\n ↓\nEpics (parent-child, dependencies) ← DATA PLANE\n ↓\nIssues (JSONL, git-backed) ← STORAGE\n```\n\n**Key insight:** Molecules work without protos - you can create ad-hoc molecules.\nProtos are templates FOR molecules, not the other way around.\n\n**New concepts to document:**\n1. Orphan vs Stale matrix (blocking × assigned dimensions)\n2. Graph pressure as staleness indicator (not time)\n3. Parallelism via absence of depends_on (default parallel, opt-in sequential)\n4. progress.Completed/Total are computed, not stored\n5. WaitsFor: all-children for dynamic fanout gates\n\n**Common pitfalls for agents:**\n- Thinking phases/steps imply sequence (NO - deps do)\n- Confusing protos with molecules\n- Temporal language inverting dependencies\n- Forgetting to squash/burn wisps\n\n**Consider splitting docs:**\n- molecules.md → conceptual overview\n- formulas.md → YAML syntax reference\n- lifecycle.md → pour/squash/burn/bond operations\n- patterns.md → Christmas Ornament, factory assembly, etc.","status":"closed","priority":2,"issue_type":"task","assignee":"beads/crew/dave","created_at":"2025-12-24T18:23:23.968937-08:00","updated_at":"2025-12-24T19:30:49.011831-08:00","closed_at":"2025-12-24T19:30:49.011831-08:00","close_reason":"Created docs/MOLECULES.md with comprehensive molecular chemistry documentation: layer cake architecture, phase metaphor, agent pitfalls, CLI commands. Updated CLI_REFERENCE.md and ARCHITECTURE.md with cross-references."}
{"id":"bd-umbf","title":"Design contributor namespace isolation for beads pollution prevention","description":"## Problem\n\nWhen contributors work on beads-the-project using beads-the-tool, their personal work-tracking issues leak into PRs. The .beads/issues.jsonl is intentionally tracked (it's the project's issue database), but contributors' local issues pollute the diff.\n\nThis is a recursion problem unique to self-hosting projects.\n\n## Possible Solutions to Explore\n\n1. **Contributor namespaces** - Each contributor gets a private prefix (e.g., `bd-steve-xxxx`) that's gitignored or filtered\n2. **Separate database** - Contributors use BEADS_DIR pointing elsewhere for personal tracking\n3. **Issue ownership/visibility flags** - Mark issues as \"local-only\" vs \"project\"\n4. **Prefix-based filtering** - Configure which prefixes are committed vs ignored\n\n## Design Considerations\n\n- Should be zero-friction for contributors (no manual setup)\n- Must not break existing workflows\n- Needs to work with sync/collaboration features\n- Consider: what if a \"personal\" issue graduates to \"project\" issue?\n\n## Expansion Needed\n\nThis is a placeholder. Needs detailed design exploration before implementation.","status":"open","priority":2,"issue_type":"feature","created_at":"2025-12-13T18:00:29.638743-08:00","updated_at":"2025-12-13T18:00:41.345673-08:00"}
{"id":"bd-uqfn","title":"Work on beads-wkt: Output control parameters for MCP tool...","description":"Work on beads-wkt: Output control parameters for MCP tools (GH#622). Add brief, fields, max_description_length params to ready/list/show. When done, submit MR (not PR) to integration branch for Refinery.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-19T22:57:10.675535-08:00","updated_at":"2025-12-20T00:49:51.929271-08:00","closed_at":"2025-12-19T23:28:25.362931-08:00","close_reason":"Implemented output control parameters for MCP tools (GH#622)"}
{"id":"bd-usro","title":"Rename 'template instantiate' to 'mol bond'","description":"Rename the template instantiation command to match molecule metaphor.\n\nCurrent: bd template instantiate \u003cid\u003e --var key=value\nTarget: bd mol bond \u003cid\u003e --var key=value\n\nChanges needed:\n- Add 'mol' command group (or extend existing)\n- Add 'bond' subcommand that wraps template instantiate logic\n- Keep 'template instantiate' as deprecated alias for backward compat\n- Update help text and docs to use molecule terminology\n\nThe 'bond' verb captures:\n1. Chemistry metaphor (molecules bond to form structures)\n2. Dependency linking (child issues bonded in a DAG)\n3. Short and active\n\nSee also: molecule execution model in Gas Town","status":"closed","priority":1,"issue_type":"feature","created_at":"2025-12-20T16:56:37.582795-08:00","updated_at":"2025-12-20T23:22:43.567337-08:00","closed_at":"2025-12-20T23:22:43.567337-08:00","close_reason":"Implemented mol command: catalog, show, bond"}