Import dyad repository as git submodule at third_party/dyad

[Copilot]

Adds the dyad repository as a git submodule for use as an external dependency.

Changes

• Submodule: Added at third_party/dyad pointing to commit fadfbc06be8d08efcd0e12a366c881c4df5c9086 (v0.28.0-5-gfadfbc0)
• Documentation: Updated README.md with submodule initialization and update instructions
• License attribution: Created THIRD_PARTY_LICENSES.md referencing dyad's Apache 2.0 license (with src/pro/ directory exception)

Usage

After cloning, initialize submodules:

git submodule update --init --recursive

Or clone with submodules in one step:

git clone --recurse-submodules <repository-url>

Original prompt

Import the external repository https://github.com/dyad-sh/dyad.git into wasalstor-web/saas by adding it as a git submodule located at third_party/dyad.

Tasks:

• Add the dyad repo as a git submodule at path third_party/dyad pointing to its default branch HEAD.
• Create a new branch for the change (e.g., import/dyad-submodule).
• Update the repository README.md to document the added submodule and instructions to initialize and update submodules (git submodule update --init --recursive).
• If the repo contains licenses, copy or reference the dyad LICENSE file into third_party/dyad or add a note in the top-level LICENSE/NOTICE section.
• Ensure the PR description clearly states the source repository URL, the submodule path, and any build or runtime implications.

Do not modify other unrelated files. If the repository has a CONTRIBUTING or PR template that requires additional steps, include them 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.

This PR should make it straightforward for maintainers to review and accept the external code import.

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

Import the external repository https://github.com/dyad-sh/dyad.git into wasalstor-web/saas by adding it as a git submodule located at third_party/dyad.

Tasks:

• Add the dyad repo as a git submodule at path third_party/dyad pointing to its default branch HEAD.
• Create a new branch for the change (e.g., import/dyad-submodule).
• Update the repository README.md to document the added submodule and instructions to initialize and update submodules (git submodule update --init --recursive).
• If the repo contains licenses, copy or reference the dyad LICENSE file into third_party/dyad or add a note in the top-level LICENSE/NOTICE section.
• Ensure the PR description clearly states the source repository URL, the submodule path, and any build or runtime implications.

Do not modify other unrelated files. If the repository has a CONTRIBUTING or PR template that requires additional steps, include them 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.

This PR should make it straightforward for maintainers to review and accept the external code import.

---

💡 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.