Skip to content

fix(volume): restore read-only native classification across API versions - #73

Closed
chen21019 wants to merge 1 commit into
mainfrom
verification/orchestration-engine-332-volume-native
Closed

chen21019 wants to merge 1 commit into
mainfrom
verification/orchestration-engine-332-volume-native

Conversation

@chen21019

Copy link
Copy Markdown

Cause and scope

The current Volume role overlay and packaged v1 role schemas omit isNative. The native unallocated-volume UI correctly requires an explicit false value, so eligible rows remain hidden.

Change

Expose only volume.isNative:r and supplement only the missing frozen v1 field from the existing core schema. No CRUD/action expansion, client mutation, database migration, frontend missing=false fallback or runtime patch.

Verification

18 targeted local tests passed with zero failure/error/skip; six new regressions cover actual frozen schemas, readonly processing order, complete unchanged action payloads, response true/false preservation and POST/PUT mutation exclusion. CI requires the named regressions. Formal artifact/startup and QA8080 native lifecycle acceptance remain pending; no full matrix claim.

Release

New numeric Engine candidate 0.183.332; existing tags are untouched. README, compatibility contract and candidate release note are aligned. Rollback restores the former missing-field behavior; no persisted data changes.

@chen21019

Copy link
Copy Markdown
Author

Superseded by #74 at immutable source 7a625ee. The failed CI run remains evidence; required named-case selection is corrected without relaxing all-suite failure or security gates. No release was published from #73.

@chen21019 chen21019 closed this Oct 2, 2026
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