v1.13.1

Fixed

• The review-workflow flag no longer changes what a write stores. In
  v1.13.0, cerefox_ingest_document read review_workflow_enabled on the
  write path and stored approved for every author while the workflow was
  off. That was never the intent — the flag is a view/hide switch, the rule
  underneath keeps running — and it quietly made a stored approved mean two
  different things depending on when it was written: a document an agent
  wrote during an "off" month came back approved once the flag was on
  again, indistinguishable from one a person had actually approved. The RPC
  now decides from author_type alone (agent → pending_review, user →
  approved) whatever the flag says; the flag governs only what surfaces
  show and enforce, exactly as documented. Turning it off and later back on
  shows the statuses the store would have had all along. The Settings
  confirmation text, cerefox doctor's OFF line and the guides say so now.
  Schema 0.16.0 → 0.16.1 (RPC-only, no migration; cerefox server deploy re-applies it). minSchema is unchanged: a 0.16.0 server merely
  keeps the v1.13.0 write behaviour until redeployed. GPT Actions OpenAPI
  3.4.0 → 3.4.1 (description text only).
• One name for the caller on every MCP tool: author. The tools had
  named the caller's identity inconsistently since v1.3.0 — author on
  ingest and set_document_projects, requestor on the reads and on the
  partial edits, both on delete/restore/set_document_metadata — and an agent
  reading the schemas literally concluded, correctly, that cerefox_insert
  and cerefox_edit had no author at all. Every tool now lists a single
  author parameter (reads included: it is the name recorded in the usage
  log). requestor is accepted silently on every tool as a compatibility
  alias, so nothing written against the old schemas breaks; when both are
  passed, author wins. One real behaviour change, stated because it is
  the only call that cannot be made invisible: on cerefox_get_audit_log,
  author used to be the entries filter; that filter is now by_author,
  and author is your identity there as everywhere else. An MCP caller that
  filtered the audit log with author: "X" now gets the unfiltered log
  (and is logged as "X") until it switches to by_author. The CLI's
  audit list --author filter and the cerefox-get-audit-log Edge Function
  body are separate surfaces and did not change. The remote MCP transport's
  require_requestor_identity enforcement accepts either name. The CLI flags
  (--author on writes, --requestor on reads) and the primitive Edge
  Function bodies used by GPT Actions are unchanged. AGENT_GUIDE.md,
  AGENT_QUICK_REFERENCE.md (and so cerefox_get_help) name the parameter
  consistently now.