Skip to content

fix(volume): expose native classification as a server-owned read field - #74

Merged
chen21019 merged 1 commit into
mainfrom
verification/orchestration-engine-332-volume-native-v2
Oct 2, 2026
Merged

chen21019 merged 1 commit into
mainfrom
verification/orchestration-engine-332-volume-native-v2

Conversation

@chen21019

Copy link
Copy Markdown

Outcome\nRestore volume.isNative as a read-only server classification in v1 and v2-beta without granting mutations.\n\n## Evidence\n18 focused unit tests pass with zero failures, errors, or skips. Tests cover frozen role overlays, the readonly processor pipeline, full action preservation, forged POST/PUT fields, and WrappedResource output. Release-gate named-case selection now checks only required methods while all suite failures remain enforced.\n\n## Boundaries\nNo DB migration, role expansion, frontend fallback, or runtime patch. Engine 0.183.332 remains a candidate until CI and immutable publication pass. Supersedes #73, whose CI receipt comparison failed; that failed run remains historical evidence.

@chen21019
chen21019 requested a review from a team as a code owner October 2, 2026 21:56
@chen21019
chen21019 merged commit 8c62799 into main Oct 2, 2026
7 checks passed
@chen21019
chen21019 deleted the verification/orchestration-engine-332-volume-native-v2 branch October 2, 2026 22:03
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.

1 participant