Loading module
Resolving locale, route permissions, and workspace projection.
svc-tenders Server Helper Inventory
Purpose
This note records the post-Sprint-19 helper inventory for services/svc-tenders/src/server.ts.
The goal is truthful classification, not forced movement.
Labels used here:
VERIFIEDREALTRANSITIONAL
Helpers that stayed in server.ts
Auth / session helpers
VERIFIED, REAL
These remain in server.ts because they are still service-shell auth concerns.
requireServiceAuth
- Current role: shared auth gate for service routes
- Classification: auth/session helper
READ 2026-03-28T23:42:21.903Z
READ 2026-03-29T04:52:41.869Z
CORE STRICT SAFE DELETE AFTER RERUN REPORT
PUBLIC | DRAFT | v1.0.0
READ 2026-03-29T03:13:33.020Z
Stayed or moved: stayedWhy: depends on token parsing, JWT verification, config, and principal resolution
- Current role: JWT verification and access-claim validation
- Classification: auth/session helper
- Stayed or moved: stayed
- Why: tightly coupled to service-shell auth flow
- Current role: bearer token extraction
- Classification: auth/session helper
- Stayed or moved: stayed
- Why: small auth-shell helper used only by
requireServiceAuth
- Current role: upstream
/auth/me principal resolution
- Classification: auth/session helper
- Stayed or moved: stayed
- Why: service-shell auth integration
- Current role: shape validation for resolved principal payload
- Classification: auth/session helper
- Stayed or moved: stayed
- Why: private auth-shell helper used only by
resolvePrincipal
- Current role: active-principal gate used by vacancy/accommodation routes
- Classification: auth/session helper
- Stayed or moved: stayed
- Why: still a shared route-shell auth helper across multiple route groups
Shared parser / query helpers
These remain in server.ts because they are still reused across many route groups.
- Current role: bounded positive integer parsing with fallback
- Classification: parser/query helper
- Stayed or moved: stayed
- Why: used broadly across route support builders
- Current role: positive float parsing
- Classification: parser/query helper
- Stayed or moved: stayed
- Why: currently shared by ICPI and general service-shell parsing
- Current role: normalized optional string parsing
- Classification: parser/query helper
- Stayed or moved: stayed
- Why: broadly shared
- Current role: uppercase-normalized string parsing
- Classification: parser/query helper
- Stayed or moved: stayed
- Why: broadly shared
- Current role: boolean query parsing
- Classification: parser/query helper
- Stayed or moved: stayed
- Why: used by tender/auction support builders after Sprint 19
- Current role: optional integer parsing
- Classification: parser/query helper
- Stayed or moved: stayed
- Why: broadly shared
- Current role: bounded integer clamping
- Classification: parser/query helper
- Stayed or moved: stayed
- Why: broadly shared by KES/ICPI and other route groups
- Current role: normalizes Express query values before parsing
- Classification: parser/query helper
- Stayed or moved: stayed
- Why: low-level shared parser helper
Broad but still transitional helpers
These still live in server.ts because they are shared or config-coupled enough that no narrower destination is obvious yet.
- Current role: none in
server.ts after Sprint 19
- Classification: removed from
server.ts
- Stayed or moved: moved
- Why: obvious tender-route support logic
- Current role: none in
server.ts after Sprint 19
- Classification: removed from
server.ts
- Stayed or moved: moved
- Why: obvious auction-route support logic
- Current role: none in
server.ts after Sprint 19
- Classification: removed from
server.ts
- Stayed or moved: moved
- Why: shared tender/auction ranking parser with an obvious support-module home
- Current role: none in
server.ts after Sprint 19
- Classification: removed from
server.ts
- Stayed or moved: moved
- Why: shared vacancy/accommodation detail extraction with an obvious support-module home
- Current role: none in
server.ts after Sprint 19
- Classification: removed from
server.ts
- Stayed or moved: moved
- Why: declaration/tender request intent normalization with an obvious support-module home
- Current role: none in
server.ts after Sprint 19
- Classification: removed from
server.ts
- Stayed or moved: moved
- Why: declaration upload bridge with an obvious declaration-support home
KES-specific boundary helpers
ensureThirdPartyKycBoundary
- Current role: blocks raw sensitive KYC payloads in third-party mode
- Classification: KES-specific boundary helper
- Stayed or moved: stayed
- Why: KES boundary check with config-dependent runtime behavior
verifyIncomingSignatureGate
- Current role: payload-signature verification gate
- Classification: KES-specific boundary helper
- Stayed or moved: stayed
- Why: KES/runtime boundary helper tied to config and crypto verification
Helpers moved out of server.ts in Sprint 18
Moved to routes/support/accommodationRouteSupport.ts
toAccommodationUnitTypeparseAccommodationPricesplitAccommodationLocationtoPublicAccommodationSummarytoPublicAccommodationDetailmapAccommodationMutationError
- all were accommodation-route-local support/mapping behavior
- their destination was obvious and low-risk
Moved to routes/support/tenderRouteSupport.ts
toTenderSummarytoTenderDetailtoTenderPortalDetail
- these were tender-route-local mapping helpers
- they only existed to satisfy tender route support
Moved to routes/support/vacancyRouteSupport.ts
hasVacancyPostingCapabilityhasVacancyApplicationCapabilitynormalizePermissionsmapVacancyMutationError
- these were vacancy-route-local support helpers
- their destination was obvious inside the vacancy support builder
Moved to routes/support/declarationRouteSupport.ts
getAuctionDeclarationCapabilitieshasAuctionDeclarationCapabilitycanCheckAuctionDeclarationgetTenderDeclarationCapabilitieshasTenderDeclarationCapabilitycanCheckTenderDeclarationparseAuctionDeclarationEvidenceGroupKeyparseTenderDeclarationEvidenceGroupKey
- these are declaration-route-local capability/evidence helpers
- their destination was obvious inside declaration support
Helpers moved out of server.ts in Sprint 19
Moved to routes/support/detailExtractionSupport.ts
- shared by vacancy and accommodation route support only
- its destination was obvious without inventing a generic helpers bucket
Moved to routes/support/requestIntentSupport.ts
- shared only by tender/declaration route support
- it is no longer a true service-shell concern
Moved to routes/support/rankingScopeSupport.ts
- shared only by tender/auction list-option parsing
- it is route-support-local, not a generic shell parser
Moved to routes/support/declarationUploadSupport.ts
runMulterSingle (now exposed as buildRunMulterSingle(...))
- still declaration-upload-specific
- the declaration evidence upload middleware remains configured in
server.ts, but the runner wrapper no longer needs to live there
Moved to routes/support/tenderRouteSupport.ts
- obvious tender-route support logic
- depends only on tender-local parsing plus shared parser inputs
Moved to routes/support/auctionRouteSupport.ts
- obvious auction-route support logic
- depends only on auction-local parsing plus shared parser inputs
Dead or stale residue
No standalone dead helper blocks were found in Sprint 19.
The only direct code cleanup in server.ts beyond helper relocation was removal of now-unused repository type imports that had been kept only for the old in-file helper bodies.
Result
After Sprint 19, the helper surface still in server.ts is easier to justify:
- auth/session shell helpers remain together
- low-level parser/query helpers remain together
- KES boundary helpers remain together
- tender/auction/declaration/vacancy/accommodation-local helper bodies no longer live in the service shell
What remains transitional/shared is explicit rather than silently mixed.