Skip to content

SuperviseOptions has no peerMail passthrough — the mailbox shipped, the seam did not #911

Description

@drewstone

createPeerMailbox and peerMailTools are exported and reachable, and peerMail is a field on serveCoordinationMcp/CoordinationToolsOptions — but SuperviseOptions (48 fields) has no way to enable it, so a supervise() caller cannot turn on the peer mail its own workers already have tool descriptions for.

Measured effect in discovery-lab: the local stand-in (tools/mail.mjs) carries a recorded retirement condition — 'retires when the lab's installed runtime carries capability mail'. The capability now exists; the seam does not; the stand-in cannot retire. Found by the 2026-08-20 fork-ratio audit (discovery-lab reports/fork-ratio-audit-2026-08-20.md).

Proposal: a peerMail option on SuperviseOptions forwarded to the coordination server, same shape as CoordinationToolsOptions.peerMail.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions