Contributing

Workflow

1. Discuss or track larger changes before massive refactors (issue / maintainer channel—follow repo norms).
2. Branch from the integration branch your team uses (main / develop).
3. Keep PRs focused—documentation + behavior should match; avoid unrelated formatting sweeps.
4. Run dotnet build and relevant dotnet test before push.

Documentation duty

When you change behavior visible to users or alter bootstrap/module contracts, update:

• User docs under docs/users/ when UX changes.
• Developer docs under docs/developers/architecture/ when registration flow, storage, or AI pipeline semantics shift.

Review expectations

• Layering: no new Infrastructure references from Core.
• Modules: prefer IModule extension over growing Bootstrapper conditionals.

See Coding standards and repository .cursor/rules/coding-standard.mdc.