chore(beads): initialize public repo-local tracking

[christso]

Summary

AllAgents clones can now bootstrap a fresh Beads database directly from the public project repository instead of discovering the broken legacy schema-v49 database and separate private remote. The new public identity uses database and issue prefix allagents, with no legacy rows or identity data migrated.

Only the portable config, metadata, and ignore policy are versioned. Embedded Dolt data, credentials, exports, backups, locks, sockets, and machine-specific paths remain local, and contributor guidance makes the public-data boundary explicit.

Supersedes #431.

Validation

• bun run build
• bun run typecheck
• bun run lint
• bun test — 1,326 passed, 5 skipped
• bun run test:e2e — 116 passed, 4 skipped
• gitleaks dir --no-banner --redact . — no leaks found

Public-branch bootstrap was reproduced with:

git clone --branch chore/repo-local-public-beads https://github.com/EntityProcess/allagents.git allagents-beads-check
cd allagents-beads-check
bd bootstrap --dry-run --json
bd bootstrap --yes
bd config get sync.remote
bd context --json
bd dolt pull
git status --short --branch

This selected the exact git+https://github.com/EntityProcess/allagents remote, recovered project 82b512b7-0232-45ba-94c5-448de92d1afc, and left the checkout clean. A disposable bd worktree create check also resolved the same database from its parent clone. bd doctor was run and reported its documented embedded-mode limitation; bd status, bd ready, remote inspection, bootstrap, and pull all succeeded.

One-time maintainer action

After merge, a maintainer using the old primary checkout should remove or archive its ignored legacy .beads directory, then run bd bootstrap. Fresh clones only need bd bootstrap; if the local umask produces the bd permissions warning, run chmod 700 .beads.

Post-Deploy Monitoring & Validation

No production runtime monitoring is required because this changes repository metadata only. During the first maintainer bootstrap after merge, verify bd context --json reports the project ID above and bd dolt remote list reports the public AllAgents URL; a legacy schema gate, different project ID, or private remote is the rollback trigger. Mitigation is to remove the local ignored database and bootstrap again from the public remote. Validation owner: repository maintainer, during the first post-merge checkout.