Repository navigation
Conversation
Phase 4 core-business pricing refactor: - pricing.engine.ts: pure pipeline extracted verbatim from the legacy PricingService (identical arithmetic order and float behavior). - strategies/: distance-tier, weight, special-handling, city-premium, deviation-cost, earnings + pricing-factory wiring all PRICING_* config. - B-10 fix: tier capacities derive from cumulative bounds (upToKm - previousUpToKm) with no hand-tuned +1 constant; proven byte-identical to legacy output by a 500-check parity harness against the golden capture. - pricing.service.ts: slim DI facade preserving the public API consumed by package.service (calculateSuggestedPrice / calculateTransporterEarnings / calculateDeviationCost / calculateDistanceCost). - Table-driven specs per strategy + golden-equality engine spec (default variant, bit-exact floats) + facade spec. Verification: tsc clean; full suite 53/53 suites, 401/401 tests; pricing 9/9 suites, 91/91 tests.
…ore, drop root phase-1-foundation.md)
…yzer with parity specs - Add pure MatchingScorer, buildTripCandidateWhere and CorridorAnalyzer under src/modules/package/matching/ (moved verbatim, no behavior change) - Slim MatchingService to orchestration: delegates scoring/analysis, Nest Logger instead of console.error, ConfigKey.Pricing.CorridorWidth - Fix TurfService console.error -> Logger (fallback path now covered) - Add table-driven specs + match fixtures; extend matching.service.spec (Logger skip, ConfigKey read/default, default-param paths) Verification: tsc clean, 56 suites / 437 tests green, scoped eslint 0 errors. No API-visible change (BREAKING 4.0 stands).
… commit messages)
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
No description provided.