docs(api): replace generic contracts with actionable lifecycle and failure semantics #18

Documentation quality gap

The XML/Wiki syntactic gates pass, but some public summaries and parameter descriptions remain generic templates. Correct signatures, tags and compilable examples do not establish that callers understand ownership, concurrency, failure, missing state or reload constraints.

Owner: each API's source project and corresponding Wiki page, with existing architecture/Wiki validation retained.

Work

Prioritize public resource, build, scripting, plugin, identity, history and extension contracts. Review actual callers and execution chains. State ownership transfer, borrowing, cancellation, thread/safe-point requirements, partial failure, nullable outcomes and generation retirement where applicable. Do not invent guarantees or document internal APIs as stable public contracts.

Acceptance

• Meaningful English public/protected XML and synchronized current Chinese Wiki guidance.
• Small compilable examples cover success and important failure/lifetime cases.
• Public API coverage, links, reference grouping and Wiki compilation remain valid.
• Review evidence distinguishes semantic review from automated syntax checks.

Evidence: documentation risk recorded in records/architecture/acceptance/FULL_ENGINE_AUDIT_2026_10_24.md.

Editor UI subset tracked by #27 and #39

Review every API changed by the Editor UI closure, including Graph presentation, frozen compiler inputs and lifecycle changes. Document ownership, thread/borrow boundaries, cancellation, failure, Missing and generation semantics with current examples. This subset does not complete the repository-wide documentation audit. PR #26 must use Refs #18 unless the full original acceptance is independently achieved.