BinaryToggle layout passes LayoutAreaHost to EntityStore-only GetData overload, breaking its NodeType build and stalling the image rollout

[systemorph-com]

What is failing
The deployment's DynamicTypePreWarmer readiness gate refused the new image because two NodeTypes regressed on it: BinaryClickerV2/BinaryToggle and Store/Review. Store/Review has since recompiled cleanly (the gate's WATCH mechanism already retracted it — a verdict formed against a half-applied content update, as designed). What remains is BinaryClickerV2/BinaryToggle: it still fails to compile on this image, and with no usable build its content renders as an untyped element (no CLR type registered — views render empty) until its sources are fixed.

Probable cause (high confidence — the Roslyn diagnostics are directly observable today)
BinaryClickerV2/BinaryToggle/Source/BinaryToggleLayout fails with CS1929 at line 52: it calls GetData<BinaryToggleData>() on a LayoutAreaHost, but the only matching extension, WorkspaceOperations.GetData<T>(EntityStore), requires an EntityStore receiver. The layout is passing the wrong receiver — most likely an API changed shape and this content was never updated to match. Note this is a content-space defect, not a platform bug: the pre-warmer gate is working exactly as designed.

Impact
One occurrence on one pod; the rollout stalls with the previous image still serving, so no user-visible outage from the stall itself. However, the stalled rollout blocks everything else baked into the new image, and BinaryToggle renders empty on it. No user-facing data loss.

Where to look

• BinaryClickerV2/BinaryToggle/Source/BinaryToggleLayout — line 52, the GetData<BinaryToggleData> call on LayoutAreaHost; pass the EntityStore instead.
• Diagnostics confirmed via GetDiagnostics on BinaryClickerV2/BinaryToggle (status: Error).
• Store/Review needs no action — already compiling green as of 2026-09-26T04:09:30Z.

Severity is sev:M (single content-space type, easy one-line fix, old image serving meanwhile). If this rollout carries other urgent changes, a human may re-rule upward since the gate blocks the whole image.

---

Evidence

Fingerprint	ea590f5bb631b81b
Category	MeshWeaver.Hosting.DynamicTypePreWarmerHostedService
Severity	Critical
Namespace	memex
Pods	memex-portal-deployment-56fbdcd48f-cbms9
Occurrences	1
First seen	2026-09-25 19:02:17Z
Last seen	2026-09-25 19:02:17Z
Routing	not determined — no configured route matches the category MeshWeaver.Hosting.DynamicTypePreWarmerHostedService. This repository is the configured fallback, not a finding about who owns the fault; the category names the LOGGER, which may not be the subject.

Recent log lines

2026-09-25 19:02:17Z memex-portal-deployment-56fbdcd48f-cbms9 crit: MeshWeaver.Hosting.DynamicTypePreWarmerHostedService[0]
      DynamicTypePreWarmer: REFUSING READINESS — 2 NodeType(s) regressed on this image: BinaryClickerV2/BinaryToggle, Store/Review (1 retired by their repository (not a regression) — Crm/Client; 1 failed with no working build to regress from (already broken, or the first bake of this instance) — HomeAssistant/Home). The rollout will stall with the previous image still serving. Each of these types is now being WATCHED: if it reaches a usable build on this image (the platform recompiles a failed type once its sources change), its regression is retracted and readiness follows — so a verdict formed against a half-applied content update clears itself. Regressions: Store/Review → CompileError: Compilation failed: Compilation failed for 'Store/Review':
      CS0246 Error (line 4448): The type or namespace name 'PackageReviewContent' could not be found (are you missing a using directive or an assembly reference?)
      CS1061 Error (line 4448): 'MessageHubConfiguration' does not contain a definition for 'AddReviewControlPlane' and no accessible extension method 'AddReviewControlPlane' accepting a first argument of type 'MessageHubConfiguration' could be found (are you missing a using directive or an assembly reference?)
      CS0103 Error (line 4448): The name 'ReviewTestsArea' does not exist in the current context
      CS1701 Warning: Assuming assembly reference 'System.Linq.Expressions, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' used by 'System.Reactive' matches identity 'System.Linq.Expressions, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' of 'System.Linq.Expressions', you may need to supply runtime policy
      CS1701 Warning: Assuming assembly reference 'System.Linq.Expressions, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' used by 'System.Reactive' matches identity 'System.Linq.Expressions, Version=10.0.0.0, Culture=neutral, PublicKeyToken…[truncated]

