Project executor skills through World State

[jif-oai]

Why

A selected executor environment can be unavailable in one model step and ready in the next. The model should see its skills only while that environment is ready, without rescanning stable files on every sample.

The product assumption is simple:

• an environment ID names one stable logical environment;
• the selected root contents do not change during the thread.

Behavior

E1 unavailable -> do not show E1 skills
E1 ready       -> discover once, cache, show through World State
E1 unavailable -> hide skills, keep cache
E1 ready again -> reuse cache, show skills again
resume         -> create a new thread cache and discover again

The cache key is the full SelectedCapabilityRoot. Availability does not invalidate it; dropping the extension's thread state does.

The step supplies the ready selected roots directly. They do not have to be turn environments:

turn environment: laptop
selected root:    worker:/plugins/lint-fix

worker ready -> lint-fix skills are visible

What changes

• Keeps executor skill catalogs in the existing skills extension.
• Passes the roots resolved as ready for the step into World State contributors.
• Loads each ready selected root at most once per thread.
• Contributes the executor catalog as the skills World State section.
• Uses the exact step catalog for explicit skill selection and body reads.
• Leaves host and orchestrator skill behavior where it already lives.

Taking a step snapshot itself does not add an RPC. Executor filesystem calls happen only on the first discovery of a stable root for that thread.

What does not change

• No filesystem watcher or content-based invalidation.
• No retry/generation framework.
• No skill runtime migration into core.
• No general rewrite of the skills extension.

Stack

1. Extension-owned World State sections.
2. This PR: project cached executor skills through World State.
3. Pin one MCP runtime to each model step.
4. Project selected MCP/app/connector metadata by environment availability.
5. One end-to-end integration scenario.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: f55c074df7

ℹ️ 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".