Add dyad repository as git submodule at third_party/dyad

[Copilot]

Adds https://github.com/dyad-sh/dyad.git as a git submodule for third-party integration.

Changes

• Submodule: third_party/dyad pointing to dyad HEAD
• README.md: Added submodule initialization instructions
• NOTICE: Created with Apache 2.0 attribution for dyad (Copyright 2025 Dyad Tech, Inc.)

Usage

Clone with submodules:

git clone --recurse-submodules https://github.com/wasalstor-web/saas.git

Or initialize after clone:

git submodule update --init --recursive

Notes

• No build system integration yet—dyad source available at third_party/dyad/ for downstream consumption
• Full license at third_party/dyad/LICENSE

Original prompt

Add the external repository https://github.com/dyad-sh/dyad.git to the wasalstor-web/saas repository as a git submodule located at third_party/dyad.

Acceptance criteria:

• Create a new branch import/dyad-submodule from the repository default branch.
• Add the submodule pointing to https://github.com/dyad-sh/dyad.git at path third_party/dyad using the default branch HEAD of the dyad repo.
• Update README.md to document the added submodule and include instructions to initialize and update submodules: git submodule update --init --recursive.
• Include or reference dyad's LICENSE in the third_party/dyad directory or add a note in the top-level LICENSE/NOTICE about the included code and its license.
• Open a pull request with a clear description including source repo URL, submodule path, branch created, and any build/runtime implications. If repository contribution rules or templates require additional info, include it in the PR description.

If adding a submodule fails due to repository policies, fall back to copying the dyad source under third_party/dyad with attribution and include the LICENSE file.

Do not modify unrelated files beyond the README and top-level license/NOTICE files as needed.

This pull request was created as a result of the following prompt from Copilot chat.

Add the external repository https://github.com/dyad-sh/dyad.git to the wasalstor-web/saas repository as a git submodule located at third_party/dyad.

Acceptance criteria:

• Create a new branch import/dyad-submodule from the repository default branch.
• Add the submodule pointing to https://github.com/dyad-sh/dyad.git at path third_party/dyad using the default branch HEAD of the dyad repo.
• Update README.md to document the added submodule and include instructions to initialize and update submodules: git submodule update --init --recursive.
• Include or reference dyad's LICENSE in the third_party/dyad directory or add a note in the top-level LICENSE/NOTICE about the included code and its license.
• Open a pull request with a clear description including source repo URL, submodule path, branch created, and any build/runtime implications. If repository contribution rules or templates require additional info, include it in the PR description.

If adding a submodule fails due to repository policies, fall back to copying the dyad source under third_party/dyad with attribution and include the LICENSE file.

Do not modify unrelated files beyond the README and top-level license/NOTICE files as needed.

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.