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

+6 -1
View File
@@ -115,6 +115,7 @@ in {
pkgs.llm-agents.t3code
pkgs.llm-agents.opencode2
pkgs.llm-agents.claude-code
pkgs.llm-agents.beads
pkgs.agent-lib
];
@@ -144,15 +145,19 @@ in {
# Independent of HOME entirely: git uses exactly this ssh config
# (absolute store path) for every gitea remote.
GIT_SSH_COMMAND = "ssh -F ${t3SshConfig}";
# bd falls back to git's user.name for its audit trail, which would
# be m3tam3re here — keep it in line with the commit identity.
BEADS_ACTOR = gitIdentityEnv.GIT_AUTHOR_NAME;
}
// gitIdentityEnv;
# Harness CLIs and git for the agents T3 Code spawns.
# Harness CLIs, git and the issue tracker for the agents T3 Code spawns.
path = with pkgs; [
git
openssh
llm-agents.opencode2
llm-agents.claude-code
llm-agents.beads
];
};