Use this first to discover the ``doc_id`` values and document
    classes available before calling ``render`` or ``audit_pdf``. For
    just the document count (a connectivity probe) call ``doc_count``
    instead; to read the raw manifest text use the ``inclusio://meta``
    resource. Reads ``data/meta.yaml`` under ``INCLUSIO_CONTENT_DIR``
    (or the packaged content root); it writes nothing.

    Returns one dict per document with id, class, src, title, and
    any `pdf_a` / `note` flags. Empty list when no manifest exists.
    

    Use this to check whether a rendered PDF meets PDF/UA-2, WTPDF, and
    PDF/A-4f before publishing; it shells out to ``verapdf`` read-only
    and never modifies the PDF or the manifest. To produce a document's
    source first call ``render``; to see which documents exist call
    ``list_docs``. This inspects existing PDFs only — it does not build
    them.

    Args:
        target: PDF path or directory. Defaults to `build/` under
            INCLUSIO_CONTENT_DIR.
        strict: When True, every blocking-flavour FAIL is surfaced
            in the response (`blocking_failure: True`); the caller
            decides whether to treat this as an error.

    Returns the audit report dict (summary, by_pdf, by_flavour).
    Requires `verapdf` on PATH; the report contains
    `verapdf_present: False` when it is not.
    

    Use this to materialise a document's source (LaTeX, Markdown, JSON,
    or text) into ``build/.cache/rendered/`` before compiling or
    auditing it. This writes the rendered output file but never mutates
    ``data/meta.yaml``. Discover valid ``doc_id`` values with
    ``list_docs`` first; audit the resulting PDF afterwards with
    ``audit_pdf``. This is the only write tool on this server — the
    others are read-only.

    Args:
        doc_id: registered template id (see `list_docs`).
        fmt: one of `latex`, `markdown`, `json`, `text`.
        mode: one of `draft`, `submission`, `camera-ready`.

    Returns `{"doc_id": …, "format": …, "output_path": …, "bytes": int}`.
    

    Use this as a cheap connectivity/health probe to confirm the server
    sees a valid manifest without transferring the full document list.
    When you need each document's id, class, and flags, call
    ``list_docs`` instead.

    Cheap probe for clients that just want to verify connectivity
    and that the engine sees a valid manifest.