Arnas Donauskas bce345ed03 chore: OSS metadata + LICENSE + SECURITY + complete env example ... Prep work so the repo is ready to be public. None of this is runtime code; it's the governance a forker expects on day one. - LICENSE: MIT at repo root. README already claimed MIT; this makes GitHub actually recognise it and show the license badge. - .github/SECURITY.md: private disclosure path via GitHub Security Advisories or email. Spells out scope, safe harbour, and what the reporter should expect — so a researcher finds it before they try to file a public issue. - .env.local.example: fleshed out with the three vars it was missing — META_APP_SECRET (required, from PR 1), NEXT_PUBLIC_SITE_URL (recommended), and AUTOMATION_CRON_SECRET (optional). Grouped as Required / Recommended / Optional with a one-line comment per entry. Includes the openssl/node generators for the secrets. - package.json: description, repository, bugs, homepage, keywords, license, author, engines.node >=20. No runtime impact; feeds npm registry metadata, GitHub's repo sidebar, and prevents forkers from silently installing on Node <20 (Next 16's floor). Typecheck clean; npm install run to refresh the lockfile for the package.json metadata additions (no dependency changes). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-20 20:41:14 +03:00
..
workflows	ci: typecheck + build on every PR	2026-04-20 19:09:32 +03:00
CODEOWNERS	chore: require Arnas as reviewer on every PR (CODEOWNERS)	2026-04-19 22:09:10 +03:00
SECURITY.md	chore: OSS metadata + LICENSE + SECURITY + complete env example	2026-04-20 20:41:14 +03:00