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.
.NET 9 core framework providing serialization (Binary, JSON, Toon), entity abstractions, database access, services, and shared utilities. Used as the foundation layer for AyCode applications.
LLM Context
Domain rules and key pitfalls live in a single file: .github/copilot-instructions.md
Tool
Auto-loaded
Action needed
GitHub Copilot
✅copilot-instructions.md
None
Claude Code
✅CLAUDE.md → references above
None
Cursor / Windsurf
✅README.md
Read copilot-instructions.md via @file
Solution-level docs in docs/:
Document
Topic
GLOSSARY.md
Core terminology reference
ARCHITECTURE.md
Solution layers, dependency rules
CONVENTIONS.md
Coding conventions
Project-level docs — each project's docs/ folder documents the code it defines:
Project
Documents
AyCode.Core/docs/
BINARY/ (README, FORMAT, FEATURES, OPTIONS, …), LOGGING/ (README, ISSUES, TODO)
Loretta
affa85e5c5