@datarecce/ui 0.1.41 → 0.2.0

package/recce-source/CONTRIBUTING.md

@@ -1,107 +0,0 @@
-# Contributing to Recce
-
-Issues and PRs are welcome!
-
-# Developer Certificate of Origin
-
-Recce DCO and signed-off-by process
-
-The Recce project use the signed-off-by language and process used by the Linux kernel, to give us a clear chain of trust for every patch received.
-
-```
-By making a contribution to this project, I certify that:
-
-(a) The contribution was created in whole or in part by me and I have the right to submit it under the open source license indicated in the file; or
-
-(b) The contribution is based upon previous work that, to the best of my knowledge, is covered under an appropriate open source license and I have the right under that license to submit that work with modifications, whether created in whole or in part by me, under the same open source license (unless I am permitted to submit under a different license), as indicated in the file; or
-
-(c) The contribution was provided directly to me by some other person who certified (a), (b) or (c) and I have not modified it.
-
-(d) I understand and agree that this project and the contribution are public and that a record of the contribution (including all personal information I submit with it, including my sign-off) is maintained indefinitely and may be redistributed consistent with this project or the open source license(s) involved.
-```
-
-## Using the Signed-Off-By Process
-
-We have the same requirements for using the signed-off-by process as the Linux kernel. In short, you need to include a signed-off-by tag in every patch:
-
-```
-This is my commit message
-
-Signed-off-by: Random J Developer <random@developer.example.org>
-```
-
-Git even has a -s command line option to append this automatically to your commit message:
-
-```
-$ git commit -s -m 'This is my commit message'
-```
-
-# Write Commit message properly
-
-Structure your commit message like this:
-
-From: [https://git-scm.com/book/ch5-2.html](https://git-scm.com/book/ch5-2.html)
-
-> Short (50 chars or less) summary of changes
->
-> More detailed explanatory text, if necessary.  Wrap it to about 72
-> characters or so.  In some contexts, the first line is treated as the
-> subject of an email and the rest of the text as the body.  The blank
-> line separating the summary from the body is critical (unless you omit
-> the body entirely); tools like rebase can get confused if you run the
-> two together.
->
-> Further paragraphs come after blank lines.
->
->   - Bullet points are okay, too
->
->   - Typically a hyphen or asterisk is used for the bullet, preceded by a
->    single space, with blank lines in between, but conventions vary here
-
-## **DO**
-
-- Write the summary line and description of what you have done in the imperative mood, that is as if you were commanding someone. Start the line with "Fix", "Add", "Change" instead of "Fixed", "Added", "Changed".
-- Always leave the second line blank.
-- Line break the commit message (to make the commit message readable without having to scroll horizontally in `gitk`).
-- The summary should be meaningful and descriptive.
-
-## **DON'T**
-
-- Don't end the summary line with a period - it's a title and titles don't end with a period.
-- Avoid mentioning specific deployments or customers. Instead, describe what problem is solved.
-
-## **Tips**
-
-- If it seems difficult to summarize what your commit does, it may be due to multiple logical changes or bug fixes, that are better split up into several commits using `git add -p`.
-
-## Recommendations
-
-- Use company email to commit. You can set in the project scope by invoking `git config user.email dev@infuseai.io` inside the repository.
-- Sign-off your commits. [[Ref](https://github.com/DataRecce/recce/blob/master/CONTRIBUTING.md#using-the-signed-off-by-process)]
-- Add `Co-authored-by` if you're pairing with someone. [[Ref]](https://help.github.com/en/github/committing-changes-to-your-project/creating-a-commit-with-multiple-authors)
-
-## Examples
-### :x: Bad
-
-```
-Fix bugs
-```
-
-* it should have a reason or cause to be fixed.
-* please write the `DCO` (git commit `-s`)
-
-
-### :white_check_mark: Good
-
-```git
-Update readme for getting started 
-
-Co-authored-by: Wei-Chun, Chang <wcchang@infuseai.io>
-Signed-off-by: popcorny <celu@infuseai.io>
-
-```
-
-* there is a purpose to add this commit
-  * feature added: two commands were introduced
-* write the `DCO`
-

package/recce-source/LICENSE

@@ -1,201 +0,0 @@
-                                 Apache License
-                           Version 2.0, January 2004
-                        http://www.apache.org/licenses/
-
-   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
-
-   1. Definitions.
-
-      "License" shall mean the terms and conditions for use, reproduction,
-      and distribution as defined by Sections 1 through 9 of this document.
-
-      "Licensor" shall mean the copyright owner or entity authorized by
-      the copyright owner that is granting the License.
-
-      "Legal Entity" shall mean the union of the acting entity and all
-      other entities that control, are controlled by, or are under common
-      control with that entity. For the purposes of this definition,
-      "control" means (i) the power, direct or indirect, to cause the
-      direction or management of such entity, whether by contract or
-      otherwise, or (ii) ownership of fifty percent (50%) or more of the
-      outstanding shares, or (iii) beneficial ownership of such entity.
-
-      "You" (or "Your") shall mean an individual or Legal Entity
-      exercising permissions granted by this License.
-
-      "Source" form shall mean the preferred form for making modifications,
-      including but not limited to software source code, documentation
-      source, and configuration files.
-
-      "Object" form shall mean any form resulting from mechanical
-      transformation or translation of a Source form, including but
-      not limited to compiled object code, generated documentation,
-      and conversions to other media types.
-
-      "Work" shall mean the work of authorship, whether in Source or
-      Object form, made available under the License, as indicated by a
-      copyright notice that is included in or attached to the work
-      (an example is provided in the Appendix below).
-
-      "Derivative Works" shall mean any work, whether in Source or Object
-      form, that is based on (or derived from) the Work and for which the
-      editorial revisions, annotations, elaborations, or other modifications
-      represent, as a whole, an original work of authorship. For the purposes
-      of this License, Derivative Works shall not include works that remain
-      separable from, or merely link (or bind by name) to the interfaces of,
-      the Work and Derivative Works thereof.
-
-      "Contribution" shall mean any work of authorship, including
-      the original version of the Work and any modifications or additions
-      to that Work or Derivative Works thereof, that is intentionally
-      submitted to Licensor for inclusion in the Work by the copyright owner
-      or by an individual or Legal Entity authorized to submit on behalf of
-      the copyright owner. For the purposes of this definition, "submitted"
-      means any form of electronic, verbal, or written communication sent
-      to the Licensor or its representatives, including but not limited to
-      communication on electronic mailing lists, source code control systems,
-      and issue tracking systems that are managed by, or on behalf of, the
-      Licensor for the purpose of discussing and improving the Work, but
-      excluding communication that is conspicuously marked or otherwise
-      designated in writing by the copyright owner as "Not a Contribution."
-
-      "Contributor" shall mean Licensor and any individual or Legal Entity
-      on behalf of whom a Contribution has been received by Licensor and
-      subsequently incorporated within the Work.
-
-   2. Grant of Copyright License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      copyright license to reproduce, prepare Derivative Works of,
-      publicly display, publicly perform, sublicense, and distribute the
-      Work and such Derivative Works in Source or Object form.
-
-   3. Grant of Patent License. Subject to the terms and conditions of
-      this License, each Contributor hereby grants to You a perpetual,
-      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
-      (except as stated in this section) patent license to make, have made,
-      use, offer to sell, sell, import, and otherwise transfer the Work,
-      where such license applies only to those patent claims licensable
-      by such Contributor that are necessarily infringed by their
-      Contribution(s) alone or by combination of their Contribution(s)
-      with the Work to which such Contribution(s) was submitted. If You
-      institute patent litigation against any entity (including a
-      cross-claim or counterclaim in a lawsuit) alleging that the Work
-      or a Contribution incorporated within the Work constitutes direct
-      or contributory patent infringement, then any patent licenses
-      granted to You under this License for that Work shall terminate
-      as of the date such litigation is filed.
-
-   4. Redistribution. You may reproduce and distribute copies of the
-      Work or Derivative Works thereof in any medium, with or without
-      modifications, and in Source or Object form, provided that You
-      meet the following conditions:
-
-      (a) You must give any other recipients of the Work or
-          Derivative Works a copy of this License; and
-
-      (b) You must cause any modified files to carry prominent notices
-          stating that You changed the files; and
-
-      (c) You must retain, in the Source form of any Derivative Works
-          that You distribute, all copyright, patent, trademark, and
-          attribution notices from the Source form of the Work,
-          excluding those notices that do not pertain to any part of
-          the Derivative Works; and
-
-      (d) If the Work includes a "NOTICE" text file as part of its
-          distribution, then any Derivative Works that You distribute must
-          include a readable copy of the attribution notices contained
-          within such NOTICE file, excluding those notices that do not
-          pertain to any part of the Derivative Works, in at least one
-          of the following places: within a NOTICE text file distributed
-          as part of the Derivative Works; within the Source form or
-          documentation, if provided along with the Derivative Works; or,
-          within a display generated by the Derivative Works, if and
-          wherever such third-party notices normally appear. The contents
-          of the NOTICE file are for informational purposes only and
-          do not modify the License. You may add Your own attribution
-          notices within Derivative Works that You distribute, alongside
-          or as an addendum to the NOTICE text from the Work, provided
-          that such additional attribution notices cannot be construed
-          as modifying the License.
-
-      You may add Your own copyright statement to Your modifications and
-      may provide additional or different license terms and conditions
-      for use, reproduction, or distribution of Your modifications, or
-      for any such Derivative Works as a whole, provided Your use,
-      reproduction, and distribution of the Work otherwise complies with
-      the conditions stated in this License.
-
-   5. Submission of Contributions. Unless You explicitly state otherwise,
-      any Contribution intentionally submitted for inclusion in the Work
-      by You to the Licensor shall be under the terms and conditions of
-      this License, without any additional terms or conditions.
-      Notwithstanding the above, nothing herein shall supersede or modify
-      the terms of any separate license agreement you may have executed
-      with Licensor regarding such Contributions.
-
-   6. Trademarks. This License does not grant permission to use the trade
-      names, trademarks, service marks, or product names of the Licensor,
-      except as required for reasonable and customary use in describing the
-      origin of the Work and reproducing the content of the NOTICE file.
-
-   7. Disclaimer of Warranty. Unless required by applicable law or
-      agreed to in writing, Licensor provides the Work (and each
-      Contributor provides its Contributions) on an "AS IS" BASIS,
-      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
-      implied, including, without limitation, any warranties or conditions
-      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
-      PARTICULAR PURPOSE. You are solely responsible for determining the
-      appropriateness of using or redistributing the Work and assume any
-      risks associated with Your exercise of permissions under this License.
-
-   8. Limitation of Liability. In no event and under no legal theory,
-      whether in tort (including negligence), contract, or otherwise,
-      unless required by applicable law (such as deliberate and grossly
-      negligent acts) or agreed to in writing, shall any Contributor be
-      liable to You for damages, including any direct, indirect, special,
-      incidental, or consequential damages of any character arising as a
-      result of this License or out of the use or inability to use the
-      Work (including but not limited to damages for loss of goodwill,
-      work stoppage, computer failure or malfunction, or any and all
-      other commercial damages or losses), even if such Contributor
-      has been advised of the possibility of such damages.
-
-   9. Accepting Warranty or Additional Liability. While redistributing
-      the Work or Derivative Works thereof, You may choose to offer,
-      and charge a fee for, acceptance of support, warranty, indemnity,
-      or other liability obligations and/or rights consistent with this
-      License. However, in accepting such obligations, You may act only
-      on Your own behalf and on Your sole responsibility, not on behalf
-      of any other Contributor, and only if You agree to indemnify,
-      defend, and hold each Contributor harmless for any liability
-      incurred by, or claims asserted against, such Contributor by reason
-      of your accepting any such warranty or additional liability.
-
-   END OF TERMS AND CONDITIONS
-
-   APPENDIX: How to apply the Apache License to your work.
-
-      To apply the Apache License to your work, attach the following
-      boilerplate notice, with the fields enclosed by brackets "[]"
-      replaced with your own identifying information. (Don't include
-      the brackets!)  The text should be enclosed in the appropriate
-      comment syntax for the file format. We also recommend that a
-      file or class name and description of purpose be included on the
-      same "printed page" as the copyright notice for easier
-      identification within third-party archives.
-
-   Copyright 2023 InfuseAI Inc.
-
-   Licensed under the Apache License, Version 2.0 (the "License");
-   you may not use this file except in compliance with the License.
-   You may obtain a copy of the License at
-
-       http://www.apache.org/licenses/LICENSE-2.0
-
-   Unless required by applicable law or agreed to in writing, software
-   distributed under the License is distributed on an "AS IS" BASIS,
-   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
-   See the License for the specific language governing permissions and
-   limitations under the License.

package/recce-source/Makefile

@@ -1,126 +0,0 @@
-.PHONY: help format lint check test clean install dev-install install-cloud install-cloud-dev build build-cloud build-all clean-build
-
-# Default target executed when no arguments are given to make.
-default: help
-
-install-dev:
-	pip install -e .[dev,mcp]
-	git config --unset-all core.hooksPath && pre-commit install
-
-install:
-	pip install .
-
-install-cloud:
-	pip install -e ./recce_cloud
-
-install-cloud-dev:
-	pip install -e ./recce_cloud[dev]
-
-help:
-	@echo "Available commands:"
-	@echo "  make help              - Show this help message"
-	@echo "  make format            - Format code with Black and isort"
-	@echo "  make format-cloud      - Format recce-cloud code"
-	@echo "  make flake8            - Run flake8 linting"
-	@echo "  make flake8-cloud      - Run flake8 on recce-cloud"
-	@echo "  make mypy              - Run type checking with mypy"
-	@echo "  make check             - Run all code quality checks without modifying files"
-	@echo "  make check-cloud       - Run code quality checks on recce-cloud"
-	@echo "  make install           - Install recce package"
-	@echo "  make install-dev       - Install recce with dev requirements"
-	@echo "  make install-cloud     - Install recce-cloud package"
-	@echo "  make install-cloud-dev - Install recce-cloud in dev mode"
-	@echo "  make dev               - Run the frontend in dev mode"
-	@echo "  make build             - Build recce package"
-	@echo "  make build-cloud       - Build recce-cloud package"
-	@echo "  make build-all         - Build both packages"
-	@echo "  make clean-build       - Clean build artifacts"
-
-format:
-	@echo "Formatting with Black..."
-	black ./recce ./tests
-	@echo "Sorting imports with isort..."
-	isort ./recce ./tests
-
-format-cloud:
-	@echo "Formatting recce-cloud with Black..."
-	black ./recce_cloud
-	@echo "Sorting imports with isort..."
-	isort ./recce_cloud
-
-flake8:
-	@echo "Linting with flake8..."
-	flake8 ./recce ./tests
-
-flake8-cloud:
-	@echo "Linting recce-cloud with flake8..."
-	flake8 ./recce_cloud
-
-# Run all code quality checks without modifying files
-check:
-	@echo "Checking code formatting with Black..."
-	black --check ./recce ./tests
-	@echo "Checking import order with isort..."
-	isort --check ./recce ./tests
-	@echo "Checking code style with flake8..."
-	flake8 ./recce ./tests
-
-check-cloud:
-	@echo "Checking recce-cloud code formatting with Black..."
-	black --check ./recce_cloud
-	@echo "Checking recce-cloud import order with isort..."
-	isort --check ./recce_cloud
-	@echo "Checking recce-cloud code style with flake8..."
-	flake8 ./recce_cloud
-
-test: install-dev
-	@echo "Running tests..."
-	@python3 -m pytest tests
-
-test-coverage: install-dev
-	@echo "Running tests with coverage..."
-	@python3 -m pytest --cov=recce --cov-report=html --cov-report=term tests
-	@echo "Coverage report generated in htmlcov/index.html"
-
-test-tox: install-dev
-	@echo "Running tests with Tox based on DBT versions..."
-	@tox run-parallel
-
-test-tox-python-versions:
-	@echo "Running tests with Tox for specific Python versions..."
-	@tox run-parallel -e 3.9,3.10,3.11,3.12,3.13
-
-install-frontend-requires:
-# Install pnpm if not installed
-	@command -v pnpm || npm install -g pnpm
-	@cd js && pnpm install
-
-dev: install-frontend-requires
-	@cd js && pnpm dev
-
-# Build targets (packaging - using uv)
-clean-build:
-	@echo "Cleaning build artifacts..."
-	@rm -rf build/ dist/ *.egg-info recce_cloud.egg-info
-	@find . -type d -name __pycache__ -exec rm -rf {} + 2>/dev/null || true
-	@find . -type f -name '*.pyc' -delete
-
-build-frontend:
-	@echo "Building frontend static files..."
-	@cd js && pnpm install --frozen-lockfile && pnpm build
-
-build: clean-build build-frontend
-	@echo "Building recce package..."
-	uv build
-
-build-cloud: clean-build
-	@echo "Building recce-cloud package..."
-	uv build --package recce-cloud
-
-build-all: clean-build build-frontend
-	@echo "Building both packages..."
-	uv build
-	uv build --package recce-cloud
-	@echo "Build complete!"
-	@echo "Packages in dist/:"
-	@ls -lh dist/

package/recce-source/README.md

@@ -1,182 +0,0 @@
-<p align="center">
-    <a href="https://reccehq.com">
-        <picture>
-            <source media="(prefers-color-scheme: dark)" srcset="https://reccehq.com/assets/images/recce-logo-stacked.avif">
-            <source media="(prefers-color-scheme: light)" srcset="https://reccehq.com/assets/images/recce-logo-stacked.avif">
-            <img alt="Recce: DataRecce.io" src="https://reccehq.com/assets/images/recce-logo-stacked.avif" width="200" style="display: block; margin: 0 auto 20px;">
-        </picture>
-    </a>
-</p>
-
-<h3 align="center">Helping data teams preview, validate, and ship data changes with confidence.</h3>
-
-<p align="center">
-    <a href="https://pypi.org/project/recce/"><img src="https://img.shields.io/badge/pip_install-recce-006DAD?style=flat-square" alt="install"></a> &nbsp;
-    <a href="https://pypi.org/project/recce/"><img src="https://img.shields.io/pypi/v/recce?style=flat-square" alt="pipy"></a> &nbsp;
-    <a href="https://pypi.org/project/recce/"><img src="https://img.shields.io/pypi/pyversions/recce?style=flat-square" alt="Python"></a> &nbsp;
-    <a href="https://pypi.org/project/recce/#files"><img src="https://img.shields.io/pypi/dw/recce?style=flat-square" alt="downloads"></a> &nbsp;
-    <a href="https://github.com/DataRecce/recce/blob/main/LICENSE"><img src="https://img.shields.io/github/license/DataRecce/recce?style=flat-square" alt="license"></a> &nbsp;
-    <a href="https://getdbt.slack.com/archives/C05C28V7CPP"><img src="https://img.shields.io/badge/Slack-4A154B?style=flat-square&amp;logo=slack&amp;logoColor=white" alt="Slack"></a> &nbsp;
-    <a href="https://discord.com/invite/5zb2aK9KBV"><img src="https://img.shields.io/discord/664381609771925514?color=%237289DA&amp;label=chat&amp;logo=discord&amp;logoColor=white&amp;style=flat-square" alt="InfuseAI Discord Invite"></a> &nbsp;
-</p>
-
-<p align="center">
-    <a href="https://cal.com/team/recce/chat?utm_source=banner&utm_campaign=oss">
-        <img alt="Book us with Cal.com" src="https://cal.com/book-with-cal-light.svg" />
-    </a>
-</p>
-
-## Trust, Verify, Ship
-
-Cut dbt review time by 90% and ship accurate data fast
-
-Recce gives data teams a faster, more reliable way to understand, review, and ship changes without all the guesswork or manual overhead.
-
-## Quick Start
-
-### Installation
-
-Recce offers two packages to fit different use cases:
-
-**For full local development and Recce Cloud features:**
-
-```bash
-pip install -U recce
-recce server
-```
-
-**For CI/CD artifact uploads only (lightweight):**
-
-```bash
-pip install -U recce-cloud
-recce-cloud upload
-```
-
-The `recce-cloud` package is a lightweight CLI tool designed specifically for CI/CD environments where you only need to upload dbt artifacts to Recce Cloud. It has minimal dependencies and installs faster than the full `recce` package.
-
-### Getting Started
-
-You can launch Recce in any dbt project in just two commands:
-
-```bash
-# cd into your dbt project
-pip install -U recce
-recce server
-```
-
-(Note: while recce is not version spsecific, `dbt-core` is currently [not compatible with Python 3.13](https://docs.getdbt.com/faqs/Core/install-python-compatibility). Please make sure to use Python 3.10 - 3.12.)
-
-This starts Recce locally, where you can explore lineage and run queries. To unlock the full set of diffing tools, such as data comparisons and impact checks, you'll need to prepare two environments to compare against. You can follow our [Getting Started](https://docs.reccehq.com/get-started/) and [5-minute Jaffle Shop tutorial](https://docs.reccehq.com/get-started-jaffle-shop/) to try it out step-by-step.
-
-## What You Get
-
-Recce gives you a clear, fast way to understand what your data changes are doing and why they matter. It helps you catch problems early, verify metrics, and share your findings with others, all as part of your normal workflow.
-
-<a href="https://pr46.demo.reccehq.com/"><img width="1347" alt="readme" src="https://github.com/user-attachments/assets/773e4c3a-0a15-49e0-8d1b-38a55af17cb0" /></a>
-
-<a href="https://reccehq.com"><img src="https://docs.reccehq.com/assets/images/1-whats-recce/diff-readme2.png" style="width: 100%; max-width: 600px; display: block; margin: 0 auto 20px;" alt="Model and column level diff"/></a>
-
-<a href="https://reccehq.com"><img src="https://docs.reccehq.com/assets/images/1-whats-recce/checklist-readme3.png" style="width: 100%; max-width: 600px; display: block; margin: 0 auto 20px;" alt="Checklist for collaboration"/></a>
-
-### Using Recce for Impact Assessment in dbt PR Review
-
-- Select nodes in the lineage to perform Checks (diffs) as part of your impact assessment during development or PR
-  review.
-- Add Checks to your Checklist to note observed impacts.
-- Share your Checklist with the PR reviewer.
-- (`Recce Cloud`) Automatically sync Check status between Recce Instances
-- (`Recce Cloud`) Block PR merging until all Recce Checks have been approved
-
-Read more about using Recce on our [blog](https://blog.reccehq.com).
-
-### What’s Included
-
-- [Lineage and impact mapping](https://docs.reccehq.com/features/lineage/): Quickly see which models and columns are affected by a change. Navigate lineage down to the column level, and spot breaking changes with clear visual cues.
-- Metric and data comparisons: Use [Profile, Value, Top-K, and Histogram Diffs](https://docs.reccehq.com/features/lineage/#node-details) to compare results before and after changes. Validate things like row counts, category distributions, and numeric ranges without writing extra SQL.
-- [Query diff](https://docs.reccehq.com/features/query/): Write and compare any two queries side by side. This is helpful when validating fixes or reviewing changes with teammates.
-- [Checklist for reviews and approvals](https://docs.reccehq.com/features/checklist/): Turn your validation steps into a checklist. Add notes, rerun checks, and share the results with reviewers or stakeholders. In Recce Cloud, checklists can sync automatically and even block PRs until checks are approved.
-- Secure by design: Recce is [SOC 2 compliant](https://trust.reccehq.com/) to meet enterprise security standards. It runs locally or in your private environment, and your data stays in your warehouse.
-
-👉 Want to dive deeper? Check out the [full documentation](https://docs.reccehq.com/).
-
-## Recce Cloud
-
-Ready to collaborate and move faster as a team? Recce Cloud adds real-time collaboration, automatic checklist sync, and PR gating, so nothing gets merged without a full review.
-
-- Share checklists across environments
-- Invite stakeholders to review data changes
-- Block merges until all Checks are approved
-- Launch demo links from your CI with full context
-
-Recce Cloud is a hosted version of Recce that standardizes your workflow, keeps teams aligned, and reduces errors—so you can ship data changes with confidence.
-👉 [View Pricing and Plans](https://reccehq.com/pricing)
-
-## Developer Documentation
-
-If you want to contribute to Recce or test local changes in your dbt project, follow these steps to install the development version.
-
-### Installing the Local Dev Version
-
-1. **Clone the repository** (if you haven't already):
-
-   ```bash
-   git clone https://github.com/DataRecce/recce.git
-   cd recce
-   ```
-
-2. **Build the project** from the repository root:
-
-   ```bash
-   make build
-   ```
-
-   This builds the frontend assets and prepares the package for installation.
-
-3. **Install the local dev version** in your dbt project:
-
-   ```bash
-   # Navigate to your dbt project
-   cd /path/to/your/dbt-project
-
-   # Install recce in editable mode (replace with your actual path to the recce repo)
-   pip install -e /path/to/recce
-   ```
-
-   Using `-e` (editable mode) means any changes you make to the Recce source code will be immediately available without reinstalling.
-
-4. **Start the Recce server** to verify the installation:
-
-   ```bash
-   recce server
-   ```
-
-### Development Tips
-
-- After making frontend changes in `js/`, run `make build` again to rebuild the static assets
-- Run `make install-dev` in the recce repository to install development dependencies
-- Use `make test` to run the Python test suite
-- Use `cd js && pnpm test` to run the frontend test suite
-
-For more detailed development guidelines, see [CONTRIBUTING.md](CONTRIBUTING.md).
-
-## Community & Support
-
-Here's where you can get in touch with the Recce team and find support, add a subscribe to our newsletter option as well:
-
-- [chat on our website](https://reccehq.com/). We welcome you to start a chat or drop us a note. Our team monitors the chat box and will follow up soon.
-- [Our discord](https://discord.com/invite/VpwXRC34jz)
-- [dbt Slack](https://www.getdbt.com/community/join-the-community) in the [#tools-recce](https://getdbt.slack.com/archives/C05C28V7CPP) channel
-- Email us [help@reccehq.com](mailto:help@reccehq.com)
-
-If you believe you have found a bug on our open source, or there is some missing functionality in Recce, please open a [GitHub Issue](https://github.com/DataRecce/recce/issues).
-
-## Recce on the web
-
-You can follow along with news about Recce and blogs from our team in the following places:
-
-- [RecceHQ.com](https://reccehq.com/)
-- [LinkedIn](https://www.linkedin.com/company/datarecce)
-- [Blog](https://blog.reccehq.com/)
-- [@datarecce](https://x.com/DataRecce) on Twitter/X
-- [@DataRecce@mastodon.social](https://mastodon.social/@DataRecce) on Mastodon
-- [@datarecce.bsky.social](https://bsky.app/profile/datarecce.bsky.social) on BlueSky