feat(repository): derive dependency scopes from queries

[omegent-app]

Why

Live repository queries already retain typed predicates in an intermediate representation. Callers should not repeat repository names, paths, or manual read scopes when model metadata can identify affected relationships.

What

Adds repositoryDependency(schema), an encoded-side schema annotation. Repository construction derives nested dependency paths from the schema AST once. The same metadata extracts aliases from writes and recognizes matching query predicates; primary IDs remain automatic. Previous and next aliases are recorded for updates and removals.

How

The query IR is inspected before it reaches Cosmos, SQL, or memory adapters. eq and in predicates over annotated fields produce scoped reads, including nested whereSome paths such as parts.-1.id. Unsupported predicates and queries containing or conservatively retain repository-wide dependencies. Existing dependencyIds and explicit withReadScope remain backwards compatible.

Remarks

Stacked on #856. Scanner consumer and linked-mode validation: macs-holding/scanner#2198. Includes a patch changeset for effect-app; package checks, lint, and all tests pass locally.

[pkg-pr-new]

Open in StackBlitz

@effect-app/cli

npm i https://pkg.pr.new/effect-app/libs/@effect-app/cli@857

effect-app

npm i https://pkg.pr.new/effect-app/libs/effect-app@857

@effect-app/eslint-codegen-model

npm i https://pkg.pr.new/effect-app/libs/@effect-app/eslint-codegen-model@857

@effect-app/eslint-shared-config

npm i https://pkg.pr.new/effect-app/libs/@effect-app/eslint-shared-config@857

@effect-app/infra

npm i https://pkg.pr.new/effect-app/libs/@effect-app/infra@857

@effect-app/vue

npm i https://pkg.pr.new/effect-app/libs/@effect-app/vue@857

@effect-app/vue-components

npm i https://pkg.pr.new/effect-app/libs/@effect-app/vue-components@857

commit: 86510d8