Fix HTTP context disposal race in Lecti selector deferred task

[Copilot]

The deferred task in Lecti/Selector.cs captured closures over HTTP context objects that are disposed after request completion, causing access violations when the task executes asynchronously.

Changes

• Capture IP address, target ID, and namespace as local variables before queuing the deferred task
• Deferred task lambda now references captured values instead of disposed context objects

// Before: captured references to context objects
async Task Task(CancellationToken ct, Repositories repos) {
    var data = new PluginData {
        Key = context.Request.HttpContext.Connection.RemoteIpAddress.MapToIPv4().ToString(),
        Value = context.Target.Id.ToString(),
        Namespace = stk.Identity.OriginManifest.Name,
    };
    ...
}

// After: capture values first
var ipAddress = context.Request.HttpContext.Connection.RemoteIpAddress.MapToIPv4().ToString();
var targetId = context.Target.Id.ToString();
var pluginNamespace = stk.Identity.OriginManifest.Name;

async Task Task(CancellationToken ct, Repositories repos) {
    var data = new PluginData {
        Key = ipAddress,
        Value = targetId,
        Namespace = pluginNamespace,
    };
    ...
}

Original prompt

---

This section details on the original issue you should resolve

<issue_title>Fix premature object disposal on objs in deferred tasks</issue_title>
<issue_description></issue_description>

<agent_instructions>Appears on the Lecti selector deferred task, for the HTTP object</agent_instructions>

Comments on the Issue (you are @copilot in this section)

• Fixes Fix premature object disposal on objs in deferred tasks #62

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.