Skip to content

fix(entity-chat): admit chat via frozen InputCommand envelope - #6

Merged
Go1c merged 1 commit into
mainfrom
feat/c1-envelope-harness
Sep 1, 2026
Merged

fix(entity-chat): admit chat via frozen InputCommand envelope#6
Go1c merged 1 commit into
mainfrom
feat/c1-envelope-harness

Conversation

@Go1c

@Go1c Go1c commented Sep 1, 2026

Copy link
Copy Markdown
Contributor

Summary

101-entity C# harness now admits frozen lumio.gameplay-envelope.v1 InputCommand (chat.input + LumioBinV1 payload + payloadSha256) instead of raw strings. ChatInput stays text-only after host decode. hello-wire-v1 is not extended.

Independent review Approved P0=0 P1=0 (P2 verifier does not recompute digest; UTF-8 GetString is lenient).

Changes

  • InputCommandEnvelope encode/decode
  • GameRoomHost.AdmitChatInput(connectionId, InputCommandEnvelope)
  • Suite + acceptance tests construct envelopes
  • verify-evidence.mjs requires scenario 6 envelope fields
  • Knowledge: entity-chat-harness.md

Test plan

  • node .spec/tools/spec-lint.mjs → OK
  • node --test integration/entity-chat/verify-evidence.mjs → 11/11
  • dotnet exec ServerGameplay.Tests 33/33 ×2
  • launcher two rounds SUCCESS, census 101; scenario 6 mappingId=chat.input payloadSha256 independently recomputed

Known gaps

  • World-level ChatRoomWorld.AdmitChatInput(ulong, ChatInput) remains text-only (C-1 fieldSemantics).
  • lumio-mvp-host FullGraph is still not the 101-entity path.

GameRoomHost and the 101-entity suite consume lumio.gameplay-envelope.v1
chat.input CommandBlocks (mappingId, LumioBinV1 payload, payloadSha256).
ChatInput stays text-only after decode.
@Go1c
Go1c merged commit 0604701 into main Sep 1, 2026
1 check passed
@Go1c
Go1c deleted the feat/c1-envelope-harness branch September 1, 2026 22:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant