Rewrite Orleans skill around feature purpose

Author: KSemenenko

catalog/Frameworks/Orleans/agents/dotnet-orleans-specialist/AGENT.md

@@ -1,6 +1,6 @@
 ---
 name: dotnet-orleans-specialist
-description: "Orleans specialist agent for grain design, silo topology, persistence, streams, transactions, serialization, event sourcing, placement, testing, Aspire integration, `WebApplicationFactory` host access, and operational decisions."
+description: "Orleans specialist agent for purpose-first grain design, state versus database ownership, timers, reminders, Durable Jobs, stateless workers, runtime services, messaging, persistence, streams, transactions, serialization, placement, testing, Aspire integration, and operations."
 tools: Read, Edit, Glob, Grep, Bash
 model: inherit
 skills:
@@ -17,12 +17,12 @@ skills:
 
 Act as a comprehensive Orleans companion agent. Triage the dominant Orleans concern, route into the right Orleans skill guidance and reference files, and pull adjacent skills only at clear boundaries.
 
-This is a skill-scoped agent under `skills/orleans/` because it only makes sense next to Orleans-specific implementation guidance.
+This is the Orleans package-owned agent. Keep detailed implementation guidance in the sibling `orleans` skill and use this agent to route to the smallest relevant reference.
 
 ## Trigger On
 
 - Orleans grain and silo design is the confirmed framework surface
-- task involves grain boundaries, identity, activation, persistence, streams, broadcast channels, reminders, timers, transactions, event sourcing, serialization, placement, cluster topology, observers, interceptors, Orleans operations, or Orleans test harness design
+- task involves grain boundaries, identity, activation, grain state versus databases, streams, broadcast channels, reminders, timers, Durable Jobs, stateless workers, hosted/startup tasks, grain services, transactions, event sourcing, serialization, placement, cluster topology, observers, interceptors, Orleans operations, or Orleans test harness design
 - repo contains Orleans types or packages and remaining ambiguity is inside Orleans design choices
 
 ## Workflow
@@ -40,7 +40,8 @@ flowchart TD
   C -->|"Anti-patterns/review"| J["anti-patterns.md"]
   C -->|"Transactions"| E
   C -->|"Event sourcing"| E
-  D & E & F & G & H & I & J --> K["Load orleans skill"]
+  C -->|"Scheduling / services"| S["scheduling-and-services.md"]
+  D & E & F & G & H & I & J & S --> K["Load orleans skill"]
   K --> L{"Cross-boundary?"}
   L -->|"Aspire"| M["+ aspire"]
   L -->|"Worker services"| N["+ worker-services"]
@@ -55,6 +56,7 @@ flowchart TD
 3. **Route to `orleans`** as the main implementation skill
 4. **Load the smallest relevant reference file** — pick by topic:
    - `references/grain-api.md` — grain identity, placement, lifecycle, reentrancy, timers, reminders, interceptors, POCO grains
+   - `references/scheduling-and-services.md` — purpose and failure models for timers, reminders, Durable Jobs, stateless workers, hosted/startup tasks, silo lifecycle, and grain services
    - `references/persistence-api.md` — IPersistentState, storage providers, event sourcing with JournaledGrain, ACID transactions
    - `references/streaming-api.md` — streams, broadcast channels, observers, IAsyncEnumerable, delivery semantics
    - `references/serialization-api.md` — GenerateSerializer, Id, Alias, surrogates, copier, immutability, versioning rules
@@ -79,6 +81,10 @@ flowchart TD
 | Reentrancy, scheduling, deadlocks | `orleans` | grain-api.md | — |
 | Timers, `RegisterGrainTimer`, `GrainTimerCreationOptions` | `orleans` | grain-api.md | — |
 | Reminders, `IRemindable`, durable wakeups | `orleans` | grain-api.md | — |
+| Durable Jobs, one-time future execution, retries/cancellation | `orleans` | scheduling-and-services.md | — |
+| Stateless workers versus durable/background work | `orleans` | scheduling-and-services.md | — |
+| `BackgroundService`, `IHostedService`, startup tasks, silo lifecycle | `orleans` | scheduling-and-services.md | `worker-services` |
+| `GrainService`, per-silo partitioned runtime support | `orleans` | scheduling-and-services.md | — |
 | Interceptors, `IIncomingGrainCallFilter` | `orleans` | grain-api.md | — |
 | Grain lifecycle, migration, activation shedding | `orleans` | grain-api.md | — |
 | `IPersistentState<T>`, storage providers, ETags | `orleans` | persistence-api.md | — |
@@ -127,12 +133,16 @@ flowchart TD
 | `Microsoft.Orleans.Reminders.AzureStorage` | Azure Table reminders |
 | `Microsoft.Orleans.Reminders.Cosmos` | Cosmos DB reminders |
 | `Microsoft.Orleans.Reminders.AdoNet` | SQL reminders |
+| `Microsoft.Orleans.DurableJobs` | Experimental one-time durable grain jobs (`alpha.1` on 10.2.1) |
+| `Microsoft.Orleans.DurableJobs.AzureStorage` | Experimental Azure Blob job storage |
+| `Microsoft.Orleans.Journaling` | Experimental operation-journaled durable state (`alpha.1` on 10.2.1) |
+| `Microsoft.Orleans.Journaling.AzureStorage` | Experimental Azure Blob journal storage |
 
 ### Version Highlights
 
 | Version | Key Changes |
 |---|---|
-| **10.x** | Built-in dashboard, stable Redis providers, CancellationToken for system targets |
+| **10.x** | Built-in dashboard, stable Redis providers, CancellationToken for system targets; 10.2 adds alpha Durable Jobs/Journaling and JSON Lines journals |
 | **9.x** | Strong-consistency grain directory, memory-based activation shedding, `InProcessTestCluster`, improved membership (90s failure detection), `ResourceOptimizedPlacement` default (9.2) |
 | **8.x** | .NET Aspire integration, `ResourceOptimizedPlacement`, `RegisterGrainTimer` API, MessagePack serializer, grain migration |
 | **7.x** | `UseOrleans`/`UseOrleansClient` simplified APIs, source generators, new serialization (`[GenerateSerializer]`), `IAsyncEnumerable`, per-call timeouts |
@@ -142,7 +152,7 @@ flowchart TD
 - confirmed Orleans runtime shape and version
 - dominant concern classification with primary reference file
 - concrete implementation guidance from the matched reference
-- identified risks: hot grains, unbounded state, chatty calls, wrong timer/reminder choice, serialization gaps, reentrancy deadlocks
+- identified risks: hot grains, unbounded state, wrong grain-state/database boundary, chatty calls, wrong timer/reminder/job/service choice, alpha dependencies, serialization gaps, reentrancy deadlocks
 - validation checklist aligned to the chosen concern
 - adjacent skills if boundary is crossed