The eighth cut and the move of next: release/fixtures/cut.v0-1-7.json

Merged
DO
6d ago
+728-2

User description

This records the v0.1.7 cut as release/fixtures/cut.v0-1-7.json, in the same form as #727's cut.v0-1-6.json. The Factory Builder asked for it on 2026-11-11.

Model-Lens inputs touched: none. The change is the fixture, tests/test_release.py and tools/mutants.py.

Size. 35,256 characters and 772 lines by git diff; 41,045 characters as the Kernel counts a diff, with its lines numbered, against a budget of 60,000.

What GitHub answered

  • Release run 43026745268 (release.yml, success) cut factory/v0.1.7 at 68efced8, the merge of "The approving act names a Pause the port could not read by the port's part (#688's dry runs 5 to 7, record 0192)" (#731). It moved factory/v0-next there, and recorded Deployment 7710970645, whose status is success. The fixture holds the run, its one job, and the job's log at the step.
  • Eval run 43024260112 (eval.yml, workflow_dispatch, success) ran on 68efced8. It ended at 13:09:17Z, before the cut was asked at 13:10:31Z, and the eval workflow lists it as its only run on that commit.
  • Read after the cut (13:12Z):
    • factory/v0.1.7 and next both name 68efced8.
    • factory/v0.1.6 still names 48687f2a, where its cut left it.
    • next has eight Deployments, newest first: v0.1.7's down to v0.1.0's.
    • GitHub marked v0.1.6's inactive when the new one was made, and kept its earlier success.

The reads went through the Maintainer's login and were trimmed to cut.v0-1-6.json's fields and headers, read for read. tools/redact_trial.py redacted them outside the repo, and only the clean output was read. It took out the names of steps[1] and steps[6], the token's mint and its post step, as for v0.1.6. Of the log's inputs, the token's line, which GitHub masked, and the exchanges' folder are left out, since tools/check_release.py keeps the four inputs a cut is asked by. removed says what was taken.

Checks it adds

  • tests/test_release.py::test_the_next_cut_moved_next_on reads each cut after the first; v0.1.7 joins its list. For v0.1.7 it holds:
    • the cut's writes;
    • the eval run (by id, workflow, event, conclusion and commit), ended before the cut, and the one run on its commit;
    • both tags at the cut commit, and v0.1.6 where it was;
    • all eight Deployments in order, newest first, and both statuses.
  • Nine mutants of the new fixture, each killed by that test, as for v0.1.6: another eval workflow, run or commit; an eval that ended after the cut; another run listed on the commit; v0.1.6 moved; the newest Deployment not v0.1.7's; its status not success; v0.1.6's Deployment still reading only success.
  • release/AGENTS.md's cut row already names the test, and is unchanged.

No record is needed: no rule changes.

Checks

CheckResult
make checksOK
tests.test_releaseOK, 29 tests
Mutants of the cuts' fixtures, run alone on an export72 of 72 killed
gitleaks on the fixtureNo leaks
Full make verifyNot run locally, by the Maintainer's standing change of 2026-11-09; CI's verify is the answer
ReviewerHeadUnread partsBlockingMajorMinorInfo
agy (Carbon)99be1e6none0000
muse99be1e6none0000
astra99be1e6none0000
claude-review99be1e6none0000
claude-security99be1e6none0000

No reader found anything. Carbon read it in two parts.

🤖 Generated with Claude Code


CodeAnt-AI Description

Record and verify the v0.1.7 release cut

What Changed

  • Adds evidence that v0.1.7 was cut successfully from the evaluated commit and factory/v0-next moved to it, while v0.1.6 stayed on its previous commit.
  • Extends release checks to validate the new cut, its evaluation and deployment results, and earlier release references.

Impact

✅ Verifiable v0.1.7 release record
✅ Catches incorrect next-tag moves
✅ Preserves v0.1.6 release history

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.