0.3.0-alpha.3 Context and Artifact Migration

Scope

Config v2 and Protocol v1 requests require no change. RunMetrics.context, RunMetrics.artifacts, and RunResult.artifacts are additive optional fields populated by normal runtime results. Existing readers and fixtures that construct the older metric shape remain compatible.

Behavior changes

• System prompts are assembled through a stable prefix; semantics still come from the original agent instructions, tools, and skills.
• Large tool output no longer exposes an external temporary path to the model. It is imported into .coremind/artifacts/ and referenced by a workspace-relative path.
• Suspected credentials block artifact persistence and model visibility.
• Project memory is never created automatically.

Rollback

1. Stop processes using the candidate runtime.
2. Preserve artifacts still required for audit together with their trace hashes.
3. Roll the complete package family back to the 0.3.0-alpha.2 candidate; do not roll back only the tools package.
4. Delete artifacts only when no audit record still references them.

Rollback does not modify existing sessions, run state, or checkpoints. Add compatibility reads before changing versions if business code depends on the new metrics.