Merge PR #3: docs: add last site update marker

Apply the same concurrency pattern used in the python-project-template:
- cancel-in-progress: false prevents the shared act_runner from
  cancelling in-progress steps when a new push lands
- pull_request trigger ensures PRs are validated before merge
- workflow_dispatch allows manual re-runs

.gitea/workflows/ci-cd.yaml

@@ -3,9 +3,20 @@ name: CI/CD Pipeline
 on:
   push:
     branches: [main]
+  pull_request:
+    branches: [main]
+  workflow_dispatch:
+
+# Serialise runs on the shared act_runner: prevents two simultaneous runs from
+# cancelling each other's in-progress steps (observed in older portfolio runs).
+# See python-project-template-internal/.gitea/workflows/ci.yaml for the same
+# pattern with full context (runs 794 and 799).
+concurrency:
+  group: ci-${{ github.ref }}
+  cancel-in-progress: false
 
 jobs:
-  deploy:
+  build:
     name: Build & Deploy
     runs-on: ubuntu-latest
     steps:

src/pages/about.astro

@@ -57,6 +57,12 @@ import Footer from '../components/layout/Footer.astro';
           I work full-time at KEO as Field Application Engineer, where I handle technical
           documentation, workflow automation, internal tools, and customer-facing support.
         </p>
+        <p class="text-text-secondary leading-relaxed mb-4">
+          <em class="text-text-tertiary text-sm">
+            Last site update: 2026-07-09 (build sha visible in the CI run that produced this
+            version of the page).
+          </em>
+        </p>
         <p class="text-text-secondary leading-relaxed mb-4">
           In parallel, I'm building <strong class="text-primary">WarrantyHub</strong> — a platform 
           for end users to manage warranties for their home products from one place.