chore: add CODEOWNERS file

[dianab-cl]

Adds .github/CODEOWNERS to assign @skip-mev/stack-team as code owners for all files.

[greptile-apps]

Greptile Summary

This PR adds a .github/CODEOWNERS file to enforce code review ownership, but the team reference in the file (@cosmos/stack-team) does not match the repository's organization (skip-mev) or the intended team stated in the PR description (@skip-mev/stack-team). GitHub silently ignores cross-org team entries, so the file will have no effect as written.

Confidence Score: 4/5

Not safe to merge as-is — the CODEOWNERS entry references the wrong org and will have no effect.

A single one-line fix is needed (wrong GitHub org in team reference). The change is otherwise minimal and low-risk, but the file is entirely ineffective until corrected.

.github/CODEOWNERS — team org must be changed from cosmos to skip-mev.

Vulnerabilities

No security concerns identified beyond the incorrect team reference, which means expected branch-protection/review enforcement from CODEOWNERS will not be active until corrected.

Important Files Changed

Filename	Overview
.github/CODEOWNERS	Adds CODEOWNERS but references @cosmos/stack-team instead of the intended @skip-mev/stack-team; the wrong org means ownership rules will not take effect.

Flowchart

%%{init: {'theme': 'neutral'}}%%
flowchart TD
    A[PR opened in skip-mev/catalyst] --> B{GitHub reads CODEOWNERS}
    B --> C["Entry: * @cosmos/stack-team"]
    C --> D{Resolve team org}
    D -->|"org = cosmos ≠ skip-mev"| E[Team reference ignored]
    E --> F[No reviewers auto-requested]
    E --> G[No ownership protection enforced]
    D -->|"Correct: * @skip-mev/stack-team"| H[Team resolved successfully]
    H --> I[Reviewers auto-requested on PR]
    H --> J[CODEOWNERS protection active]

Loading

_{Reviews (1): Last reviewed commit: "Apply suggestion from @dianab-cl" | Re-trigger Greptile}