Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
3 changes: 0 additions & 3 deletions developer_manual/api/_external-email-signers-release.inc
Original file line number Diff line number Diff line change
Expand Up @@ -44,6 +44,3 @@ the exact source commit used in this build is in the linked provenance:
* `Guest signing and visible signature <https://github.com/LibreSign/libresign/blob/stable33/playwright/e2e/sign-envelope-unauthenticated-visible-signature.spec.ts>`_
* `Unauthenticated email-token signing <https://github.com/LibreSign/libresign/blob/stable33/playwright/e2e/sign-email-token-unauthenticated.spec.ts>`_
* `Sequential signing <https://github.com/LibreSign/libresign/blob/stable33/playwright/e2e/multi-signer-sequential.spec.ts>`_

**Evidence limit:** source tests are present; their existence does not
prove that SMTP, browser behavior or PDF signing passed in this deployment.
13 changes: 6 additions & 7 deletions developer_manual/api/external-email-signers.rst
Original file line number Diff line number Diff line change
Expand Up @@ -68,9 +68,9 @@ from the default LibreSign folder. Select this LibreSign release in the
workflow configuration: versions 13/14 use ``mandatory: 1``; versions
15/development use ``requirement: "required"``. Native completion events
belong to the development documentation and are not required by polling.
Automated discovery was exercised only on LibreSign 15.0.12; versions 13,
14 and development still require runtime verification. The link pins the
README and its relative 21-node JSON workflow to one immutable revision.
Confirm that this release meets the OCS and WebDAV prerequisites before
using the shared workflow. The pinned link keeps its README and relative
JSON workflow at the same immutable revision.
Do not replace release-specific cURL/PHP fixtures with development payloads.

.. include:: _external-email-signers-release.inc
Expand Down Expand Up @@ -220,9 +220,8 @@ Protect invitation links, App Passwords, signer metadata and PDFs.
Poll with backoff; native webhooks require a separately verified
LibreSign event contract for the deployed Nextcloud version.

The release-specific section links to browser-test sources from that
application branch. Their presence is source evidence; running them
against the installed release is still necessary to establish E2E behavior.
Contract checks cannot prove SMTP, browser signing or certificate trust.
Validate browser signing, SMTP delivery and certificate trust on the target
installation before relying on the integration. Contract checks alone do
not establish operational compatibility.

Consult the OpenAPI reference beside this page for exact schemas.
4 changes: 2 additions & 2 deletions developer_manual/integration/index.rst
Original file line number Diff line number Diff line change
Expand Up @@ -88,8 +88,8 @@ Read the relevant guide
WebDAV discovery and authenticated download in the default LibreSign
folder. The shared example selects the request schema for LibreSign
13/14 (``mandatory``) or 15/development (``requirement``). The discovery
step was exercised only on LibreSign 15.0.12; versions 13, 14 and
development still require runtime verification. Native completion
step requires default LibreSign storage and requester WebDAV access.
Verify these prerequisites on the target installation. Native completion
events are documented only for development; the workflow uses OCS polling.

Contract and ownership boundaries
Expand Down
7 changes: 1 addition & 6 deletions style_guide.rst
Original file line number Diff line number Diff line change
Expand Up @@ -2,8 +2,6 @@
LibreSign manuals style guide
=============================

*This is a work in progress*

See the `Documentation README <https://github.com/LibreSign/documentation/blob/main/README.rst>`_ for information on setting up your documentation build environment

See `reStructuredText Primer <https://www.sphinx-doc.org/en/master/usage/restructuredtext/basics.html>`_ for a complete
Expand Down Expand Up @@ -131,10 +129,7 @@ or add a caption. Captions must follow a blank line and be italicized, like this
*Figure 1: The file listing and administration page.*

Images must go into a sub-directory of the directory containing your manual
page. Currently the manuals have both a single master images directory, and
image directories local to each chapter. A single master images directory is
difficult to maintain and inevitably becomes cluttered with obsolete images. Eventually
the single master directories will be gone.
page.

Example URL
-----------
Expand Down
Loading