Rebrand platform as FitmentOps

[armanvibecoding]

Summary

• Rebrands the standalone platform and repository as FitmentOps.
• Replaces the corrupted, duplicated legacy README with a bilingual landing page and separate, complete English and Turkish guides.
• Adds security, contribution, and pull-request documentation.
• Centralizes public brand/contact configuration and removes fabricated phone, address, company-age, inventory-size, and hiring claims.
• Updates browser metadata, SEO markers, email branding, JWT defaults, database name, startup scripts, package identity, solution name, and CI paths.
• Removes unused search-engine captures and an unreferenced image from the repository root.
• Makes iyzico signing-path validation deterministic across Windows and Linux and adds regression coverage for unsafe signing inputs.

Why

The previous repository still presented the identity, owner link, screenshots, contact details, and claims of the original prototype. Several README sections were duplicated and displayed corrupted Turkish encoding. The public identity no longer represented the substantially expanded commerce and operations system.

Impact

• Product/repository name becomes FitmentOps.
• The Visual Studio solution is now FitmentOps.sln.
• Local development database default becomes FitmentOpsDb.
• JWT defaults become FitmentOps.API / FitmentOps.Web; deployments should provide explicit issuer and audience values.
• Public contact fields remain hidden until VITE_SUPPORT_* values are configured.
• The contact form creates a local email draft and no longer fabricates a successful server submission.
• Internal AutoPartsStore.* namespaces remain unchanged to avoid a high-risk, cosmetic namespace migration.
• Documentation is published separately as README.en.md and README.tr.md, with README.md acting as the language entry point.

Validation

• .NET 9 Release build: 0 warnings, 0 errors.
• Targeted iyzico signing tests: 17 passed.
• Backend unit tests: 357 passed.
• Real-host integration tests: 10 passed.
• dotnet format --verify-no-changes: passed.
• EF pending model changes: none.
• Frontend ESLint: passed.
• Frontend tests: 9 passed.
• Frontend production build: passed.
• npm audit: 0 vulnerabilities.
• Repository secret scan: passed.
• Workflow YAML and JSON parsing: passed.
• Legacy identity scan and staged diff checks: passed.

Rollout

Update bookmarks and clone URLs to https://github.com/armanvibecoding/FitmentOps. Existing GitHub links redirect after the repository rename. Deployed environments should explicitly configure JWT, database, public-origin, and contact settings.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 4cbda024e3

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Keep JWT issuer/audience fallbacks aligned

When a deployment or test host provides only Jwt:Key and relies on the issuer/audience fallbacks, the bearer middleware now validates FitmentOps.API / FitmentOps.Web, but JwtService.GenerateToken still falls back to AutoPartsStore / AutoPartsStoreUsers (Services/JwtService.cs). In that configuration, login/register can return successfully signed tokens that every protected endpoint rejects with 401, so the new defaults should be updated in both places or centralized.

Useful? React with 👍 / 👎.