Dai Ha 987ccef4c7 fleetd #613: log role-fallback gaps at boot, name contextHighNudge in the heartbeat line ...

- reportRoleFallbackGaps(cfg), called right after cfg.validateAll() in Fleetd.main, logs every
  MemberRole with no fleet.<role>s: pool (naming the profile count and the resolved
  defaultProfileFor(role) first choice) and, separately, every role with no
  fleet.charters.<role>: entry. Log only — the deliberate 'unconstrained' fallback in
  FleetConfig#candidateProfiles / CompositePeerLauncher#poolFor is unchanged, and a config with
  profiles: and no fleet: block still starts and still spawns.
- LeadHeartbeatLoop#start()'s boot line now also names contextHighNudge (fleetd #609), alongside
  the three settings it already logged.
- RoleFallbackGapReportTest (new) and two new LeadHeartbeatLoopTest cases pin both lines' content
  via a ListAppender, raising the dev.ltms.fleet logger past logback-test.xml's WARN override for
  the INFO-level lines.

2026-09-22 10:12:09 +07:00

..

docs

CB-634: one shared "fleet" workspace + rename bridged -> fleetd cutover

2026-08-25 04:01:08 +02:00

src

fleetd #613: log role-fallback gaps at boot, name contextHighNudge in the heartbeat line

2026-09-22 10:12:09 +07:00

.gitignore

CB-634: one shared "fleet" workspace + rename bridged -> fleetd cutover

2026-08-25 04:01:08 +02:00

fleetd.example.yaml

fleetd #609: nudge an idle lead to hand over when its own context reads HIGH

2026-09-20 17:11:54 +07:00

pom.xml

fleetd #131: enforce package boundaries with an ArchUnit cycle test

2026-09-03 20:22:46 +07:00