Skip to content

Bind release candidate verification to a complete artifact inventory #516

Closed

Description

@devantler

🤖 Generated by the Agentic Engineer

Problem and evidence

Marketplace verification trusts a successful but incomplete filesystem inventory. A controlled observer emitting an empty inventory lets the real verifier accept a candidate directory with an additional linked entry, while the complete native inventory correctly rejects it.

Expected outcome

Candidate verification must independently establish the complete expected artifact entries and their regular file boundaries. A plausible empty or partial inventory cannot prove that unexamined entries are absent.

Acceptance criteria

  • Reproduce the incorrect VERIFIED result through the actual verifier.
  • Bind the observed candidate directory to the expected complete entry set.
  • Reject extra entries, linked intermediate directories and failed or incomplete observations.
  • Preserve valid candidate verification and read-only caller behavior.
  • Run preparation, verification and historical inspection 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.

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