Migrate NestJS RouterModule route prefix postExtract shape

[jununfly]

This was generated by AI during triage.

Parent

Roadmap node 1-6-7. Framework post-extract Rust migration exploit candidate.

Plan: docs/plans/2026-06-29-rust-side-framework-post-extract-protocol-plan.md.

What to build

Implement the first default-path Rust-produced framework postExtract update shape: NestJS RouterModule route-name prefix rewrites. Rust should produce typed route-name updates for the allowlisted NestJS shape, and the TypeScript shell should apply them through the validator introduced by #659.

Acceptance criteria

• Produce Rust-side updates for the allowlisted NestJS shape: provider=nestjs, updateKind=route-name-prefix, nodeKind=route, field=name.
• Apply those updates through the TypeScript-shell validator from Define Rust-side framework postExtract update protocol #659.
• Preserve route node id and qualifiedName.
• Preserve existing route-handler edges after the route name update.
• Keep repeated indexing idempotent.
• Fail closed for unsupported framework postExtract providers and update shapes.

Blocked by

• Define Rust-side framework postExtract update protocol #659

[jununfly]

This was generated by AI during triage.

Closing as implemented. NestJS RouterModule route-prefix postExtract updates now have a Rust producer fixture that emits guarded route name updates through the shared protocol, without moving parse-time framework extraction or direct DB writes into Rust.

Verification: cargo test -p zcodegraph-core rust_produces_nestjs_router_module_route_name_post_extract_updates; npx vitest run __tests__/rust-framework-post-extract-protocol.test.ts; npm run build.