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

beads sync: close bd-1eak

Browse Source
This commit is contained in:
beads/crew/grip
2025-12-31 12:34:57 -08:00
committed by Steve Yegge
parent 18fbab6a38
commit 297b3af233
1 changed files with 3 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

5
.beads/issues.jsonl
View File

@@ -32,7 +32,7 @@
{"id":"bd-1dez.6","title":"bd mol publish: Push formula to GitHub repo","description":"Publish a formula to a GitHub repository for sharing.\n\n## Usage\n```bash\n# Create new repo and publish\nbd mol publish mol-my-workflow --repo github.com/myorg/mol-my-workflow\n\n# Update existing repo\nbd mol publish mol-my-workflow --repo github.com/myorg/mol-my-workflow --tag v1.1.0\n```\n\n## Implementation\n1. Export proto to formula.json (if not already a file)\n2. Validate formula structure\n3. Create GitHub repo if --create flag (uses `gh repo create`)\n4. Copy formula.json to repo\n5. Generate README.md from formula description\n6. Commit and push\n7. Create git tag if --tag specified\n8. Add mol-formula topic to repo\n\n## Flags\n- `--repo \u003curl\u003e` - Target GitHub repo (required)\n- `--tag \u003cversion\u003e` - Create version tag\n- `--create` - Create repo if doesn't exist\n- `--private` - Create as private repo\n\n## Workflow\n```bash\n# Full publish flow\nbd mol distill my-epic --name my-workflow\nbd mol promote bd-proto-xxx --as my-workflow\nbd mol publish mol-my-workflow --repo github.com/me/mol-my-workflow --create --tag v1.0.0\n```\n","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-25T12:06:41.419764-08:00","updated_at":"2025-12-25T21:53:13.421752-08:00","closed_at":"2025-12-25T21:53:13.421752-08:00","dependencies":[{"issue_id":"bd-1dez.6","depends_on_id":"bd-1dez","type":"parent-child","created_at":"2025-12-25T12:06:41.420209-08:00","created_by":"daemon"}]}
{"id":"bd-1dez.7","title":"Formula versioning: Version field and git tag integration","description":"Add versioning support to formulas for tracking updates.\n\n## Formula Version Field\n```json\n{\n \"formula\": \"mol-code-review\",\n \"version\": \"1.2.0\",\n \"min_bd_version\": \"0.25.0\",\n ...\n}\n```\n\n## Version Semantics\n- Use semver: MAJOR.MINOR.PATCH\n- MAJOR: Breaking changes to step structure\n- MINOR: New optional steps or variables\n- PATCH: Documentation, bug fixes\n\n## Git Tag Integration\n- `bd mol install repo@v1.2.0` fetches that tag\n- `bd mol install repo` fetches latest tag (or main if no tags)\n- `bd mol publish --tag v1.2.0` creates tag\n\n## Proto Version Tracking\nLocal proto should store:\n```\nsource_repo: github.com/anthropics/mol-code-review\nsource_version: v1.2.0\ninstalled_at: 2025-12-25T12:00:00Z\n```\n\nThis enables `bd mol update` to check for newer versions.\n","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-25T12:06:42.674849-08:00","updated_at":"2025-12-25T19:43:22.501926-08:00","closed_at":"2025-12-25T19:43:22.501926-08:00","dependencies":[{"issue_id":"bd-1dez.7","depends_on_id":"bd-1dez","type":"parent-child","created_at":"2025-12-25T12:06:42.67694-08:00","created_by":"daemon"}]}
{"id":"bd-1dez.8","title":"Installation tracking: .beads/installed.json","description":"Track installed formulas for update checking and provenance.\n\n## File Format\n```json\n{\n \"mol-code-review\": {\n \"source\": \"github.com/anthropics/mol-code-review\",\n \"version\": \"v1.2.0\",\n \"installed_at\": \"2025-12-25T12:00:00Z\",\n \"formula_hash\": \"abc123...\"\n },\n \"mol-polecat-work\": {\n \"source\": \"local\",\n \"version\": \"1\",\n \"installed_at\": \"2025-12-24T10:00:00Z\"\n }\n}\n```\n\n## Commands That Update This\n- `bd mol install` - Adds entry\n- `bd mol update` - Updates version/timestamp\n- `bd cook` - Adds entry with source:local\n- `bd mol uninstall` - Removes entry (new command)\n\n## Usage\n```bash\nbd mol list --installed # Shows installed with source/version\nbd mol outdated # Shows formulas with available updates\n```\n\n## Sync Behavior\n- installed.json is gitignored (local state)\n- Only formulas/ directory is synced\n- Each clone tracks its own installations\n","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-25T12:06:43.934727-08:00","updated_at":"2025-12-25T19:38:04.14827-08:00","closed_at":"2025-12-25T19:38:04.14827-08:00","dependencies":[{"issue_id":"bd-1dez.8","depends_on_id":"bd-1dez","type":"parent-child","created_at":"2025-12-25T12:06:43.937653-08:00","created_by":"daemon"}]}
{"id":"bd-1eak","title":"Add bd refile command to move issues between rigs","description":"Add a `bd refile \u003csource-id\u003e \u003ctarget-rig\u003e` command to move issues between rigs.\n\nBeads already has the routing infrastructure:\n- ResolveBeadsDirForID - routes reads by prefix\n- ResolveBeadsDirForRig - routes writes by rig name\n- GetRoutedStorageForID - opens cross-rig storage connections\n\nImplementation:\n1. Get source issue via routing\n2. Create new issue in target rig (existing --prefix mechanism)\n3. Close source issue with 'Refiled to \u003cnew-id\u003e'\n4. Optionally: migrate deps, link the two issues\n\nThis is pure beads - no gastown involvement needed.","status":"in_progress","priority":2,"issue_type":"feature","created_at":"2025-12-31T12:29:18.161088-08:00","created_by":"beads/crew/grip","updated_at":"2025-12-31T12:29:28.015535-08:00"}
{"id":"bd-1eak","title":"Add bd refile command to move issues between rigs","description":"Add a `bd refile \u003csource-id\u003e \u003ctarget-rig\u003e` command to move issues between rigs.\n\nBeads already has the routing infrastructure:\n- ResolveBeadsDirForID - routes reads by prefix\n- ResolveBeadsDirForRig - routes writes by rig name\n- GetRoutedStorageForID - opens cross-rig storage connections\n\nImplementation:\n1. Get source issue via routing\n2. Create new issue in target rig (existing --prefix mechanism)\n3. Close source issue with 'Refiled to \u003cnew-id\u003e'\n4. Optionally: migrate deps, link the two issues\n\nThis is pure beads - no gastown involvement needed.","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-31T12:29:18.161088-08:00","created_by":"beads/crew/grip","updated_at":"2025-12-31T12:34:23.548938-08:00","closed_at":"2025-12-31T12:34:23.548938-08:00","close_reason":"Implemented bd refile command"}
{"id":"bd-1pr6","title":"Time-dependent worktree detection tests may be flaky","status":"hooked","priority":3,"issue_type":"task","created_at":"2025-12-26T01:21:22.065353-08:00","updated_at":"2025-12-30T15:44:43.360441-08:00"}
{"id":"bd-1ri4","title":"Test prefix bd-","status":"tombstone","priority":2,"issue_type":"task","created_at":"2025-12-27T14:24:41.240483-08:00","created_by":"stevey","updated_at":"2025-12-27T14:24:50.419881-08:00","deleted_at":"2025-12-27T14:24:50.419881-08:00","deleted_by":"daemon","delete_reason":"delete","original_type":"task"}
{"id":"bd-1slh","title":"Investigate charmbracelet-based TUI for beads","description":"Now that we've merged the create-form command (PR #603) which uses charmbracelet/huh, investigate whether beads should have a more comprehensive TUI.\n\nConsiderations:\n- Should this be in core or a separate binary (bd-tui)?\n- What functionality would benefit from a TUI? (list view, issue details, search, bulk operations)\n- Plugin/extension architecture vs build tags vs separate binary\n- Dependency cost vs user experience tradeoff\n- Target audience: humans who want interactive workflows vs CLI/scripting users\n\nRelated: PR #603 added charmbracelet/huh dependency for create-form command.","notes":"Foundation is in place (lipgloss, huh), but not a priority right now","status":"deferred","priority":3,"issue_type":"feature","created_at":"2025-12-17T14:20:51.503563-08:00","updated_at":"2025-12-20T23:31:34.354023-08:00"}
@@ -212,7 +212,7 @@
{"id":"bd-8wgo","title":"bd merge omits priority:0 due to omitempty JSON tag","description":"GitHub issue #671. The merge code in internal/merge/merge.go uses 'omitempty' on the Priority field, which causes priority:0 (P0/critical) to be dropped from JSON output since 0 is Go's zero value for int. Fix: either remove omitempty from Priority field or use a pointer (*int). This affects the git merge driver and causes P0 issues to lose their priority.","status":"closed","priority":1,"issue_type":"bug","created_at":"2025-12-21T14:35:15.083146-08:00","updated_at":"2025-12-21T15:41:14.522554-08:00","closed_at":"2025-12-21T15:41:14.522554-08:00"}
{"id":"bd-8x3w","title":"Add composite index (issue_id, type) on dependencies table","description":"GetBlockedIssues uses EXISTS clauses that filter by issue_id AND type together.\n\n**Query pattern (ready.go:427-429):**\n```sql\nEXISTS (\n SELECT 1 FROM dependencies d2\n WHERE d2.issue_id = i.id AND d2.type = 'blocks'\n)\n```\n\n**Problem:** Only idx_dependencies_issue exists. SQLite must filter type after index lookup.\n\n**Solution:** Add migration:\n```sql\nCREATE INDEX IF NOT EXISTS idx_dependencies_issue_type ON dependencies(issue_id, type);\n```\n\n**Note:** This complements the existing idx_dependencies_depends_on_type for the reverse direction.","status":"closed","priority":3,"issue_type":"task","created_at":"2025-12-22T22:58:52.876846-08:00","updated_at":"2025-12-22T23:15:13.840789-08:00","closed_at":"2025-12-22T23:15:13.840789-08:00","dependencies":[{"issue_id":"bd-8x3w","depends_on_id":"bd-h0we","type":"discovered-from","created_at":"2025-12-22T22:58:52.877536-08:00","created_by":"daemon"}]}
{"id":"bd-8x43","title":"Add 'bd where' command to show active beads location","description":"## Problem\n\nWhen using redirects, it's unclear which beads database is actually being used. This caused debugging confusion during the v0.39.0 release.\n\n## Proposed Solution\n\nAdd `bd where` command:\n\n```bash\nbd where\n# → /Users/stevey/gt/beads/mayor/rig/.beads (via redirect from crew/dave/.beads)\n\nbd where --json\n# → {\"path\": \"...\", \"redirected_from\": \"...\", \"prefix\": \"bd\"}\n```\n\n## Alternatives Considered\n\n- `bd info --beads-path` - but `bd where` is more discoverable\n- Just fix the UX so it's never confusing - defense in depth is better\n\n## Desire Paths\n\nThis supports the 'desire paths' design principle: make the system's behavior visible so agents can debug and understand it.","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-27T21:15:52.666948-08:00","created_by":"beads/crew/dave","updated_at":"2025-12-27T21:27:50.301295-08:00","closed_at":"2025-12-27T21:27:50.301295-08:00"}
{"id":"bd-8xnf","title":"Add bd mol progress command","description":"New command showing molecule progress without listing steps.\n\nOutput format:\n Molecule: gt-hanoi-xyz (Towers of Hanoi - 20 disks)\n Progress: 347,892 / 1,048,575 (33.2%)\n Current step: gt-hanoi-xyz.move-347893\n Rate: ~1,200 steps/hour\n ETA: ~9.7 hours remaining\n\nUses indexed query on dependencies table:\n SELECT COUNT(*), SUM(CASE WHEN status='closed' THEN 1 ELSE 0 END)\n FROM dependencies d JOIN issues i ON d.issue_id = i.id\n WHERE d.depends_on_id = ? AND d.type = 'parent-child'","status":"in_progress","priority":1,"issue_type":"task","created_at":"2025-12-31T00:52:52.613276-08:00","created_by":"gastown/crew/max","updated_at":"2025-12-31T12:29:05.403828-08:00","dependencies":[{"issue_id":"bd-8xnf","depends_on_id":"bd-5nu1","type":"parent-child","created_at":"2025-12-31T00:54:00.815655-08:00","created_by":"gastown/crew/max"}]}
{"id":"bd-8xnf","title":"Add bd mol progress command","description":"New command showing molecule progress without listing steps.\n\nOutput format:\n Molecule: gt-hanoi-xyz (Towers of Hanoi - 20 disks)\n Progress: 347,892 / 1,048,575 (33.2%)\n Current step: gt-hanoi-xyz.move-347893\n Rate: ~1,200 steps/hour\n ETA: ~9.7 hours remaining\n\nUses indexed query on dependencies table:\n SELECT COUNT(*), SUM(CASE WHEN status='closed' THEN 1 ELSE 0 END)\n FROM dependencies d JOIN issues i ON d.issue_id = i.id\n WHERE d.depends_on_id = ? AND d.type = 'parent-child'","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-31T00:52:52.613276-08:00","created_by":"gastown/crew/max","updated_at":"2025-12-31T12:34:38.443209-08:00","closed_at":"2025-12-31T12:34:38.443209-08:00","close_reason":"Implemented bd mol progress command with efficient indexed queries","dependencies":[{"issue_id":"bd-8xnf","depends_on_id":"bd-5nu1","type":"parent-child","created_at":"2025-12-31T00:54:00.815655-08:00","created_by":"gastown/crew/max"}]}
{"id":"bd-8y9t","title":"Remove bd mol spawn - use pour/wisp only","description":"Remove the spawn command from bd mol. Replace with:\n\n- bd pour \u003cproto\u003e - Instantiate as mol (liquid, persistent)\n- bd wisp \u003cproto\u003e - Instantiate as wisp (vapor, ephemeral)\n\nRationale:\n- 'spawn' doesn't fit the chemistry metaphor\n- Two phase transitions (pour/wisp) are clearer than one command with flags\n- Avoids confusion about defaults\n\nImplementation:\n1. Add bd pour command (currently bd mol spawn --pour)\n2. Add bd wisp command (currently bd mol spawn without --pour)\n3. Remove bd mol spawn\n4. Update all docs/tests\n\nGas Town tracking: gt-ingm.6","status":"closed","priority":1,"issue_type":"task","created_at":"2025-12-24T12:40:51.698189-08:00","updated_at":"2025-12-24T12:52:55.307-08:00","closed_at":"2025-12-24T12:52:55.307-08:00"}
{"id":"bd-8zbo","title":"Code smell: runCook function is ~275 lines","description":"attached_args: Refactor runCook function (~275 lines)\n\nThe runCook() function in cmd/bd/cook.go (lines 83-357) is ~275 lines handling:\n\n1. Flag parsing and validation\n2. Mode determination (compile vs runtime)\n3. Formula parsing and resolution\n4. Control flow, advice, and expansion application\n5. Dry-run output\n6. Ephemeral mode JSON output\n7. Persist mode database operations\n8. Result display\n\nConsider extracting:\n- parseAndValidateFlags() - flag handling\n- loadAndResolveFormula() - parse, resolve, apply transformations\n- outputDryRun() - dry run display logic\n- outputEphemeral() - ephemeral JSON output\n- persistFormula() - database persistence logic\n\nThe function has multiple exit points and nested conditionals that make it hard to follow.\n\nLocation: cmd/bd/cook.go:83-357","status":"closed","priority":3,"issue_type":"chore","created_at":"2025-12-28T15:33:08.808191-08:00","created_by":"beads/crew/dave","updated_at":"2025-12-28T16:37:29.397832-08:00","closed_at":"2025-12-28T16:37:29.397832-08:00","dependencies":[{"issue_id":"bd-8zbo","depends_on_id":"bd-784c","type":"parent-child","created_at":"2025-12-28T15:38:04.25998-08:00","created_by":"daemon"}]}
{"id":"bd-90fs","title":"Merge: amber-1767138546434","description":"branch: polecat/amber-1767138546434\ntarget: main\nsource_issue: amber-1767138546434\nrig: beads","status":"closed","priority":2,"issue_type":"merge-request","created_at":"2025-12-30T15:57:38.681293-08:00","created_by":"beads/polecats/amber","updated_at":"2025-12-30T18:12:30.966277-08:00","closed_at":"2025-12-30T18:11:08.005131-08:00"}
@@ -367,6 +367,7 @@
{"id":"bd-eijl","title":"bd ship command for publishing capabilities","description":"Add `bd ship \u003ccapability\u003e` command that:\n\n1. Finds issue with `export:\u003ccapability\u003e` label\n2. Validates issue is closed (or --force to override)\n3. Adds `provides:\u003ccapability\u003e` label\n4. Protects `provides:*` namespace (only bd ship can add these labels)\n\nExample:\n```bash\nbd ship mol-run-assignee\n# Output: Shipped mol-run-assignee (bd-xyz)\n```\n\nPart of cross-project dependency system.\nSee: gastown/docs/cross-project-deps.md","status":"closed","priority":2,"issue_type":"feature","created_at":"2025-12-21T22:37:19.123024-08:00","updated_at":"2025-12-21T23:11:47.498859-08:00","closed_at":"2025-12-21T23:11:47.498859-08:00"}
{"id":"bd-eko4","title":"Add pre-migration orphan cleanup to avoid chicken-and-egg fix failure","description":"## Problem\n\nWhen the database has orphaned foreign key references (dependencies or labels pointing to non-existent issues), the migration invariant check fails, preventing the database from opening. This creates a chicken-and-egg problem:\n\n1. `bd doctor --fix` tries to open the database\n2. Opening triggers migrations with invariant checks\n3. Invariant check fails due to orphaned refs\n4. Fix never runs because database won't open\n\n## Root Cause\n\nAggressive tombstone deletion (e.g., deleting ~1000 old tombstones) left behind orphaned:\n- 218+ dependencies where issue_id not in issues\n- 222+ dependencies where depends_on_id not in issues \n- 30+ labels where issue_id not in issues\n\n## Current Workaround\n\nDirect SQL to clean up before bd can run:\n```sql\nDELETE FROM dependencies WHERE NOT EXISTS (SELECT 1 FROM issues WHERE id = issue_id);\nDELETE FROM dependencies WHERE NOT EXISTS (SELECT 1 FROM issues WHERE id = depends_on_id) AND depends_on_id NOT LIKE 'external:%';\nDELETE FROM labels WHERE NOT EXISTS (SELECT 1 FROM issues WHERE id = issue_id);\n```\n\n## Proposed Fix\n\nAdd a pre-migration cleanup step that runs BEFORE invariant checks:\n1. Option A: Run orphan cleanup as part of migrations (before invariant check)\n2. Option B: Add `bd doctor --force-fix` that bypasses invariant checks\n3. Option C: Have invariant check auto-clean orphans instead of failing\n\nOption A is cleanest - orphan cleanup should be part of normal migration.","status":"closed","priority":2,"issue_type":"bug","created_at":"2025-12-28T23:18:24.65227-08:00","created_by":"beads/crew/dave","updated_at":"2025-12-29T13:46:30.625571-08:00","closed_at":"2025-12-29T13:46:30.625571-08:00","close_reason":"Implemented Option A: CleanOrphanedRefs runs before captureSnapshot in RunMigrations, preventing chicken-and-egg problem"}
{"id":"bd-elqd","title":"Systematic bd sync stability investigation","description":"## Context\n\nbd sync has chronic instability issues that have persisted since inception:\n- issues.jsonl is always dirty after push\n- bd sync often creates messes requiring manual cleanup\n- Problems escalating despite accumulated bug fixes\n- Workarounds are getting increasingly draconian\n\n## Goal\n\nSystematically observe and diagnose bd sync failures rather than applying band-aid fixes.\n\n## Approach\n\n1. Start fresh session with latest binary (all fixes applied)\n2. Run bd sync and carefully observe what happens\n3. Document exact sequence of events when things go wrong\n4. File specific issues for each discrete problem identified\n5. Track the root causes, not just symptoms\n\n## Test Environment\n\n- Fresh clone or clean state\n- Latest bd binary with all bug fixes\n- Monitor both local and remote JSONL state\n- Check for timing issues, race conditions, merge conflicts\n\n## Success Criteria\n\n- Identify root causes of sync instability\n- Create actionable issues for each problem\n- Eventually achieve stable bd sync (no manual intervention needed)","status":"tombstone","priority":1,"issue_type":"task","created_at":"2025-12-16T22:57:25.35289-08:00","updated_at":"2025-12-17T16:11:17.070763-08:00","deleted_at":"2025-12-17T16:11:17.070763-08:00","deleted_by":"batch delete","delete_reason":"batch delete","original_type":"task"}
{"id":"bd-eph-5h2","title":"beads-release","description":"Beads release workflow - from version bump to verified release.\n\nThis formula orchestrates a complete release cycle:\n1. Preflight checks (clean git, up to date)\n2. Documentation updates (CHANGELOG, info.go)\n3. Version bump (all components)\n4. Git operations (commit, tag, push)\n5. CI verification (GitHub Actions)\n6. Artifact verification (GitHub, npm, PyPI)\n7. Local installation update\n8. Daemon restart\n\n## Usage\n\n```bash\nbd wisp create beads-release --var version=0.37.0\n```\n\nOr assign to a polecat:\n```bash\ngt sling beads/polecats/p1 --formula beads-release --var version=0.37.0\n```","status":"open","priority":2,"issue_type":"epic","assignee":"beads/crew/emma","created_at":"2025-12-30T21:17:38.213979-08:00","updated_at":"2025-12-30T21:58:21.773586-08:00","ephemeral":true}
{"id":"bd-epww","title":"Document pinned status in CLI_REFERENCE.md","description":"## Task\n\nThe `pinned` status is a valid issue status but is not documented in CLI_REFERENCE.md.\n\n## Current Status Values (from types.go:295-301)\n\n- open\n- in_progress\n- blocked\n- deferred\n- closed\n- tombstone\n- **pinned** ← undocumented\n\n## Definition\n\n`StatusPinned Status = \"pinned\" // Persistent bead that stays open indefinitely (bd-6v2)`\n\n## Where to Document\n\nAdd to the 'Issue Types' or create a new 'Issue Statuses' section in docs/CLI_REFERENCE.md.\n\n## Related\n\nThe pinned status is heavily used by gt for hook management (`--status=pinned`).","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-27T17:12:35.296002-08:00","created_by":"gastown/crew/joe","updated_at":"2025-12-27T19:13:05.640767-08:00","closed_at":"2025-12-27T19:13:05.640767-08:00"}
{"id":"bd-etyv","title":"Smart --var detection for mol distill","description":"Implemented bidirectional syntax support for mol distill --var flag.\n\n**Problem:**\n- spawn uses: --var variable=value (assignment style)\n- distill used: --var value=variable (substitution style)\n- Agents would naturally guess spawn-style for both\n\n**Solution:**\nSmart detection that accepts BOTH syntaxes by checking which side appears in the epic text:\n- --var branch=feature-auth → finds 'feature-auth' in text → works\n- --var feature-auth=branch → finds 'feature-auth' in text → also works\n\n**Changes:**\n- Added parseDistillVar() with smart detection\n- Added collectSubgraphText() helper\n- Restructured runMolDistill to load subgraph before parsing vars\n- Updated help text to document both syntaxes\n- Added comprehensive tests in mol_test.go\n\n**Edge cases handled:**\n- Both sides found: prefers spawn-style (more common guess)\n- Neither found: helpful error message\n- Empty sides: validation error\n- Values containing '=' (e.g., KEY=VALUE): works via SplitN\n\nEmbodies the Beads philosophy: watch what agents do, make their guess correct.","status":"closed","priority":2,"issue_type":"task","created_at":"2025-12-21T11:08:50.83923-08:00","updated_at":"2025-12-21T11:08:56.432536-08:00","closed_at":"2025-12-21T11:08:56.432536-08:00"}
{"id":"bd-exy3","title":"Ephemeral patrol molecules leaking into beads","description":"## Problem\n\nEphemeral patrol orchestration molecules (e.g., mol-deacon-patrol, wisp step issues) keep appearing in `bd ready` output in gastown beads.\n\nThese are ephemeral/wisp issues that should:\n1. Never be synced to the beads-sync branch\n2. Live only in .beads-wisp/ (ephemeral storage)\n3. Be squashed to digests, not persisted as regular beads\n\n## Examples found\n\n- gt-wisp-6ue: mol-deacon-patrol\n- gt-pacdm: mol-deacon-patrol \n- gt-wisp-mpm: Check own context limit\n- gt-wisp-lkc: Clean dead sessions\n\n## Investigation needed\n\n1. Where are these being created? (gt mol bond? manual bd create?)\n2. Why are they using the gt- prefix instead of staying ephemeral?\n3. Is the wisp storage (.beads-wisp/) being used correctly?\n4. Is bd sync accidentally picking up ephemeral issues?\n\n## Expected behavior\n\nPatrol molecules and their steps should be ephemeral and never appear in `bd ready` or `bd list`.","status":"closed","priority":1,"issue_type":"bug","created_at":"2025-12-27T17:04:16.51075-08:00","created_by":"gastown/crew/joe","updated_at":"2025-12-27T19:18:16.809273-08:00","closed_at":"2025-12-27T19:18:16.809273-08:00"}