How long does the integration take?

Change one base URL in an OpenAI-compatible client, or install the Python or TypeScript SDK; the quickstart routes a first request in a few minutes.

Will this lock us into another vendor?

No. The router is Apache-2.0 open source, your provider keys stay yours, and the API is OpenAI-compatible, so leaving is a change of base URL.

What happens when a provider fails?

The router falls back to the next model your policy allows and records the fallback in the trace, so an outage costs a retry, not an incident.

KeyLoad.ProcessRecoveryTests - Skill

Name: KeyLoad.ProcessRecoveryTests
Author: managedcode

Imported from managedcode/KeyLoad (tests/KeyLoad.ProcessRecoveryTests/AGENTS.md). Install upstream with npx skills add managedcode/KeyLoad --skill KeyLoad.ProcessRecoveryTests. Copyright stays with the author.

KeyLoad.ProcessRecoveryTests

Purpose, entry points and ownership

Owns real-process recovery of canonical ZoneTree WAL/files, persisted command outcomes, projections, subscriptions and derived indexes.
Main suites include StorageRecovery/Cases/StorageRecoveryProcessTests.cs, StorageRecovery/Cases/StoragePublicationRecoveryTests.cs, DocumentStorage/Cases/CommandIdempotencyProcessRecoveryTests.cs, EventStreams/Cases/SharedDomainProcessRecoveryTests.cs, EventStreams/Cases/ProjectionProcessRecoveryTests.cs and Messaging/Cases/Subscription/SubscriptionFilterProcessRecoveryTests.cs.
Feature cases belong under matching canonical <SliceName>/ paths; real process-host and shared recovery fixture infrastructure may remain shared.
Program.cs delegates ordinary arguments to the generated Microsoft.Testing.Platform application helper. The explicit --recovery-process argument runs the owning fault scenario in this same test assembly; its exit code, original markers, real abrupt termination, process readers and file-release checks remain part of the test.
Use the real KeyLoad.ProcessRecoveryTests process where required. Preserve node-local ZoneTree storage ownership (files never move with activations; Orleans does all clustering, ADR-136).
These tests establish process-recovery behavior only. They must never be presented as power-loss durability, endurance or complete production qualification; do not substitute mocks/fakes or weaken fault assertions.
Use the installed Orleans skill for Orleans decisions and the relevant installed skill for formatting, Aspire or diagnostics. Follow the owner's explicit installation and dependency scope.
Treat recovery ordering, atomic file publication and filesystem durability as critical contracts. Report unconfigured coverage/complexity gates honestly.

Boundaries and protected risks

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.

Commands and verification

From the repository root:

dotnet test --project tests/KeyLoad.ProcessRecoveryTests/KeyLoad.ProcessRecoveryTests.csproj --no-build --no-restore --output Detailed

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.

Skills

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.

Install KeyLoad.ProcessRecoveryTests and it becomes one more candidate the router can pick - when it fits.

A listing is a routing target with a manifest: what it does, which domains it covers, what it costs and who publishes it. Once installed it sits beside your own models and tools, is scored like any other candidate for each request, and shows up in the trace when it wins. Ratings come from workspaces that installed it, one per account.

{ "ocm": "1", "id": "managedcode-keyload-keyload-processrecoverytests", "kind": "skill", "name": "KeyLoad.ProcessRecoveryTests", "description": "Follow the [root policy](../../AGENTS.md) 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.", "publisher": "managedcode", "version": "1.0.0", "capabilities": { "domains": [ "coding", "customer_support" ], "tags": [ "skill-md", "github-agents" ], "languages": [ "en" ] }, "quality_prior": 0.6, "examples": [ "Follow the [root policy](../../AGENTS.md) 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." ], "primary": false, "metadata": { "source": { "provider": "github-agents", "repository": "https://github.com/managedcode/KeyLoad", "path": "tests/KeyLoad.ProcessRecoveryTests/AGENTS.md", "ref": "62abf192128d77b5618b244c3527e85c3feba409", "url": "https://github.com/managedcode/KeyLoad/blob/62abf192128d77b5618b244c3527e85c3feba409/tests/KeyLoad.ProcessRecoveryTests/AGENTS.md", "key": "managedcode/KeyLoad/tests/KeyLoad.ProcessRecoveryTests/AGENTS.md" } }, "instructions": "# KeyLoad.ProcessRecoveryTests\n\n## Purpose, entry points and ownership\n\n- Owns real-process recovery of canonical ZoneTree WAL/files, persisted command outcomes, projections, subscriptions and derived indexes.\n- Main suites include `StorageRecovery/Cases/StorageRecoveryProcessTests.cs`, `StorageRecovery/Cases/StoragePublicationRecoveryTests.cs`, `DocumentStorage/Cases/CommandIdempotencyProcessRecoveryTests.cs`, `EventStreams/Cases/SharedDomainProcessRecoveryTests.cs`, `EventStreams/Cases/ProjectionProcessRecoveryTests.cs` and `Messaging/Cases/Subscription/SubscriptionFilterProcessRecoveryTests", "cost": { "context_tokens": 779 } }

KeyLoad.ProcessRecoveryTests

About

KeyLoad.ProcessRecoveryTests

Purpose, entry points and ownership

Boundaries and protected risks

Commands and verification

Skills

Install KeyLoad.ProcessRecoveryTests and it becomes one more candidate the router can pick - when it fits.

What it costs to adopt - in engineering time.

One base URL

No vendor lock-in

Failover built in

Use it

Manifest

Reviews