Sequence diagram for wallet connection flow in wagmi App

[Dargon789]

Reviewer's Guide

Adds a new wagmi-based Vite demo project for wallet connection (likely for CodeSandbox dev), introduces Fortify AST and Azure Pipelines CI workflows plus GitHub issue/security templates, and updates the indexer changelog for a 2.0.0 release placeholder along with various sandbox/config/cache files.

Sequence diagram for wallet connection flow in wagmi App

sequenceDiagram
  actor User
  participant App
  participant useConnect

  User ->> App: click connector button
  App ->> useConnect: connect(connector)
  alt [connection succeeds]
    useConnect -->> App: status=connected
  else [connection fails]
    useConnect -->> App: error.message
  end
  App -->> User: render account.status and addresses

Loading

Flow diagram for React app bootstrapping with Wagmi and React Query

flowchart LR
  Browser --> ReactDOM_root
  ReactDOM_root --> WagmiProvider
  WagmiProvider --> QueryClientProvider
  QueryClientProvider --> App
  WagmiProvider --> Wagmi_config
  App --> useAccount
  App --> useConnect
  App --> useDisconnect

Loading

File-Level Changes

Change	Details	Files
Introduce a wagmi-based Vite React demo app for wallet connections (CodeSandbox-style dev environment).	Add a Vite React entry point that bootstraps React, WagmiProvider, QueryClientProvider, and polyfills Buffer on globalThis Implement an App component that displays wagmi account status and allows connecting/disconnecting via injected, Coinbase Wallet, and WalletConnect connectors Configure wagmi with mainnet and sepolia chains, HTTP transports, and connectors including WalletConnect with projectId from Vite env Add Vite config, TypeScript configs, basic dark/light CSS, HTML shell, and project metadata (package.json, README, gitignore, npmrc, biome config, vite env types) for the wagmi project	wagmi-project/src/main.tsx wagmi-project/src/App.tsx wagmi-project/src/wagmi.ts wagmi-project/src/index.css wagmi-project/src/vite-env.d.ts wagmi-project/index.html wagmi-project/vite.config.ts wagmi-project/tsconfig.json wagmi-project/tsconfig.node.json wagmi-project/package.json wagmi-project/README.md wagmi-project/.gitignore wagmi-project/.npmrc wagmi-project/biome.json
Add Fortify Application Security Testing GitHub Actions workflow for SAST scanning.	Create a Fortify AST Scan GitHub Actions workflow triggered on pushes, PRs to master, scheduled cron, and manual dispatch Configure job permissions, Java 17 setup, and use fortify/github-action to run SAST scan against Fortify on Demand with secrets-based configuration hooks	.github/workflows/fortify.yml
Add Azure Pipelines definition for basic Node.js build.	Configure pipeline trigger on master branch using ubuntu-latest agent Install Node.js 10.x via NodeTool task and run npm install and npm run build	azure-pipelines.yml
Introduce repository governance and security meta-files (issue templates and security policy).	Add bug report, feature request, and custom GitHub issue templates Add a SECURITY.md with version support matrix and placeholder instructions for reporting vulnerabilities	.github/ISSUE_TEMPLATE/bug_report.md .github/ISSUE_TEMPLATE/feature_request.md .github/ISSUE_TEMPLATE/custom.md SECURITY.md
Update indexer service changelog with 2.0.0 placeholder entry.	Add new 2.0.0 section with a Major Changes heading and a placeholder item indicating a changeset	packages/services/indexer/CHANGELOG.md
Add miscellaneous project/environment artifacts for hosting and tooling.	Add CodeSandbox tasks configuration file placeholder Add CNAME and v8-compile-cache artifacts likely from a previous run/environment	.codesandbox/tasks.json CNAME v8-compile-cache-0/x64/11.3.244.8-node.19/zSprojectzSsequence.jszSnode_moduleszS.pnpmzS@preconstruct+cli@2.8.7zSnode_moduleszS@preconstructzSclizSbin.js.MAP v8-compile-cache-0/x64/11.3.244.8-node.19/zSprojectzSworkspacezSnode_moduleszS.pnpmzS@preconstruct+cli@2.8.7zSnode_moduleszS@preconstructzSclizSbin.js.MAP

Possibly linked issues

• Feature/integration #17: They describe the same wagmi integration and repo setup: wagmi project, SECURITY.md, Azure pipeline, and placeholders.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

Originally posted by @sourcery-ai[bot] in #586 (comment)