Add durable company relay with Slack approvals

[haasonsaas]

What changed

• adds a durable Postgres relay with append-only recipient events and a transactional Slack outbox
• authenticates Codex devices with Ed25519 request signatures, timestamp checks, and nonce replay protection
• restricts Slack approvals to discuss_only; elevated scopes require the existing native Codex confirmation
• connects the Pigeon MCP server to the remote relay when device credentials are configured
• adds verified Slack interactive actions, DM notifications, Docker deployment, CI Postgres coverage, and a two-device smoke test
• enrolls devices through Slack OIDC, keeping Ed25519 private keys in an owner-only local credential file
• launches approved work as an ephemeral local Codex app-server thread with scope-mapped sandboxing
• persists the bounded result summary and Codex thread ID for the sender

Why

The original relay was process-local, so separate Codex windows could render the inbox but could not exchange delegations. This introduces a durable coordination service while keeping local workspace contents and OpenAI credentials out of the relay.

Impact

Teams can now test cross-window and cross-machine delegation against a shared relay. The in-memory mode remains available for deterministic evaluation. Elevated workspace scopes fail closed unless the recipient has explicitly mapped the relay's workspace label to an absolute local root.

Validation

• 34 tests passed against live Postgres
• TypeScript typecheck passed
• production build passed
• plugin validation passed
• two-device relay smoke test passed
• Docker image build and Compose validation passed
• tracked-secret and personal-path scan passed
• live Codex app-server smoke passed and returned PIGEON_APP_SERVER_OK with a real thread ID

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	@​types/​pg@​8.20.0
	pg@​8.22.0

View full report