[kerenaugustine79]

Summary

Align MIT licensing and streamline issue/PR templates

What was solved

#1075 — LICENSE MIT consistency across packages

Make the repository's MIT licensing consistent across packages by aligning the root LICENSE with the license metadata declared in each package manifest (root, apps/api, and any SDK/contract packages), and cross-linking the license from the top-level docs so contributors and Stellar Wave participants see one authoritative MIT statement. This is a licensing/consistency change only — no runtime, authz, or money-path behavior is touched, so the issue's security/flagging requirements are satisfied by confirming no code paths change.

Addressed:

• Changed: README.md, apps/api/package.json, CONTRIBUTING.md
• Ensure the root LICENSE file contains a complete, canonical MIT license text with correct copyright holder and year.
• Make every package manifest's license field consistent with the root LICENSE (e.g. "license": "MIT" in package.json files) so tooling and npm consumers see the same license.
• Cross-link the LICENSE from README.md (and CONTRIBUTING.md if it references licensing) so contributors have a single authoritative source.

#1076 — Issue templates point to heavy AC style

Update the Swyft issue templates so they no longer push contributors toward the heavy, AC-style process described in the issue. The scope is limited to the files under .github/ISSUE_TEMPLATE/ (bug.md and feature.md), aligning them with the repo's actual contribution expectations while keeping the templates useful and lightweight.

Addressed:

• Changed: .github/ISSUE_TEMPLATE/bug.md, .github/ISSUE_TEMPLATE/feature.md, .github/PULL_REQUEST_TEMPLATE.md, CONTRIBUTING.md
• Revise .github/ISSUE_TEMPLATE/bug.md and .github/ISSUE_TEMPLATE/feature.md to remove the heavy AC-style framing and replace it with concise, contributor-friendly prompts.
• Keep templates consistent with existing repo conventions (front matter, labels, structure) and cross-reference CONTRIBUTING.md/SECURITY.md where appropriate.
• Do not modify unrelated files, workflows, or application code; scope is limited to issue templates.

#1077 — PR template requires contract drift check note

Update the PR template so contributors must complete a contract drift check note, aligning the template with the issue's requirement that PRs document contract drift and invariants. The change is documentation-only and scoped to the PR template, with a cross-link to CONTRACTS.md for the drift-check reference.

Addressed:

• Changed: .github/PULL_REQUEST_TEMPLATE.md
• Add a required 'Contract drift check' section/checkbox to .github/PULL_REQUEST_TEMPLATE.md so PRs must state whether contract drift exists and how it was verified.
• Reference CONTRACTS.md as the source of truth for contract drift and invariants, keeping the note concise and contributor-friendly.
• Keep the change documentation-only: do not modify CI workflows, contracts, or application code.

Changes

• README.md (modify)
• apps/api/package.json (modify)
• CONTRIBUTING.md (modify)
• .github/ISSUE_TEMPLATE/bug.md (create)
• .github/ISSUE_TEMPLATE/feature.md (modify)
• .github/PULL_REQUEST_TEMPLATE.md (modify)

Approach

1. LICENSE MIT consistency across packages #1075 — LICENSE MIT consistency across packages (Changed: README.md, apps/api/package.json, CONTRIBUTING.md)
2. Issue templates point to heavy AC style #1076 — Issue templates point to heavy AC style (Changed: .github/ISSUE_TEMPLATE/bug.md, .github/ISSUE_TEMPLATE/feature.md, .github/PULL_REQUEST_TEMPLATE.md, CONTRIBUTING.md)
3. PR template requires contract drift check note #1077 — PR template requires contract drift check note (Changed: .github/PULL_REQUEST_TEMPLATE.md)

Issues

Closes #1075
Closes #1076
Closes #1077