fix(api): enforce create-only response fields on POST actions - #77
Merged
Merged
Conversation
chen21019
force-pushed
the
verification/orchestration-engine-0.183.333
branch
from
October 3, 2026 06:50
9276f06 to
0d94f7d
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Fix the shared read-on-create-only response boundary: only POST creation (no action) can return these fields; POST lifecycle actions are redacted. All three wrapper callers share the actual dispatch distinction. Preserve true first-secret delivery, ordinary readable fields, null-redaction representation, v1/v2 role schemas and account authorization. Bump the numeric component to 0.183.333 and align README/compatibility/candidate note. Local focused checks: 19 tests, zero failures/errors/skips (14 new cases and five adjacent controls). Independent limited source review found no confirmed bypass/regression. Exact-source CI and immutable publication are pending. Existing failed QA receipts remain HOLD; native QA8080 lifecycle and full role matrix are not claimed complete. No database/proxy/authentication changes.