TypeScript ecosystem: add fixture matrix, rule coverage, docs, examples, and Wiki updates

[bjcorder]

Parent

Part of #89.

Context

Expanded TypeScript framework and ORM support should be fixture-backed and documented. This issue tracks cross-cutting validation and public-facing docs for the TypeScript ecosystem expansion.

Scope

• Add fixture families, each with safe/ and unsafe/ cases where appropriate:
  • nestjs_typeorm
  • nestjs_mongoose
  • fastify_drizzle
  • hono_kysely
  • koa_knex
  • adonis_lucid
  • remix_drizzle_or_prisma
  • sveltekit_drizzle_or_mongodb
  • trpc_typeorm_or_drizzle
  • graphql_mongoose_or_sql
• Cover route/entrypoint discovery, request source extraction, auth evidence, authorization evidence, tenant/object scope evidence, validation evidence, service tracing, ORM/raw SQL/document sinks, suppressions, baselines, and CI behavior.
• Ensure all relevant INV001-INV008 and HINT001-HINT006 scenarios have TypeScript expansion fixture coverage.
• Add text, JSON, and SARIF output assertions for expanded TypeScript diagnostics.
• Update README, docs/, config schema docs, testing fixture docs, examples, and Wiki pages for expanded TypeScript support.
• Add recipes for at least NestJS, Fastify/Hono, and one file-based full-stack framework.

Acceptance Criteria

• Each targeted TypeScript framework/data-layer family has safe and unsafe CLI integration tests or a documented staged subset.
• Expanded TypeScript fixtures assert positive findings and safe-case absence of false positives.
• Expanded TypeScript support appears in public docs and Wiki with clear implementation status and limitations.
• Example recipes show .rulepath.yml, scan output, CI/baseline use, and suppression guidance.
• Existing v1 TypeScript fixtures remain green.

Test Plan

• Add TypeScript ecosystem fixture integration tests under crates/rulepath_cli/tests or a TypeScript-specific integration test file.
• Add output shape assertions for text, JSON, and SARIF.
• Validate docs links and config snippets.
• Run cargo fmt --all -- --check, cargo clippy --locked --workspace --all-targets, cargo test --locked --workspace, and cargo build --locked --workspace.