Initial commit: plan, spec, tickets and dashboard skill templates

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

rpa-dashboard-ai/templates/reference/web/index.html

@@ -0,0 +1,35 @@
+<!doctype html>
+<html lang="en">
+  <head>
+    <meta charset="UTF-8" />
+    <meta name="viewport" content="width=device-width, initial-scale=1.0" />
+    <link rel="icon" type="image/png" href="/logo-mark.png" />
+    <!--
+      Two webfonts, and only for the sign-in screen — Sora for its display type
+      (brand name, headline, button) and IBM Plex Sans for its body. Both are
+      carried over from the approved login mockup, which is the whole reason
+      they are here: the screen is meant to render identically to it.
+
+      The INTERFACE behind sign-in stays on the system stack, which is a
+      documented density decision for 11-13px data-dense lists, where a webfont
+      costs a network dependency to look almost identical to Segoe UI (see
+      DESIGN.md Typography). Neither family is set on `body`.
+
+      `display=swap` plus the full local fallback in each `.sb-login` rule is
+      what makes this safe on an internal network: if fonts.googleapis.com is
+      blocked the sign-in screen falls back to the system stack and every other
+      surface never wanted a webfont in the first place.
+    -->
+    <link rel="preconnect" href="https://fonts.googleapis.com" />
+    <link rel="preconnect" href="https://fonts.gstatic.com" crossorigin />
+    <link
+      href="https://fonts.googleapis.com/css2?family=Sora:wght@600;700;800&family=IBM+Plex+Sans:wght@400;500;600&display=swap"
+      rel="stylesheet"
+    />
+    <title>Extraction and Automation Tool</title>
+  </head>
+  <body>
+    <div id="root"></div>
+    <script type="module" src="/src/main.tsx"></script>
+  </body>
+</html>