Add safe 1.4 flow

.dockerignore

@@ -0,0 +1,3 @@
+node_modules
+build
+*.log

.env.example

@@ -1,2 +1,4 @@
 VITE_WALLET_CONNECT_PROJECT_ID=YOUR_PROJECT_ID
-VITE_RELAYER_URL=https://auth.prove.email/
+VITE_RELAYER_URL=https://auth.prove.email/
+VITE_ALCHEMY_API_KEY=
+VITE_VAULT_PRIVATE_KEY=

.eslintrc.cjs

@@ -1,18 +1,62 @@
 module.exports = {
   root: true,
-  env: { browser: true, es2020: true },
+  env: { browser: true, es2020: true, node: true },
   extends: [
-    'eslint:recommended',
-    'plugin:@typescript-eslint/recommended',
-    'plugin:react-hooks/recommended',
+    "eslint:recommended",
+    "plugin:@typescript-eslint/recommended",
+    "plugin:react-hooks/recommended",
   ],
-  ignorePatterns: ['dist', '.eslintrc.cjs'],
-  parser: '@typescript-eslint/parser',
-  plugins: ['react-refresh'],
+  ignorePatterns: ["dist", ".eslintrc.cjs"],
+  parser: "@typescript-eslint/parser",
+  plugins: ["react-refresh", "import"],
   rules: {
-    'react-refresh/only-export-components': [
-      'warn',
+    "import/order": [
+      1,
+      {
+        groups: [
+          "external",
+          "builtin",
+          "internal",
+          "sibling",
+          "parent",
+          "index",
+        ],
+        pathGroups: [
+          {
+            pattern: "components",
+            group: "internal",
+          },
+          {
+            pattern: "common",
+            group: "internal",
+          },
+          {
+            pattern: "routes/ **",
+            group: "internal",
+          },
+          {
+            pattern: "assets/**",
+            group: "internal",
+            position: "after",
+          },
+        ],
+        pathGroupsExcludedImportTypes: ["internal"],
+        alphabetize: {
+          order: "asc",
+          caseInsensitive: true,
+        },
+      },
+    ],
+    "sort-imports": [
+      "error",
+      {
+        ignoreCase: true,
+        ignoreDeclarationSort: true,
+      },
+    ],
+    "react-refresh/only-export-components": [
+      "warn",
       { allowConstantExport: true },
     ],
   },
-}
+};

.github/pull_request_template.md

