• Joined on 2026-03-08
ltms pushed to main at fleet/fleetd 2026-09-11 01:16:41 +02:00
2051ceeb26 Merge #481: the handover skill (fleetd #480 Unit B)
325d0771a4 fleetd #480 Unit B: add handover skill for lead session handoff
Compare 2 commits »
ltms merged pull request fleet/fleetd#481 2026-09-11 01:16:40 +02:00
fleetd #480 Unit B: add handover skill for lead handoff
ltms commented on issue fleet/fleetd#480 2026-09-11 01:14:55 +02:00
Lead session rollover: the lead asks for a handover, fleetd verifies it, clears the pane and boots the next lead

Two corrections to the ticket body, one of them a defect in my own brief

1. The roll order in the ticket body is wrong — this is my mistake, not a worker's

The body says the roll is:…

ltms commented on issue fleet/fleetd#480 2026-09-11 01:12:56 +02:00
Lead session rollover: the lead asks for a handover, fleetd verifies it, clears the pane and boots the next lead

What the test suite pins about /clear, and what it does not

Checked while Unit A was being built, against 7b97aae.

member/ClaudeCodeLauncherTest.java:786 (`clearContextUsesTheClaudeComma…

ltms opened issue fleet/fleetd#480 2026-09-11 01:09:38 +02:00
Lead session rollover: the lead asks for a handover, fleetd verifies it, clears the pane and boots the next lead
ltms pushed to main at fleet/fleetd 2026-09-11 00:59:15 +02:00
7b97aae85b docs: move the redeploy procedure out of CLAUDE.md into a skill
ltms commented on issue fleet/fleetd#479 2026-09-10 23:39:42 +02:00
Exhaustion detection is armed on 2 of 8 profiles, and the default profile is not one of them

The design question in my previous comment is already decided and shipped, as #415. Do not re-litigate it. The fleet01 lead found it; I verified every claim below in my own tree before writing…

ltms commented on issue fleet/fleetd#413 2026-09-10 23:34:15 +02:00
Building in the fleetd tree disarms the running daemon, and nothing warns at either end

This ticket is filed as "the next start finds nothing". It is worse than that: **rebuilding under a live daemon can silently truncate the outgoing process's shutdown drain, drop in-flight…

ltms commented on issue fleet/fleetd#479 2026-09-10 23:33:43 +02:00
Exhaustion detection is armed on 2 of 8 profiles, and the default profile is not one of them

I have to correct this ticket's premise. The startup line I asked for already exists, and it already reports the gap precisely. I filed a ticket asking for shipped work. Here is what is…

ltms commented on issue fleet/fleetd#479 2026-09-10 23:25:31 +02:00
Exhaustion detection is armed on 2 of 8 profiles, and the default profile is not one of them

Second host, and it changes which option in the Scope section I would pick.

What the fleet01 lead measured on their host

Reported to me over the coordinator channel. **I did not run these…

ltms commented on issue fleet/fleetd#427 2026-09-10 23:21:31 +02:00
A config key's hot/deferred class is a claim about every consumer, and nothing checks it that way

A live instance of this ticket's shape, found today. It is not in the code — it is in the config file's own comment, which is the surface an operator actually reads.

What I measured

`fleetd/f…

ltms opened issue fleet/fleetd#479 2026-09-10 23:21:03 +02:00
Exhaustion detection is armed on 2 of 8 profiles, and the default profile is not one of them
ltms closed pull request fleet/fleetd#475 2026-09-10 23:16:05 +02:00
fleetd #474: ConfigRef.reload() runs the charter tool-surface gate too
ltms commented on pull request fleet/fleetd#475 2026-09-10 23:15:59 +02:00
fleetd #474: ConfigRef.reload() runs the charter tool-surface gate too

Merged. Your work is on origin/main as 4466ee0, and the follow-up that closes the one gap my battery found is 49a404d (PR #476). git rev-list --count origin/main..HEAD = 0.

Closing this…

ltms closed issue fleet/fleetd#474 2026-09-10 23:15:36 +02:00
A charter naming an unregistered tool is refused at startup but accepted on reload
ltms commented on issue fleet/fleetd#474 2026-09-10 23:15:31 +02:00
A charter naming an unregistered tool is refused at startup but accepted on reload

Closing. I said on this ticket that I would close it when a test kills M2. That test now exists and kills M2 by name.

What shipped

Two commits, both on origin/main:

  • 4466ee0 — the…
ltms closed pull request fleet/fleetd#476 2026-09-10 23:15:05 +02:00
fleetd #474 follow-up: pin main's config wiring against M2
ltms commented on pull request fleet/fleetd#476 2026-09-10 23:14:56 +02:00
fleetd #474 follow-up: pin main's config wiring against M2

Merged locally as 49a404d and pushed. git rev-list --count origin/main..HEAD = 0, origin/main = 49a404d. Closing this PR by hand — a local --no-ff merge does not close a Gitea PR.

I…

ltms pushed to main at fleet/fleetd 2026-09-10 23:13:28 +02:00
49a404ddf3 Merge #474 follow-up: pin main's ConfigRef wiring against the surviving mutation
72d6a6878b fleetd #474 follow-up: pin main's config wiring against M2
Compare 2 commits »
ltms opened issue fleet/fleetd#478 2026-09-10 15:52:38 +02:00
A directory in parityOverlay is reported as copied and arrives empty — Files.copy does not recurse