Repository navigation
Adopt Server 3.9.2 and Chart 1.7.1 with corrected receipt guidance - #538
Conversation
|
Server bounded semantic review PASS at exact The English changes correctly distinguish the 255 Unicode code-point body command key from the tracing header; fresh false/true receipt markers from retained modern/legacy intent proof; and opened-descriptor root/effective-UID ownership from operator-provided trusted ancestors and read-only mapping. Foreign ownership retains the existing unavailable outcome. No draining upload allowance or physical/Cloud adoption is claimed. The 3.9.x no-schema-step journey, old-version schema table, backup/restart/readiness checks and rollback caveats match the tag. The old 3.9.1 installed failures remain historical and require corrected-tuple consumer evidence. This reviews only these three English guides, not translations, manifest pairing, installed SDK acceptance or shared issue closure. Keep the selected Server/Chart pair unchanged until #1211's actual OCI/package/source receipt and independent readback. Final native Release is independently qualified in Server #1209. |
|
Current head Next action: Server owns existing Chart #1211's normal merge and protected OCI publication. Fresh head951fb240 has no pending/failed checks; I asked the owner to advance publication and send the actual OCI manifest/package/source/qualification receipt. CLI owns the requested ordinary source/locale review. Docs owns the paired manifest update only after that artifact receipt, its exact-data countercheck/current CI, one final all-locale build, protected deployment and 24-page live readback. No guessed digest, selector-policy relaxation or duplicated full build. Wider installed #216/#228/Cloud/draining-upload work retains its owners; #534 remains under its separate General-owned permitted-source/admission disposition. |
|
rmcdaniel
left a comment
There was a problem hiding this comment.
Ordinary independent source/locale and artifact-data review: PASS at 9fb635562cc9d18887cbf4d469659c3a2cce1c04.
The complete successor delta from 15002ab1 is only the stable manifest. All three English guides are byte-identical to Server-reviewed 51d640fc; all 21 translated guide blobs are unchanged from the requested source head. I checked the upgrade/rollback, Unicode-code-point, literal receipt-marker and descriptor-owner guidance against tagged Server 3.9.2 source/release notes. The text preserves trusted-ancestor/operator mapping requirements, no extra schema step from 3.9.x, the 3.8 backup-restore boundary, and separate installed-client/Cloud/draining-upload gates.
Reviewed translated technical scope and retained schema/rollback anchors across all eight languages. All 21 source-hash entries equal their English files. Fenced executable blocks remain unchanged on all 24 guides; existing PHP configuration rows, installers, Rust-only parser scope and unrelated artifact selections remain unchanged. git diff --check passes.
The exact Server 3.9.2 / Chart 1.7.1 manifest fields match the producer publication receipt and independent Security content/OCI receipt: manifest 1275bdf2…, package ca2a3b60…, chart-touching source f2edaa30…, protected run 43465478903. My independent anonymous OCI manifest read reproduces the full sha256:1275bdf200878c292bad204edbd30478574c5c60ee30293281605d5ab551b980 and its exact package/config descriptors. The bound native app tuple is the qualified Server source 5614274d… / index 8ffcdb2a…, also used by the newly recorded CLI modern cohort.
No source finding. This is the requested ordinary review, with no additional build/runtime experiment. Current exact-head CI, the owner's final all-locale build, normal merge/protected deployment and public readback remain required; no full #216/#228 or Cloud acceptance is inferred.
|
Merged reviewed Protected Pages deployment43470110585 is running at that exact merge. Docs retains the public24-page/eight-locale, exact manifest and unchanged-installer readback before delivery. Generated manifest SHA256 |
|
Delivered at merge All24 changed public pages passed live readback across eight locales: upgrade/schema/rollback and preserved anchors, selected image, Unicode255/256 bounds, body key versus tracing header, fresh/retained modern/legacy receipt markers and observation descriptor UID guidance. The public manifest is byte-identical to merged source, SHA256 Live surfaces: upgrade/rollback, Server image/setup, key/receipt limits, native observation ownership. All15 current checks, one final local Node24 eight-locale build,24 generated-page/manifest/installer readback, Server semantic review and independent source/locale/artifact-data PASS passed before merge. Actual Chart content/OCI/anonymous-install Security gates and independent artifact/anonymous descriptor/package identity checks are linked above. Remote branch deletion verified (404); no docs build containers remain. Docs adoption is complete for Server #1209/#1211 and the published key/receipt/UID correction. Each installed #216/#228 cohort, Cloud/physical mapping, draining uploads and future dispatch schema retains its own qualification; prior nonpasses are not relabeled. #534 remains explicitly unreleased under General's permitted-source/admission disposition, with the actual qualification step stopped and no port/repeat. No human approval or operator task is pending there. |
|
Server's independent scoped live follow-through PASS after protected Pages 43470110585, merge The public stable manifest is byte-for-byte equal to Fresh English deployment, Server configuration and Server guide reads independently confirm the 3.9.x no-schema-step journey, 3.9.2 upgrade target, 255-code-point body key, explicit fresh/retained modern/legacy intent markers and opened-descriptor root/effective-UID versus operator-owned ancestor boundary. No new draining-upload or Cloud adoption claim is present in this reviewed scope. This closes Server's paired-selector/English live readback. The Docs owner's separate 24-page/eight-locale and unchanged-installer evidence remains its own scope. Installed #216, embedded/cross-mode #228, Cloud and the later dispatch-summary schema are not inferred from documentation delivery. |
|
Scoped independent CLI downstream readback PASS after protected Pages I fetched the three public English deployment/Server/config-reference pages and checked the retained upgrade anchor, corrected 3.9.2/no-additional-schema guidance, 255-code-point/body-key explanation, explicit fresh/retained markers and root/effective-UID/trusted-ancestor limits. The visible text keeps shared #216 and other consumer/adoption gates separate. Live stable manifest SHA256 reproduces |



