Skip to content

Remove the Beads redirect from the repository #53

Description

@ckrough

This repository is bound to GitHub Issues: .daedalus/config.json carries "tracker": "github", and the operator confirmed GitHub Issues over the competing federated Beads store. One artifact of the old binding survives: .beads/redirect, which points bd at /Users/ckrough/Documents/professional/.beads. While that file exists, any bd command run from inside this repository resolves against the professional store, so this repo still reads as Beads-tracked to every tool that detects a tracker by directory signal.

Remove the redirect once the open issues it pointed at are confirmed migrated to this repo's GitHub Issues.

The engram skills reference .beads/ as one tracker-detection signal among Linear and GitHub (engram/skills/briefing/SKILL.md, engram/skills/working/SKILL.md). Those are deliberately tool-agnostic and stay as they are; this issue is about this repository's own binding, not about what a published skill supports.

Acceptance Criteria

  • Every open Beads issue scoped to this repository in the professional store is confirmed already migrated to backchainai/backchain-plugins GitHub Issues, or is migrated as part of this change, with the finding recorded in the PR description.
  • .beads/redirect and the now-empty .beads/ directory are removed.
  • No remaining file in this repository binds it to Beads: no .beads/ directory, no Beads reference in .daedalus/config.json, CONTRIBUTING.md, or CLAUDE.md.
  • The tracker-agnostic detection prose in the engram skills is unchanged.
  • The structure gate (bash scripts/gates/structure.sh) and claude plugin validate . both exit 0.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions