Skip to content

Establish the release evidence plan core #72

Closed

Description

@mowind

Part of #70.

Goal

Establish the canonical release evidence-plan core and migrate all source evidence that does not require the approved upstream checkout.

Scope

  • Add the source, artifact, and compatible HSK metadata CLI shape in .github/scripts/hashkey_release_gate.py.
  • Define semantic evidence results, sticky non-fail-fast aggregation, explicit blocked prerequisites, cleanup, interruption, and exit-code contracts.
  • Keep the host-process runner private; tests may use a recording/failing implementation without exposing runner injection to production callers.
  • Move gate/repository contracts, Foundry and four CLI conformance slices, build matrix, static checks, no-default runtime regression, and full workspace commands into the Python-owned source plan.
  • Preserve required --locked, --no-fail-fast, toolchain, and stack environment policy.
  • Do not cut over Make/workflows in this ticket.

Acceptance Criteria

  • Interface-first tests prove exact source membership and exactly-once execution of each semantic item.
  • full-workspace and non-hashkey-regression are mandatory members.
  • An early leaf failure followed by later success still fails the phase and preserves every failure.
  • Only a true prerequisite produces blocked; independent later evidence still runs.
  • Legacy shell orchestration may remain only as a temporary caller during the series, not as a second membership authority.

Activity

  1. mowind commented on Aug 4, 2026

    @mowind
    OwnerAuthor

    Implemented in commit 76ddb6c. Python now owns the fixed 17-item source evidence plan, private host executor, locked/no-fail-fast command policy, sticky non-fail-fast aggregation, blocked golden prerequisites, and canonical source CLI operation with interface tests.

  2. mowind commented on Aug 4, 2026

    @mowind
    OwnerAuthor

    Closed by 76ddb6c.

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

Metadata

Metadata

Assignees

No one assigned

    Labels

    ready-for-agentFully specified and ready for an AFK agent

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions