docs(examples): add the CMS proof-of-concept dogfooding artifact

A WordPress-inspired CMS whose entire backend is PiCloud Rhai scripts
deployed with pic apply, plus a SvelteKit frontend. Built to dogfood the
project tool, CLI, and SDK; exercises docs/kv/files/users, docs+queue+cron
+pubsub triggers, the transactional-outbox notification chain, a docs
before-interceptor, set_if CAS, SSE, per-app CORS, env overlays, and a
durable Workflow (validate -> enrich || seo -> publish -> finalize) started
with workflow::start and polled with workflow::run_status, visualized live
with Svelte Flow.

FINDINGS.md / SECURITY.md capture every gap, surprise, and security issue
found (each tagged [PiCloud] vs [CMS]); the platform fixes for the
actionable ones ship in the preceding commit.

Also folds in the read-only `pic` allowlist entries added to
.claude/settings.json during the session (fewer-permission-prompts).

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

examples/cms-poc/frontend/vite.config.ts

@@ -0,0 +1,23 @@
+import { sveltekit } from '@sveltejs/kit/vite';
+import { defineConfig } from 'vite';
+
+// The browser calls same-origin /cms/* on :5173; Vite proxies to the PiCloud
+// backend on :8081. This sidesteps PiCloud's lack of CORS (FINDINGS F-030) and
+// avoids CORS preflight entirely (the request is same-origin to the browser).
+export default defineConfig({
+  plugins: [sveltekit()],
+  server: {
+    port: 5173,
+    proxy: {
+      '/cms': {
+        target: 'http://localhost:8081',
+        changeOrigin: true
+      },
+      // SSE realtime stream (live comments)
+      '/realtime': {
+        target: 'http://localhost:8081',
+        changeOrigin: true
+      }
+    }
+  }
+});