Cluster overview action policy refinement
The existing overview route permits AuthenticatedRead. Edit cluster, New node, per-node Edit and Deployments destinations require ConfigEditor (Administrator or Designer). Their page action links now use the existing ConfigEditor policy through AuthorizeView; the action column is likewise omitted for denied readers. No destination/endpoint/route policy, query or business callback changes.
Before source change the four-role regression was red2 (Reader/Operator see forbidden authoring destinations) and green2 (Designer/Administrator). Final real ASP.NET authorization engine run4/4 verifies all four destinations plus retained readable cluster/node content and exact destination AuthorizeAttribute policies.
The first fixture compile needed required RedundancyMode and an explicit Deployments type due namespace ambiguity. Adding AuthorizeView exposed bUnit's intentional MissingBunitAuthorizationException guard registrations: AddAuthorizationCore uses TryAdd and therefore did not replace these defaults. Intermediate failed runs (including diagnostic fixture compile) are retained. The final fixture removes only the two bUnit authorization service/policy-provider guard descriptors, installs the real authorization engine, and supplies an explicit authenticated role principal. It retains all destination, denied/allowed and readable-content assertions. No production behavior was changed to accommodate the fixture.
Source ownership refinement was documented in the implementation chapter before this behavior change. Root navigation/Home/namespace files remain a separate scope. No real LDAP, database, fleet or deployment operations.