[miinhho]

What is this PR for?

This PR fixes notebook-scoped AngularModel values not appearing in %angular output in the Angular-based New UI.

The server sends notebook-scoped updates without a paragraphId. The existing consumer only accepts updates whose paragraphId matches the current paragraph, so it discards these updates even though both paragraphs finish successfully.

The fix:

• Applies updates and removals according to their notebook and paragraph scopes.
• Retains values received before output creation and hydrates newly created or recreated output contexts.
• Preserves the original scope and interpreter group when updating an existing model from the UI.
• Cleans up retained bindings when paragraphs or published views are removed.
• Reapplies server values after template-local edits, even when the incoming value matches the cache.
• Preserves retained values when loading revisions that do not replay the Angular object registry.
• Aligns SDK scope types with server payloads and includes interpreter-group identity in interpreter-originated removal messages.

What type of PR is it?

Bug Fix

What is the Jira issue?

• https://issues.apache.org/jira/browse/ZEPPELIN-6758

How should this be tested?

From zeppelin-web-angular, run the affected consumer and SDK tests:

npm run test:shell -- \
src/app/services/ng-z.service.spec.ts \
src/app/services/runtime-compiler.service.spec.ts \
src/app/core/paragraph-base/paragraph-base.spec.ts \
src/app/pages/workspace/notebook/notebook.component.spec.ts \
src/app/pages/workspace/published/paragraph/paragraph.component.spec.ts \
src/app/pages/workspace/share/result/result.component.spec.ts \
projects/zeppelin-sdk/src/angular-object-values.spec.ts \
projects/zeppelin-sdk/src/interfaces/notebook-wire-fields.spec.ts

Check the SDK contracts and build the Angular application:

npm run typecheck:sdk-contracts
npm run build:angular -- --configuration development

For the server-side removal change, run NotebookServerTest#interpreterRemovalPreservesGroupAndRoutesAllScopes using the project's server-test setup. It checks interpreter-group metadata and notebook/global removal routing.

Manual testing

Use the Angular-based New UI with a working Spark interpreter.

1. Create a notebook-scoped model:

%spark
import org.apache.zeppelin.display.angular.notebookscope.AngularModel

val controlValue = AngularModel("controlValue", "hello")

2. Run a separate paragraph:

%angular
<div>value={{controlValue}}</div>

Verify that the output displays value=hello.
3. Update and then remove the model from Spark:

%spark
controlValue() = "updated"

%spark
controlValue.remove()

Verify that the output changes to value=updated and then clears the value.

Scope isolation, native UI-to-server updates, output recreation, and navigation cases are covered by the regression tests listed above.

Questions:

• Does the license files need to update? No
• Is there breaking changes for older versions? No
• Does this needs documentation? No