This repository stays lightweight. Full AI governance policy lives in ../turbo-cloud.
- Keep plugin composition and service registration in
TurboSamplePlugin/TurboSamplePlugin.cs. - Keep startup orchestration in
TurboSamplePlugin/SamplePluginService.cs. - Add protocol changes under:
TurboSamplePlugin/Revision/<revision>/Parsers/<Domain>/TurboSamplePlugin/Revision/<revision>/Serializers/<Domain>/
- Treat
TurboSamplePlugin/Revision/README.mdas the local source of truth for revision layout. - Do not move or duplicate revision parsers/serializers into
turbo-cloud. - For handler/grain architecture decisions (for example extended profile flow), follow:
../turbo-cloud/AGENTS.md../turbo-cloud/CONTEXT.md
- For task recipes and portable prompt contract, use
../turbo-cloud/AGENTS.mdas canonical. - Keep
PacketHandlersandEventHandlersfocused on message/event flow. - Keep database concerns in
TurboSamplePlugin/Database/.
When adding packet mappings in TurboSamplePlugin/Revision/Revision20260112:
- Update
TurboSamplePlugin/Revision/Revision20260112/Headers.cs:- add/update incoming
MessageEventid constants - add/update outgoing
MessageComposerid constants
- add/update incoming
- Add parser class under:
TurboSamplePlugin/Revision/Revision20260112/Parsers/<Domain>/*MessageParser.cs
- Add serializer class under:
TurboSamplePlugin/Revision/Revision20260112/Serializers/<Domain>/*MessageComposerSerializer.cs
- Register mappings in:
TurboSamplePlugin/Revision/Revision20260112/Revision20260112.cs- incoming:
Parsersdictionary withMessageEventkey - outgoing:
Serializersdictionary with composer type +MessageComposerid
- Ensure the required
usingdirectives are present inRevision20260112.csfor new parser/serializer namespaces.
dotnet build TurboSamplePlugin/TurboSamplePlugin.csproj -t:TurboSamplePluginFastCheck
dotnet build TurboSamplePlugin/TurboSamplePlugin.csproj -t:TurboSamplePluginQualityGate