ltms
0 Followers · 0 Following
  • Joined on 2026-03-08
Repositories Projects Packages Public Activity Starred Repositories
ltms commented on issue fleet/fleetd#480 2026-09-12 00:50:39 +02:00
Lead session rollover: the lead asks for a handover, fleetd verifies it, clears the pane and boots the next lead

leadRollover: is now configured and LIVE on the Mac

The operator authorised the fleetd.yaml edit, with one requirement: use a relative path to a file in the workspace, not an absolute…

ltms opened issue fleet/fleetd#488 2026-09-12 00:50:03 +02:00
fleet.leaders.<name>.cwd is never validated — a relative value is silently accepted
ltms closed pull request fleet/fleetd#487 2026-09-12 00:47:06 +02:00
fleetd #480 follow-up: resolve relative leadRollover.handoverPath against the lead's workspace
ltms pushed to main at fleet/fleetd 2026-09-12 00:46:45 +02:00
7f9137fcb6 fleetd #480: ignore the handover file, and note the absolute-path guarantee in the handover skill
3bf3968bc7 Merge #487: resolve a relative leadRollover.handoverPath against the calling lead's workspace (fleetd #480 follow-up)
261aa056f9 fleetd #480 follow-up correction 2: guarantee resolveHandoverPath is always absolute
042b8c99dd fleetd #480 follow-up correction: cover Fleetd.leadRollover(...)'s own wiring behaviourally
4bfab6b718 fleetd #480 follow-up: resolve a relative leadRollover.handoverPath against the calling lead's workspace
Compare 5 commits »
ltms commented on issue fleet/fleetd#480 2026-09-11 02:33:29 +02:00
Lead session rollover: the lead asks for a handover, fleetd verifies it, clears the pane and boots the next lead

Shipped and deployed — 2026-09-11

All three units merged, docs updated, daemon redeployed, tool proven reachable on the live daemon.

ltms pushed to main at fleet/fleetd 2026-09-11 02:30:36 +02:00
008a457557 docs: fleet_handover is shipped — update the charter table and the handover skill
ltms pushed to main at fleet/fleetd 2026-09-11 02:27:57 +02:00
9494a6b99a Merge #485: fleetd #480 Unit C — the fleet_handover MCP tool
eb0557621e fleetd #480 correction round: collapse FleetMcp to one required constructor
62646957ea fleetd #480 Unit C: wire fleet_handover MCP tool onto LeadRollover
Compare 3 commits »
ltms deleted branch worker/480-c-handover-tool-8ed764-6 from fleet/fleetd 2026-09-11 02:27:57 +02:00
ltms merged pull request fleet/fleetd#485 2026-09-11 02:27:56 +02:00
fleetd #480 Unit C: fleet_handover MCP tool
ltms pushed to main at fleet/fleetd 2026-09-11 02:21:07 +02:00
a0eed6f01b Merge #484: fleetd #480 Unit E — a BLOCKED pane is not a settled pane
e2a91e883e fleetd #480 Unit E correction: retire "injectable" wording from the log lines
802c0ab701 fleetd #480 Unit E: BLOCKED is not a settled turn boundary
Compare 3 commits »
ltms deleted branch worker/480-e-blocked-is-not-settled-e3d8e7-7 from fleet/fleetd 2026-09-11 02:21:07 +02:00
ltms merged pull request fleet/fleetd#484 2026-09-11 02:21:06 +02:00
fleetd #480 Unit E: BLOCKED is not a settled turn boundary
ltms opened issue fleet/fleetd#486 2026-09-11 02:20:12 +02:00
LeadRollover's settle poll has no bound of its own, so a regression shows up as a CI hang instead of a red test
ltms commented on issue fleet/fleetd#480 2026-09-11 01:58:01 +02:00
Lead session rollover: the lead asks for a handover, fleetd verifies it, clears the pane and boots the next lead

Lead status, 2026-09-11 — Unit A merged, two units in flight, one criterion I cannot prove

Unit A merged (PR #483, merge commit 4bab23e)

leadRollover: config block + `dev.ltms.fleet.l…

ltms pushed to main at fleet/fleetd 2026-09-11 01:51:23 +02:00
4bab23e241 Merge #483: fleetd #480 Unit A — lead rollover core (config + executor)
a94262271b fleetd #480 correction round: defer the roll, and gate it on caller identity
5c12865c25 fleetd #480 Unit A: lead rollover core (config block + executor)
Compare 3 commits »
ltms deleted branch worker/480-a-rollover-core-6fc2ad-4 from fleet/fleetd 2026-09-11 01:51:23 +02:00
ltms merged pull request fleet/fleetd#483 2026-09-11 01:51:21 +02:00
fleetd #480 Unit A: lead rollover core (config block + executor)
ltms opened issue fleet/fleetd#482 2026-09-11 01:22:51 +02:00
A context reset changes the peer's session id, and fleetd keeps reporting the dead one — so resumeSessionId would resume the conversation clearAfterTurn just discarded
ltms commented on issue fleet/fleetd#480 2026-09-11 01:20:04 +02:00
Lead session rollover: the lead asks for a handover, fleetd verifies it, clears the pane and boots the next lead

Two more design points, found by re-reading the flow

1. The roll must target the CALLING lead, not "the primary" — this is invariant 3

msg/LeadHeartbeatLoop.java:245 resolves its…

ltms pushed to main at fleet/fleetd 2026-09-11 01:17:22 +02:00
3f8c956325 docs: the handover skill must not promise a tool that does not exist