Ota Pressure-Tests Its .NET Contract on OrchardCore

The Ota team stress-tested its readiness contract model against OrchardCore, a large real-world ASP.NET Core codebase, rather than a toy repository. The goal was to prove that a deliberately narrow slice — one unit-test project's restore, build, and test steps, verified on both native and container paths — could be modeled honestly without claiming ownership of the entire repo.

Two maturity upgrades stood out. First, dotnet restore moved from a single shell-run line into a structured dependency-hydration step that explicitly declares its source and working directory. Second, dotnet build and dotnet test were similarly restructured into explicit executable, argument, and working-directory fields, letting native and container modes vary only in context rather than duplicating shell text.

What mattered here wasn't a dramatic bug discovery but a governance lesson: the contract deliberately avoided claiming the full OrchardCore solution, its functional test lanes, or its asset/documentation workflows. Instead it owned one clear contributor-readiness slice and proved it thoroughly, backed by a green matrix run (#28971743168) across Ubuntu, macOS, and Windows for both native and container execution.

For engineers evaluating CI/readiness tooling, the takeaway is that a contract which narrows honestly and proves exactly what it claims is more trustworthy than one that overclaims broad repo coverage it can't actually verify.