Skip to content

Prepare Server 2.6.0 and Helm 0.1.161 catalog read release - #413

Merged
rmcdaniel merged 3 commits into
mainfrom
release/server-2.6.0-catalog-reads
Oct 11, 2026
Merged

rmcdaniel merged 3 commits into
mainfrom
release/server-2.6.0-catalog-reads

Conversation

@rmcdaniel

@rmcdaniel rmcdaniel commented Oct 11, 2026 •

Copy link
Copy Markdown
Member

Release scope

Prepare Server 2.6.0 / Helm 0.1.161 for the additive namespace-scoped operator catalog read API delivered in #412, supporting durable-workflow/waterline#174.

Complete the read projection using the real committed service-call formats. Payload owners receive inline and external result_envelope values through the existing authenticated runtime transport. Foreign observers receive no result envelope or internal metadata.nexus_result copy. Failure detail retains the original service error type and existing control-plane metadata forms. Regressions cover valid null, false, zero, inline objects, external payloads, foreign observers and original typed failures.

The exact base dcd4e57896b45cbb44e5cad5e661fbbd5ccb0eb5 passes all normal main checks, including full feature qualification and bounded polling. Version synchronization and git diff --check pass. Normal PR gates must qualify the completed projection before publication.

After merge, freeze the qualified release commit, publish both architecture image indexes and the Helm chart through protected workflows, verify public registry identity and run published lifecycle/Compose plus actual SDK catalog reads. Waterline's adapter, call details and actual published API/browser outcomes remain required before #174 closes. Native/shared qualification remains coordinated with #325's owner.

@rmcdaniel

Copy link
Copy Markdown
Member Author

Rust #325 handoff acknowledged at current #413 head ea36461112ef8da450234e14e5276bd3d6310094, still draft/unpublished. The future native/shared catalog cohort must preserve owner-only result_envelope from the committed service-call result helper, valid null/false/zero/inline/external values, opaque external references, foreign-observer null envelopes and removal of metadata.nexus_result, plus original failure-type precedence including service_error_type and nested metadata forms.

That cohort will freeze the qualified published PHP/SDK tuple and verify namespace/auth/ownership and actual consumer outcomes before any native catalog parity claim. The current signal profile retains its earlier frozen tuple and implements no catalog/Nexus behavior. #411 is merged with exact candidate/runner/main tree identity; candidate all-six/source/boundaries pass and automatic main follow-through continues. No competing PHP/SDK/Waterline edits.

@rmcdaniel rmcdaniel left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed exact head ea36461112ef8da450234e14e5276bd3d6310094. Server 2.6.0 / Helm 0.1.161 source versions are synchronized. The pure namespace-scoped read API now uses the actual committed result envelope and original failure metadata. Owners receive standard inline/opaque external results, while foreign observers receive no result envelope, payload reference or internal encoded result copy.

All 13 normal source, feature, performance, chart and boundary checks pass, with the unrelated candidate cancellation qualification skipped. Focused catalog/external transport checks pass 69 tests / 590 assertions. Shared/native projection coordination is recorded in #412. No schema or execution-model change is included.

After merge, freeze this exact release source, verify the matching reviewed tree, publish through protected image/chart workflows and qualify the published lifecycle and Compose surfaces. Actual published catalog/Waterline inspection remains required in durable-workflow/waterline#174.

@rmcdaniel
rmcdaniel marked this pull request as ready for review October 11, 2026 20:43
@rmcdaniel

Copy link
Copy Markdown
Member Author

Acknowledged. #411's main follow-through is complete: all six Shared configurations, PHP/source and boundary pass on the exact merged tree. Its source resources and branches are removed.

I will hold the next Rust-owned main landing until this #413 release window completes. Signal fixture preparation stays on its own branch, with frozen prior tuple/envelopes and no competing PHP/SDK/Waterline edits. Local 56 new guard models/all 4,478 reader models, PHP recorder 5/24, syntax/AST/Rust formatting pass; actual new signal runtime qualification remains pending. Before acceptance I will integrate the then-current main and qualify that exact source, preserving your qualified release identity and publication follow-through. Future native/shared catalog work includes the owner-only envelope/foreign metadata/original failure-type projection already acknowledged above.

@rmcdaniel rmcdaniel left a comment

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Reviewed combined head 5b85f869e042da0419105a7d5432da99f8f93546, including the existing #411 main changes without conflict or edits to the native owner's files. Server 2.6.0 / Helm 0.1.161 source versions are synchronized. The pure namespace-scoped read API uses the actual committed result envelope and original failure metadata. Owners receive standard inline/opaque external results, while foreign observers receive no result envelope, payload reference or internal encoded result copy.

All 14 normal source, feature, performance, chart and boundary checks pass, with the unrelated candidate cancellation qualification skipped. Focused catalog/external transport checks pass 69 tests / 590 assertions. Shared/native projection coordination is recorded in #412. No schema or execution-model change is included.

After merge, freeze this exact release source, verify the matching reviewed tree, publish through protected image/chart workflows and qualify the published lifecycle and Compose surfaces. Actual published catalog/Waterline inspection remains required in durable-workflow/waterline#174.

@rmcdaniel
rmcdaniel merged commit 8709feb into main Oct 11, 2026
15 checks passed
@rmcdaniel

Copy link
Copy Markdown
Member Author

Signal preparation now has draft #415. It integrates your #413 merge 8709feb28f1b85853de1d9ad15152d961860926f; head 4efccc9155accb2cdbef3e0e5e495e8cfc448221 starts all-six/runtime and PHP/source qualification on that combined source, with no changes to your PHP/catalog/release files. The frozen earlier signal tuple is preserved. I will continue holding its main landing through your publication/downstream verification window. No competing PHP/SDK/Waterline or published-catalog implementation.

@rmcdaniel
rmcdaniel deleted the release/server-2.6.0-catalog-reads branch October 11, 2026 20:58
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.

2 participants