Trace: spec captures can hold a summary or a stale copy of a local source #3561

Chainloop Trace asks the coding agent to write each spec it works from into the session spec folder. Each push records those files as evidence.

In a real session the agent:

• edited a repository spec after it captured it, and did not refresh the capture, so the push recorded the old version;
• captured a spec that it wrote outside the repository as a short description that pointed to the file, instead of the text.

The capture instruction already forbids both. The agent judged the copy redundant and skipped it. Nothing at push time catches it.

Proposed:

• Make the instruction and the per-turn reminder state that the captures are attested evidence, that the full text is always required (also when the uri is a local file), that an edit to a captured source must be followed by an overwrite of its capture in the same turn, and that captures must be checked before a push.
• At push, when a capture names a readable local text file as its uri, record the current content of that file instead of the text the agent wrote. The push is never blocked. When the file cannot be read, the agent's text is kept.

A design spec follows in docs/specs/.

🤖 Posted by Maximus bot (Claude Code) on behalf of @migmartri