Present DryCar as a focused product case study

[msaitdogmus]

What changed

• rewrote the repository as a focused DryCar Care product case study
• replaced dated screenshots with ten current desktop and mobile captures from production
• documented the architecture, security model, threat controls, and verified test results
• removed the complete reconstructed production source tree from the public repository
• added three small, buildable samples for booking capacity, ASP.NET Core security, and face liveness
• replaced the old application build workflow with a portfolio integrity workflow

Why

The repository previously exposed far more reconstructed implementation detail than a public portfolio needs, while the product story was difficult to understand quickly. This change makes the work legible to an engineering or hiring team without presenting the public repository as the production source of truth.

Impact

• visitors can understand the product, decisions, security posture, and operating flows from the README
• current visuals show the redesigned public, customer, and administration experiences
• production secrets and complete business implementation remain outside the public repository
• representative samples still demonstrate coding style and core engineering choices

Validation

• representative C# samples build on .NET 8 with 0 warnings and 0 errors
• Python sample passes syntax compilation
• all local Markdown and HTML image links resolve
• all ten PNG screenshots pass signature and dimension checks
• staged-content secret pattern scan passes
• live regression documented as 20/20 public viewport checks and 5/5 authenticated admin routes
• temporary administrator and customer test records were removed after capture