Add discovery registry review flow

docs/repo-reality-scanner.md

@@ -131,6 +131,39 @@ is present in the current scan and has `mode: replacement`. Missing candidates
 from additive scopes, such as broad LLM evidence bundles, are left alone.
 Existing tombstones are preserved so repeated scans can explain graph drift.
 
+## Registry Review And Acceptance
+
+Discovery snapshots can be stored in the Fabric registry for review:
+
+```bash
+railiance-fabric scan . \
+  --repo-slug railiance-fabric \
+  --previous-snapshot previous-discovery.json \
+  --output discovery.json
+
+railiance-fabric registry ingest-discovery discovery.json \
+  --repo-slug railiance-fabric
+```
+
+The registry keeps discovery snapshots separately from accepted graph snapshots
+by repo, commit, and scan profile. It exposes latest/list/diff API routes so a
+dry run can be reviewed without changing the accepted graph.
+
+Accepted discovery can be projected into a normal graph snapshot:
+
+```bash
+railiance-fabric registry accept-discovery railiance-fabric 12 \
+  --accepted-key discovery:railiance-fabric:service-declaration:example
+```
+
+By default, the accept path only projects candidates already marked
+`review_state: accepted`. Passing `--accepted-key` explicitly includes selected
+candidate stable keys. Existing accepted graph nodes win over discovery nodes
+with the same graph id, so repo-owned declarations are preserved. Projected
+nodes carry discovery stable key, origin, review state, confidence, provenance,
+and source anchors in graph attributes; the graph explorer payload exposes
+those fields for review.
+
 ## Connector Follow-Up
 
 Connector follow-up is explicit and separated from repo-local extraction: