Neutral wording in import docs; portable tool output paths

Import-surface docs and docstrings describe the automation as a
migration script; status-doc references in CHANGELOG/ADR-009/ROADMAP
point at repo files. Screenshot/verify tools write to /tmp/shopdb-shots
(created on import) instead of a machine-specific directory.

scripts/site_imports/wjf/README.md

@@ -15,8 +15,8 @@ loader. Instead, copy the pattern:
    resolve foreign keys and a crashed run resumes.
 
 The import API is the stable contract; loaders are per-site. The mapping itself
-can be produced with the agent-assisted workflow (point Fable/Opus agents at a
-source DB + this contract -> they emit the mapping + a loader skeleton).
+is the bulk of the work: enumerate the source tables against this contract and
+write one stage per entity (this loader is the worked example).
 
 ## Running (against a THROWAWAY import database)