Owns the four delivery workflows: build-and-tests.yml, benchmarks.yml, website.yml and release.yml. Build and Tests owns Release functional qualification; Benchmarks runs one job per database, data type and node count and uploads each job's result file; Website only downloads the result files of one Benchmarks run, generates the static landing page and publishes Pages; Release owns explicitly authorized packaging and publication. Website must never build .NET/AppHost, start Aspire or containers, run product/browser/TUnit/analyzer/coverage suites, depend on product checks, or trigger on product/test-infrastructure changes. Adding such coupling requires specific owner approval. Preserve pinned actions, source identities, original artifacts and least-privilege permissions.

Follow the root policy and the owning feature specification. Keep changes in their actual owner, preserve unrelated work, and remove replaced code together with exclusive callers and fixtures. Use Orleans calls for distributed execution and silo-local ZoneTree owners for files. Preserve persisted authorization, operation correctness, resource bounds, cancellation and joined shutdown. Never turn a static check or focused test into a claim of complete runtime qualification.

From the repository root:

dotnet build KeyLoad.slnx --no-restore -warnaserror

Use the root's complete solution, TUnit, real process recovery and Aspire SDK/MCP gates as applicable. Local checks are development evidence; delivered-source qualification and public measurements require exact-source Linux GitHub artifacts. Do not weaken compiler, analyzer, source-identity, coverage or runtime assertions.

Use the installed Orleans skill for Orleans design and the relevant installed formatting, Aspire or diagnostics skill when the task needs it. Follow explicit owner scope and dependency-adoption rules.