huskies

3,846 Commits 1 Branch 38 Tags

3 Commits

Include renames

Author	SHA1	Message	Date
TimmyandClaude Fable 5	f39c4b7c4b	Remove all alternate update paths — fleet redeploy is release + upgrade all Killed: - rebuild_and_restart (in-container cargo self-compile): the MCP tool, the `rebuild` chat command in all four transports, the web-ui bot command, and the underlying function. This was the path that caused the exec() deadlocks. - upgrade_sled gateway MCP tool: second entry point to sled upgrades, defaulted to serving the gateway's own macOS binary to Linux sleds. - GET /api/huskies-binary (both sled and gateway route trees): served current_exe(), wrong platform when the gateway is macOS. Superseded by /api/artifacts/ which now also serves on the gateway route tree. - `huskies upgrade` CLI subcommand and --source flag: third way of doing the same download-and-replace. Escape hatch for a bricked sled is `docker cp` + restart. Kept, distinct jobs: `project-rebuild` (container/image updates), `rebuild gateway` + script/local-release (gateway self-update). Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_019fHdm92yjvguPi2LiXfLB9	2026-07-15 16:46:11 +01:00
dave	75533225e4	fix: commit minor fmt residue blocking mergemaster cherry-picks Master had 8 uncommitted single-line whitespace changes (blank-line trimming in test mod headers, etc.) left over from a previous mergemaster cargo-fmt run that didn't get committed. Each subsequent merge attempt hit: cherry-pick failed: 'Your local changes to the following files would be overwritten by merge. Please commit your changes or stash them.' So merges had been silently un-mergeable for the last several rounds — mergemaster correctly reported the issue but had no way to fix master's own state from inside the merge_workspace. Files affected (all whitespace-only): - chat/transport/matrix/bot/messages/{handle_message,on_room_message}.rs - chat/transport/slack/commands/{llm,mod}.rs - http/mcp/agent_tools/worktree.rs - http/workflow/story_ops/{create,criterion,update}.rs cargo clippy --all-targets -- -D warnings: clean cargo fmt --all --check: clean 2636 tests pass.	2026-04-27 11:17:31 +00:00
dave	1f02de8cd0	refactor: split chat/transport/slack/commands.rs (875) into mod + llm The 875-line commands.rs is split: - llm.rs: handle_llm_message (LLM turn for non-command messages, ~190 lines) - mod.rs: SlackSlashCommandPayload + slash_command_to_bot_keyword + handle_incoming_message + tests (~700 lines) Tests stay co-located with handle_incoming_message in mod.rs. All 2636 tests pass; clippy clean.	2026-04-27 02:32:11 +00:00

Author

SHA1

Message

Date

TimmyandClaude Fable 5

f39c4b7c4b

Remove all alternate update paths — fleet redeploy is release + upgrade all

Killed:
- rebuild_and_restart (in-container cargo self-compile): the MCP tool,
  the `rebuild` chat command in all four transports, the web-ui bot
  command, and the underlying function. This was the path that caused
  the exec() deadlocks.
- upgrade_sled gateway MCP tool: second entry point to sled upgrades,
  defaulted to serving the gateway's own macOS binary to Linux sleds.
- GET /api/huskies-binary (both sled and gateway route trees): served
  current_exe(), wrong platform when the gateway is macOS. Superseded
  by /api/artifacts/ which now also serves on the gateway route tree.
- `huskies upgrade` CLI subcommand and --source flag: third way of
  doing the same download-and-replace. Escape hatch for a bricked sled
  is `docker cp` + restart.

Kept, distinct jobs: `project-rebuild` (container/image updates),
`rebuild gateway` + script/local-release (gateway self-update).

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_019fHdm92yjvguPi2LiXfLB9

2026-07-15 16:46:11 +01:00

dave

75533225e4

fix: commit minor fmt residue blocking mergemaster cherry-picks

Master had 8 uncommitted single-line whitespace changes (blank-line trimming
in test mod headers, etc.) left over from a previous mergemaster cargo-fmt
run that didn't get committed. Each subsequent merge attempt hit:

  cherry-pick failed: 'Your local changes to the following files would be
  overwritten by merge. Please commit your changes or stash them.'

So merges had been silently un-mergeable for the last several rounds —
mergemaster correctly reported the issue but had no way to fix master's
own state from inside the merge_workspace.

Files affected (all whitespace-only):
- chat/transport/matrix/bot/messages/{handle_message,on_room_message}.rs
- chat/transport/slack/commands/{llm,mod}.rs
- http/mcp/agent_tools/worktree.rs
- http/workflow/story_ops/{create,criterion,update}.rs

cargo clippy --all-targets -- -D warnings: clean
cargo fmt --all --check: clean
2636 tests pass.

2026-04-27 11:17:31 +00:00

dave

1f02de8cd0

refactor: split chat/transport/slack/commands.rs (875) into mod + llm

The 875-line commands.rs is split:

- llm.rs: handle_llm_message (LLM turn for non-command messages, ~190 lines)
- mod.rs: SlackSlashCommandPayload + slash_command_to_bot_keyword + handle_incoming_message + tests (~700 lines)

Tests stay co-located with handle_incoming_message in mod.rs. All 2636 tests pass; clippy clean.

2026-04-27 02:32:11 +00:00