root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(FN-3452): document mesh lease recovery semantics

Browse Source 
Documents mesh lease recovery semantics across the agents, architecture, and multi-project reference files, adding 32 lines of clarifying documentation to explain how mesh leases are recovered in the system.

Fusion-Task-Id: FN-3452
This commit is contained in:
Fusion
2026-05-09 11:24:24 -07:00
committed by gsxdsm
parent 0bd460bb7f
commit e0a84b27fb
16 changed files with 486 additions and 22 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
docs/agents.md
View File

@@ -850,6 +850,8 @@ Implementation tasks require an agent with `role: "executor"`.
## Heartbeat Monitoring and Trigger Scheduling
Heartbeat/executor ownership now actively renews persisted task lease metadata while work is running (`checkoutLeaseRenewedAt` plus owner node/run context). Abandonment recovery is fenced by `checkoutLeaseEpoch` and executed only through `MeshLeaseManager.recoverAbandonedLease(...)`, so stale owners cannot reclaim tasks after recovery.
Fusion's `HeartbeatTriggerScheduler` supports five trigger types:
- `timer` — periodic wake based on heartbeat interval