Skip to content

Contract legacy release gate interfaces #77

Closed

Description

@mowind

Part of #70.

Goal

Hard-cut every legacy release-gate interface and complete the end-to-end evidence regression.

Scope

  • Reduce .github/scripts/hashkey-release-gate.sh to repo/interpreter resolution plus exec argument forwarding and exit preservation.
  • Delete all, public individual stages, skip/only composition, approved-repository/revision print flags, workflow-owned basic|execution, and direct production calls to the private artifact helper.
  • Update repository contract validation and CONTEXT.md to distinguish complete source evidence from full release eligibility.
  • Add static deletion checks so old callers, stage membership, and pre-gate draft/upload choreography cannot return.
  • Run the complete source phase and end-to-end Linux tar, designated Linux execution, ARM64, Windows ZIP, ordinary stable, HashKey stable, and nightly lifecycle paths.

Acceptance Criteria

  • Python is the only source/artifact membership authority.
  • Shell, Make, and workflows contain no legacy aliases or duplicated plan/mode policy.
  • No release draft or asset upload appears before gated finalize.
  • All focused, archive, workflow-structure, and complete source regressions pass.
  • Independent review reports no blocker or major issue against the architecture contract.

Activity

  1. mowind commented on Aug 4, 2026

    @mowind
    OwnerAuthor

    Implemented in commit 67c5fd3. The shell gate is now a pure Python launcher; Make/CI/workflow callers use only canonical operations; artifact smoke is a private designated-Linux execution helper without basic/execution modes; legacy pin-print flags are removed; structural validation locks target matrix, ordering, needs, no pre-gate draft/upload, and no legacy interfaces; CONTEXT.md now distinguishes source evidence from complete release eligibility.

  2. mowind commented on Aug 4, 2026

    @mowind
    OwnerAuthor

    Closed by 67c5fd3.

  3. mowind commented on Aug 4, 2026

    @mowind
    OwnerAuthor

    Follow-up fix 96a4ff8: finalize now uses the canonical metadata operation with --validate-release-metadata, expected tag, and gated commit, avoiding Cargo metadata schema confusion and locking the generate-to-validate lifecycle.

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