0bfc85a4f2
Introduced Newtonsoft.Json-backed persistence. Improved backing-store reliability and serialization across the caching stack. Improved networking security posture. Key changes: - Add new GameCult.Caching.NewtonsoftJson project with SingleFile/MultiFile backing stores and polymorphic known-type envelopes. - Add MessagePack helper serialization (DatabaseEntrySerialization) and update MessagePack backing stores to use the shared options/resolver; add DatabaseLink formatter and generator/analyzer docs. - Update CultLib.sln to include the new projects and new caching tests project. - Improve CultCache persistence behavior: track pending store operations, wait for operations on PullAll, and centralize async push handling with error logging. - Harden file I/O in multi-file/single-file stores: atomic temp-file writes, safe Replace/Move semantics, rename-safe deletes, and improved file-watcher subscription and debounce disposal. - Add README files and documentation for several subprojects and packaging projects. These changes add JSON persistence support, improve serialization consistency, and make on-disk operations more robust and observable.
11 lines
766 B
Markdown
11 lines
766 B
Markdown
# AGENTS.md
|
|
|
|
## Repository Guidance
|
|
|
|
- Refrain from commenting on current changes in README files unless the user explicitly asks for that commentary.
|
|
- Treat clean API surface as a core project priority.
|
|
- Favor developer ergonomics in public APIs, examples, naming, defaults, and documentation.
|
|
- Prefer interfaces and behaviors that are predictable, easy to discover, and easy to integrate correctly.
|
|
- Keep public abstractions small and coherent; avoid exposing internal workflow complexity through the API when it can be encapsulated.
|
|
- When adding documentation or examples, optimize for practical usage by downstream developers.
|
|
- When proposing or implementing changes, consider how they affect usability, readability, and maintenance for library consumers.
|