Repository navigation
docs: prepare history-backed datetime search recovery in all eight locales - #400
Conversation
|
|
Published Workflow 2.12.0 at immutable source Normal Packagist source and dist identify that exact commit. A fresh Composer consumer, without source overrides, matches all 646 installed source/manifest files byte-for-byte. On PHP 8.3.36 / Laravel 12 / SQLite, the normally installed package passes 31 focused cases / 246 assertions: four UTC-offset writer inputs and microsecond SQL boundaries, eight registered Artisan repair cases (preview, apply, repeat, latest-history/namespace/pruning refusal and transactional rollback), and 22 UTF-8 timeline summary/unchanged-evidence boundaries. The initial consumer harness pointed at the wrong migration directory and had eight pre-assertion errors; that failed preparation is retained separately, with no product or regression-test edit. The published-package workflow has passed its package contract and is running its supported Laravel upgrade matrix. Source checks and this installed package receipt do not claim that every pending cell has passed. This qualifies the package and the documented history-backed repair command. A Server image containing this package, and its actual HTTP/database acceptance, remain required before closing the original Server-facing datetime/timeline delivery. Existing installed Server 2.11.0 still carries Core 2.10.1; no old image/tag is changed or called repaired. Native/shared/frozen catalog adoption remains separate. The wider canonical failure-storage limit remains with shared #225. All consumer/compiler/cache/runtime resources from this acceptance are removed; original failures, source identities, lockfiles and compact evidence remain. Website PR #400 now has the actual package/normal-command receipt needed for its staged 2.12.0 minimum; Pages and all-eight-route verification remain before Website completion. General independently verified all seven reviewed-source hashes and every full executable block against English. Direct current PR Sonar review has zero open/confirmed findings. The prepared package gate is satisfied; no Server image or HTTP adoption is inferred. |
Datetime search projections written by older code can retain an offset’s wall time, and a writer upgrade alone does not correct old rows. All eight search-attribute guides now explain the one-run history-backed repair command, preview/apply procedure, namespace/key guards, refusal rules and verification. Refs #399 and workflow#898 / workflow#914.
Publication gate: keep this PR in draft and unmerged until the final actual Core package contract, registry source/dist identity and normal installed command receipt arrive. Source914 merged
b3bbfdb5258c68546ae38ca1fde52818e4b05d12prepares prospective2.12.0; it is not a released safeguard yet. The staged2.12.0 minimum must be reconciled with the final artifact. Existing accepted Website work continues independently.The commands match the public signature: exact run ID, preview by default, explicit
--apply, optional exact non-empty--namespace, repeated--key, optional--json. The text requires latest retained explicitly typed upsert evidence and a matching original logical sequence, and refuses pruned/missing/stale/timezone-ambiguous selections. One unprovable selected key refuses the whole operation. It describes backups/all-writer upgrades, readback/repeat verification, andrefusedversus uncertain-storageunverified.Only derived attributes and their summary are repaired in the storage transaction; authoritative history, business commands, run/task identities and leases remain unchanged. No pruned-history restoration, separate Server visibility-query fix, image/runtime adoption or tuple promotion is claimed from a Core tag.
Validation: all seven reviewed-source hashes and complete executable blocks match English; local translation/whitespace checks precede push. No unpublished package was installed or represented as qualified. Exact refreshed-head94f3d198 checks all pass, including documentation contracts39988491847. Sonar6369953592 has zero new/accepted issues and hotspots. The package gate, actual Pages and all eight live guides still precede Website delivery. Core898 product closure stays with General.