Skip to content

Loop Engineering v0.2.0 — github-pr-review Candidate

Choose a tag to compare

View all tags
@nian1123 nian1123 released this 13 Sep 01:37
· 77 commits to main since this release
v0.2.0
0c2e87a
This commit was created on GitHub.com and signed with GitHub’s verified signature.
GPG key ID: B5690EEEBB952194
Verified
Learn about vigilant mode.

Loop Engineering v0.2.0

  • Repository Release: v0.2.0
  • Workflow Definition: github-pr-review/v0.1.0
  • Definition status: Candidate
  • Stable status: no Stable Supported Profile

Repository and Workflow Definition versions have independent lifecycles. v0.2.0 introduces the Workflow-first direction and publishes the first github-pr-review Candidate; it does not rename that Definition to v0.2.0 and does not promote it to Stable.

Included

  • A complete project-owned PR Review file set: Workflow, Event Prompt configuration, Codex Compatible Executor, static Compatibility Profile, result schema and trusted Check publisher.
  • Supported non-Draft PR lifecycle routing plus manual reruns, Fresh Goal Runs, per-PR serialization, SHA freshness and same-SHA Check idempotency.
  • Read-only Agent boundaries, isolated trusted control scripts, explicit terminal mapping and fail-closed validation.
  • A Candidate Publication Gate covering routing, prompt formation, mappings, permissions, validation, SHA freshness, idempotency and failure paths.

The gate evidence is static analysis and automated contract execution with a controlled Fake Action. It is not a real Consumer Project compatibility result, and Agent final text is not proof of publication or success. Real Consumer validation and a consistent Evidence Bundle remain required for Stable Promotion.

Coexistence and migration

github-pr-review/v0.1.0 and every github-development-ticket v0.1.x Definition can be installed side by side because they are separate products. The new Candidate does not consume or migrate Legacy Thread Records, labels, Controller state or Workflow Instances. There is no automatic migration.

The published github-development-ticket v0.1.0, v0.1.1 and v0.1.2 files, tags and validation history remain available as the previously validated Legacy Frozen line. That line remains usable but receives only serious security fixes and factual corrections; it gains no new workflow capabilities.

Upgrade boundary

The Candidate pins openai/codex-action source tag v1 to commit 86365089eb2b84e0a8fb0717b304f8bdcb13b20e. Changing the Action SHA, mapping, Executor or Profile creates a modified Workflow Instance outside this Candidate claim. An official upgrade requires a new Definition version and renewed validation.

Assets 2
Loading