You are a builder agent working ONE issue of the Arcodange erp backlog, end-to-end, unattended.

Ground rules:
- Your working directory is an isolated git worktree of the erp repo, on branch `arcodange/known-patterns-fix`. Work ONLY inside it.
- Read AGENTS.md at the repo root first (orientation + operating rules), then the SKILL.md of anything you touch. A change that makes a documented claim false updates that doc in the same commit.
- Commit your changes on the current branch with a conventional-commit message (e.g. `fix(bank-reco): ...`). Do NOT push. Do NOT open a PR. Do NOT post to Gitea.
- Skill credential .env files are gitignored and absent from this worktree; if a command needs one, the operator's copies live at /Users/gabrielradureau/Work/Arcodange/erp/.claude/skills/<skill>/.env (read-only APIs). If a credentialed command cannot run, report that honestly in EVIDENCE instead of fabricating output.
- End your final message with a section titled `EVIDENCE:` containing (1) what changed and why, (2) the output of `git log --oneline -3` and `git diff HEAD~1 --stat`, (3) the output (or honest failure) of the acceptance command.

The issue you are executing — erp#56 (verbatim):
---
Title: fix(bank-reco): known-patterns.json — Mistral is an ANNUAL subscription, not monthly

Small correction from the 2026-07-11 regularization (source: the actual invoice PDF `MSTRL-API-814045-001`, 2026-04-02, "Abonnement annuel - Le Chat Pro - Annual", 143,90 HT / 172,68 TTC).

`.claude/skills/arcodange-bank-reco/known-patterns.json` currently documents the MISTRAL.AI card debit as "Récurrent mensuel" — it is **annual** (next expected ~2027-04). This mis-set expectation cost investigation time ("where are the May/June Mistral debits?" — there are none).

While in there:
- Anthropic (CLAUDE.AI SUBSCRIPTION) pattern: April was on the Qonto card, but the **May/June receipts (#2344-8391, #2997-4837 in books@) have no Qonto debit** — probably the personal card (fk_account=3, API-invisible). Document the pattern as "payment rail moved — personal-card lane, see #57".
- Both AI subscriptions are now RECORDED supplier invoices (post-replay), so these patterns may graduate from "known bank-only gap" to "matched" — re-check what `bank match` reports after the prod replay and prune accordingly.

**Acceptance:** `bank match --since 2026-01-01` after the prod replay shows no stale "intentional gap" annotations for entries that are now properly recorded.

---
**Execution** — Blocked by: the **prod replay** of the 2026-07-11 pack (the re-check depends on it; the annual-vs-monthly text fix itself can land anytime) · Blocks: none · Human gates: none.
**Start:** `claude --worktree known-patterns-fix` from the erp repo root; edit `.claude/skills/arcodange-bank-reco/known-patterns.json`, then (post-replay) run `bank match --since 2026-01-01`.
**Done means:** corrected patterns + post-replay match output posted here → PR merged with `Closes #56`.
---

Note on the "Blocked by" line: the prod replay of the 2026-07-11 pack was executed on 2026-07-15 (erp PR #64), so the re-check is unblocked. `bank match` is run as `bin/arcodange bank match --since 2026-01-01`.