Skip to content

Cut over World regression enforcement to the product-owned gate #166

Description

@devantler

🤖 Generated by the Agentic Engineer

Delivered outcome

World regression enforcement now uses the cross-product reviewed-base runner and World's fixed local admission action. The existing GitHub Actions identity supplies the executed result; candidate-controlled validator bytes cannot supply the trusted implementation. The old singleton association is retired through its retained, non-deleting managed record.

The final source cleanup is delivered by #763 (5df28658db1fcb1484d5358d0580a3853e653ecc) and World #1557 (c79e5804b6c9f12ae3479f50521592f9563fca32). The separate shared-CI repair #765 is merged and main CI, release, CD, push and quality checks have succeeded.

Completed acceptance

  • Retain the maintainer's 2026-10-24 planning decoupling: World #1495 remains open, with its runtime target and safety criteria unchanged.
  • Add shared-runner enrollment and the repository-bound executed-result requirement additively, while the established source remains required.
  • Deliver reviewed protected merges and signed configuration publication; verify reconciliation and complete native bindings.
  • Observe complete, nonzero evaluation from the immutable reviewed base at the exact native candidate/run/attempt.
  • Preserve executable validator/workflow, omission/masking, identity, duplicate-name, containment and cleanup refusal controls; prove the real candidate validator cannot replace the reviewed executor.
  • Retire only the singleton association after native overlap proof, retaining its non-deleting lifecycle and unrelated rules.
  • Repeat real positive and refusal controls after retirement, with the trusted result still required.
  • Remove the unused central World source after complete consumer/source closure, and update catalogue documentation and tests.

Fresh complete native readback at 2026-10-25 20:50 UTC confirms the retained old World record is disabled at its observed current generation, has no workflow association or bypass, and the shared runner plus repository-bound executed result remain required. All 49 unrelated policy appearances match the pre-retirement baseline; the other two consumers remain protected.

After retirement, the real positive control passed all 187 trusted scenes. The negative control used a candidate no-op validator, but the reviewed action still executed and rejected the candidate parser error. The full source CI retains scene omission, masking, identity, duplicate-name, containment, deadline and cleanup controls. These are distinct evidence layers; this does not claim that every mutation variant was separately submitted as a native control PR.

World #746 is completed. No additional App, broader credential authority, imperative ruleset change or CI-performance waiver is part of this delivery.

Activity

  1. self-assigned this
    on Aug 20, 2026
  2. added theissue type on Aug 20, 2026
  3. changed the title [-]Require trusted World at Ruin regression workflow[/-] [+]Cut over World regression enforcement to the product-owned gate[/+] on Aug 20, 2026
  4. changed the issue type fromtoon Aug 20, 2026
  5. devantler commented on Aug 20, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Maintainer supersession — safe migration back

    The original creation objective completed, but the ownership decision is superseded by the boundary merged in devantler-tech/monorepo#2944 at e0961399e8186435505c43d98d4fa7f58dce0bd1. World at Ruin-specific workflows and policy now belong with World at Ruin unless a second real repository demonstrates the same product-neutral contract.

    Current state is working and remains untouched during the replacement slice: organization ruleset 21102220 stays active with no bypass actors, and its Actions source stays active. This issue is reopened to own only the reviewed cutover after World Epic devantler-tech/actions#745 and additive gate task World devantler-tech/actions#746.

    Ordered cutover

    1. Wait for World devantler-tech/actions#746 to merge and prove a World-owned gate under a distinct check context.
    2. Add the thinnest repository-scoped declarative binding for that World-owned check; keep organization rule 21102220 active so both gates are required. No World workflow or policy logic moves into this repository.
    3. Read back both live rules and run positive plus fail-closed canaries, including candidate workflow deletion and duplicate-name spoof attempts.
    4. Only after coexistence evidence, move the organization workflow rule through a reviewed reversible deactivation (evaluate or disabled, according to the live provider contract) and verify the World-owned check remains blocking.
    5. Retire the old organization rule resource only after a soak period and only through reviewed declarative state. The dependent Actions cleanup happens last.

    Acceptance gates

    • World devantler-tech/actions#746 is merged, live, exact-head reviewed, and independently required
    • Both old and new checks are simultaneously required during canary proof
    • The replacement has no bypass actors and applies only to World default-branch changes
    • A candidate cannot satisfy the binding by emitting a duplicate check name
    • Organization rule deactivation produces no enforcement gap
    • Live readback and terminal workflow evidence are recorded before any source removal

    No ruleset mutation is being made in this issue update.

  6. moved this from 👀 In Review to 📥 Backlog in 🌊 Project Boardon Aug 20, 2026
  7. added 2 commits that reference this issue on Oct 5, 2026
  8. devantler commented on Oct 24, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    The cutover remains blocked by World at Ruin #746 and #1495, both independently re-read as open. The runtime prerequisite was already in this issue’s delivery criteria but was missing from its native dependency list. I added that link, preserved the existing #746 dependency, and removed the redundant blocked label in accordance with the portfolio’s issue-tracking contract.

    Resume after complete representative feedback is proven below 900 seconds, or after an explicit scoped planning-decoupling decision, then complete the retained overlap and refusal controls before retiring the singleton source. This tracking correction does not complete any delivery criterion or authorize an enforcement change.

  9. devantler commented on Oct 25, 2026

    @devantler
    ContributorAuthor

    🤖 Generated by the Agentic Engineer

    Completed: the final reviewed source cleanup, normal protected merge and all post-merge workflows are verified.

    The final source cleanup is delivered by #763 (5df28658db1fcb1484d5358d0580a3853e653ecc) and World #1557 (c79e5804b6c9f12ae3479f50521592f9563fca32). The separate shared-CI repair #765 is merged and main CI, release, CD, push and quality checks have succeeded.

    Fresh complete native readback at 2026-10-25 20:50 UTC confirms the retained old World record is disabled at its observed current generation, has no workflow association or bypass, and the shared runner plus repository-bound executed result remain required. All 49 unrelated policy appearances match the pre-retirement baseline; the other two consumers remain protected.

    After retirement, the real positive control passed all 187 trusted scenes. The negative control used a candidate no-op validator, but the reviewed action still executed and rejected the candidate parser error. The full source CI retains scene omission, masking, identity, duplicate-name, containment, deadline and cleanup controls. These are distinct evidence layers; this does not claim that every mutation variant was separately submitted as a native control PR.

    World #1495 and World #1397 remain independent unfinished performance work; no performance or warm-reuse outcome is inferred from this ownership cleanup.

  10. moved this from 🧊 Icebox to ✅ Done in 🌊 Project Boardon Oct 25, 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

Fields

No fields configured for Refactor.

Projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions