Plugin tools declare ctx.ask as Promise<void> and await it, but the
framework ask is an Effect. The fromPlugin bridge wired ask straight
through as `(req) => toolCtx.ask(req)`, so the returned Effect was
awaited unexecuted: the permission prompt was a silent no-op and the
tool ran as if every request had been granted.

Run the framework ask through EffectBridge.make().promise() so an
awaited ctx.ask(...) actually executes the permission flow with the
Instance/Workspace context intact, and update the plugin ToolContext
contract to Promise<void> (dropping the now-unused Effect import).

Regression test: a .opencode/tool plugin whose execute awaits ctx.ask
now observes the framework Effect run exactly once (red before the
bridge, green after).

Semantic port of anomalyco/opencode#28217.

…Bridge

Plugin tools declare ctx.ask as Promise<void> and ctx.metadata as void, but
the framework versions are Effects. The fromPlugin bridge spread toolCtx
straight through, so the returned Effects were never executed: an awaited
ctx.ask(...) resolved an inert Effect (permission prompt a silent no-op, tool
ran as if granted) and ctx.metadata(...) discarded its Effect (title/metadata
never applied).

Bridge both through EffectBridge.make().promise(): ask is awaited, metadata is
fire-and-forget (void contract) with a warn on failure. Update the plugin
ToolContext ask contract to Promise<void> (dropping the now-unused Effect
import); metadata was already typed void.

Regression test: a .opencode/tool plugin whose execute awaits ctx.ask and calls
ctx.metadata now observes both framework Effects run exactly once (0 before the
bridge, 1 after).

Semantic port of anomalyco/opencode#28217 (ctx.metadata gap caught in review).

…Bridge (#1127)

Plugin tools declare ctx.ask as Promise<void> and ctx.metadata as void, but the
framework versions are Effects. The fromPlugin bridge spread toolCtx straight
through, so the returned Effects were never executed: an awaited ctx.ask(...)
resolved an inert Effect (permission prompt a silent no-op, tool ran as if
granted) and ctx.metadata(...) discarded its Effect (title/metadata never
applied).

Bridge both through EffectBridge.make().promise(): ask is awaited, metadata is
fire-and-forget (void contract) with a warn on failure. Update the plugin
ToolContext ask contract to Promise<void> (dropping the now-unused Effect
import); metadata was already typed void.

Regression test: a .opencode/tool plugin whose execute awaits ctx.ask and calls
ctx.metadata now observes both framework Effects run exactly once (0 before the
bridge, 1 after).

Semantic port of anomalyco/opencode#28217. The ctx.metadata half (same bug
class, missed upstream) was caught in review. Known follow-up: the bridged ask
is not tied to toolCtx.abort, matching upstream's abort-naive bridge (Codex P2).

…ffect (anomalyco#28217)

…ffect (anomalyco#28217)

…ffect (anomalyco#28217)