_{Re-addressed by the current identity function: this incident inherited 863037202534652c (Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.}

_{Opened automatically from Admin/_LogIncident/ea590f5bb631b81b. Recurrences are folded into this issue rather than opening new ones.
It also stands for the whole log site dfc2d467bfa61745: other fingerprints of this site fold in here as comments rather than opening tickets of their own.}

[systemorph-com]

Folded in — a DIFFERENT fingerprint from the same log site.

This issue tracks the log site dfc2d467bfa61745 (MeshWeaver.Hosting.DynamicTypePreWarmerHostedService), and these occurrences belong to it. They carry their own fingerprint — the masking split one site across several — so before this they would have opened a SEPARATE ticket. One log site fanned out into 46 of those, which is why they fold here instead. Nothing is discarded: the distinguishing evidence is below, and splitting this back out is a person's call.

Folded fingerprint	9df081c97d57767d
Log site	dfc2d467bfa61745
Category	MeshWeaver.Hosting.DynamicTypePreWarmerHostedService
Severity	Critical
Detail	DynamicTypePreWarmer: GATE NOT ARMED — {n} NodeType(s) regressed on this image and NOTHING CONSUMES THIS STATE, so nothing is blocked. Startup continues and instances of these types will fail. To make it enforce, run a host that registers the bake readiness check with '{value}'=true, and give the startupProbe a full cold-bake budget. {n} NodeType(s) regressed on this image: {path} ({n} failed with no working build to regress from (already broken, or the first bake of this instance) — {path}, {path}, {path}). Regressions: {path} → CompileError: Compilation failed: Compilation failed for '{value}':
Namespace	memex-cloud
Pods	memex-portal-deployment-6d84f5d754-xkfk4
Occurrences	1
First seen	2026-09-26 10:47:16Z
Last seen	2026-09-26 10:47:16Z
Already folded here	1 fingerprint(s)
Incident	Admin/_LogIncident/9df081c97d57767d
Triage called it	Portal bake of Feedback/Digest compiles against a stale FeedbackHandover, and the bake-readiness gate is not armed so the broken build ships

What triage wrote about this fingerprint

What is failing

Two things, one incident:

1. The cold-bake of the Feedback/Digest NodeType on the memex-portal-deployment image fails to compile: CS0117 'FeedbackHandover' does not contain a definition for 'RouteOf' (line 339) and for 'Deliver' (line 344) — these are called from Feedback/Digest/Source/DigestSchedule (Post/PostOnActivation), which pulls in the shared source Feedback/Feedback/Source/FeedbackHandover.
2. The bake-readiness gate on this deployment is not armed: no host registers the check with 'PreWarm:GateReadiness'=true, so the failed bake blocks nothing — startup continues and every instance of the affected type will fail at runtime.

Probable cause

For (1), medium confidence in a stale-source / version-skew bake: the live definition of Feedback/Feedback/Source/FeedbackHandover (v12, 2026-09-24) does define RouteOf and Deliver, and the hub compile on the control instance succeeded with them (Feedback/Digest compilationStatus: Ok, v90 compiled 2026-09-26T04:11). The pod's pre-warm bake, however, resolved a FeedbackHandover that predates those members — most plausibly the image's bake picked up an older copy of the shared source (note the type's buildProvenance: StaleAdopted and the mismatched currentSourceFingerprint vs adoptedSourceFingerprint). The bake environment and the live hub compile disagree about which FeedbackHandover is current; the bake loses.

For (2), high confidence and simple: the deployment's host does not register the bake readiness check (PreWarm:GateReadiness=true) and the startupProbe has no cold-bake budget, so the pre-warmer's regression report is advisory only. The log message itself spells out the remedy.

Impact

One occurrence, one pod (memex-cloud), at startup. Instances of Feedback/Digest on this image will fail when activated — the weekly wrong-answer digest schedule and its signed posts to the control inbox do not run from this pod. Not an outage of the portal itself, but the digest feature is silently dead there, and the unarmed gate means the next genuinely broken bake would also ship. Three further types on this image also have no working build to regress from (Hosting/InstanceAction, MeshWeaver/samples/...), though those read as first-bake/side-effect noise rather than defects.

Where to look

• Start at Feedback/Digest/Source/DigestSchedule (the CS0117 call sites) and how the pre-warm bake resolves the shared sources listed on Feedback/Digest (shared=@Feedback/Feedback/Source/FeedbackHandover), versus how the live hub compile resolves the same path.
• The pre-warmer itself: MeshWeaver.Hosting.DynamicTypePreWarmerHostedService.
• Ops fix for (2): register the bake readiness check with 'PreWarm:GateReadiness'=true on the portal host and give the startupProbe a full cold-bake budget.

Not a duplicate as far as I can find — no existing incident or issue covers this bake/gate symptom for this component.

Still occurring: 1 more since the last update (1 total).

• Last seen: 2026-09-26 10:47:16Z
• Pods: memex-portal-deployment-6d84f5d754-xkfk4

Recent log lines

2026-09-26 10:47:16Z memex-portal-deployment-6d84f5d754-xkfk4 crit: MeshWeaver.Hosting.DynamicTypePreWarmerHostedService[0]
      DynamicTypePreWarmer: GATE NOT ARMED — 1 NodeType(s) regressed on this image and NOTHING CONSUMES THIS STATE, so nothing is blocked. Startup continues and instances of these types will fail. To make it enforce, run a host that registers the bake readiness check with 'PreWarm:GateReadiness'=true, and give the startupProbe a full cold-bake budget. 1 NodeType(s) regressed on this image: Feedback/Digest (3 failed with no working build to regress from (already broken, or the first bake of this instance) — Hosting/InstanceAction, MeshWeaver/samples/Graph/Data/PensionFund/BalanceSheet, MeshWeaver/samples/Graph/Data/Type/article). Regressions: Feedback/Digest → CompileError: Compilation failed: Compilation failed for 'Feedback/Digest':
      CS0117 Error (line 339): 'FeedbackHandover' does not contain a definition for 'RouteOf'
      CS0117 Error (line 344): 'FeedbackHandover' does not contain a definition for 'Deliver'
      CS1701 Warning: Assuming assembly reference 'System.Linq.Expressions, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' used by 'System.Reactive' matches identity 'System.Linq.Expressions, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' of 'System.Linq.Expressions', you may need to supply runtime policy
      CS1701 Warning: Assuming assembly reference 'System.Linq.Expressions, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' used by 'System.Reactive' matches identity 'System.Linq.Expressions, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' of 'System.Linq.Expressions', you may need to supply runtime policy
      CS1701 Warning: Assuming assembly reference 'System.Linq.Expressions, Version=8.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' used by 'System.Reactive' matches identity 'System.Linq.Expressions, Version=10.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' of 'System.Linq.Expressions', …[truncated]

_{Re-addressed by the current identity function: this incident inherited 863037202534652c (Systemorph/MeshWeaver.Plugins#1796). Those nodes are superseded and will not fold, file or comment again.}