Mesh as gameplay (communication delays)

name: Mesh Gameplay Delays overview: Wire the Mesh into captain/campaign mechanics so network intel and commerce notices arrive only after FTL propagation delay, while same-system (berth) access stays immediate — with mailbox sync, payloads, and a bridge inbox. todos:

• id: payload

content: Add Subject/Body/Topic on MeshPacket + Commerce.Spot feed; publish helpers status: completed

• id: mailbox-sync

content: MeshMailboxSync each hour from ship/player current system status: completed

• id: gameplay-pulse

content: "MeshGameplayPulse: daily spot digests, escrow notices, Emergency from drama" status: completed

• id: job-board-delay

content: Network ListSpot from mesh digests; berth stays live BuildSpot status: completed

• id: bridge-cli-docs-tests

content: Captain UI/CLI inbox surface; gameplay docs; delay/sync unit tests status: completed isProject: false

Design rule

Same system (berth / co-located node)  → live / push / force Emergency now
Other systems                          → mesh hop delay, then visible / pull

This extends the existing CCA glass rule (gameplay.md): see the network, accept only at dock — but network sight itself is delayed by the mesh.

flowchart LR
  origin[Origin_system_publish]
  drones[Pulse_drones_FTL_hops]
  node[Local_node_cache]
  inbox[Captain_feed_inbox_and_mailbox]
  board[Network_spot_board]
  origin --> drones --> node --> inbox --> board
  berth[Berth_live_BuildSpot] --> boardLocal[Berth_spot_board]

1. Minimal packet payload

Extend `MeshPacket`:

• string Subject (short)
• string Body (compact text; spot digests are line-oriented)
• string Topic (stable kind: spot-digest, escrow, emergency, …)

PublishEngine.PublishPulse / helpers accept subject/body/topic. No crypto, no JSON schema package — plain text lines for digests.

Add feed id MeshFeedId.CommerceSpot (Commerce.Spot). Keep News.* and Emergency.

2. Mailbox location sync (delays only matter if you move)

Each campaign hour in `CampaignRunner.PulseDaysAsync` before MeshPulse.TickHour:

• Resolve Calypso / tramp current system from shipment CurrentHubId or berth (`LiveSession.CurrentHubSystemId`)
• MailboxEngine.Move for ship:{RegistryName} and player person:{PlayerFlavorId} to that MeshNodeId
• Firms/households/things stay on seeded home nodes (v1)

New helper: Universe/Mesh/Sins/MeshMailboxSync.cs.

3. Publish gameplay traffic — `MeshGameplayPulse`

New file Universe/Mesh/Sins/MeshGameplayPulse.cs, called once per day from PulseDaysAsync (after day pulses / escrow), not every hour (keeps flood volume sane).

Wire escrow hooks in `EscrowBook` via a small callback or by scanning open/release in MeshGameplayPulse from milestones / escrow counters already logged — prefer publishing at open/release sites inside EscrowBook when Ids.Mesh is available (pass mesh by ref on TickDay or publish from runner after escrow tick using escrow events list).

Chosen approach: EscrowBook appends lightweight EscrowNotice records; MeshGameplayPulse.TickDay drains them and publishes identity packets from the carrier’s current system node (or Sol if unknown).

4. Network spot board reads mesh (the delay mechanic)

Change `CaptainJobBoard.ListSpot`:

• `berthOnly` / local board: keep live BuildSpot for currentSystemId only (same-system = no FTL delay).
• Network board: build candidates only from `Commerce.Spot` digests already in the captain’s feed inbox (person: or ship:ST Calypso) at the current mailbox node — parse Body lines into SpotCandidate. Accept still requires AtOrigin (dock act unchanged).

If no digests have arrived yet, network board is empty/thin (honest lag), not a silent fallback to omniscient BuildSpot.

Subscribe Calypso (person + ship) to Commerce.Spot at seed in `SeedMesh` / smoke path.

5. Captain bridge + CLI surface

• `CaptainBridgeModel`: add mesh lines — Emergency count, mailbox push count, last N inbox subjects (mailbox + feed), and note network intel is mesh-delayed.
• Existing Feed list can prepend Emergency / mesh notices (from inbox packets) ahead of milestone vox.
• `CaptainConsole` status: show mesh lag hint (mesh inbox N · emergency M · network digests K).

No new Avalonia control package — reuse scorecard / feed lines.

6. Docs + tests

• Update gameplay.md and mesh-and-communications.md: network intel delayed; berth live; escrow/Emergency via mesh.
• Unit tests:
• Spot digest published at Sol is not in Wolf inbox until hops complete; after delay, network parse yields candidates.
• Berth ListSpot still live without digest.
• Mailbox sync moves ship identity with system change → catch-up push.
• Escrow notice identity packet eventually mailboxed when co-located.

Explicit non-goals (this pass)

• Full MeshState in save files (seed→hour replay rebuilds mesh during --load)
• Ansible channel, postage cash, bulk archives, Limbo ceremony
• Intra-system radio mesh beyond co-location
• Replacing berth accept rules

Touch list (primary)

• Mesh kernel: ModelTypes / PublishEngine payload
• MeshMailboxSync, MeshGameplayPulse, escrow notice drain
• CaptainJobBoard, CampaignRunner, CampaignWorld seed subscriptions
• CaptainBridgeModel, CaptainConsole, docs, unit tests