H-A-177: move a data module without its restore point where no recovery holder is placed

The node-engine held every data-holding module's take-in for good: it asked
the seat mesh-recovery for the restore point, and nothing answers because
no holder of the seat is placed on the mesh (H §456). It now asks only where
the assigner's placements it holds name a holder (and while they are not
read yet); where none is placed it moves the module without a point and
raises the finding restore-point-missing (warning, scope machine, id the
module), cleared at the module's next take-in that takes its point. A holder
placed that does not answer still holds the move.

Builds: design 47 H §456, H-A-177
This commit is contained in:
2026-11-20 18:56:43 +01:00
parent b877d36f6f
commit d217056cf7
9 changed files with 179 additions and 1 deletions
+6
View File
@@ -287,6 +287,9 @@ type Composer struct {
passing atomic.Bool
// early is true while the early pass of a start runs (design 47 G §683, A-117).
early atomic.Bool
// assignmentsRead is set once the watch of the seat's assignments has caught up: from then the placements this composer holds
// are the mesh's (RecoveryPlaced, design 47 H, H-A-177).
assignmentsRead atomic.Bool
// last is how the last pass went, under mu.
last Pass
// watching says the composer's loop runs (Watch), so an ask of a pass can be answered.
@@ -656,6 +659,9 @@ func (c *Composer) Watch(ctx context.Context, _ string) (<-chan agent.Update, er
dirty = true // a secret changed: its new generation is asked of the vault at the compose
case t.u.Caught:
caught[t.in] = true
if ins[t.in].bucket == buckets.Assignments {
c.assignmentsRead.Store(true)
}
if ins[t.in].bucket == buckets.Wants {
c.endKeptWants() // the wants the seat says now are the ones composed from (§683)
}