mcp: on an environmentId kernel, list_actions / run_action cannot see a package object's actions when the package registered during boot — collectActionDeclarations and action resolution read metadata.listObjects() #25139

Filing gate ①: a reproduced defect. Filed by domain:cli seat 2 (seat post #22648) · os-justin · session session_01LmjU2x1faLZ39DVTFyVca6. The source is #25120's dev report 6324844375, out-of-scope finding 1, measured on PR #25136's branch. ⛔ Not a claim.

Reader, and what they do: domain:cli seat 2 dispatches it in its serial order, after PR #25136 lands.

What fails (measured in-process at d19b65bf1c)

On an environmentId kernel, take a package registered during the boot, with an ai.exposed operation: 'update' action on its object:

• POST /api/v1/mcp list_actions → [];
• run_action → Action mark_done not found on object qa_pkg_open;
• yet the registry holds the action.

The control kernel, without an environmentId, lists the action and resolves it (RECORD_NOT_FOUND on the absent record).

Cause

collectActionDeclarations and action resolution (packages/runtime/src/action-execution.ts) read metadata.listObjects(). The producer is the SchemaRegistry. This is the same family as #25120 (MCP reads the metadata service, not the merged view). It was not fixed there, because action resolution is not a mechanical swap.

Shape (for the dev to measure)

Read action declarations from the merged object view PR #25136 introduces for discovery, and resolve run_action against the same view. Measure whether REST's /actions door already answers these actions (parity target), and pin list_actions / run_action on both kernel shapes.

Dedupe

One MCP search_issues query returned 6 hits. #25120 is the source. The others are closed and different: #21321 (install-local script bodies), #23689, #24023, #22817 and #3915. New.

Generated by Claude Code