0.2.0

One import is now enough

import OpenRouterForFoundationModels alone resolves LanguageModelSession, @Generable, and the rest of the framework surface — the module re-exports whichever framework it was built against. Previously a consumer had to add the matching import themselves, and which one was correct depended on the ServerFoundationModels trait they set, which the installation docs got wrong for trait users. Existing code that imports the framework explicitly keeps working.

import OpenRouterForFoundationModels   // that's it, under either trait configuration

Fixed

• The ServerFoundationModels dependency floor said from: "0.6.0" while 0.1.0 had already removed the 0.6.0 compatibility shims. Local resolution happened to pick 0.7.0 so it never surfaced, but a consumer pinned to 0.6.x would have failed to compile. The manifest now requires 0.7.0, matching what 0.1.0 documented.

Internal

• The ServerFoundationModels trait is spelled once, in FoundationModelsExports.swift, instead of in all 15 source, test, and example files. The trait and its conditional dependency in Package.swift are unchanged.

Both trait configurations build and pass 123 tests, matching the 0.1.0 baseline exactly; Linux CI is green under the ServerFoundationModels backend.