Implement project reports in HTML, PDF, and CIF

.codecov.yml

@@ -4,6 +4,11 @@
 github_checks:
   annotations: true
 
+ignore:
+  - 'src/easydiffraction/report/templates/html/vendor/**'
+  - 'src/easydiffraction/report/templates/tex/styles/**'
+  - 'src/easydiffraction/utils/_vendored/jupyter_dark_detect/**'
+
 comment:
   layout: 'reach, diff, flags, files'
   behavior: default

.codefactorignore

@@ -1,11 +1,13 @@
 # CodeFactor exclude patterns configuration must be done online:
 # https://www.codefactor.io/repository/github/easyscience/diffraction-lib/ignore
 #
-# Last updated: 2026-01-05
+# Last updated: 2026-05-29
 #
 # Exclude patterns:
 # deps/**
 # docs/**
+# src/easydiffraction/report/templates/html/vendor/**
+# src/easydiffraction/report/templates/tex/styles/**
 # src/easydiffraction/utils/_vendored/jupyter_dark_detect/**
 # tests/**
 # tmp/**

.prettierignore

@@ -25,6 +25,11 @@ docs/docs/assets/
 # Node
 node_modules
 
+# Vendored snapshots
+src/easydiffraction/report/templates/html/vendor/
+src/easydiffraction/report/templates/tex/styles/
+src/easydiffraction/utils/_vendored/jupyter_dark_detect/
+
 # Misc
 .benchmarks
 .cache

THIRD_PARTY_LICENSES.md

@@ -0,0 +1,13 @@
+# Third-Party Licenses
+
+This file indexes third-party assets vendored in this repository.
+
+## Report LaTeX Styles
+
+The vendored report LaTeX style files are documented in
+`src/easydiffraction/report/templates/tex/styles/LICENSES.md`.
+
+## Report HTML Assets
+
+The vendored report HTML assets are documented in
+`src/easydiffraction/report/templates/html/vendor/LICENSES.md`.

docs/dev/adrs/accepted/analysis-cif-fit-state.md

@@ -25,6 +25,7 @@ Analysis-owned fit state needs to persist:
 - fit bounds and bound provenance
 - pre-fit scalar snapshots for recovery workflows
 - compact status metadata for the latest saved fit projection
+- software-provenance snapshot for the latest successful fit
 - deterministic correlation summaries
 - minimizer-specific fit outputs on the paired `_fit_result.*` category
 - per-parameter posterior summaries on `_fit_parameter`
@@ -104,6 +105,34 @@ round-trip project schema remains common.
 correlation summaries keyed by a persisted `id`. Only unique parameter
 pairs are stored.
 
+### Software provenance
+
+`_software` stores the runtime software snapshot recorded after a
+successful fit. It is part of the project save / load contract and feeds
+report rendering plus the IUCr export software labels. It is not a user
+configuration category.
+
+The category stores name, version, and URL triples for:
+
+- `framework`
+- `calculator`
+- `minimizer`
+
+Each role is persisted as scalar items on the same category:
+
+- `<role>_name`
+- `<role>_version`
+- `<role>_url`
+
+The category also stores:
+
+- `timestamp`
+
+`timestamp` is an ISO-8601 UTC string for the fit that produced the
+snapshot. Projects saved before this category existed load with all
+software fields unset and `timestamp` set to `None`; rerunning a fit
+populates the snapshot.
+
 ### Minimizer fit projection
 
 The active `_minimizer.*` category stores user-selected solver inputs
@@ -230,9 +259,10 @@ Load order is:
 
 1. standard analysis configuration
 2. `_minimizer.*` settings according to the active `_minimizer.type`
-3. common and family-specific `_fit_result.*` fields on the paired class
-4. `_fit_parameter` and `_fit_parameter_correlation`
-5. posterior sidecar arrays when a Bayesian result is expected
+3. `_software.*` provenance fields when present
+4. common and family-specific `_fit_result.*` fields on the paired class
+5. `_fit_parameter` and `_fit_parameter_correlation`
+6. posterior sidecar arrays when a Bayesian result is expected
 
 Persist backend runtime objects, optimizer instances, and raw driver
 payloads nowhere in this design.

docs/dev/adrs/accepted/project-facade-and-persistence.md

@@ -16,7 +16,8 @@ Persistence.
 
 `Project` is the top-level user facade. It owns project metadata,
 structures, experiments, rendering preferences, display helpers,
-analysis, report helpers, verbosity, and save/load behavior.
+analysis, report helpers, publication metadata, verbosity, and save/load
+behavior.
 
 A later proposal considered renaming this facade to `Workspace` so that
 `project` could be reserved for the scientific project information
@@ -50,9 +51,18 @@ through `project.report` and written only when requested, using
 `reports/<project>.cif`; default project saves do not write
 `summary.cif`.
 
-Expose submission-report helpers as `project.report`. The previous
-`project.summary` placeholder and its `summary.cif` output are not part
-of the persistence layout.
+Expose submission-report helpers as `project.report`. This facade is a
+hybrid surface: its scalar output configuration persists to
+`project.cif` as `_report.*`, while its methods render report artifacts
+under `reports/`. The previous `project.summary` placeholder and its
+`summary.cif` output are not part of the persistence layout.
+
+Expose journal-submission metadata as `project.publication`. It is a
+top-level owner with CIF-aligned sibling categories for `_journal.*`,
+`_journal_date.*`, `_journal_coeditor.*`, `_publ_contact_author.*`,
+`_publ_body.*`, and the `_publ_author.*` loop. These singleton
+publication categories persist in `project.cif` and feed report exports;
+`reports/<project>.cif` remains export-only.
 
 Keep project information available as `project.info`. The Python name
 avoids a confusing `project.project` access path, while the persisted
@@ -79,6 +89,11 @@ The saved project directory path is runtime file-I/O state, not a
 serialized project-information field. If the path is exposed in Python,
 it must not emit a `_project.path` CIF item.
 
+The project-level singleton categories currently persisted in
+`project.cif` are `_project.*`, `_chart.*`, `_report.*`, `_table.*`,
+`_verbosity.*`, `_journal.*`, `_journal_date.*`, `_journal_coeditor.*`,
+`_publ_contact_author.*`, `_publ_body.*`, and the `_publ_author.*` loop.
+
 ## Consequences
 
 The saved layout mirrors the current object graph while preserving the