Skip to content

Verify the complete expected marketplace release tree #517

Closed

Description

@devantler

🤖 Generated by the Agentic Engineer

Problem and evidence

Marketplace verification trusts a successful but incomplete changed-path observation when inspecting a release commit. A controlled empty observation allows the verifier to accept a real child commit that also changes unrelated tracked content. The complete native observation correctly rejects it.

Expected outcome

Verify the complete release tree against independently reconstructed expected content. Parent identity and two manifest blobs alone cannot establish that all other committed content is preserved.

Acceptance criteria

  • Reproduce the incorrect VERIFIED result with a real Git child commit.
  • Bind the complete tree to the expected two-manifest release change.
  • Refuse omitted changes, extra tracked content and incomplete producer observations.
  • Preserve valid release commits and historical read-only inspection.
  • Run release verification and preparation regression suites.

Rough size: S. Part of #101.

Activity

  1. added theissue type on Oct 5, 2026
  2. moved this to 🫴 Ready in 🌊 Project Boardon Oct 5, 2026
  3. self-assigned this
    on Oct 5, 2026
  4. added a commit that references this issue on Oct 5, 2026
  5. devantler commented on Oct 5, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Delivered in merged PR #520 (merge commit 105e3b0). Original-observation write plans preserve concurrent updates, candidate verification requires a complete closed artifact inventory, and full expected Git tree comparison prevents unrelated release changes from hiding behind an empty diff. Current-head review and the complete replacement native CI run passed before merge; the 42 verifier cases and real concurrent writer/rollback controls are green.

  6. moved this from 👀 In Review to ✅ Done in 🌊 Project Boardon Oct 5, 2026
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