docs: strengthen ERP architecture and recruiter-facing evidence

[mkarson1997]

What changed

• add a system architecture document for the WPF/MVVM/service/EF Core/SQLite boundaries
• document localization/RTL and language-aware company-settings migration
• document the defensive backup/restore and startup-recovery path
• add recruiter-facing engineering proof points and architecture/security controls to the README
• keep the screenshots section honest as a placeholder until real captures are committed
• add explicit standalone-desktop non-claims instead of implying a server/SaaS security model

Why

KARZOUN ERP already demonstrates substantial product engineering, localization and local-data recovery behavior. This makes the engineering evidence legible quickly while keeping the current single-machine scope explicit.

No runtime behavior changes.

Summary by Sourcery

Document KARZOUN ERP’s architecture, recovery safeguards, engineering evidence, and standalone product boundaries without changing runtime behavior.

New Features:

• Add recruiter-facing engineering proof points covering architecture, localization, recovery, release integrity, verification, and supply-chain practices.
• Add a dedicated architecture document describing application boundaries, localization-aware settings migration, backup/recovery safety, and standalone trust boundaries.

Enhancements:

• Clarify the product’s single-machine deployment model and explicitly document capabilities it does not claim.
• Improve README structure and accuracy, including honest screenshot placeholder wording and concise feature descriptions.

CI:

• Document Windows CI build verification and CodeQL security analysis in the project’s engineering overview.

Documentation:

• Expand README documentation with architecture, engineering evidence, recovery behavior, release verification, and explicit non-claims.

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[Copilot]

Copilot was unable to review this pull request because the user who requested the review has reached their quota limit.

[sourcery-ai]

Sorry @mkarson1997, you've used your own review budget of 250,000 diff characters for the last 7 days.

You can request another review in 2 days and 3 hours by commenting @sourcery-ai review. Upgrade to get a review now.

[sourcery-ai]

Reviewer's Guide

This documentation-only PR makes the ERP’s architecture, localization and migration model, defensive local-data recovery path, release controls, and standalone security boundaries easier to evaluate while explicitly avoiding claims beyond the current single-machine product scope.

Sequence diagram for defensive database restore

sequenceDiagram
    actor User
    participant App as Application
    participant Backup as Backup / Restore
    participant Temp as Temporary SQLite copy
    participant DB as Live SQLite database
    participant Safety as Emergency backup

    User->>App: Select restore candidate
    App->>Backup: Restore
    Backup->>Backup: Validate source
    Backup->>Temp: Migrate temporary copy
    Backup->>Temp: Validate migrated copy
    Backup->>Safety: Create emergency backup
    Backup->>DB: Apply verified replacement
    alt application fails
        Backup->>DB: Roll back from emergency backup
    end

Loading

Entity relationship diagram for localized company settings

erDiagram
    COMPANY ||--o{ COMPANY_LOCALIZED_SETTINGS : has
    COMPANY {
        int CompanyId PK
    }
    COMPANY_LOCALIZED_SETTINGS {
        int CompanyId FK
        string LanguageCode
        string DocumentDefaults
    }

Loading

File-Level Changes

Change	Details	Files
Adds a documented architecture and local trust model for the standalone WPF application.	Describes WPF/MVVM, service, EF Core, SQLite, document, localization, and backup/recovery boundaries. Documents the request/persistence flow and clarifies that views remain separate from persistence and recovery concerns. States explicit non-claims for multi-user, server-side authorization, cloud synchronization, certification, and disaster recovery.	docs/ARCHITECTURE.md README.md
Makes localization and language-aware company configuration behavior legible to reviewers and users.	Documents English, Turkish, and Arabic resource dictionaries with Arabic RTL behavior. Explains per-company/per-language document settings and uniqueness constraints. Documents startup migration that preserves older shared company settings.	docs/ARCHITECTURE.md README.md
Documents defensive database backup, restore, migration, and startup-recovery behavior.	Describes validation before and after temporary-copy migration. Documents emergency backup, replacement, rollback, and preservation of corrupted databases during startup recovery.	docs/ARCHITECTURE.md README.md
Strengthens README engineering evidence and release/security transparency without changing runtime behavior.	Adds CI, CodeQL, and release badges plus recruiter-facing proof points for architecture, persistence, recovery, documents, verification, and supply-chain hygiene. Adds an architecture overview linking to the detailed document. Keeps screenshots explicitly marked as unavailable until real captures are committed. Clarifies standalone deployment, local data location, checksum-backed releases, and current scope boundaries.	README.md

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.