Update to Mathbox

{
  "description": "Integrate an already validated mathematical result, correction, citation, or referee response into an authoritative LaTeX manuscript while preserving hypotheses, evidence status, notation, and dependencies. Use only when the user explicitly requests manuscript integration. Do not use to invent a proof or to perform routine copyediting.",
  "included_files": [
    {
      "relative_path": "agents/openai.yaml",
      "size_in_bytes": 282
    },
    {
      "relative_path": "evals/evals.json",
      "size_in_bytes": 2950
    },
    {
      "relative_path": "evals/trigger-evals.json",
      "size_in_bytes": 501
    },
    {
      "relative_path": "references/integration-checklist.md",
      "size_in_bytes": 903
    }
  ],
  "name": "manuscript-integrate",
  "skill_md_contents": "---\nname: manuscript-integrate\ndescription: >-\n  Integrate an already validated mathematical result, correction, citation, or referee response into an authoritative LaTeX manuscript while preserving hypotheses, evidence status, notation, and dependencies. Use only when the user explicitly requests manuscript integration. Do not use to invent a proof or to perform routine copyediting.\n---\n\n# Manuscript integration\n\nTransfer validated mathematics into the live manuscript. Integration does not\nsupply mathematical validation or human review.\n\n## Preconditions\n\n1. Determine repository root, inspect the worktree, and read applicable\n   instructions.\n2. Resolve the authoritative manuscript, proof source, current status/claims,\n   conventions, literature ledger, bibliography, and verification commands.\n3. Identify the exact validated result and its evidence/review status.\n   If `.mathbox/` is present, use the available `research-state` workflow to\n   check the current claim revision, artifact freshness and dependency closure.\n   Read the proof itself; a generated `proved` label does not validate it.\n4. Stop if the source proof conflicts with current status or the target\n   manuscript is ambiguous.\n5. If a required external theorem has not been checked, pause integration and\n   route that source question through the available `literature-check` skill\n   (`mathbox:literature-check` in plugin installations). That workflow checks an\n   authorized project-local cache before fetching. Resume only after the exact\n   source implication is verified. If the skill is unavailable, perform the\n   exact-source check directly. If the source remains unavailable, keep that\n   result conditional rather than supplying validation here. Continue any\n   independent, already validated integration work the user authorized.\n\n## Build the integration map\n\nState:\n\n- source theorem/lemma/correction and durable location;\n- target section and theorem hierarchy;\n- exact hypotheses, coefficient regime, grading, signs, variance, range, and\n  exceptions;\n- notation translation;\n- external dependencies and citations;\n- downstream statements, introduction claims, examples, and cross-references\n  affected;\n- project maps, theorem inventories, source guides, status files and verification\n  benchmarks whose meaning depends on the changed scope;\n- validation plan and human-review obligation.\n\n## Edit\n\n- Change the smallest coherent manuscript region.\n- Keep hypotheses adjacent to the claim and preserve every limitation.\n- Distinguish internal proof, external input, computation, heuristic, and open\n  question.\n- Do not make a publishable theorem depend accidentally on an optional stronger\n  conjecture or unfinished route.\n- Preserve historical source files; correct the live manuscript and record the\n  correction rather than rewriting chronology.\n- Update notation, theorem names/numbers, references, citations, introduction,\n  comparison, and outlook only where the result requires it.\n- For a scope removal or restriction, search every project-declared dependent\n  view before claiming consistency. Update authorized dependents together; if a\n  protected or separately governed file cannot be changed, mark the exact\n  conflict in the live view and do not report the propagation complete.\n- Do not edit generated output or bibliography entries without checking the\n  project's source convention.\n\nUse [integration-checklist.md](references/integration-checklist.md) for\nload-bearing theorem changes.\n\n## Synchronize durable state\n\nWhen the mathematical state changes, update the durable proof, claims/status,\none standalone research record, and its compact history-index entry together.\nUse the project-designated paths, or `research/records/` and `RESEARCH_LOG.md`\nby default. Do not put route details in the index, rewrite indexed history, or\nlog routine prose or formatting. Keep any specialist or human-review obligation\nopen until it has actually occurred.\n\n## Verify\n\n1. Perform a conservative pass with the `mathbox:proofread-math` plugin skill\n   over the changed TeX and needed context.\n2. Run the documented targeted mathematical verifier.\n3. Run the appropriate out-of-tree or canonical manuscript build.\n4. Inspect undefined references/citations, warnings in the changed region,\n   theorem numbering, bibliography changes, and `git diff --check`.\n5. Search for the superseded statement, scope and terminology across declared\n   dependents; classify each remaining occurrence as current, historical or\n   stale.\n6. Review the final diff for unintended semantic or generated-file changes.\n\n## Report\n\nReport the integrated result, files changed, source evidence, claim/status\nchanges, commands and warnings, unresolved mathematical or manuscript risk, and\nremaining human review.\n"
}