Skip to content

fix(beads): harden worktree identity checks#1460

Draft
christso wants to merge 4 commits into
mainfrom
av-21i-beads-workmux-hardening
Draft

fix(beads): harden worktree identity checks#1460
christso wants to merge 4 commits into
mainfrom
av-21i-beads-workmux-hardening

Conversation

@christso

@christso christso commented Jun 21, 2026

Copy link
Copy Markdown
Collaborator

Summary

AgentV no longer tracks checkout-local Beads identity or live Beads config. The repo keeps only the Beads template (.beads/config.yaml.example) and .beads/.gitignore, while .beads/config.yaml, .beads/metadata.json, and runtime state stay local.

This also removes the stale AgentV workflow note that treated .beads/metadata.json as intentionally tracked. Developer-specific Beads workflow guidance now lives in the shared Beads skill.

Verification

  • git diff --check
  • bd --readonly config get federation.remote reports git+https://github.com/EntityProcess/agentv-beads.git from the local config
  • git ls-files .beads reports only .beads/.gitignore and .beads/config.yaml.example

Post-Deploy Monitoring & Validation

No additional production monitoring required. This is repo coordination config only. After merge, copy .beads/config.yaml.example to .beads/config.yaml in a local checkout, then validate with git ls-files .beads and bd --readonly config get federation.remote.


Compound Engineering
Codex GPT-5

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 21, 2026

Copy link
Copy Markdown

Deploying agentv with  Cloudflare Pages  Cloudflare Pages

Latest commit: b089848
Status: ✅  Deploy successful!
Preview URL: https://6df9e633.agentv.pages.dev
Branch Preview URL: https://av-21i-beads-workmux-hardeni.agentv.pages.dev

View logs

@christso

Copy link
Copy Markdown
Collaborator Author

Review/dogfood update: PR #1460 is not merge-ready as-is. The focused dogfood pass for the current checkout passed, but the stricter review found two P1 Beads identity/bootstrap regressions:

  1. Removing .beads/metadata.json strands existing embedded Dolt data under the wrong database identity. Without metadata, bd falls back to database beads; bd --readonly list returns no issues. Restoring metadata resolves database av and returns real av-* issues.
  2. bd bootstrap keys off sync.remote, not federation.remote. Because EntityProcess/agentv still advertises refs/dolt/data, fresh bootstrap can choose the code repo instead of EntityProcess/agentv-beads.

I pushed a stacked draft fix PR here: #1461

That branch adds sync.remote and restores the stable metadata identity behavior; its net diff against origin/main is only .beads/config.yaml adding sync.remote. Verification covered fresh bootstrap, existing embedded-Dolt data, red check without metadata, and diff checks.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant