cm45t3r / candlestick / 29552177465

100%

push

github

feat(patternChain): trend-context-aware confidence, deprecate static confidence (#99)

* feat(patternChain): trend-context-aware confidence, deprecate static confidence

Pattern functions are evaluated independently with no shared trend
context. On real data (AAPL, 2025-07-22/23) this lets the identical
candle qualify as both `hammer` (bullish reversal, expects a preceding
downtrend) and `hangingMan` (bearish reversal, expects a preceding
uptrend) — opposite signals on the same shape, disambiguated only by
context. Each pattern's static `confidence` also can't distinguish a
textbook occurrence from a marginal one.

Adds an opt-in `trendContext` option to `patternChain`:

- `trendMethod: "sma-slope" | "ema-slope" | "pct-change"` — built-in
  trend measures (src/trend.js), signed fractions comparable across
  price levels.
- `externalTrend` / `trendFn` — escape hatches for callers with a more
  advanced trend/regime model, mirroring #96/#97's design for
  volatility (this package implements neither GARCH nor an HMM itself).
- Each match derives its expected preceding-trend direction from its
  existing `type`+`direction` metadata (src/contextFit.js):
  reversal patterns expect the OPPOSITE trend, continuation patterns
  expect the SAME trend, neutral patterns expect nothing. This is the
  exact rule that resolves the hammer/hangingMan contradiction above.
- Results carry `trendContext` (a coarse label) and `contextFit` (0-1).
  `enrichWithMetadata` additionally computes `effectiveConfidence`
  (`confidence * contextFit`) — the trend-aware alternative to the
  now-deprecated static `confidence` (kept for backward compatibility,
  marked `@deprecated` in JSDoc/types, not scheduled for removal before
  a major version).
- `resolveConflicts: true` optionally drops the lower-`contextFit` side
  of a same-candle, opposite-direction conflict (default: surface both).

Reuses `src/seriesResolver.js` (#97) for the method/external/callback
resolution, same precede... (continued)

884 of 893 branches covered (98.99%)

Branch coverage included in aggregate %.

346 of 346 new or added lines in 5 files covered. (100.0%)

3254 of 3260 relevant lines covered (99.82%)

15716.31 hits per line