Butkhuzi Residue Cleanup
This cleanup pass removed the remaining TypeScript-side Butkhuzi host residue from services/svc-tenders without restoring Butkhuzi as an active svc-tenders runtime.
Resolving locale, route permissions, and workspace projection.
Current scope: Guest
Category: 10_normative | Version: v1.0.0
Owner: DOCUMENT_CUSTODIAN | Review cycle: 90 days
Approval authority: GOVERNANCE_ADMIN
Documentation portal is read-only. Editing and mutation endpoints are disabled.
Kvary platform is originally created in Georgian. Where a Georgian version exists, Georgian is authoritative for platform UI, documentation, and legal interpretation.
Translations into other languages are provided for convenience. Some records may originate in other languages and carry their own source or legal locale for a specific flow, but where a Georgian version is available, the Georgian version prevails for platform-level wording and interpretation.
Metadata incomplete: Document ID, Version, Status, Owner Role, Last Review Date, Next Review Date, Change Log
This cleanup pass removed the remaining TypeScript-side Butkhuzi host residue from services/svc-tenders without restoring Butkhuzi as an active svc-tenders runtime.
The following retired TypeScript host files were explicitly checked and are no longer present on disk:
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.
ButkhuziRepository import remained even though the active Butkhuzi route host had already been retired from the TypeScript server composition.deleteButkhuziNormsBySource(...) passthrough still referenced this.butkhuziRepository even though the root TypeScript repository no longer owned active Butkhuzi hosting.ButkhuziRepository import from server.ts.deleteButkhuziNormsBySource(...) passthrough from repository.ts.butkhuziRepository
registerButkhuziRoutes
butkhuzi/contracts
butkhuzi/validation
inside services/svc-tenders/src TypeScript files.svc-tenders and why.js artifacts still reference Butkhuzi because they were generated before retirement and were not part of this focused TypeScript residue cleanup.svc-tenders on purpose via the extracted-service topology.svc-butkhuzi remains the canonical Butkhuzi runtime. This cleanup did not reintroduce Butkhuzi as an active svc-tenders host.
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.