chore: drop remaining context module legacy refs

Follow-up sweep after acb737e25 — the context module's UI + Dexie
tables + AI route were already removed, but a handful of registry-style
refs in the monorepo's plumbing still pointed at the dead module:

- packages/shared-utils/src/analytics.ts: drop the `context: createModuleTracker('context')`
  entry from the `track` map and delete the unused `ContextEvents`
  helper (no consumers — every analytics call site that used it lived
  in the deleted module).
- packages/shared-utils/src/analytics.ts (cont.): the deletion above
  removes the only typed reference to track.context, so the property
  cleanly disappears from the inferred type.
- package.json: drop 6 dead npm scripts (`context:dev`, `dev:context:web`,
  `dev:context:app`, `dev:context:full`, `dev:context:local`, `setup:db:context`)
  — all referenced `@context/*` workspace packages that were removed
  with the module. `pnpm context:dev` would silently succeed-with-zero-targets
  before; now it correctly errors as unknown script.
- scripts/generate-env.mjs: drop the two `apps/context/apps/{server,web}/.env`
  generator entries pointing at non-existent app directories.
- scripts/validate-monorepo.mjs: drop `'@context/'` from the internal
  workspace prefix list — fences a class of dependency that no longer
  exists.
- .env.development: fix a stale comment pointing at the renamed
  /api/v1/context/import-url endpoint (now /api/v1/kontext/import-url
  per acb737e25).
- apps/context/: delete the leftover directory (CLAUDE.md describing
  vanished paths + a package.json with a `dev:mobile` script filtering
  the @context/mobile package that was deleted with all per-product
  mobile apps on 2026-04-20).

What remains and is intentional: historical plan docs / devlogs /
audit reports / generated complexity-map.html / Dexie v57 drop
migration / pnpm-lock.yaml (regenerates on next `pnpm install`).
Unrelated `'context'` strings (MemoryCategory enum, Kontext-Agent
template id, encryption-vaults DB column, Astro landing /context
content collection) stay — different concepts that happen to share
the word.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>

apps/context/CLAUDE.md

@@ -1,24 +0,0 @@
-# Context — consolidated into the unified Mana app
-
-This product was migrated into the unified Mana monorepo. The legacy
-per-product `apps/context/apps/backend/` (NestJS) and
-`apps/context/apps/web/` directories have been removed. Active code now
-lives in:
-
-- **Backend compute routes**: [`apps/api/src/modules/context/routes.ts`](../api/src/modules/context/routes.ts) (AI text generation via mana-llm, server-side credit deduction)
-- **Frontend module** (local-first): [`apps/mana/apps/web/src/lib/modules/context/`](../mana/apps/web/src/lib/modules/context/)
-- **Web route**: [`apps/mana/apps/web/src/routes/(app)/context/`](../mana/apps/web/src/routes/(app)/context/)
-- **Mobile app**: [`apps/context/apps/mobile/`](apps/mobile/)
-
-For monorepo-wide patterns (auth, sync, encryption, services), see the
-[root `CLAUDE.md`](../../CLAUDE.md) and [`apps/mana/CLAUDE.md`](../mana/CLAUDE.md).
-
-The previous "Context App" guide describing a NestJS backend with its
-own spaces/documents/token tables was deleted in the audit cleanup of
-2026-04-09 — it had been inaccurate since the consolidation. The
-token-economy logic now lives in `mana-credits`. Pre-consolidation
-reference is in git history.
-
-> **Note:** The legacy `apps/context/pnpm-lock.yaml` (242 KB, separate
-> workspace setup) and the broken `dev:web` / `dev:server` filter scripts
-> in `apps/context/package.json` are tracked in audit items #2 and #26.

apps/context/package.json

@@ -1,8 +0,0 @@
-{
-	"name": "context",
-	"version": "0.1.0",
-	"private": true,
-	"scripts": {
-		"dev:mobile": "pnpm --filter @context/mobile dev"
-	}
-}