v2.5.0 — Technical context

Technical context brings a small, deterministic observation set into comparison
briefings through an explicit, default-off selection. Trend, momentum and
unannualized volatility use each asset's own eligible Yahoo adjusted observations.
Exact formulas, dates, source identities and supporting closes are inspectable;
short or unsupported history remains unavailable while prices stay usable.
Deep may offer conditional interpretations from supplied evidence. Reference
checks do not certify reasoning, source adjustments, sessions or bar completion.

Implementation PRs #242–#245 are merged. The maintainer confirmed the completed
workflow works as intended on 2026-11-02. No new provider, dependency, embedding
or database migration is introduced. Release preparation passed build-and-test, clean-install and PostgreSQL contract
checks and merged as #246. Published with maintainer authorization from fad1c95.

Added

• Technical briefing browser workflow (v2.5) — a default-off Technical
  observations selector sits beside news/macro, including technical-only requests.
  Citations open exact metrics, formulas, own dates, provenance and supporting
  adjusted closes. Partial/unsupported inputs remain visible without invented
  zeros. Client validation rejects wrong scope, metadata, conventions, windows
  and references; changing scope cancels and clears old work without automatic
  generation or replay. No client-side indicator calculation is introduced.
• Opt-in technical briefing evidence (v2.5) — context APIs accept an explicit
  default-off technical selection, projected from the same fresh price snapshot
  without another history fetch. Exact per-asset metrics, source identities,
  supporting dates/values and quality caveats get packet-local references.
  Interpretation must cite usable metrics with their linked pairs and acknowledge
  each available asset; unavailable metrics and group/section IDs cannot replace
  numerical evidence. Existing Deep deadlines/repair/cancellation remain;
  price-only synthesis stays scoped.
• Deterministic technical observations (v2.5) — comparison responses add a
  20-close mean gap, 20-period return and unannualized sample volatility of 20
  returns, computed from the bounded adjusted-input contract. Per-metric dates,
  formulas, units, history requirements and stable observation identities make
  calculations inspectable; insufficient/invalid inputs stay unavailable rather
  than becoming zero or shorter periods. Existing price/drawdown outputs remain
  unchanged.
• Technical input contract (v2.5 foundation) — comparison responses expose
  independently assessed own-date Yahoo adjusted inputs, exact provenance/window
  and stable identities. A bounded source copy preserves defects and metadata
  before adapter normalization; incomplete, conflicting or unsupported inputs
  are withheld without blocking prices or fetching another provider. Adjustment,
  session and bar-completion verification remain explicitly unclaimed.