Publish curated RepoPulse source from d5e4a9e3bf5b0a127b751c9fba917b5e40be41d5

PUBLIC_SOURCE_EXPORT.md

@@ -1,3 +1,3 @@
 # Public source export
 
-This source snapshot was generated from the private canonical repository at revision `3d59b4f5c726a1c060e1af7c8dc2ec37ddd48f84`. It contains no private Git history or operational evidence. Changes are published from the canonical repository.
+This source snapshot was generated from the private canonical repository at revision `d5e4a9e3bf5b0a127b751c9fba917b5e40be41d5`. It contains no private Git history or operational evidence. Changes are published from the canonical repository.

PUBLIC_SOURCE_MANIFEST.json

@@ -1,6 +1,6 @@
 {
   "schemaVersion": 1,
-  "sourceRevision": "3d59b4f5c726a1c060e1af7c8dc2ec37ddd48f84",
+  "sourceRevision": "d5e4a9e3bf5b0a127b751c9fba917b5e40be41d5",
   "files": [
     {
       "path": ".dockerignore",
@@ -29,8 +29,8 @@
     },
     {
       "path": "README.md",
-      "sha256": "daf72438ac9243a092c38f5d3b8d7131245142d4a800dae91ac84fe874ab4814",
-      "bytes": 5271
+      "sha256": "a70daf2bbd2ac9fcf74b407901f07d9324ca05a486e117e7eb89d722d35e1ae9",
+      "bytes": 5879
     },
     {
       "path": "backend/Dockerfile",

README.md

@@ -59,6 +59,12 @@ Use only the repository-read permissions needed for the intended catalog and rev
 
 Protect deployment with an authenticated proxy or configure `REPOPULSE_OPERATOR_TOKEN`; the mutation API uses `X-RepoPulse-Token`. Limit network access and the scan mount. Direct development without `REPOPULSE_SCAN_ROOT` can read any path accessible to that process.
 
+## Run your first repository review
+
+Choose one repository from the Gitea catalog or an allowed local path, queue a scan and wait for its completion. Confirm the recorded revision and coverage limits, then open the highest-priority finding and inspect its location and rationale. Use subsequent scans to compare finding deltas after a change.
+
+Resolve connector or acquisition failures before interpreting a stale report as the latest repository state. A clean scan means that no enabled heuristic reported a finding within the scan budget; it is not proof of security, correctness or deployment readiness.
+
 ## Interpret results
 
 Findings are deterministic observations with locations and severity. Health scores reflect documented deductions; release gates report **READY**, **READY WITH WARNINGS** or **BLOCKED** under repository policy. Remediation guidance explains confidence, priority and a suggested first action. RepoPulse never edits external repositories automatically.