packages/analytics: fix entry point, lint, and CI coverage

[BigBen-7]

Three small, mechanical infra gaps in `packages/analytics`, combined since they're all quick and independent of the real fix in #851.

1. No entry point (main/types)

`packages/analytics/package.json` has no `"main"`, `"types"`, or `"exports"` field:

```json
{
"name": "@stellar-explain/analytics",
"version": "0.1.0",
"private": true,
"scripts": { ... },
"devDependencies": { ... }
}
```

`tsc` builds to `dist/` (per `tsconfig.json`'s `outDir`), but nothing in the manifest points there — `import ... from "@stellar-explain/analytics"` can't resolve today. This is a hard blocker for #851 (nothing can import the package until this is fixed).

Fix: add
```json
"main": "dist/index.js",
"types": "dist/index.d.ts"
```
and confirm `src/index.ts` actually re-exports the public API (EventEmitter, sinks, etc.).

2. Lint is completely broken

`"lint": "eslint src"` is defined but `eslint` isn't a devDependency at all — standalone install + lint fails with `eslint: command not found`. Even with `eslint` available (e.g. hoisted from `packages/ui` at the workspace root), it still fails because the package only has a legacy `.eslintrc.json`, and the resolved ESLint version (9.x) no longer reads that format:

```
ESLint: 9.39.5
ESLint couldn't find an eslint.config.(js|mjs|cjs) file.
```

Fix: add `eslint` as an explicit devDependency, replace `.eslintrc.json` with a flat `eslint.config.mjs` — follow the pattern already working in `packages/ui/eslint.config.mjs` or `packages/cli/eslint.config.mjs`.

3. No CI coverage

`.github/workflows/ci.yml` only triggers on `packages/core/` and `packages/cli/` — a push/PR touching only `packages/analytics/` or `packages/ui/` runs no CI at all (confirmed: zero mentions of "analytics" in any workflow file). This is how #1 and #2 above went unnoticed.

Fix: add a job (or extend the `paths` filters) to run install/build/typecheck/lint/test for `packages/analytics` and `packages/ui`, mirroring `ci.yml`'s existing `cli` job.

---

Related: #851 (the actual analytics/ui disconnect — depends on item 1 here to even be possible).

[Anichris-koded]

Hi, my name is Koded, and I’m a professional software engineer experienced in building maintainable, production-ready TypeScript packages and monorepos. I can resolve the missing entry point in packages/analytics by properly configuring main, types, and exports, ensuring the package can be imported reliably across the project. My approach focuses on clean package architecture, TypeScript compatibility, predictable module resolution, and seamless integration with dependent applications.

[Anichris-koded]

Hi, my name is Koded, and I’m a professional software engineer experienced in TypeScript, package architecture, and monorepo development. I can resolve the missing entry point in packages/analytics by configuring the appropriate main, types, and exports fields, making the package reliably importable across the codebase. My approach ensures clean module resolution, proper type support, and maintainable integration with dependent services and applications.

[limxiy]

I’d like to take this on as a focused package-infrastructure cleanup. I’ll fix the analytics package entry points and public exports, make ESLint work correctly with the current flat-config setup, and extend CI coverage to analytics and UI.

I’ll also verify the changes with install, build, typecheck, lint, and test runs so these gaps are caught automatically going forward.
ETA is 24 hrs

[grantfox-oss]

🦊 GrantFox — @limxiy has been assigned to this issue as part of the Third Campaign campaign!

Next steps:

1. Open a Pull Request referencing this issue (e.g., Closes #853)
2. Your PR will be reviewed by the StellarCommons maintainers

Good luck! Track your progress on GrantFox.

[grantfox-oss]

🎉 This issue has been marked as completed on GrantFox as part of the Third Campaign campaign!

@limxiy's PR #855 was approved and merged by @Tinna23.

🏆 @limxiy: You earned 35 FoxPoints for this contribution! Your current tier: Explorer (885 total points). Track your full progress on GrantFox.

👏 Great work, @limxiy! Keep contributing to StellarCommons.