@@ -0,0 +1,30 @@
+## Description
+
+<!-- Please include a summary of the change and which issue is fixed. Also, list any dependencies that are required for this change. -->
+
+<!-- Fixes # (issue) -->
+
+## Type of change
+
+- [ ] Bug fix (non-breaking change which fixes an issue)
+- [ ] New feature (non-breaking change which adds functionality)
+- [ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
+- [ ] This change requires a documentation update
+
+## How Has This Been Tested?
+
+<!-- Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration -->
+
+- [ ] Test A
+- [ ] Test B
+
+## Checklist:
+
+- [ ] My code follows the style guidelines of this project
+- [ ] I have performed a self-review of my own code
+- [ ] I have commented my code, particularly in hard-to-understand areas
+- [ ] I have made corresponding changes to the documentation
+- [ ] My changes generate no new warnings
+- [ ] I have added tests that prove my fix is effective or that my feature works
+- [ ] New and existing unit tests pass locally with my changes
+- [ ] Any dependent changes have been merged and published in downstream modules

.github/workflows/build.yml

@@ -0,0 +1,18 @@
+name: Build Project
+
+on: [push, pull_request]
+
+jobs:
+  build:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up Node.js
+        uses: actions/setup-node@v2
+        with:
+          node-version: "22"
+          cache: "yarn"
+      - name: Install dependencies
+        run: yarn install
+      - name: Build
+        run: yarn build

.github/workflows/formatting.yml

@@ -0,0 +1,18 @@
+name: Code Formatting Check
+
+on: [push, pull_request]
+
+jobs:
+  formatting:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up Node.js
+        uses: actions/setup-node@v2
+        with:
+          node-version: "22"
+          cache: "yarn"
+      - name: Install Prettier
+        run: yarn add --dev prettier
+      - name: Check code formatting
+        run: yarn prettier --check .

.github/workflows/linting.yml

@@ -0,0 +1,18 @@
+name: Lint Code Base
+
+on: [push, pull_request]
+
+jobs:
+  eslint:
+    runs-on: ubuntu-latest
+    steps:
+      - uses: actions/checkout@v2
+      - name: Set up Node.js
+        uses: actions/setup-node@v2
+        with:
+          node-version: "22"
+          cache: "yarn"
+      - name: Install dependencies
+        run: yarn install --frozen-lockfile
+      - name: Run ESLint
+        run: yarn eslint . --max-warnings 0

CODING_GUIDELINES.md

@@ -0,0 +1,117 @@
+# Coding Guidelines for Email Recovery Demo
+
+This document outlines the coding guidelines for contributing to the **Email Recovery Demo**. Following these guidelines will help maintain a consistent and high-quality codebase.
+
+## 1. Code Formatting
+
+- **Tool**: Use **Prettier** to automatically format your code. Ensure that all code is formatted before committing.
+  - Run `npx prettier --write .` to format the entire codebase.
+- **Indentation**: Use 2 spaces per indentation level. Do not use tabs.
+- **Line Length**: Aim to keep lines under 100 characters. Longer lines should be broken up for readability.
+- **Function Length**: Aim to keep functions short and focused. If a function is too long, consider breaking it up into smaller functions.
+- **Imports**: Organize imports into the following sections:
+
+  1. External dependencies (e.g., libraries from `node_modules`).
+  2. Absolute imports (e.g., `import { func } from 'src/utils';`).
+  3. Relative imports (e.g., `import { func } from '../utils';`).
+
+  Example:
+
+  ```ts
+  import fs from "fs";
+  import { validateEmail } from "src/utils";
+  import { parseInput } from "../parsers";
+  ```
+
+- **Braces**: Use braces for all control structures, even single-line blocks.
+
+  Example:
+
+  ```ts
+  if (condition) {
+    doSomething();
+  }
+  ```
+
+- **Semicolons**: Always use semicolons to terminate statements.
+- **Whitespace**: Use a single space after commas and colons, but no space before them.
+
+  Example:
+
+  ```ts
+  const arr = [1, 2, 3];
+  const obj = { name: "Alice", age: 30 };
+  ```
+
+## 2. Code Linting
+
+- **Tool**: Use **ESLint** to enforce code quality. Run `npx eslint .` before committing your code.
+- **Handling Lints**: Address all warnings and errors reported by ESLint. Avoid ignoring lint rules unless necessary, and if you do, provide a comment explaining why.
+
+## 3. Naming Conventions
+
+- **Variables and Functions**: Use `camelCase` for variable and function names.
+
+  Example:
+
+  ```ts
+  const userName = "Alice";
+  ```
+
+- **Classes and Interfaces**: Use `PascalCase`.
+
+  Example:
+
+  ```ts
+  class UserAccount { ... }
+  ```
+
+- **Constants**: Use `UPPER_CASE` for constant values.
+
+  Example:
+
+  ```ts
+  const MAX_USERS = 100;
+  ```
+
+## 4. Documentation
+
+- **JSDoc**: Document all public functions, methods, and classes using JSDoc comments.
+
+  Example:
+
+  ```ts
+  /**
+   * Creates a new user account.
+   * @param {string} name - The name of the user.
+   * @returns {UserAccount} A new UserAccount object.
+   */
+  function createUserAccount(name: string): UserAccount {
+    // function body
+  }
+  ```
+
+- **Inline Comments**: Add comments in code where the intent or logic is not immediately clear.
+
+## 5. Error Handling
+
+- **Use of `try`/`catch`**: Use `try`/`catch` blocks for error-prone code. Always handle errors gracefully.
+
+  Example:
+
+  ```ts
+  try {
+    const data = await fetchData();
+  } catch (error) {
+    console.error("Error fetching data", error);
+  }
+  ```
+
+- **Custom Errors**: When appropriate, define custom error types by extending the `Error` class.
+
+## 6. Testing
+
+- **Tool**: Use **Jest** for writing unit and integration tests. Ensure that all new functionality has corresponding tests.
+  - Run `npm test` to execute the test suite.
+- **Test Structure**: Organize tests in a `__tests__` directory or in files with the `.test.ts` or `.spec.ts` suffix.
+- **Coverage**: Aim for at least 80% code coverage. Run `npm test -- --coverage` to check coverage metrics.