…parent

…g, delivery errors)

…integration test

The sender-echo markers duplicated information already shown by the
message tool call itself (✉ Sent to parent / ✉ Replied to subagent sat
right under the visible tool call), and the subagent's "Reply from
parent" marker was written twice — once by the parent's reply branch and
again by the subagent's own send path.

Keep only the incoming markers: the parent sees "✉ Message from
subagent", the recipient subagent sees "✉ Reply from parent", each once.
Drop the now-unused marker direction field.

…r before adding inbox markers

…tree-cap

…dation, fire-and-forget only

…skip-on-cancel)

…ow + gating verification

…ranch comment

experimentalS2S runtime flag; s2s_inbox/s2s_token/s2s_allow tables (hand-written migration + Drizzle s2s.sql.ts mirror so fresh-DB CREATE and upgrade paths agree); session_slug_unique migration neutralized to DROP INDEX (slugs are not unique). Store is one statement per method: atomic single-winner claims via UPDATE…RETURNING with drained_at IS NULL / accepted_by IS NULL guards, TTL enforced in the claimToken WHERE clause, and deleteInbox so a delivered row is hard-deleted (distinct from a merely-claimed crashed row). S2SCapsule v1 envelope with forward/back-compat serde and optional sender_name. UUIDv7 generator.

…up wiring

Per-instance wake poller (C′) lazily forked from SessionPrompt.loop via attach so it captures the live fiber's InstanceRef; runLoop turn-boundary drain (D) of s2s_inbox in-context; 60s reaper that reopens ONLY crashed claims (delivered rows are deleted). LayerNode.group exposes only DIRECT children, so S2SStore/Messaging/SessionStatus are spliced as direct members of every prompt-serving group (app httpapi + control-plane workspace) — this is what made cross-process delivery actually work. marker.ts: shared Marker.render + escapeAttr (escapes " ' for untrusted attribute values so a peer cannot break out of the <external-context> name=/session= attributes); escape() for element content/visible markers. Slug-decoupled: Messaging.enqueue lazily inits the inbox queue and registerSlug is dropped from the loop, so s2s rides session_id only and the slug registry stays coordinator-messaging-owned. s2s frames carry the sender session name + addressable session_id.

s2s tool (invite/accept/msg/leave/relay) gated behind experimentalS2S: single-use 10-min invite tokens, durable bidirectional s2s_allow consent, peers addressed by globally-unique session_id (accept reports the inviter's id). Same-process sends hit the in-process inbox; cross-process persist to s2s_inbox for the recipient's poller. Outbound 50/hr is a SOFT per-process throttle (documented as such in code + s2s.txt); the durable cross-process bound is the recipient INBOX_CAP (exact now that delivered rows are deleted). Registry wires S2SStore into ToolRegistry; message tool gains peer-slug send (message_allow). TUI renders the ✉ inbox marker (session name + id) and the session-list surface.

…s on session deletion

…eted events for comms dashboard

(cherry picked from commit 939ffdd61748fed5ae41429be9d0b80e9ea3992a)

- Rewrite LayerNode.make positional→object form in poller/store
- Add defaultLayer re-exports (raw layer) to 37 modules
- Export layer variable for modules used via .layer access
- Rewrite coordinator-messaging + s2s tests to LayerNode.group pattern
- Switch tests to testEffectShared for Database memoMap sharing
- Add NodePath to runLoopInfra for CrossSpawnSpawner deps
- Create task-event.ts schema + manifest registration
- Regenerate SDK types (task.completed, messaging.peer_sent, s2s.delivered)
- Fix topology-repro.test.ts positional LayerNode.make + buildLayer→compile

…ator suites

SessionProjector.node added to the s2s/coordinator runLoop harnesses (session
readback needs projection at current dev), the reaper harness gets an explicit
EventV2 layer, the poller runLoop shares the file-level :memory: database via
node replacement, and the fork-fiber-sensitive suites (poller, coordinator
runLoop) build per-test layers (testEffect) instead of a shared memoMap build
so forked poller/drain fibers see the same instances as the test assertions.

Drops the defaultLayer = layer re-exports from 28 modules nothing consumes;
the 8 that remain (Agent, Config, Session, Truncate, Messaging, S2SStore,
EventV2Bridge, CrossSpawnSpawner) back the three s2s test harnesses that still
compose with Layer.mergeAll. Follow-up: convert those harnesses to LayerNode
and delete the bridge entirely.

Wrap completedPayload assembly in Effect.exit so any defect
during session/message reads falls back to the base payload
instead of killing the publish path. Use optional chaining and
nullish defaults for token/cost field access to tolerate missing
or malformed assistant rows. Rewrite test to observe the actual
published event via Deferred + listen instead of relying on
message persistence alone.