Add report fragments and export manifest

docs/ASSESSMENT-OPERATIONS.md

@@ -79,6 +79,7 @@ A completed CLI command prints a JSON result with:
 - `assessment_package`: JSON assessment package path,
 - `report`: Markdown report path,
 - `submission_package`: portable submission package manifest path,
+- `export_manifest`: portable generic JSON export manifest path,
 - `retention_summary`: compact durable summary path.
 
 The output directory uses this contract:
@@ -95,7 +96,9 @@ normalized/findings.json
 normalized/mappings.json
 reports/assessment-package.json
 reports/report.md
+reports/fragments.json
 reports/submission-package.json
+exports/export-manifest.json
 artifacts/
 ```
 
@@ -107,6 +110,12 @@ raw artifact manifest, and repeats the certification boundary. It is a portable
 handoff manifest for preparation evidence, not an authority-specific final
 submission.
 
+Extension report fragments are recorded in `reports/fragments.json`, embedded in
+`reports/assessment-package.json`, and rendered into the Markdown report.
+`exports/export-manifest.json` is the first generic portable export surface. It
+is derived from the assessment package and carries summary, policy, mapping,
+fragment, count, source-lock, and boundary references.
+
 Use the retained run helpers for history:
 
 ```sh
@@ -121,6 +130,10 @@ PYTHONPATH=src python3 -m guide_board runs trend --runs-dir runs
 PYTHONPATH=src python3 -m guide_board runs gate --runs-dir runs
 ```
 
+Trend summaries include status changes, unexpected finding deltas, unresolved
+review deltas, mapping target deltas, evidence result deltas, and a compact
+human-readable summary string for each target/assessment pair.
+
 ## Local Service Flow
 
 Start the service from the guide-board repository: