fix: YNAB API 1.86 parity (Milestone 0) + eval dry-run intent capture - #18

…ark report

Implements g57.8 (simulated mutation-intent capture) and completes the
reporting half of g57.5/g57.6:

- server: MCP_YNAB_EVAL_DRY_RUN_INTENTS_PATH opt-in intercepts every
  mutating handler (except the Code Mode dispatcher) and persists the
  validated payload to intended_writes.json instead of dispatching.
  No env var => production behavior unchanged.
- dual runner: per-surface intent artifacts seeded before each run,
  grading.json written for every task/config after runs finish.
- grading: deterministic assertions (completion, write-safety, expected
  read ops, task-specific text expectations, intended-write payload shape).
- benchmark: viewer-compatible benchmark.json + token-delta-first
  benchmark.md at the iteration root.
- evals.json: adds intent_expectation + text expectations to all tasks.
- README documents the dry-run recorder and benchmark workflow.

Raise the dependency floor to ynab>=4.3.0,<5 and refresh uv.lock. Pins
OpenAPI 1.86 contracts with focused tests:

- until_date exists on all five transaction-list methods
- goal_frequency is modeled on NewCategory (monthly/weekly/yearly)
- update_transactions decodes an HTTP 200 SaveTransactionsResponse
  (4.1.0 mapped bulk-write success to 209, which the live API no longer
  returns)
- get_transactions_by_category is owned by TransactionsApi, and the
  permissive CategoriesApi mock route is removed

…cp-ynab-parity-account-types)

The account formatter iterated only 8 of 13 AccountType values, silently
dropping cash, lineOfCredit, personalLoan, medicalDebt and otherDebt
accounts from display and totals.

- add the five missing types with display names and correct
  asset/liability classification (cash is an asset; the rest are
  liabilities)
- keep unknown future account types visible in their own group instead
  of dropping them; unknown types are never miscounted into totals
- use _format_dollar_amount for summary signs (fixes $-500.00 output)
- tests cover all 13 enum values, asset/liability totals, and unknown-type
  visibility

…p (mcp-ynab-parity-category-read)

get_transactions_by_category constructed CategoriesApi and called
get_transactions_by_category on it, but that method exists only on
TransactionsApi — a guaranteed AttributeError against a real SDK.
Permissive MagicMock tests invented the missing method and hid the bug.

- call TransactionsApi.get_transactions_by_category instead
- update unit tests to mock the TransactionsApi route
- add a real-SDK ownership assertion: TransactionsApi has the method,
  CategoriesApi does not

…r default (mcp-ynab-parity-unbounded)

API 1.85 defaults an omitted since_date to one year ago. merge_payees,
attention queries with days_back=None, "defaults to all" reconciliation
reads, and alternate-ID scans all relied on that implicit truncation and
could silently miss transactions older than one year.

- add date_bounds.ALL_HISTORY_SINCE_DATE (1970-01-01) as the explicit
  all-history bound
- merge_payees: pass the bound and report the scanned range in its output
- get_transactions_needing_attention: days_back=None now fetches all
  history and reports the range
- get_account_reconciliation_profile / subset-matches: since_date=None
  now means an explicit all-history bound
- alternate-ID resolution: transfer/matched ids scan all history instead
  of YNAB's default; unparseable import_id dates fall back to the bound
- regression tests cover every site, including pre-one-year fixtures

…parity-scheduled-dates)

The official API requires a scheduled transaction start date strictly in
the future and no more than five years out. create_scheduled_transaction
defaulted to local today and passed any value straight to the SDK.

- default start date is tomorrow in UTC (strictly future)
- today and past dates fail locally with a clear ValueError
- dates more than five calendar years out fail locally (Feb 29 handled)
- the exact five-year limit is accepted
- nothing invalid ever reaches the API (no HTTP 400 round-trip)
- tests cover UTC reference frame, today/past rejection, the five-year
  boundary, and over-limit rejection

…6 progress

Closed: mcp-ynab-parity-sdk, -account-types, -category-read, -unbounded,
-scheduled-dates, the Milestone-0 epic, and g57.8 (dry-run intent capture,
forced past the orthogonal g57.7 read-snapshot dependency).