Skip to content

Verify: replace import empties the store before validating #451

Closed

Description

@possiblyneal

Part of #448

Question

Does fork issue #436 reproduce (a replace import with a bad optional section leaves the store emptied), and does a validate-first fix hold? Upstream: rohitg00#1573, rohitg00#1576.

Activity

  1. self-assigned this
    on Nov 18, 2026
  2. possiblyneal commented on Nov 18, 2026

    @possiblyneal
    OwnerAuthor

    Resolved: apply. Fork issue #436 reproduces on fdc3d45 and the validate-first fix holds; details, test path and branch in #436 (comment). #436 is now ready-for-agent; /ship lands it.

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

Metadata

Metadata

Assignees

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions