The Versions page (VersionViews.Versions) can hand itself to the Collaboration plugin: when the node Collaboration/Workspace is on the mesh, the page embeds that workspace's TrackChanges area and links back to the built-in list (?builtin=1).

It used to delegate whenever the node EXISTED. On memex.meshweaver.cloud (2026-11) the node existed while its type, Collaboration/Review, failed to compile (CS0103 for CommentsExtensions, AnnotationExtensions and ChangeRendering). Its hub therefore served the default areas and no TrackChanges, and every click on Versions showed "Area not found — No renderer is registered for area TrackChanges on hub Collaboration/Workspace".

The rule

The page delegates only when both answers are yes:

  1. The node exists. PluginSurfaceProbe.Exists reads the query index. This step is bounded and activates no hub, because a hub probe of a missing node costs the full activation timeout.
  2. The workspace's own hub lists TrackChanges. A GetLayoutAreasRequest goes to Collaboration/Workspace, and the probe waits at most 5 s for the answer.

Otherwise the reader gets the built-in list.

Why it fails closed

MeshNodeLayoutAreas.CanRenderArea, the probe behind the node menu, fails open. It has two reasons. Its closed direction would remove an affordance such as Delete, Copy or Move and put nothing in its place. And the layout definition it reads might not be the one that serves the node.

Neither reason applies here:

So each of these answers "do not delegate":

The listing carries only VISIBLE areas. A TrackChanges view marked [Browsable(false)] would therefore also read as "not rendered", and the reader would get the built-in list rather than a dead page.

Pinned by VersionsWithUnrenderableWorkspaceTest (the workspace's type has no TrackChanges, so the page shows the built-in list) and VersionsWithRenderableWorkspaceTest (the type renders TrackChanges, so the page still delegates), both in MeshWeaver.Graph.Views.Test.