v0.7.0

Input validation and point-in-time correctness. This release contains a

breaking request-schema change.

- Replaced the vendor-specific `tickVolume` and `realVolume` inputs with one
  required `volume` field. Callers choose the activity or volume series before
  sending bars. Legacy volume fields are rejected instead of being silently
  preferred, ignored, or replaced with zero.
- Bars now require finite positive OHLC values, valid candle geometry, a
  finite non-negative volume, and strictly increasing unique UTC timestamps.
- Indicator specifications now reject unknown, malformed, and inconsistent
  parameters before calculation.
- Removed the inert `recentBars` request field from REST and MCP.
- Structural objects now expose origin, confirmation, observation, and
  mitigation timestamps where applicable. This separates where a pattern
  formed from when it became knowable.
- Previous-period high and low now use the immediately completed fixed UTC
  bucket. Weeks run Monday through Sunday. The nested aggregation bucket is
  independent of the top-level chart interval label.
- Session output is documented and validated as fixed UTC clock windows, not
  an exchange calendar or daylight-saving-aware schedule.
- Support and resistance now use a bounded 500-bar evidence window and require
  distinct touches to be at least five bars apart.
- Updated the REST schema, MCP contract, metadata catalog, agent skill, and
  README to describe the actual calculations and their limitations.