Compliance docs: Stop scan, the 6-hour bound

Task 6605 changed the Compliance matrix. Three reader-doc pages now describe the old behaviour: - apps/docs/content/using-jaah/compliance/run-a-compliance-scan.md (steps 5 and the Rescan all bullet): say that **Stop scan** appears while a scan runs and turns each waiting row into **Scan error**; that a run with no result after 6 hours turns into **Scan error** on its own; that **Rescan all** comes back once no row is still scanning; that a row keeping an earlier level shows **Result from <time>**; and that **Order** now works during a scan, with rows still scanning kept last. - apps/docs/content/using-jaah/compliance/how-compliance-works.md (§ Scanning): same facts, briefly. - apps/docs/content/administration/security-and-audit/repository-compliance.md: check it for "Scanning…"/Order wording and update if stale. Out of scope: any code change; rule content, packs, the Architectural Guard. Done means: the three pages describe Stop scan, the time bound, "Result from", and sorting while scanning; `./dc check full` green.

Three Compliance reader docs now cover Stop scan, the 6-hour Scan error bound, Rescan all returning, Result from <time> and Order while scanning. Full gate green (2nd run; 1st docs link check transient). PR #5603 merged; dev Jaah Deploy succeeded.