Workable 1.1.80926.1

• net10.0

  • Microsoft.Extensions.DependencyInjection.Abstractions (>= 10.0.0)
  • Microsoft.Extensions.Hosting.Abstractions (>= 10.0.0)
  • Microsoft.Extensions.Logging.Abstractions (>= 10.0.0)
  • Workable.Abstractions (>= 1.1.80926.1)

# 1.1.080926.1

Date: 2026-08-09

## Breaking Changes

- Precomputed `WorkAuthorizationSnapshot` values are now scoped to the logical Workable system that produced them. Consumers that manually create trusted snapshots should migrate from `WorkAuthorizationSnapshot.Create(...)` to `WorkAuthorizationSnapshot.CreateForSystem(systemName, ...)`. Previously persisted snapshots and snapshots created through the old factory or positional constructor are unscoped; Workable no longer trusts their groups directly and instead resolves authorization for the retained actor through the target system's configured group providers. Applications that relied exclusively on an unscoped frozen snapshot without a functional actor-based fallback provider must migrate before upgrading.

## Added

- Added expiring persistent execution diagnostics for developer and agent analysis of recently executed work. A completed artifact can include iteration metadata, structured logs, exception and activity identifiers, a complete profile tree, and compact summaries grouped by stable instrumentation keys such as `sql.client` and `http.client`.
- Added work-definition and system-wide persistence policies. Retention is mandatory and limited to one minute through 30 days; work definitions can inherit, override, or explicitly disable the system policy.
- Added `IWorkExecutionDiagnosticsRepository` as the provider contract for artifact lifecycle, querying, temporary capture rules, and bounded expiration cleanup.
- Added SQL Server storage for normalized diagnostic, log, instrumentation-summary, and capture-rule rows. `AddWorkableSqlServerPersistence(...)` registers diagnostics storage without requiring durable queueing; SQL durable-queue registration also supplies the diagnostics repository.
- Added temporary system-level and work-definition-level persistent capture rules. Rules select a minimum log level and logs-only, `Bounded`, or `Full` profile behavior, and always have separate active and artifact-retention expirations.
- Added admin UI controls for temporary persistent capture. The controls are available only when the system advertises registered persistence, support all-work and work-type targeting, and expose active rules and their expiration.
- Added HTTP query, detail, and capture-rule routes under `/workable/execution-diagnostics`, with equivalent named-system routes.
- Added the MCP tools `workable_query_execution_diagnostics` and `workable_get_execution_diagnostic`. Agents can select recent iterations, inspect compact dependency counts, and then request full logs or profile evidence only when needed.
- Added per-artifact SQL and HTTP profiling-availability snapshots, dropped-log and dropped-profile indicators, omitted-node counts, and log-truncation reporting so clients can distinguish zero operations from unavailable or incomplete evidence.
- Added execution-diagnostics policy, logging, profiling, and SQL persistence benchmarks plus unit and live SQL integration coverage.
- Added `WorkAuthorizationScope` and `WorkAuthorizationSnapshot.CreateForSystem(...)`. A scoped null system name explicitly identifies the default unnamed system, while a null scope identifies a legacy or otherwise unscoped snapshot.

## Changed

- Persistent evidence uses its own log level and limits independently of the retained worker log buffer. Reaching `WorkLoggingConfiguration.MaximumBufferedEntries` does not stop eligible persistent entries from being offered to the diagnostics writer.
- Persistent diagnostics automatically enables the configured profile capture mode outside Production. Static persistence configuration in Production records logs without automatically enabling profiling; a temporary rule can explicitly request bounded or full profiling for a short investigation.
- Profile materialization, JSON serialization, size validation, instrumentation-summary construction, and repository I/O now run on a bounded background writer. Work execution uses a non-blocking admission path and drops best-effort evidence instead of waiting on the repository under pressure.
- Temporary persistent capture rules are cached in an immutable, definition-indexed snapshot. Iteration admission does not query the database, while local mutations update the cache immediately and cleanup refreshes reconcile other processes.
- SQL schema deployment uses a dedicated execution-diagnostics component version in the existing `SchemaVersion` table. Runtime auto-deployment and the SQL schema CLI produce the same additive schema.
- `IWorkSystem.CreateSession(...)` reuses a precomputed authorization snapshot only when its actor and logical system scope match the request and target system. Otherwise it resolves groups for the existing actor against the target system and captures a replacement snapshot.
- Built-in HTTP, MCP, SignalR, workflow, host-lifecycle, sample, and benchmark authorization snapshot producers now stamp the logical system that supplied their authorization groups.

## Fixed

- Expiration cleanup no longer applies completed-artifact retention to incomplete diagnostics. An incomplete row must cross the abandonment threshold, preventing one host from deleting a quiet iteration still running on another host that shares the persistence scope.
- Cleanup drains bounded backlog passes promptly while retaining its configured cap and delay, and its timing-sensitive regression test now accepts legitimate extra cleanup passes.

## Security

- Viewing persisted rules and evidence requires `ViewDiagnostics`. Creating or deleting a persistent capture rule requires `ControlSystem`; capture policy never grants permission to queue matching work.
- Persistent capture is unavailable until a repository is registered. Every static or temporary artifact has mandatory expiration, cleanup is bounded, and completed artifacts become unreadable as soon as they expire even before physical deletion.
- Writer capacity, queued bytes, per-iteration logs and bytes, message/property/exception lengths, profile nodes, serialized profile size, query sizes, capture-rule counts, and selector lengths are bounded. Saturation drops diagnostics rather than blocking application work.
- Log messages, structured properties, exception data, and application-authored profile context are retained as supplied and may contain sensitive values. Applications should redact them before logging, keep retention short, and restrict diagnostics access. Built-in SQL profiling continues to redact obvious secret parameters, omit binary values, and enforce statement/parameter limits.
- Sharing a `WorkRequestContext` across systems no longer carries authorization groups from the source system into the target system. Foreign, actor-mismatched, and unscoped snapshots use the target system's normal authorization fallback, and the resulting session captures only the replacement target-system snapshot. Worker and workflow persistence continues to remove authorization snapshots from stored request contexts.

## Documentation

- Added a persistent execution-diagnostics guide covering registration, schema deployment, work/system policy, production behavior, profiling modes, memory and artifact bounds, UI and API controls, MCP discovery, agent interpretation, privacy, and custom repository semantics.
- Linked the feature from the root README, documentation index, general diagnostics concept, logging guide, HTTP and MCP adapters, admin UI, sample host, SQL Server integration, and abstractions extension-point documentation.