Add discovery connector follow-up

docs/repo-reality-scanner.md

@@ -131,6 +131,52 @@ 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.
 
+## Connector Follow-Up
+
+Connector follow-up is explicit and separated from repo-local extraction:
+
+```bash
+railiance-fabric scan . \
+  --repo-slug railiance-fabric \
+  --connector local-fabric-registry \
+  --connector-manifest registry/local-repos.yaml \
+  --dry-run
+```
+
+The connector interface has slots for:
+
+- package registries
+- container registries
+- API catalogs
+- service catalogs
+- deployment inventories
+- existing Fabric registry data
+
+The first implementation is `local-fabric-registry`, an offline-safe connector
+that reads a local onboarding manifest such as `registry/local-repos.yaml`. It
+adds a `FabricRegistryEntry` candidate, a `cataloged_as` edge from the
+repository node, and registry-sourced attributes such as domain, remote URL,
+default branch, State Hub repo id, and declaration paths.
+
+Connector evidence uses its own replacement scope with source kind
+`fabric_registry`, so rescans can replace catalog facts without retiring
+repo-local evidence. Connector run metadata is recorded under `connector_runs`
+with status, source, message, and candidate counts.
+
+Connector-derived facts should be treated this way:
+
+- accepted: only when the connector reads explicit repo-owned declarations or a
+  catalog already governed as authoritative for that field
+- candidate: stable local registry facts such as onboarding manifest entries,
+  declared remote URLs, State Hub ids, and declaration paths
+- review-only: missing catalogs, rate limits, connector failures, ambiguous
+  matches, or facts from catalogs with unclear ownership
+
+Failures do not corrupt the scan. Missing catalogs become
+`connector_unavailable` review artifacts, malformed catalogs become
+`connector_failed` artifacts, and future remote connectors should use
+`connector_rate_limited` when backoff is required.
+
 ## Identity
 
 Identity is the main safety boundary. The scanner must not append guesses on