chore: tighten publish workflow and docs around generated build artifacts

Restructure repository and publishing ergonomics after the TypeScript migration by moving fully to generated build artifacts, improving contributor guidance, and documenting usage with a more explicit developer-first README.

Repository and workflow updates:
- Stop tracking compiled  output in git and treat it as generated build output.
- Keep npm package output unchanged by continuing to publish  via package  and lifecycle build hooks.
- Update  with a more complete Node/TS baseline:
  - ignore , tsbuildinfo, coverage output, common debug logs, env-local variants, and editor/OS noise.
- Update  as a defense-in-depth publish filter for local-only, source-only, and tool metadata files.
- Replace  with  in  so build happens consistently during
> @timmsy/riftjs@3.1.0 prepack
> npm run build

> @timmsy/riftjs@3.1.0 build
> tsc -p tsconfig.json and
> @timmsy/riftjs@3.1.0 prepack
> npm run build

> @timmsy/riftjs@3.1.0 build
> tsc -p tsconfig.json.

Documentation overhaul:
- Rewrite README into a practical, step-by-step guide with clear install/setup flow.
- Add separate quick-start examples for CommonJS and TypeScript users.
- Expand endpoint reference with explicit inputs, outputs, option shapes, and pacing behavior.
- Document supported region routing behavior and normalized error semantics.
- Clarify local development lifecycle (, , optional env vars) and package output structure.
- Link maintainer guidance from the README.

Maintainer guidance and in-code intent notes:
- Add  with project scope, API stability expectations, typing standards, rate-limit posture, and release checklist.
- Add maintainability comments in core TS modules to preserve implementation intent around:
  - strict region validation
  - class API surface wiring
  - Data Dragon base URL concurrency handling
  - conservative pacing defaults and sequential detail fetching
  - test skip semantics for no-match accounts
- Standardize maintainer comment attribution to .

Net effect:
This commit reduces repository noise, keeps published package behavior stable, and significantly improves onboarding/maintenance clarity for both users and contributors without changing the public runtime API surface.

Author: Timmsy1998

.gitignore

@@ -1,4 +1,30 @@
-node_modules
+# Dependencies
+node_modules/
+
+# Environment files (keep examples committed)
 .env
-test.js
+.env.local
+.env.*.local
+
+# Logs
 *.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+
+# TypeScript incremental build metadata
+*.tsbuildinfo
+
+# Build output (generated locally, not tracked)
+dist/
+
+# Test and coverage output
+coverage/
+.nyc_output/
+
+# OS / editor noise
+.DS_Store
+Thumbs.db
+.idea/
+.vscode/

.npmignore

@@ -1,6 +1,32 @@
+# Local environment files
 .env
+.env.local
+.env.*.local
 .env.example
+
+# Source and project-only files
+src/
+tsconfig.json
+MAINTAINER_NOTES.md
+.github/
+
+# VCS/editor metadata
+.git/
 .gitignore
-*.test.js
-test.js
+.DS_Store
+Thumbs.db
+.idea/
+.vscode/
+
+# Logs and reports
 *.log
+npm-debug.log*
+yarn-debug.log*
+yarn-error.log*
+pnpm-debug.log*
+coverage/
+.nyc_output/
+*.tsbuildinfo
+
+# Node modules (safety)
+node_modules/

MAINTAINER_NOTES.md

@@ -0,0 +1,50 @@
+# Maintainer Notes
+
+These are personal notes for future maintenance. They are intentionally direct.
+
+## Project intent
+
+- Keep this package small and predictable.
+- The goal is to provide a thin wrapper around Riot endpoints, not an abstraction framework.
+- Prefer explicit methods over clever generic request builders.
+
+## API stability
+
+- Avoid breaking constructor behavior in `RiotAPI` and `DataDragon`.
+- Keep method names stable unless there is a strong reason to change them.
+- If a method signature changes, update:
+  - `src/types.ts`
+  - `README.md`
+  - `src/test-endpoints.ts`
+
+## TypeScript expectations
+
+- Source of truth is always `src/`.
+- `dist/` is build output, committed for npm consumers and transparency.
+- Keep strict typing on, and do not weaken it just to silence compiler warnings.
+
+## Error handling stance
+
+- Error messages should stay readable in terminal logs.
+- `RiotAPI` should keep returning normalized `Error` messages.
+- Data Dragon wrappers should preserve the root error message.
+
+## Rate limit and pacing
+
+- Multi-request methods exist because Riot rate limits are easy to hit.
+- Keep pacing defaults conservative unless usage data says otherwise.
+- If defaults change, call it out clearly in changelog and README.
+
+## Release checklist (quick)
+
+1. Run `npm run build`
+2. Run `npm test`
+3. Verify `README.md` examples still match real method signatures
+4. Verify `package.json` points to `dist/index.js` and `dist/index.d.ts`
+5. Commit source and matching `dist` output together
+
+## Notes to self
+
+- Keep docs practical. Most users want a working snippet first.
+- Do not overcomplicate return types until there is clear demand.
+- If Riot deprecates an endpoint, mark it clearly and provide migration guidance.