Telegram (ask questions / claim the issue here first): https://t.me/+DOylgFv1jyJlNzM0
Why this matters
scripts/ is a real TypeScript package (scripts/package.json, scripts/deploy.ts ~290 lines run via ts-node) but no CI job installs it or runs tsc --noEmit on it. ci.yml's env-docs-check only executes scripts/check-env-docs.mjs directly. A type error or stellar-sdk API drift in deploy.ts would only be discovered during an actual mainnet/testnet deploy.
Acceptance criteria
Files to touch
.github/workflows/ci.yml
scripts/package.json
scripts/deploy.ts
Out of scope
- Adding a lint config to scripts/ if none exists (typecheck is sufficient for this issue)
- Running an actual deploy in CI
Why this matters
scripts/ is a real TypeScript package (scripts/package.json, scripts/deploy.ts ~290 lines run via ts-node) but no CI job installs it or runs tsc --noEmit on it. ci.yml's env-docs-check only executes scripts/check-env-docs.mjs directly. A type error or stellar-sdk API drift in deploy.ts would only be discovered during an actual mainnet/testnet deploy.
Acceptance criteria
Files to touch
.github/workflows/ci.ymlscripts/package.jsonscripts/deploy.tsOut of scope