Point certification artifacts at the private archive by key only

Two public docs named the private sibling repo and its directory layout
as the artifact location. Keep the dated archive key so the artifacts
stay findable, drop the repo-internal path from public view.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

docs/synthid.md

@@ -779,5 +779,6 @@ initially took a flat `0.30` floor instead of the area curve. The later provider
 remeasurement established a common pass at `0.25` across three valid sources and
 separately repeated `QWEN_ZIMAGE_GOOGLE_STRENGTH = 0.27` across those sources and
 three accounts. OpenAI now has its own measured flat operating point; unknown
-content keeps the resolution curve. An explicit strength still wins. Certification artifacts: raiw-app
-`data/certification/text-restoration-2026-08-18/` (the failing re-baseline).
+content keeps the resolution curve. An explicit strength still wins.
+Certification artifacts: private archive `text-restoration-2026-08-18` (the
+failing re-baseline).

docs/text-protection-research.md

@@ -367,5 +367,5 @@ against base MAEs of 24.7/16.8/10.2. Since 0.27.1 the anchor is off by default
 (`fidelity_anchor` parameter on `remove_watermark` / `InvisibleOptions` /
 `--fidelity-anchor`); Google rows were not re-queried because the default
 strength leaves that fixture's base detected (the vendor-strength lane tracks
-that separately). Certification artifacts: raiw-app
-`data/certification/text-restoration-2026-08-19-A1/` (sha256-stamped rows).
+that separately). Certification artifacts: private archive
+`text-restoration-2026-08-19-A1` (sha256-stamped rows).