Add Cloudflare Workers deploy config and Gitea Actions workflow

Adds wrangler.toml (static asset deploy config for the portfolio
Worker) and .gitea/workflows/deploy.yml so pushes to main
automatically redeploy the site via wrangler-action.

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

.gitea/workflows/deploy.yml

@@ -0,0 +1,22 @@
+name: Deploy to Cloudflare Workers
+
+on:
+  push:
+    branches:
+      - main   # change if your default branch is named differently, e.g. master
+
+jobs:
+  deploy:
+    runs-on: ubuntu-latest
+    steps:
+      # Absolute https:// URLs are used here (rather than the bare
+      # `actions/checkout@v4` shorthand) so this works regardless of how this
+      # Gitea instance has DEFAULT_ACTIONS_URL configured.
+      - name: Checkout
+        uses: https://github.com/actions/checkout@v4
+
+      - name: Deploy
+        uses: https://github.com/cloudflare/wrangler-action@v3
+        with:
+          apiToken: ${{ secrets.CLOUDFLARE_API_TOKEN }}
+          accountId: ${{ secrets.CLOUDFLARE_ACCOUNT_ID }}

wrangler.toml

@@ -0,0 +1,15 @@
+# Cloudflare Workers config for the static portfolio site.
+# Replace `name` with your existing Worker's name in the Cloudflare dashboard
+# if one already exists at portfolio.ayushyamitabh.workers.dev — the name here
+# determines which Worker gets deployed to.
+name = "portfolio"
+
+# Set this to the date you first deploy; Wrangler uses it to pin runtime behavior.
+compatibility_date = "2026-09-17"
+
+# Serves every file in this directory as a static asset. Since index.html sits
+# at the repo root, "." works; move it into e.g. "./public" and update this if
+# you'd rather keep the repo root clean.
+[assets]
+directory = "."
+not_found_handling = "404-page"