feature.Order emits WarnDeepFeatureChain (depth ≥ 16) and returns *FeatureDAGTooDeepError (depth ≥ 64). Today these only fire from inside Engine.Up's feature-fetch path — config.Resolve runs feature ordering against partial metadata (no installsAfter/dependsOn known yet), so depth warnings are never surfaced to callers using Resolve standalone for inspection.
Plan
Re-run feature.Order after fetch in Engine.Up (already happens) AND emit any warnings from there as config.Warning entries on Workspace.Config.Warnings. That preserves Resolve-without-fetch as fast/cheap and surfaces the depth signal where it actually matters (after metadata is known).
Smaller scope: just thread the warnings through. No behavior change; just visibility.
feature.OrderemitsWarnDeepFeatureChain(depth ≥ 16) and returns*FeatureDAGTooDeepError(depth ≥ 64). Today these only fire from insideEngine.Up's feature-fetch path —config.Resolveruns feature ordering against partial metadata (no installsAfter/dependsOn known yet), so depth warnings are never surfaced to callers usingResolvestandalone for inspection.Plan
Re-run
feature.Orderafter fetch inEngine.Up(already happens) AND emit any warnings from there asconfig.Warningentries onWorkspace.Config.Warnings. That preservesResolve-without-fetch as fast/cheap and surfaces the depth signal where it actually matters (after metadata is known).Smaller scope: just thread the warnings through. No behavior change; just visibility.