[sox8502]

Summary

Artifacts directories have been growing into run-output dumps (one project reached 32 GB / 827k files), making the Artifacts tab unusable. Agents were told the folder holds "durable project outputs" and orx-reports even suggested a models/ subfolder, with no rule against copying run outputs or pointing run code at it.

This tightens the agent guidance only:

• SYSTEM_PROMPT.md: artifacts are finished deliverables the user reads; never a run's output directory; run outputs (checkpoints, logs, per-sample results, sweep dumps, archives, datasets, caches, copied repos) stay with the run and are cited with run tags.
• orx-reports: drop the models/ suggestion; add an explicit do-not-save list; summarize raw results into one small table instead of copying them.

Test plan

• cargo test --locked playbook/skill tests (65 passed)
• GitHub CI (fmt, clippy, build, test) passing; Greptile 5/5
• Start a new chat, run an experiment, ask for a report; confirm only the report, figures, and a small table land in Artifacts

[sox8502]

@greptileai review

[greptile-apps]

Confidence Score: 5/5

[Medium impact] This guidance-only PR appears safe to merge.

Summary

This PR limits Artifacts to finished deliverables and keeps raw experiment files with their runs.

• Agents keep run outputs outside the Artifacts directory.

_{Reviews (1) · Last reviewed commit: "Keep run outputs out of the artifacts di..." · Reviewed by Greptile}