BUTKHUZI RESIDUE CLEANUP

Physical TypeScript host file check

The following retired TypeScript host files were explicitly checked and are no longer present on disk:

• services/svc-tenders/src/butkhuzi
• registerButkhuziRoutes.ts
• butkhuziRouteSupport.ts

That means this final pass did not need to delete any remaining Butkhuzi TypeScript host files, because the TypeScript host slice was already physically retired.

Leftover references found

• Dead compile residue in server.ts: a stale ButkhuziRepository import remained even though the active Butkhuzi route host had already been retired from the TypeScript server composition.
• Dead compile residue in repository.ts: a stale deleteButkhuziNormsBySource(...) passthrough still referenced this.butkhuziRepository even though the root TypeScript repository no longer owned active Butkhuzi hosting.
• Stale generated JavaScript residue still present on disk: server.js, repository.js, registerButkhuziRoutes.js, butkhuziRouteSupport.js.
• Migration-only residue still present: Butkhuzi historical migrations remain under migrations.

What was removed

• Removed the stale ButkhuziRepository import from server.ts.
• Removed the dead deleteButkhuziNormsBySource(...) passthrough from repository.ts.
• Confirmed there are no remaining TypeScript imports or active-host references for: butkhuziRepository registerButkhuziRoutes butkhuzi/contracts butkhuzi/validation inside services/svc-tenders/src TypeScript files.

What still remains in svc-tenders and why

• Historical .js artifacts still reference Butkhuzi because they were generated before retirement and were not part of this focused TypeScript residue cleanup.
• Historical Butkhuzi migrations remain because they are migration/history residue, not active route-host wiring.
• Shared gateway routing remains outside svc-tenders on purpose via the extracted-service topology.

Canonical runtime

svc-butkhuzi remains the canonical Butkhuzi runtime. This cleanup did not reintroduce Butkhuzi as an active svc-tenders host.

Editor cache note

Because the retired .ts files are already gone, any editor errors still pointing at them are most likely stale TypeScript server or VS Code indexing state. A TypeScript server restart or window reload is recommended after this cleanup.