Ozeki Resilience 0.3.3 rc.14 — Recovery preparation

Ozeki Resilience 0.3.3 rc.14 — setup and recovery preparation

GitHub candidate; not yet submitted to WordPress.org. Submitted rc.13 is awaiting the reviewer's response. Publication is not approved.

• Clear initial-protection guidance and a wider bucket input, in English/Japanese.
• Check missing language packs, WordPress/plugin requirements and local prerequisites for the selected recovery point/history; show next actions and recheck after preparation.
• Actual restoration repeats checks before changing destination content. No archived software installer, no original/history migration.
• Recovery guides link to the read-only recovery IAM policy. Update recovery destinations too.

The exact ZIP passed isolated fresh installation, rc.13 replacement, all-file/source checks, bilingual admin rendering and preparation contracts. Plugin Check 2.1.0: 0 errors, 100 warnings, unchanged per-code counts from rc.13. Earlier isolated real-S3 tests of the same code verified missing-condition handling and successful history-5 recovery after preparation.

The same ZIP is installed on community; existing content/settings are preserved, protection remains on, scheduling and automatic cleanup remain off. Earlier ZIPs/tags are unchanged.

SHA-256: 453acc6930d57da11da72eaba5adf9c386d0d79aa179cfd15b12b82ad0ba5a2a

Use ozeki-resilience-0.3.3.zip, not GitHub's Source code archive. Plugin header/Stable tag remain 0.3.3; rc.14 identifies this candidate.

Detailed verification and compatibility notes

---

rc.14はWordPress.org未提出です。提出済みrc.13は審査担当者の回答待ちで、公開承認済みではありません。

保存開始の案内・バケット名欄・復旧前の不足条件と再確認を日英で整えました。原本・履歴の移行は不要です。復旧先にも更新版を用意してください。隔離環境の導入・更新とPlugin Checkを確認し、同じZIPをcommunity本番へ反映しました。既存ZIP・タグは保全しています。

Ozeki Resilience 0.3.3 rc.13 — Flamingo recovery correction

0.3.3 rc.13 — Flamingo recovery correction

rc.13更新受付・審査メール返信完了（申請者からの報告）。審査担当者の回答待ちであり、公開承認済みではありません。 / The author confirmed rc.13 upload acceptance and sending the reply to the original review email. We are awaiting the reviewer response; publication is not approved. Submitted ZIPs, tags and matching source remain unchanged.

Flamingoの復旧時に受信値が欠落する問題を修正しました。閲覧・再保存・再復旧に必要な値を、受信ごとの定義に基づき適用します。既存原本の移行は不要です。欠落状態で再保存した受信は、値が残る以前の原本から復旧してください。

Restores declared receipt values without admitting arbitrary metadata. Existing originals/history remain unchanged. Install the updated reader on recovery destinations. Receipts already re-saved empty need an earlier original containing their values. Previous rc.12 compatibility requirements remain in effect.

