Project documentation

This section is for people working on CStructSharp itself. If you only want to use the library, begin with the library guides.

New contributors should read these pages in order:

1. Project overview explains what belongs in the core library and what does not.
2. Contributor setup prepares the SDK, restores local tools, and establishes a clean test baseline.
3. Repository map shows which project owns each kind of change.
4. Architecture follows a layout from source text to a read, write, or update operation.
5. Contributing workflow explains the fail-first change loop and review expectations.

Keep these reference pages nearby:

• Dependencies explains which packages reach library users and which stay in build/test tooling.
• Building gives core-only, non-Web, documentation, and package commands.
• Testing explains the purpose of each test and quality layer.
• Debugging gives a repeatable path for SDK, layout, byte, fuzz, coverage, and mutation failures.
• Release process separates candidate validation from publishing.
• Documentation deployment and documentation maintenance cover the site.
• Traceability codes explains the LANG-nn/QA-nn tags the contracts carry.

Routine development uses CStructSharp.NonWeb.sln. The WebAssembly adapter and browser apps are optional and are tested together only during final integration, because rebuilding them for every core or documentation change adds substantial time without improving those focused checks.