Skip to content

Add automatic protected policy selection for MR reviews - #266

Merged
xeonvs merged 24 commits into
mainfrom
feature/264-auto-policy-0.13.0
Oct 23, 2026
Merged

xeonvs merged 24 commits into
mainfrom
feature/264-auto-policy-0.13.0

Conversation

@xeonvs

@xeonvs xeonvs commented Oct 23, 2026 •

Copy link
Copy Markdown
Owner

Scope

Safety and behavior

The review, receipt v11, publication, and approval paths bind the authenticated MR and CI job identity. They reject synthetic merged-result or merge-train commits, stale code or authority, and contradictory legacy results. An unprotected actual target cannot receive automatic approval. Protected policy movement is accepted only when bounded Git ancestry proves a fast-forward from the captured policy commit. Local private diagnostics retain marked non-postable JSON while reporting only admitted findings.

Verification

  • Full local runtime quality gate before the dependency-only correction: 2300 passed, 5 qualified skips, 357 subtests; 86.54% aggregate coverage.
  • Focused correction suite: 189 passed, including a real remote policy advance after checkout and local diagnostic retention.
  • Three completed Codex Security diff scans over the implementation and correction deltas reported zero findings. The final OCR 1.13.3 review completed 31/31 selected items with DLP admission and identified two medium bugs; both were fixed in separate commits and verified with focused regressions and the final quality gate.
  • PR CI first found vulnerable opentelemetry-api 1.44.0. The resolver floor and lock now require 1.45.1; the new shared local/CI audit passes with no known vulnerabilities. The isolated audit preserves the active environment and uses CI-pinned uv 0.13.4. Fifty-one focused workflow/documentation tests and pip check pass; PR CI reruns the full matrix on this final head.
  • Plan lifecycle, instruction contract, documentation navigation, whitespace, public-tree and complete feature-history secret checks passed.

Delivery

This feature PR precedes the deterministic TestPyPI development artifact and the protected v0.13.0 release PR. The release PR will archive the complete plan and reset PLANS.md; publication, immutable receipt, tracked issue closure, and site readback follow the protected release workflow. Only #264 belongs to the v0.13.0 release issue set.

xeonvs added 23 commits October 23, 2026 10:52
Record issue #265 as inactive BL-025 with explicit authorization, coverage alternatives, graph shapes, scope limits, and future validation. Align the roadmap without activating runtime behavior or release scope.
@xeonvs
xeonvs marked this pull request as ready for review October 23, 2026 12:52
@xeonvs
xeonvs merged commit 24b0ba0 into main Oct 23, 2026
1 check passed
@xeonvs
xeonvs deleted the feature/264-auto-policy-0.13.0 branch October 23, 2026 13:10
xeonvs added a commit that referenced this pull request Oct 23, 2026
## Release authorization

Stable version: 0.13.0. Tracked release issue: #264. The release
workflow owns its issue state after the immutable receipt is read back.
Planning issue #265 was completed with the feature PR and is not in this
release issue set.

This PR advances the stable and next version markers to 0.13.0 and
0.14.0, records source epoch `1792761040` and the exact issue set,
renders the Towncrier section, and updates the checksum-pinned GitLab
example. It archives the complete repository plan and returns `PLANS.md`
to its inactive state. External publication and readback remain pending
in the archive's Post-Close Delivery section.

## Reviewed input

- Protected feature PR #266 merged as signed
`24b0ba096672c711005ead2f9ddd47e3d557e4d9`; its tree equals the reviewed
feature head `dc62581675d7cf99e0463b78876d3eddbe00a923`.
- TestPyPI development run `39959060145` published and verified
`0.13.0.dev122` wheel and sdist. Independent registry readback found
both files and their SHA-256 digests.
- Local release preparation: 108 focused tests passed; plan lifecycle,
instruction contract, documentation navigation, Ruff, local dependency
audit, staged/tree/history Gitleaks, and Twine passed. Two
source-epoch-controlled builds produced identical wheel and sdist bytes.
- The first release PR matrix identified a stale `docs/configuration.md`
example version. The same release commit now corrects it and records a
release-preparation guard; 114 focused environment, release,
documentation and integration tests passed. The amended head awaits the
protected matrix.
- The release notes are the exact new 0.13.0 Towncrier section followed
by the adjacent `v0.12.1...v0.13.0` comparison link.

## After merge

The protected Release workflow must authorize the exact reviewed tree,
publish and verify stable registry artifacts, provenance, the annotated
tag, immutable GitHub Release and receipt, then update the tracked
issue. Independent external and site readback follow without another
repository PR.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant