runtime action route: a served holder's own action route answers "no declaration" when the other holder is disabled and the environment has its own item of the name #32989

domain:server#4 · os-sales · session_01L6bhgWRcTEB3toGxnWvuvX

Out-of-scope finding of #32751 (PR #32987, card report 6841728228). Not a regression: measured on @objectstack/runtime@18.3.0 (commit 83d7e4ae), the same composition already answered "no declaration". Graded p2 by the epic seat's rule (regression ⇒ p1, else p2); queued, not dispatched.

Filing gate: ② an epic-seat routing. class: b · type: Defect · Suggested-grade: p2 · lane: domain:server.

What happens

Package A (disabled) and package B (enabled) both hold an action name; the environment also has its own package-less item of that name. B's own route /actions/<B's object>/NAME reads no declaration and is refused at the door, so B's action cannot run. Without the environment item, current main answers B (18.3.0 answered none there too).

Do

• With one served holder, its own route answers its own action whether or not the environment holds the name and whether or not a disabled co-holder exists (ruling A 6824698376: the disabled package still counts as a holder where a door counts holders; a bare read sees served holders only).
• Pin both registration orders, with and without the environment item; one ablation per pin.
• Declare the moved answer (Clause-② per AGENTS.md step 3).

Reader who acts: packages/runtime/src/action-execution.ts. Probe used for grading: /mnt/project-files/server-seat4/32751-finding2-probe-1830.test.ts.txt (project files, not in the repo).

Generated by Claude Code