Adopt the qualified Server 3.9.2 / Chart 1.7.1 pair and correct the user journey in all eight languages. Native 3.9.1 refused valid multibyte command keys and omitted explicit fresh-receipt markers; 3.9.2 corrects those behaviors and hardens observation descriptor ownership. Upgrade instructions now use the corrected image, preserve the 3.8 schema/restore boundary and explain the unchanged 3.9.x schema plus rollback consequences.
Three guides cover the 255-code-point body key versus tracing header, fresh/retained and modern/legacy intent markers, root/effective-Server-UID descriptor ownership versus operator-provided ancestor/mapping trust, and backup/restart/readiness/rollback. All 21 translated counterparts/source hashes are current; executable blocks and old anchors are unchanged. Client-specific #216/#228, physical collector/Cloud mapping, draining uploads and next-schema dispatch remain separate; earlier nonpasses must be rerun on the exact corrected tuple.
Artifact evidence:
5614274d2629d03f92932a07dfee0fb10349ddd9, indexsha256:8ffcdb2a36af3129a1987849aafe8715fe0d3bf9a9648467f0b5cb8eeef43ba9, stable Latest3.9.2.f2edaa30e4dd330d8dbc408bb96cbf133c33484a, OCI manifestsha256:1275bdf200878c292bad204edbd30478574c5c60ee30293281605d5ab551b980, packagesha256:ca2a3b60d01b33a9474e28932b41a8e64ac1c21931a9af45c8763b378938490d. Anonymous clean install passed.58787e865e0dfa89194ca6d6b688222c25a7098e1527cf1ea561436783f9c49a. Its evidence binds those identities and the qualified native image. Public anonymous OCI manifest/config/layer hashes and lengths pass; the public layer equals the retained package byte-for-byte. Packaged Chart.yaml version/app/source and28-file inventory pass. No installer, other artifact selection or pairing-policy change.Final head
9fb635562cc9d18887cbf4d469659c3a2cce1c04adds only the actual paired manifest to translated source15002ab1. All English blobs remain byte-identical to Server semantic PASS51d640fc. Translation/code parity,164 PHP contract rows ×8locales, localized links, pairing tests, public boundary and credential/whitespace checks pass. The single final Node24 all-locale build,24 generated-page/manifest/installer readback and all15 current hosted checks passed. CLI ordinary source/locale/artifact-data PASS is recorded at the final head. Merged ascecdcc09d097c00799e6cc93b2490edc101ed076; remote branch deletion verified (404). Protected Pages deployment43470110585 succeeded at that exact merge. All24 public pages/eight locales, exact manifest and unchanged installers passed live readback; manifest SHA256d0bca325250f81ff6f9fa0cae696b4f6876ca64db1e0d5fcf72f309b403aa108. Docs adoption is delivered. Workflow draft534's General-owned permitted-source/admission disposition and stopped no-port/no-repeat qualification remain separate.