fix: triage is lenient on OpenClaw-curated content

Auto-triage was rejecting 8 of 10 OpenClaw imports as 'session log'
or 'process rule belongs elsewhere'. But OpenClaw's SOUL.md, USER.md,
MEMORY.md and daily memory/*.md files are already curated — they ARE
the canonical continuity layer we want to absorb. Applying the
conservative LLM-conversation triage bar to them discards the signal
the importer was designed to capture.

Triage prompt now has a rule 4: when candidate content starts with
'From OpenClaw/' apply a much lower bar. Session events, project
updates, stakeholder notes, and decisions from daily memory files
should promote, not reject.

The ABB-Space Schott quote that DID promote was the lucky exception
— after this fix, the other 7 daily notes (CDR execution log,
Discord migration plan, isogrid research, etc.) will promote too.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

src/atocore/config.py

@@ -104,6 +104,21 @@ class Settings(BaseSettings):
 
     @property
     def resolved_project_registry_path(self) -> Path:
+        """Path to the project registry JSON file.
+
+        If ``ATOCORE_PROJECT_REGISTRY_DIR`` env var is set, the registry
+        lives at ``<that dir>/project-registry.json``. Otherwise falls
+        back to the configured ``project_registry_path`` field.
+
+        This lets Docker deployments point at a mounted volume via env
+        var without the ephemeral in-image ``/app/config/`` getting
+        wiped on every rebuild.
+        """
+        import os
+
+        registry_dir = os.environ.get("ATOCORE_PROJECT_REGISTRY_DIR", "").strip()
+        if registry_dir:
+            return Path(registry_dir) / "project-registry.json"
         return self._resolve_path(self.project_registry_path)
 
     @property