Skip to content

Keep release artifact writes in the reserved output directory #498

Closed

Description

@devantler

🤖 Generated by the Agentic Engineer

Problem

Replacing the reserved candidate directory before the final copy can redirect preparation into another location while it still reports success. The earlier containment check does not bind the actual write.

Proposed direction

Repair the owning observation or output boundary, with a regression that fails on current main before changing the implementation. Preserve the existing conservative behavior and public interface.

Acceptance criteria

  • Bind artifact writes to the exact directory reserved by this invocation and detect output replacement before reporting success.
  • Preserve source checkout state and refuse redirected output.
  • Test normal output, directory replacement and final artifact/status readback failure through the real preparation command.

Size: S/M. Part of #101.

Activity

  1. added theissue type on Oct 4, 2026
  2. self-assigned this
    on Oct 4, 2026
  3. added a commit that references this issue on Oct 5, 2026
  4. devantler commented on Oct 5, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Delivered by merged PR #504 at commit 1c1b7a2. Merged-main bytes match the reviewed tree; full native CI, independent exact-head review and actual release/orchestrator evaluation are recorded on the PR. Failed preparation retains public output for inspection and preserves foreign files; the documented identity observations do not grant atomic reservation or concurrent-content serialization.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

Fields

Priority

None yet

Effort

None yet

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions