fix(t3code): provide Beads to T3 Code agents on m3-hermes

bd was neither on the t3code service PATH nor on the system. Add it to
both, like the harnesses, and set BEADS_ACTOR so the audit trail matches
the m3ta-chiron commit identity.

Also take the bd 1.3.2 migration of .beads (config, gitignore, hooks) and
ignore the .beads.gate.lock it creates in the repo root.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
m3tam3reandClaude Opus 5.5 committed 2026-11-01 13:09:34 +01:00
1 parent cf1c4b9f31
commit a2d226583f
9 files changed
+246 -57

No files matched your search

+7
View File
@@ -71,3 +71,10 @@ bd.db
# They would override fork protection in .git/info/exclude.
# Config files (metadata.json, config.yaml) are tracked by git by default
# since no pattern above ignores them.
# Added by bd (missing required patterns)
*.gate.lock*
last_pull
proxieddb/
dolt-server-config.yaml
proxied_server_client_info.json