Publish curated RepoPulse source from d5e4a9e3bf5b0a127b751c9fba917b5e40be41d5

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.