Skip to content

Prevent checkpoint snapshots from recursively capturing artifact directories #2040

Description

@chubes4

Problem

A recipe runtime whose artifactsDirectory is inside the working tree creates checkpoint snapshot artifacts under that directory. Restoring those checkpoints materializes the configured artifact tree into the runtime snapshot payload; later artifact collection emits a nested artifacts/... tree containing sibling runs, manifests, request-worker files, and snapshots. Parent bundle verification then reports those files as orphaned.

Evidence

Confirmed while completing #2017 with one immutable checkpoint baseline per campaign. The final finding bundle's manifest correctly lists all six adversarial nested bundles, but artifacts verify --bundle <absolute-runtime-bundle> reports the recursively captured artifacts/wordpress-adversarial-vulnerable/... tree and checkpoint snapshots as orphaned. The standalone artifact verifier smoke passes.

Expected

Checkpoint snapshot capture/restore must exclude host artifact storage by construction. Do not solve this with post-hoc deletion; preserve snapshot restore semantics and manifest integrity.

Refs #2017

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions