chore: rename Stirling-Image to ashim across entire codebase

Complete rebrand from Stirling-Image to ashim following the project
move to https://github.com/ashim-hq/ashim.

Changes across 117 files:
- Package scope: @stirling-image/* → @ashim/*
- GitHub URLs: stirling-image/stirling-image → ashim-hq/ashim
- Docker Hub: stirlingimage/stirling-image → ashimhq/ashim
- GitHub Pages: stirling-image.github.io → ashim-hq.github.io
- All branding text: "Stirling Image" → "ashim"
- Docker service/volumes/user: stirling → ashim
- Database: stirling.db → ashim.db
- localStorage keys: stirling-token → ashim-token
- Environment variables: STIRLING_GPU → ASHIM_GPU
- Python cache dirs: .cache/stirling-image → .cache/ashim
- SVG filter IDs, test prefixes, and all other references

apps/web/src/pages/privacy-policy-page.tsx

@@ -20,7 +20,7 @@ export function PrivacyPolicyPage() {
           <section>
             <h2 className="text-lg font-semibold text-foreground mb-2">Overview</h2>
             <p>
-              Stirling Image is a self-hosted, open-source image processing application. Your
+              ashim is a self-hosted, open-source image processing application. Your
               instance is operated and controlled entirely by whoever deployed it. This policy
               describes how the software itself handles your data.
             </p>
@@ -29,7 +29,7 @@ export function PrivacyPolicyPage() {
           <section>
             <h2 className="text-lg font-semibold text-foreground mb-2">Local Processing</h2>
             <p>
-              All image processing happens entirely on the server where Stirling Image is deployed.
+              All image processing happens entirely on the server where ashim is deployed.
               Your images are never sent to external services or third-party APIs. When you upload
               an image for processing, it is handled in memory or in temporary storage on the host
               machine and is not retained after the operation completes.
@@ -39,8 +39,8 @@ export function PrivacyPolicyPage() {
           <section>
             <h2 className="text-lg font-semibold text-foreground mb-2">No Tracking or Analytics</h2>
             <p>
-              Stirling Image does not include any telemetry, analytics, or tracking. No data is
-              collected about your usage patterns, and no information is sent to Stirling Image
+              ashim does not include any telemetry, analytics, or tracking. No data is
+              collected about your usage patterns, and no information is sent to ashim
               developers or any third party. There are no cookies used for tracking purposes.
             </p>
           </section>
@@ -58,7 +58,7 @@ export function PrivacyPolicyPage() {
           <section>
             <h2 className="text-lg font-semibold text-foreground mb-2">No Third-Party Services</h2>
             <p>
-              Stirling Image does not integrate with or send data to any external services.
+              ashim does not integrate with or send data to any external services.
               AI-powered features (background removal, upscaling, OCR) run locally using bundled
               models. No cloud APIs are involved.
             </p>
@@ -67,7 +67,7 @@ export function PrivacyPolicyPage() {
           <section>
             <h2 className="text-lg font-semibold text-foreground mb-2">Open Source</h2>
             <p>
-              Stirling Image is fully open source. You can audit the source code to verify these
+              ashim is fully open source. You can audit the source code to verify these
               claims at any time. Transparency is a core principle of this project.
             </p>
           </section>
@@ -75,7 +75,7 @@ export function PrivacyPolicyPage() {
           <section>
             <h2 className="text-lg font-semibold text-foreground mb-2">Your Control</h2>
             <p>
-              Because Stirling Image is self-hosted, the instance operator has full control over all
+              Because ashim is self-hosted, the instance operator has full control over all
               data. You can delete your data at any time by removing files from the server or
               deleting the database. No data exists outside of your infrastructure.
             </p>