Skip to content

chore: finalize v1.4.0 release-facing compliance - #29

Merged
megyptm merged 1 commit into
codex/transaction-savepoint-orchestration-wu3-standards-compliancefrom
codex/transaction-savepoint-orchestration-wu3-release-remediation
Sep 18, 2026
Merged

megyptm merged 1 commit into
codex/transaction-savepoint-orchestration-wu3-standards-compliancefrom
codex/transaction-savepoint-orchestration-wu3-release-remediation

Conversation

@megyptm

@megyptm megyptm commented Sep 18, 2026 •

Copy link
Copy Markdown
Collaborator

النطاق المحمي

  • إزالة اسم فرع Phase المؤقت من CI وجعل pull_request عامًا، مع إبقاء push على main وجميع الوظائف والبوابة الحالية.
  • تثبيت عنوان CHANGELOG النهائي لـv1.4.0 بتاريخ 2026-09-18 وإزالة صياغة الإصدار الانتقالية.
  • توضيح الفرق بين SQL المتوافق مع ملف MySQL/MariaDB وبين التحقق الفعلي على MySQL 8.4.10، مع التصريح بأن MariaDB غير متحققة مستقلًا في CI الحالي.
  • استكمال رؤوس SQL للـfixtures بسياسات الغرض الاختباري، ordering/scope، soft-delete، uniqueness، Host FK/JOIN، ودورة التنظيف.

الحماية

لا يوجد تغيير في production runtime أو public API أو Standards/Profile أو transaction/savepoint semantics. لا يوجد tag أو GitHub Release.

التحقق

نجحت بوابات CI على HEAD النهائي، بما في ذلك:

  • Workflow lint / actionlint
  • Composer validation / dependency resolution / platform requirements / audit
  • PHP syntax
  • PHPStan max
  • PHP CS Fixer
  • Unit/Regression على PHP 8.2 و8.3 و8.4 و8.5
  • Lowest dependencies على PHP 8.2 + MySQL 8.4.10
  • Consumer Verification Harness على MySQL الحقيقي
  • Integration repeatability على PHP 8.2 و8.5 + MySQL 8.4.10
  • MySQL residue verification
  • Repository integrity
  • CI Gate

جميع adopted Standards/Profile files ظلت بدون تعديل ومثبتة على commit 44c8827095ab4007c355aa21c56b853f3b49d795.

@megyptm
megyptm merged commit 87669ab into codex/transaction-savepoint-orchestration-wu3-standards-compliance Sep 18, 2026
10 checks passed
@megyptm
megyptm deleted the codex/transaction-savepoint-orchestration-wu3-release-remediation branch September 18, 2026 03:18
megyptm added a commit that referenced this pull request Sep 18, 2026
* chore: adopt pinned standards and close compliance gaps

* fix: type consumer harness process pipes

* chore: finalize release-facing compliance wording (#29)
megyptm added a commit that referenced this pull request Sep 18, 2026
* chore: open transaction savepoint integration draft

* feat(transaction): add savepoint transaction runner (WU1) (#24)

* feat(transaction): add savepoint transaction runner

* fix(transaction): tighten savepoint cleanup semantics

* test(transaction): verify savepoint orchestration on MySQL (WU2) (#25)

* test(transaction): verify savepoints on MySQL

* ci: verify transaction savepoint table residue

* Finalize Transaction Savepoint Orchestration Draft (#26)

* docs: Finalize transaction savepoint orchestration implementation

* Update and finalize docs regarding SavepointTransactionRunnerInterface
* Generate ADR 0003 for transaction savepoint orchestration
* Update package reference, README, and CHANGELOG
* Add a verification report on local testing
* Ensure all tests, PHPStan max, and php-cs-fixer pass
* Unrelated fixes left untouched

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>

* docs: clarify transaction runner distinctions and ADR metadata

* Clarify that PdoTransactionRunner and PdoSavepointTransactionRunner are both permanent, public, supported options, and neither replaces the other.
* Ensure wording regarding operation-local savepoint orchestration strictly notes that it "does not commit or fully roll back the caller-owned transaction, and the outer transaction remains active."
* Add standard metadata (Status, Decision date, Runtime status, Implementation authorization, Related contract) to ADR 0003.
* Align verification report with the precise MySQL 8.4 boundary and explicitly mention MySQL residue verification, removing unverified data points.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>

---------

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>

* Prepare v1.4.0 Release (#27)

* Prepare v1.4.0 release

Updates CHANGELOG.md for the new release, updates the transaction savepoint
ADR and its index to show Implemented for v1.4.0. No runtime changes.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>

* Clean up release documentation and migrate domain

- Deletes transient phase artifacts.
- Adds canonical `PDO_TRANSACTION_ARCHITECTURE.md`.
- Synchronizes ADR #3 and its index to point to the new architecture document.
- Updates README and Package Reference to link to the new architecture doc.
- Performs repository-wide string replacement from `maatify.com` to `maatify.dev`.
- Retains existing v1.4.0 preparation state.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>

* Fix documentation missing items and failure precedence semantics

- Adds missing SavepointTransactionRunnerInterface and PdoSavepointTransactionRunner to the public API inventory in PERSISTENCE_PACKAGE_REFERENCE.md.
- Corrects PDO_TRANSACTION_ARCHITECTURE.md to detail exact failure precedence for Savepoints, rather than a broad claim that callbacks always return.
- Confirms zero stale phase artifacts, `maatify.com` domains, and "pending release" verbiage remain.
- Updates metadata preparation description for the PR.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>

* Update README to accurately reflect both transaction runners

This commit ensures the README represents both v1.3.0 and v1.4.0
capabilities symmetrically without duplicating low-level details.
It updates Key Features, the Transaction Usage section, and the
Critical Runtime Behavior section to include PdoSavepointTransactionRunner.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>

* Correct PdoSavepointTransactionRunner cleanup wording in README

Updates the Critical Runtime Behavior section to accurately reflect that
savepoint cleanup can fail, clarifying the exact return value and best-effort
rollback semantics without duplicating full architectural details.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>

* Refine PdoSavepointTransactionRunner fallback wording in README

In the transaction usage selection section, this corrects the fallback
wording to clarify that it attempts best-effort rollback without fully
terminating the caller-owned transaction.

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>

---------

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>

* chore: adopt pinned standards and complete compliance work unit (#28)

* chore: adopt pinned standards and close compliance gaps

* fix: type consumer harness process pipes

* chore: finalize release-facing compliance wording (#29)

---------

Co-authored-by: google-labs-jules[bot] <161369871+google-labs-jules[bot]@users.noreply.github.com>
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