Yichus / Reference / API MCP tools
api_fact_diff
Diff the fact families between two versions of a program: which agenda cards appeared, vanished or changed, so a review reads the DELTA a change made rather than re-reading the whole program. Optional delta claims are checked against the same report and answered with refuted, exactly as api_verify_claims answers claims about one version. Same job as yichus fact-diff, which reads the two versions from disk and turns refutals into a nonzero exit code.
Kind: FactDiff. Family changes: MCP servers list it once api_tools opens that family. Origin: Yichus/Mcp::catalog.
CLI: yichus fact-diff — the same FactDelta over two program versions; the CLI reads them from two sets of paths and the tool from before_sources and after_sources; the declared entry packages are --entry on the CLI and entries on the tool.
Parameters
before_sources(required, array) — JSON array of {fileName, source} for the BEFORE version.after_sources(required, array) — JSON array of {fileName, source} for the AFTER version.claims(optional, object) — Optional JSON object with a claims array, each claim naming a subject and the change it asserts.entries(optional, array) — Optional JSON array of the program's entry package names, e.g. ["Demo/App"], the unused-export premise as in api_explore's agenda, applied to both versions: declared, unused-export cards are drawn and diffed; absent, they are not drawn and a delta claim about them is not-provable. A name either version does not supply fails the call, naming that version.
Read the result according to this tool’s scope: static checks, bounded execution checks, and descriptive diagrams answer different questions. A successful call is not a general approval of the program. The safety and permissions guide compares the checks and provides editable ownership, guard, and role examples.