Skip to content

Release v3.2.2 - #148

Merged
Paulo Lacerda (placerda) merged 10 commits into
mainfrom
release/3.2.2
Oct 14, 2026
Merged

Paulo Lacerda (placerda) merged 10 commits into
mainfrom
release/3.2.2

Conversation

@placerda

Copy link
Copy Markdown
Collaborator

Changed

  • Include Hosted api-version=v1 and support current and legacy conversation envelopes.
  • Register classic persisted history only for the orchestrator backend.
  • Include the previously integrated technical exception-registry validation policy.

Validation

  • Runtime regressions and installed wheel acceptance passed in the feature PR, including Linux container acceptance and all required quality gates.
  • Azure validation and deployment intentionally omitted at maintainer request.

Paulo Lacerda (placerda) and others added 10 commits October 9, 2026 19:06
Review all 30 exceptions; retain seven unchanged and submit 23 corrected exact-source records as proposals without inherited approval. Full suite: 554 passed. Typing and architecture passed; remaining lint/exception/policy findings require protected review.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Preserve source-bound evidence, expiry, protected evaluator integrity and fail-closed CI. Registry edits alone no longer require protected review; checker adoption still does.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Keep ownership assignments, protected-file enforcement and bootstrap failure unchanged. Describe technical policy differences without soliciting reviewers or administrative approval.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…-review-pr

fix: make boundary diagnostics safe and simplify exception validation
Update stale developer-doc statements that claimed the old protected
checker still rejected the new evaluator pending adoption, and that a
reference PR against the adopted develop base remained missing.

PR #144 (merged ec18a73) adopted the new evaluator into the protected
develop base, so the protected checker now applies it to subsequent
PRs. This PR is the reference PR exercising the adopted base and
coordinator-owned required-check controls.

Independent human review of the recorded exception decisions (see
.quality/exception-technical-review.json) remains outstanding, tracked
by issue #695. This PR demonstrates base adoption only, not completed
review.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…ce-proof

docs: reference PR proving adopted UI quality policy on new develop base
…idance

Correct docs/python-development.md to state that recorded exception
decisions are governed by their technical evidence (exact fingerprints,
same-source bound tests, unexpired stage validation) rather than a
separate independent human review step. The prior text incorrectly
stated that independent human review (issue #695) remained outstanding,
which resurrected a bureaucracy requirement explicitly removed by the
repository owner. Integrity/fingerprint/expiry/check-validation
language is preserved unchanged.

Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
…-blocker

docs: remove stale independent-review blocker from policy adoption guidance
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
Co-authored-by: Copilot App <223556219+Copilot@users.noreply.github.com>
@placerda

Copy link
Copy Markdown
Collaborator Author

This release incorporates the technical exception-policy adoption already explicitly authorized by the maintainer, implemented in #144 and merged into develop on 2026-10-10 (platform ADR-0020). Main still runs the older protected evaluator: its three policy findings reject the previously approved evaluator/CODEOWNERS/registry migration; the associated BLE001 and exception-review findings consume stale main records rather than the technically validated candidate records. Runtime unit and installed Linux-container acceptance, typing and architecture are successful; the same runtime source passed every protected-develop quality gate in #147. This is a deliberate adoption operation, not a claim of a remotely passing legacy gate. No checker, gate or exception allowance is being changed by this release preparation. A genuine follow-up release-only PR against the newly adopted main evaluator will be required to pass every check before publishing v3.2.2.

@placerda
Paulo Lacerda (placerda) merged commit cd0fb74 into main Oct 14, 2026
7 of 11 checks passed
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