Contribution environment setup

[RibatTRW]

Environment setup for contributing to lnreader, completed on this machine (2026-08-22):

• Fork RibatTRW/lnreader + clone at C:\Users\clang\dev\lnreader (origin = fork, upstream = lnreader/lnreader)
• Node v26.5.1, pnpm 11.22.0
• Temurin JDK 17.0.20+8 (JAVA_HOME set user-level)
• Android SDK cmdline-tools + platform-tools + android-36 platform + build-tools 36.0.0 (ANDROID_HOME set user-level)
• pnpm install (1358 packages)
• pnpm run generate:env:debug (creates .env required by @env imports)
• pnpm run type-check green
• Agent-skills config: docs/agents/* + AGENTS.md section (branch agent-setup-docs)
• Triage labels seeded on this fork

Next up:

• First real contribution (pick an upstream issue or bug)

[RibatTRW]

Verified finding (2026-08-22): pnpm run format:check fails on a pristine upstream checkout — 21 files are flagged, all byte-identical to lnreader/lnreader@master (5a0717d). Root cause: upstream pins prettier 2.8.8 but the tree has drifted from it, and no GitHub Actions workflow runs format:check (build/lint/testing/types only), so nothing catches the drift upstream.

Implications for us:

• format:check failures on untouched upstream files are not our environment's fault — don't "fix" unrelated files in contribution PRs (upstream AGENTS.md: don't reformat unrelated code).
• The enforced gates are pnpm run lint and pnpm run type-check (both green here); run prettier only on files we actually touch.
• Also note: repo-local git config core.autocrlf=false is set in this clone to keep the working tree byte-faithful (host default autocrlf=true smears LF→CRLF and confuses prettier further).