• Final ZIP: new installation and rc.12 replacement passed on WordPress 7.1.3 / PHP 8.3.36 in local isolated containers; all 3,814 installed files match.
• Settings, activation and 4 posts retained; recorded state hashes match. Pending operations/results were absent in this fixture.
• Exact-ZIP application/Flamingo regression contracts passed. Prior real-S3 receipt use, resaving and repeated recovery results are documented separately.
• Plugin Check 2.1.0: 0 errors / 100 warnings, same per-code counts as rc.12.
• Product source matches; vendor unchanged; 8 bundled guides and 80 relative links verified; no development/test documents bundled.
• Installable asset: ozeki-resilience-0.3.3.zip (not GitHub's source archive).
• SHA-256: 34eee728e5c6d78f6e8368256d60676a0df7085e8a35ed343f787afd2898c2b8

Full results and compatibility notes

Submission status is based on the author's confirmation in this chat, not an independent inspection of the receipt or sent email. Packaged/tagged documents and build-time evidence retain their build-time status; this release description and the main-branch submission record show the current status.

Ozeki Resilience 0.3.3 rc.12 — WordPress.org candidate

0.3.3 rc.12 — 更新受付・返信完了 / Awaiting reviewer response

TablePressの復旧先に安全な必須設定値を用意し、未編集Markdownを含む参照関係を再保存・再復旧へ引き継ぐ候補です。保存された実行用設定は実行せず、原文・既存S3原本・履歴は書き換えません。

互換性： 旧形式は読めます。新しい参照情報を含む原本・Baseline・Checkpointにはrc.12以降の対応版が必要です。rc.11はその新形式を拒否します。復旧先にも更新版を用意してください。

最終ZIPを隔離WordPressへ新規導入し、rc.11からの更新で設定・投稿件数・状態保持を確認しました。配置3,814ファイルがZIPと一致。Plugin Check 2.1.0はエラー0／警告100。復旧済み2サイトで表と編集／未編集Markdownの実ブラウザ10チェック、参照形式と旧reader互換性の確認も成功しています。詳しい試験範囲は記録を参照してください。

申請者からrc.12の更新受付と元の審査メールへの返信完了の報告を受けました。審査担当者の回答待ちであり、公開承認済みではありません。 以前のZIP・タグは保全しています。

English

This candidate supplies safe TablePress runtime defaults and carries verified site/image origins across subsequent saves and complete-site recovery, including untouched Markdown. Archived executable settings are not executed; originals and existing history are not rewritten.

Existing data remains readable. New context-dependent originals and recovery points require rc.12 or a later compatible reader; rc.11 explicitly rejects them. Prepare the updated version on recovery destinations too.

The exact ZIP passed isolated fresh installation and update from rc.11, file/source consistency, browser checks on two recovered sites, and format/legacy-reader contract checks. Plugin Check: 0 errors, 100 warnings. See the verification record for scope and limitations. The author confirmed rc.12 upload acceptance and sending the reply to the original review email. We are awaiting the reviewer response; publication is not approved.

• Verification / 確認・申請準備記録
• Matching source / 対応ソース
• Update instructions / 更新手順

Install ozeki-resilience-0.3.3.zip, not GitHub's automatically generated Source code archive.

ZIP: 8,288,605 bytes / 3,814 files
SHA-256: 8084a992fb593a65ca239fc8dc5b30b01061237424d768f106a2d1c63788ac6b

受付・返信完了は申請者の報告に基づきます。提出済みZIPとタグは変更していません。ZIP・タグ内の未提出表記は作成時点の記録として残します。

Completion is recorded from the author's confirmation, not an independent inspection of the receipt or sent email. Submitted assets and tags are unchanged; packaged/tagged documents retain their build-time status.

Ozeki Resilience 0.3.3 rc.11 — submitted, awaiting reviewer response

0.3.3 rc.11 — submitted, awaiting reviewer response / 提出済み・審査担当者の回答待ち

The rc.11 update was accepted on November 11, 2026 (JST), and the author confirmed sending the reply to the original review email. Awaiting the reviewer response; publication is not approved.

WP-Members now restores supported member-field flags and definitions needed for continued use. ACF free database-definition changes and deletions are saved independently of article edits. Existing originals/history are not rewritten. New ACF definition history and its Baselines/Checkpoints require rc.11 or a later compatible reader; old readers reject them. Trusted WordPress, themes and plugins are still installed separately.

rc.11は2026年11月11日（日本時間）に更新受付・元の審査メールへの返信が完了しました。審査担当者の回答待ちであり、公開承認済みではありません。 会員項目の値と必要な定義の復旧、ACF定義単独の変更・削除の履歴保存を含みます。新しいACF復旧点にはrc.11以降の対応する復旧処理を用意してください。

• Install ozeki-resilience-0.3.3.zip, not GitHub's Source code archive. Plugin version: 0.3.3; candidate: rc.11.
• ZIP: 8,285,733 bytes / 3,813 files.
• SHA-256: 0fcbbac0a7e8dcadbbb5d5b247248a3c8081ceb1b4ee6c2771f7e19cc5233c1c.
• Plugin Check 2.1.0: 0 errors / 99 existing warnings, unchanged by file/type/code/message from rc.10.
• Exact-ZIP fresh installation/activation and rc.10 update passed in isolated WordPress 7.1.3 / PHP 8.3.36. Installed files match; configuration, empty pending state and prior result hashes remained unchanged across update. Administration rendered in a new process.
• Recovery through existing real-S3 history 22 passed, including members, inquiries, tables and articles; original/history hashes unchanged. ACF definition, queue and member regression checks passed against installed ZIP code. These checks use CLI/API, not a new browser timeout test.
• Eight maintained guides and 78 bundled relative links checked; no development/test artifacts; unchanged vendor dependencies.

Matching source · Verification and limits at build time · Update instructions / 更新手順

Submitted rc.10 and all previous ZIPs/tags remain unchanged. The rc.11 upload and review-email reply are complete.

GitHub Actions: PHP 8.1 and 8.3 passed (run). All 37 packaged product files match the source tag byte-for-byte; runtime vendor files match rc.10.

Submission evidence: the author supplied the WordPress.org Submitted files screenshot showing rc.11 dated November 11, 2026, then confirmed that the reply was sent. The earlier email screenshot was a draft; it is not evidence of sending. Current record: https://github.com/ozekihiroshi/ozeki-wordpress-resilience/blob/main/docs/releases/wordpress-org-033-rc11.md

Only the release description and main-branch documentation were updated. The submitted ZIP, assets and source tag remain unchanged; their bundled pre-submission wording records the build-time status.

Ozeki Resilience 0.3.3 rc.9

WordPress.org 0.3.3 rc.9 — November 10 review response

Submitted November 11, 2026 (JST): update accepted and review-email reply sent. Awaiting the reviewer response; publication is NOT approved. The reviewer requested changes to rc.8 on November 10. All submitted ZIPs/tags remain preserved.

今回の修正 / Changes

• Markdown本文が送られた保存では、nonceが欠落・不正なら保存前に拒否します。nonceだけ・本文が配列などの不完全な送信も拒否し、保存済み原本への切替で処理を続行しません。利用者の編集権限確認は別途維持します。
• 復旧ポイント、復旧終了番号、個別復旧番号、定期保持設定を入力受付時にサニタイズし、型・形式・範囲を確認します。不正な保持設定は既存設定を置き換えません。
• 通常の記事保存や本文を送らない操作、独立したMarkdown原本、保存形式、復旧範囲は維持します。WordPress・テーマ・プラグインは信頼できる配布元から別途準備する方針も変わりません。

The Markdown editor path is now detected from either submitted source or nonce, rather than requiring both before entering nonce validation. Missing/non-string/invalid nonces and missing/non-string source fail before lock acquisition or S3 work. The independent capability check remains. Non-editor saves use previously stored source and do not consume an unverified POST original.

Recovery references and end numbers are sanitized at the form boundary and then checked against the existing exact schema, numeric syntax and integer bounds. GFS leaves are sanitized recursively; malformed rows/nested values are rejected before persistence. Individual recovery selections now require an array of positive integer strings. The shared administrative action still requires both manage_options and check_admin_referer().

All product POST/GET/REQUEST occurrences were reviewed, including configuration, cleanup confirmations, recovery selections, the core meta-box selector and startup routing. Two narrowly scoped PHPCS explanations document intentional behavior: Markdown originals are bounded UTF-8 text, not executable/rendered output; startup reads a sanitized action only to block unsafe requests, leaving login/logout validation to core. These are documented analysis exceptions, not added nonce bypasses. No global suppression was added.

ZIP and corresponding source

• Installable ZIP
• Corresponding source
• Header / stable version: 0.3.3; candidate identifier: rc.9.
• 8,283,466 bytes; 3,813 files.
• SHA-256: be152094f4c67affba938fc19e202d1ee61dba9179a5c4c313c12c7715ed5d69.
• Package audit: product files match source, 78 bundled relative links resolve, eight maintained guides, no development scripts/tests. Vendor dependencies are unchanged from rc.8. ZIP differences are the two READMEs, readme.txt, Plugin.php, GfsPolicy.php and the explanatory comment in Startup.php.
• Submitted rc.8 SHA-256 remains 1f826c27aebb28e81b726ac71f0c58a4d5f8400afe09a4d33a3c68b80c79118b.

確認結果 / Verification

• Fresh isolated WordPress 7.1.3 / PHP 8.3.36 with WP_DEBUG enabled: standard ZIP installation and activation; 3,813 installed files match; administration screen renders.
• Existing isolated community/dm sites: standard rc.8 → rc.9 update preserves configuration, pending-state hashes, previous result records and activation. Pending queues were empty; this does not claim an upgrade with queued work.
• Actual admin-action handlers in isolated WordPress: 24 malformed recovery input cases rejected without changing posts; malformed GFS retains the prior settings; missing/wrong admin nonce and unauthorized user rejected.
• Actual WordPress save hooks with real S3: Markdown creation/update preserves Japanese text and code examples; native article creation/update confirms successfully. Six incomplete/invalid editor submissions leave the document and confirmed history unchanged. Baseline and Checkpoint form operations succeed.
• Real-S3 recovery on dm: successful recovery through history number 8, with 266 post records reported. The two newly saved native/Markdown assets match the source digest a094acd84a1c30d2e5456742e1006c2bcb96ea8d714ac1c24475f5e5dbf1a5ec; no pending history remains. Existing files already matched, so this run reports zero file replacements.
• These checks invoke real WordPress APIs/hooks and admin-action handlers from PHP CLI; they do not constitute a new browser timeout/interaction test. Earlier browser evidence is retained separately.
• All existing independent M1 package contract commands plus the new editor-nonce contract pass on PHP 8.3. Test fixtures supply standard WordPress sanitization helpers where the product now uses them.
• Plugin Check 2.1.0: 0 errors / 99 warnings on the exact candidate ZIP. No input-sanitization or nonce warnings remain. The remaining categories are direct database access (34), no caching (32), meta queries (30), diagnostic error logging (2), and Japanese root README (1). These remain documented warnings, not approval.

See sanitized verification summary and Plugin Check results. Production sites were not used; the existing dedicated S3 test prefix and isolated database tables were reused. No saved S3 assets were deleted or reformatted.

Submission and reply / 更新受付と返信

2026年11月11日（日本時間）、既存申請へrc.9をアップロードし、画面の「New version of Ozeki Resilience uploaded for review.」を確認しました。07:53の自動受付メールでもrc.9の補足説明とファイル受領を確認しています。元の11月10日審査メールへ返信し、Gmailの送信完了を確認しました。現在は審査担当者の回答待ちであり、公開承認済みではありません。

The upload page lists November 10, 2026 (site date); the receipt email is November 11 at 07:53 JST. The site still displayed “Being Reviewed — waiting on action from you” immediately after upload. The waiting-for-reviewer description records our completed upload/reply, not an observed approval or a claim that the portal label changed.

Before submission, related request paths were reviewed again: shared administrator capability/nonce checks, partial editor submissions, malformed recovery references/numbers and GFS input, and archival originals versus escaped display. No additional submission blocker was identified in that bounded review. This is not a new end-to-end test of every integration or content format.

GitHub Actions PHP 8.1 and 8.3 passed: https://github.com/ozekihiroshi/ozeki-wordpress-resilience/actions/runs/42917044052

Only current documentation and release notes were updated after submission. The rc.9 source tag and ZIP remain immutable; the ZIP retains the pre-submission status wording present when built. Current status is recorded here and in the main-branch READMEs.

Full sent reply: https://github.com/ozekihiroshi/ozeki-wordpress-resilience/blob/main/docs/releases/wordpress-org-033-rc9.md

Ozeki Resilience 0.3.3 rc.10 — recovery corrections

Ozeki Resilience 0.3.3 rc.10 — recovery corrections

Submitted November 11, 2026 (JST): the existing WordPress.org application accepted rc.10, and the reply to the original review email was sent. Awaiting the reviewer response; publication is not approved.

• Fix WP-Members version identifiers and integer page references, and initialize required operational settings from the trusted installed plugin defaults.
• Keep mismatched ACF values in immutable originals/history; report them as not applied while recovering other supported content.
• Exact-ZIP clean installation and rc.9 update passed. Configuration/state hashes were retained.
• Real-S3 full-site recovery through history 22, including members, inquiry, table and articles, and a separate subsequent WordPress startup/admin render passed. Stored originals/history were unchanged.
• Plugin Check 2.1.0: 0 errors / 99 documented warnings, unchanged categories from rc.9.
• Source/ZIP audit: 3,813 files, 8 maintained bundled guides, 78 valid local links, no development files. Dependencies unchanged.

Installable asset: ozeki-resilience-0.3.3.zip (8,283,977 bytes)
SHA-256: a762c181772ded58ac403ad520a731278c4c73ed91181d3326bd1cab6420acbf

Validation record
Exact source

日本語: ACF・WP-Membersの復旧修正を含むrc.10は、2026年11月11日（日本時間）に更新受付と元の審査メールへの返信が完了しました。審査担当者の回答待ちであり、公開承認済みではありません。復旧処理の完了だけでなく、その後のWordPress起動も確認しました。提出済みrc.9のZIP・タグはそのまま残しています。インストールには添付のプラグインZIPを使い、GitHubのSource code ZIPは使用しないでください。

Ozeki Resilience 0.3.3 rc.8 - pending submission

0.3.3 rc.8 was submitted to the existing WordPress.org application on November 2, 2026 (JST). Upload accepted; reply in the original review-email thread sent. Awaiting the reviewer response; publication is NOT approved. Previous ZIPs and tags are preserved.

readme.txt・日英README・導入ガイドに、必要性と設計原則を反映しました。独立原本、信頼できるソフトウェアの別途準備、認識された設定の選択的適用、復旧のための冗長性と余裕を説明しています。

This is a documentation-only update from rc.7. All 3,796 runtime files are byte-identical. The five changed bundled files explain purpose, recovery principles, preparedness and optional integrations. Standard Posts and Pages do not require another plugin; integrations require their compatible runtime separately. Recovery does not deploy or execute archived theme/plugin code.

Verified: 3,813 installed files match the exact ZIP; admin screen renders; 78 bundled relative links resolve; eight maintained guides; no development scripts/tests/tools. Plugin Check 2.1.0: 0 errors / 107 recorded warnings. Existing rc.7 functional evidence remains applicable to the identical runtime; full recovery tests were not repeated for this wording update.

Installable ZIP: ozeki-resilience-0.3.3.zip (8,283,015 bytes)
SHA-256: 1f826c27aebb28e81b726ac71f0c58a4d5f8400afe09a4d33a3c68b80c79118b
Use the attached ZIP, not GitHub's Source code archive.

Validation and submission/reply record:
https://github.com/ozekihiroshi/ozeki-wordpress-resilience/blob/main/docs/releases/wordpress-org-033-rc8.md

CI follow-up: standalone recovery-result tests needed a WordPress locale stub after the UI guidance change. The fixtures were corrected on main (93ed60c), with English/Japanese interruption assertions. No packaged file or existing tag was changed. Historical failed runs remain visible. The corrected main run is https://github.com/ozekihiroshi/ozeki-wordpress-resilience/actions/runs/41340847737 .

提出済み：2026年11月2日（日本時間）、rc.8の更新受付と審査メールへの返信が完了。審査担当者の回答待ちで、公開承認済みではありません。

The ZIP/tag retain preparation-time documents; the linked main-branch record contains the current submission status. No release asset or tag was replaced.

Ozeki Resilience 0.3.3 rc.7 - pending submission

0.3.3 rc.7 is prepared and validated, but has not been submitted to WordPress.org. Submitted rc.6 remains awaiting the reviewer response. Publication is not approved.

復旧先の保存・削除を防止し、必要なソフトウェアの版、不足条件、中断・失敗後の操作を日英で案内します。保存形式と既存S3資産は変更しません。

The exact ZIP passed fresh installation and rc.6-to-rc.7 updates on isolated community/dm sites. All 3,813 installed files matched; settings, pending state and recovery results were preserved. Plugin Check 2.1.0: 0 errors / 107 documented warnings. The same runtime passed real-S3 scale, interruption/retry, scheduled-dispatch and browser save/recovery checks; see the record for the tested limits.

Installable ZIP: ozeki-resilience-0.3.3.zip (8,282,477 bytes)
SHA-256: b8e2d8d8961463da42f223990461f29ff7a3546212f459983ec1ebec0d307b58

Use the attached installable ZIP, not GitHub's Source code archive.

Validation and submission-note draft: https://github.com/ozekihiroshi/ozeki-wordpress-resilience/blob/main/docs/releases/wordpress-org-033-rc7.md

This candidate does not replace the submitted rc.6 record. Existing ZIPs and tags are preserved.

Ozeki Resilience 0.3.3 rc.6 - publication documentation

2026年10月28日にrc.6の更新受付と審査メールへの返信が完了しました。審査担当者の回答待ちです。WordPress.orgの公開承認はまだ得ていません。

The rc.6 update was accepted for review and the reply to the original review email was sent on October 28, 2026. Awaiting a response from the reviewer; WordPress.org publication is not approved.

rc.5と同じ実行コードを保ち、公開用の文書を整理しました。導入・復旧、AWS準備、更新、保存再開、利用条件を同梱し、過去の試験経緯や実装資料を除外しています。旧版へのダウンロード案内も修正しました。

Same runtime as the tested rc.5 candidate, with consolidated bilingual user documentation and corrected download guidance. Earlier ZIPs and tags remain historical records.

Download ozeki-resilience-0.3.3.zip below (not Source code). SHA-256: e7ca01f16903945bbf67d6e6254f5e2f6a8e28afa7fced586675df55556e22b3.

Isolated installation: passed, 3,812 installed file hashes match. Plugin Check 2.1.0: 0 errors / 107 recorded warnings. 3,795 runtime files are byte-identical to rc.5; existing recovery/update validation applies.

導入 / Setup · 確認結果 / Validation

Ozeki Resilience 0.3.3 rc.3 - review response candidate

Historical review package / 過去の審査候補です。 This is not the package recommended by the current setup guide. 現行ガイドに対応する新規導入用ZIPではありません。Current distribution status / 現行版の配布状況. The original ZIP and tag are preserved unchanged.

---

WordPress.org審査対応候補 0.3.3 rc.3。2026年10月28日、既存申請への更新受付と元の審査メールへの返信が完了しました。審査担当者の回答待ちで、公開承認済みではありません。 初期指摘の対象は0.3.2 rc.1です。

The 0.3.3 rc.3 update was received and our reply was sent in the original review thread on October 28, 2026. We are awaiting the reviewer's response; publication has not been approved.

入力検証・nonce・HTML属性出力を修正し、AWS SDKを3.401.5へ更新しました。PHP名前空間はOzekiResilience\M1へ変更。復旧機能を維持し、ホストのファイル変更禁止を尊重します。既存の保存名とhooksは互換性のため維持しています。

• Plugin Check 2.1.0: 0 errors / 104 warnings.
• Isolated WordPress 7.1.3 / PHP 8.3.35 / MariaDB / simulated S3: fresh installation, active 0.3.2 update/state preservation, native article and archived theme-file recovery, ACF free readiness and bilingual rendering passed.
• 34 local contract checks passed. Composer audit reports no known advisories. This is not a new browser/live-AWS/full-ACF-recovery trial.
• Recovery-policy and legacy-identifier questions remain for the reviewer; this is not a claim that all findings are cleared.

対応記録 / review disposition
送信済み返信 / sent reply
対応ソース / exact product source

Source commit: 2ff4306a0c8715467100866b1aa9185d708e3402
ZIP: ozeki-resilience-0.3.3.zip — 8,590,043 bytes / 3,922 files.
SHA-256: 066c4ae4f47f943a8b7cb4fa31efd6e256ad47772bdb1f4bd99c22a39804973e

Earlier submitted ZIPs and tags remain unchanged. The upload receipt and reply sending have been confirmed. Reviewer decisions on recovery and legacy identifiers remain pending; the existing application has not been approved.