Fix scheduled chat automation dispatch

[louis4li]

Issue

Closes aevatarAI/aevatar-framework#171

Scope

• Expose scheduled automation tools for NyxID chat turns when published profile members are empty.
• Prefer direct scheduled automation tools while retaining Ornn search/publish for explicit Ornn intent or fallback.
• Carry provider-confirmed scheduled creator receipts through NyxID chat task lifecycle.
• Propagate NyxID Assistant owner/provider metadata through shared scheduled delivery metadata mapping.
• Persist scheduled invocation authorization facts into workflow schedule targets so fired schedules pass dispatch authorization.

Verification

• dotnet test test/Aevatar.AI.Tests/Aevatar.AI.Tests.csproj --nologo --filter AgentTurnToolCatalogMaterializerTests -v minimal
• dotnet test test/Aevatar.Capabilities.Tests/Aevatar.Capabilities.Tests.csproj --nologo --filter MainnetBootScriptTests -v minimal
• dotnet test test/Aevatar.GAgents.ChannelRuntime.Tests/Aevatar.GAgents.ChannelRuntime.Tests.csproj --nologo --filter ScheduledAgentCreatorToolTests -v minimal
• dotnet test test/Aevatar.Workflow.Application.Tests/Aevatar.Workflow.Application.Tests.csproj --nologo --filter WorkflowScheduleApplicationServiceTests -v minimal
• Focused NyxID chat regression set: 326 passed.
• Focused channel runtime regression set: 95 passed.
• bash tools/ci/test_stability_guards.sh
• bash tools/ci/architecture_guards.sh
• Local Mainnet host reachable on http://127.0.0.1:5107; selected NyxID node ce344be6-dcd3-46d0-ac81-b4902633ab4b restored to online/dispatchable.
• Final NyxID proxy /api/workflow/observatory/me and one-shot fired delivery retest: blocked by local HTTPS TLS handshake EOF to https://nyx-api.chrono-ai.fun, also affecting unrelated user-context-mock proxy requests.

Notes

• Earlier local one-shot schedule creation reached ScheduledDispatchFireStartedEvent but failed because the scheduled invocation authorization fact was missing from the workflow target. This PR maps that fact from the creator authorization plan into the workflow schedule configuration and service invocation target.
• The final proxy blocker is external/connectivity-level: direct curl https://nyx-api.chrono-ai.fun/health fails with LibreSSL SSL_connect: SSL_ERROR_SYSCALL, and nyxid proxy request user-context-mock /api/status fails with the same TLS handshake EOF.

Generated with Claude Code.

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-09-09T04:19:58.221838Z	50868de	PR opened

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 50868deb0f

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Preserve owner LLM selection through schedule mapping

When the authorization planner resolves an owner-specific LLM route, it sets both OwnerLlmStateVersion > 0 and OwnerLlmSelection, but this mapper unconditionally discards the selection. ScheduledServiceInvocationDispatchPort.ValidateOwnerLLMSelectionAndPayload then rejects every fired schedule in such a scope because IsValidExplicitOwnerLLMSelection(null) is false; the workflow schedule model must carry the typed selection and BuildWorkflowChatRequest must copy its route/model into LlmControl, as the Studio scheduling path already does.

AGENTS.md reference: AGENTS.md:L11-L11

Useful? React with 👍 / 👎.

[chatgpt-codex-connector]

Configure the NyxID assistant delivery provider

With the checked Mainnet configuration, both new option values passed here are null: appsettings.json configures only AssistantActions:Enabled, and MainnetHostBuilderExtensions only supplies that same default. Consequently CreateNyxIdAssistantMetadata emits no outbound provider slug, and an ordinary public-chat reminder that does not invent nyx_provider_slug reaches ScheduledAgentCreateRequestMapper.Plan and fails with channel_outbound_provider_slug_unavailable; configure or resolve the provider for the Mainnet NyxID assistant path rather than exposing a creator that cannot use its default metadata.

Useful? React with 👍 / 👎.