Loretta
affa85e5c5
Refactor docs: topic folders, TOON, XCUT, protocol sync - Migrated all topic documentation into dedicated folders with canonical `README.md`, `ISSUES.md`, and `TODO.md` per topic (e.g., `LOGGING/`, `SIGNALR/`, `BINARY/`, `TOON/`). - Added comprehensive TOON serializer documentation: design, format, options, attributes, inference, issues, and TODOs. - Introduced `XCUT` folder for cross-cutting issues and TODOs, with canonical entries and topic cross-references. - Updated all references and navigation to use new folder-based doc paths; fixed links and clarified doc structure. - Enhanced AI agent protocol: enforce session skill preloading, `[LOADED_DOCS: ...]` short-name prefix, and mandatory `docs-check` skill for doc/code sync. - Updated `.csproj` to include all `README.md` files for IDE visibility. - Improved and clarified SignalR, grid, and project-level documentation. - Minor code/test tweaks and doc content corrections for consistency. |
||
|---|---|---|
| .. | ||
| SIGNALR | ||
| README.md | ||
README.md
AyCode.Services.Server documentation
Topic documentation for the AyCode.Services.Server project (Layer 0, server-side services).
Topics
SIGNALR/— Server-side SignalR (hub base + data source pattern)
Navigation
Per the AI Agent Core Protocol (folder navigation rule), start from this README when browsing docs/. Each topic folder has its own README.md with the main content, plus optional TOPIC_ISSUES.md (known issues) and TOPIC_TODO.md (planned work).
See also
- Client-side SignalR:
../../AyCode.Services/docs/SIGNALR/README.md - Binary-over-SignalR wire format:
../../AyCode.Services/docs/SIGNALR_BINARY_PROTOCOL/README.md