From 94e5c23c62090461a32c838e20e2da4e18c3be7d Mon Sep 17 00:00:00 2001
From: Dimoshka <dmytro.prylutskyi@outlook.com>
Date: Tue, 20 Oct 2026 14:16:44 +0000
Subject: [PATCH 01/12] chore(workspace): move the melos scripts to the Melos 8
 forms

Melos 8 changes how scripts are declared: a plain string is handed to
/bin/sh verbatim, so a nested `melos exec` call only resolves when a
global melos binary happens to be on PATH. Declaring `exec` with a
`command` lets Melos 8 rewrite the nested call to `dart run melos:melos`,
and `packageFilters` replaces the `--dir-exists`/`--depends-on` CLI
flags with their camel-cased config keys.

The `ci` script becomes a `steps` list, so the same rewrite applies to
each step that is a bare script name.

The workspace now resolves Melos 8.9.0 from the lock file, which also
drops the platform/cli_util/pub_updater/coverage constraints that Melos
7.8.2 required.

Signed-off-by: Dimoshka <dmytro.prylutskyi@outlook.com>
---
 pubspec.lock | 20 ++++++++++----------
 pubspec.yaml | 30 +++++++++++++++++++++++-------
 2 files changed, 33 insertions(+), 17 deletions(-)

diff --git a/pubspec.lock b/pubspec.lock
index a09401e..5895e3b 100644
--- a/pubspec.lock
+++ b/pubspec.lock
@@ -173,10 +173,10 @@ packages:
     dependency: transitive
     description:
       name: cli_util
-      sha256: "71e43f1976c3eae2d9468a5b4d6600bf8cae61508b87f27fa1799228935d48ab"
+      sha256: "89b8801ba49f8b593fbf2d3e59efd0f566c46cd4ba6837ae2610c72b52a0f899"
       url: "https://pub.dev"
     source: hosted
-    version: "0.5.2"
+    version: "0.6.0"
   clock:
     dependency: transitive
     description:
@@ -221,10 +221,10 @@ packages:
     dependency: transitive
     description:
       name: coverage
-      sha256: "956a3de0725ca232ad353565a8290d3357592bf4250f6f298a185e2d949c5d3d"
+      sha256: ff89e37c19355194e279d26dafe8e4bece46c9ea63a30be4dc68214f5bc290d3
       url: "https://pub.dev"
     source: hosted
-    version: "1.15.1"
+    version: "1.16.0"
   crypto:
     dependency: transitive
     description:
@@ -538,10 +538,10 @@ packages:
     dependency: "direct dev"
     description:
       name: melos
-      sha256: "5fc1a858e3d90fdc42f2f423b95f901214bbc3d9e80c99125d9352f12453721d"
+      sha256: "140e51d7990b5134663e64b39e19d3b64ead16382e69127c205942c91e752b16"
       url: "https://pub.dev"
     source: hosted
-    version: "7.8.2"
+    version: "8.9.0"
   meta:
     dependency: transitive
     description:
@@ -626,10 +626,10 @@ packages:
     dependency: transitive
     description:
       name: platform
-      sha256: a36d119c13416516a7b5913fbe8af8531e11633d784c550b2125f76c758524ec
+      sha256: "5d6b1b0036a5f331ebc77c850ebc8506cbc1e9416c27e59b439f917a902a4984"
       url: "https://pub.dev"
     source: hosted
-    version: "3.2.0"
+    version: "3.1.6"
   pool:
     dependency: transitive
     description:
@@ -674,10 +674,10 @@ packages:
     dependency: transitive
     description:
       name: pub_updater
-      sha256: "739a0161d73a6974c0675b864fb0cf5147305f7b077b7f03a58fa7a9ab3e7e7d"
+      sha256: "3aadeb8c68d15ef9d117b36474ddcc543b48ae1e64f7dd71407da26df66bf7c8"
       url: "https://pub.dev"
     source: hosted
-    version: "0.5.0"
+    version: "0.6.0"
   pubspec_parse:
     dependency: transitive
     description:
diff --git a/pubspec.yaml b/pubspec.yaml
index c5722ab..4328c70 100644
--- a/pubspec.yaml
+++ b/pubspec.yaml
@@ -20,15 +20,31 @@ workspace:
   - tools/*
 
 dev_dependencies:
-  # [VERIFY T12] Melos 8.x exists; the specification pins the 7.x line.
-  # See docs/spec/open-questions.md before moving to 8.
-  melos: ^7.0.0
+  melos: ^8.0.0
 
 melos:
   scripts:
     format: dart format --set-exit-if-changed .
-    analyze: melos exec -c 1 -- dart analyze --fatal-infos
-    gen: melos exec -c 1 --depends-on build_runner -- dart run build_runner build --delete-conflicting-outputs
+    analyze:
+      exec:
+        command: dart analyze --fatal-infos
+        concurrency: 1
+    gen:
+      exec:
+        command: dart run build_runner build --delete-conflicting-outputs
+        concurrency: 1
+      packageFilters:
+        dependsOn: build_runner
     arch: dart run tools/arch_check/bin/arch_check.dart
-    test: melos exec -c 4 --dir-exists=test -- dart test
-    ci: melos run format && melos run analyze && melos run arch && melos run test
+    test:
+      exec:
+        command: dart test
+        concurrency: 4
+      packageFilters:
+        dirExists: test
+    ci:
+      steps:
+        - format
+        - analyze
+        - arch
+        - test

From c4fd162a4c4be567ad23ba8033ea5ec97059857f Mon Sep 17 00:00:00 2001
From: Dimoshka <dmytro.prylutskyi@outlook.com>
Date: Tue, 20 Oct 2026 14:16:54 +0000
Subject: [PATCH 02/12] ci: run melos from the workspace lock instead of a
 global install

The global install pinned Melos 7 while the workspace lock now resolves
Melos 8, so the runner and the workspace disagreed about the script
schema. Running `dart run melos:melos` uses the version from
pubspec.lock, which keeps CI and local runs on the same tool.

`flutter pub get` stays ahead of every `dart run` step because `dart
run` resolves the package through the workspace
`.dart_tool/package_config.json`. `flutter pub get` is required rather
than `dart pub get` because the workspace contains Flutter packages.

Signed-off-by: Dimoshka <dmytro.prylutskyi@outlook.com>
---
 .github/workflows/ci.yml | 12 +++++-------
 1 file changed, 5 insertions(+), 7 deletions(-)

diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 6807fdd..41d2081 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -20,9 +20,6 @@ jobs:
         with:
           channel: stable
 
-      - name: Install Melos
-        run: dart global activate melos ^7.0.0
-
       - name: Resolve workspace
         run: flutter pub get
 
@@ -30,14 +27,15 @@ jobs:
       # - name: Check generated code is up to date
       #   run: dart run tools/codegen_check/bin/codegen_check.dart
 
+      # Melos comes from the workspace lock file: `dart run melos:melos`, no global install.
       - name: Format
-        run: melos run format
+        run: dart run melos:melos run format
 
       - name: Analyze
-        run: melos run analyze
+        run: dart run melos:melos run analyze
 
       - name: Architecture rules
-        run: melos run arch
+        run: dart run melos:melos run arch
 
       - name: Test
-        run: melos run test
+        run: dart run melos:melos run test

From 01b7f0a80c2b2868eddbf697ec6b2e29d075057f Mon Sep 17 00:00:00 2001
From: Dimoshka <dmytro.prylutskyi@outlook.com>
Date: Tue, 20 Oct 2026 14:17:11 +0000
Subject: [PATCH 03/12] chore(deps): record the build_runner ceiling in the
 member pubspecs

The pin comment only said that build 4 was needed, which left the
reasoning implicit. Name the two packages that actually hold build at
^4.0.4 - injectable_generator 3.1.3 and schemantic_builder 1.0.0 - so
the ceiling can be revisited when either of them moves to build 5.

The constraint itself is unchanged, so the resolution is unchanged.

Signed-off-by: Dimoshka <dmytro.prylutskyi@outlook.com>
---
 clients/app/pubspec.yaml        | 2 +-
 clients/site/pubspec.yaml       | 2 +-
 packages/contracts/pubspec.yaml | 2 +-
 packages/design/pubspec.yaml    | 2 +-
 runtime/core/pubspec.yaml       | 2 +-
 5 files changed, 5 insertions(+), 5 deletions(-)

diff --git a/clients/app/pubspec.yaml b/clients/app/pubspec.yaml
index 7e4e198..7fe8ef0 100644
--- a/clients/app/pubspec.yaml
+++ b/clients/app/pubspec.yaml
@@ -17,6 +17,6 @@ dependencies:
   flutter_bloc: ^9.1.1
   injectable: ^3.0.0
 dev_dependencies:
-  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, injectable_generator needs build 4
+  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 and schemantic_builder 1.0.0 pin build ^4.0.4
   flutter_lints: ^6.0.0
   injectable_generator: ^3.0.0
diff --git a/clients/site/pubspec.yaml b/clients/site/pubspec.yaml
index acca3e8..d7698f0 100644
--- a/clients/site/pubspec.yaml
+++ b/clients/site/pubspec.yaml
@@ -12,4 +12,4 @@ dependencies:
   alteri_one_design: ^0.0.1
   jaspr: ^0.23.5
 dev_dependencies:
-  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, injectable_generator needs build 4
+  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 and schemantic_builder 1.0.0 pin build ^4.0.4
diff --git a/packages/contracts/pubspec.yaml b/packages/contracts/pubspec.yaml
index 2a0b118..1e24573 100644
--- a/packages/contracts/pubspec.yaml
+++ b/packages/contracts/pubspec.yaml
@@ -18,5 +18,5 @@ dependencies:
   schemantic: ^1.0.0
   meta: ^1.19.0
 dev_dependencies:
-  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, injectable_generator needs build 4
+  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 and schemantic_builder 1.0.0 pin build ^4.0.4
   test: ^1.33.0
diff --git a/packages/design/pubspec.yaml b/packages/design/pubspec.yaml
index 12cf59f..1b96e0e 100644
--- a/packages/design/pubspec.yaml
+++ b/packages/design/pubspec.yaml
@@ -19,5 +19,5 @@ dependencies:
     sdk: flutter
   yaml: ^3.1.4
 dev_dependencies:
-  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, injectable_generator needs build 4
+  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 and schemantic_builder 1.0.0 pin build ^4.0.4
   flutter_lints: ^6.0.0
diff --git a/runtime/core/pubspec.yaml b/runtime/core/pubspec.yaml
index ae5ed93..be6173a 100644
--- a/runtime/core/pubspec.yaml
+++ b/runtime/core/pubspec.yaml
@@ -22,7 +22,7 @@ dependencies:
   shelf: ^1.4.3
   yaml: ^3.1.4
 dev_dependencies:
-  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, injectable_generator needs build 4
+  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 and schemantic_builder 1.0.0 pin build ^4.0.4
   injectable_generator: ^3.0.0
   bloc_test: ^10.0.0
   mocktail: ^1.0.5

From 8a59d4c091f3af3e87ac5f42225ebdfdf6aa3c03 Mon Sep 17 00:00:00 2001
From: Dimoshka <dmytro.prylutskyi@outlook.com>
Date: Tue, 20 Oct 2026 14:20:15 +0000
Subject: [PATCH 04/12] docs(adr): record the Melos 8 tooling line

The spec pinned Melos 7 while 8.9.0 was the current pub.dev release, and the
question of the line was open as Q2 with the technical check T12 on the
script syntax. The owner approved the Melos 8 line on 2026-10-20.

The record is needed because two constraints are not visible from the
pubspecs alone: Melos 8 rewrites a nested melos call to 'dart run
melos:melos' only in the exec: and steps: forms, and two dependencies
cannot move because the generators pin build ^4.0.4 and genkit_openai
pins openai_dart ^8.1.0.

Signed-off-by: Dimoshka <dmytro.prylutskyi@outlook.com>
---
 docs/adr/0011-melos-8-tooling.md | 32 ++++++++++++++++++++++++++++++++
 1 file changed, 32 insertions(+)
 create mode 100644 docs/adr/0011-melos-8-tooling.md

diff --git a/docs/adr/0011-melos-8-tooling.md b/docs/adr/0011-melos-8-tooling.md
new file mode 100644
index 0000000..3faad3c
--- /dev/null
+++ b/docs/adr/0011-melos-8-tooling.md
@@ -0,0 +1,32 @@
+# 0011. Melos 8 tooling line
+
+- Status: Accepted
+- Date: 2026-10-20
+
+## Context
+The workspace was on Melos 7.8.2 while Melos 8.9.0 is the current pub.dev release, and the spec pinned the old line in several places. The question of the Melos line was open as Q2 in `docs/spec/open-questions.md`, with the technical check T12 covering the script syntax. The Dart SDK that ships with Flutter stable no longer has `dart global activate`, so a global Melos installation is no longer a practical way to run the scripts.
+
+Melos 8 also changed how the scripts are written. A nested Melos call is rewritten to `dart run melos:melos` only in the `exec:` and `steps:` forms. A legacy plain-string script is handed to the shell unchanged and fails with `melos: not found` when no global `melos` binary is on `PATH`.
+
+Two dependencies could not move to their latest versions. `build_runner` 2.17.1 requires `build >=5.0.0 <5.1.0`, while `injectable_generator` 3.1.3 and `schemantic_builder` 1.0.0 both pin `build: ^4.0.4`; `build_runner` 2.17.0 is retracted on pub.dev. `openai_dart` stays on the 8.1.x line because `genkit_openai` 1.0.0 pins `openai_dart: ^8.1.0`.
+
+## Decision
+The owner approved the Melos 8 line on 2026-10-20. This closes Q2 and the technical check T12.
+
+Melos runs from the workspace lock file: `dart run melos:melos run <script>`. No global installation is needed, neither in CI nor on a workstation. A contributor who prefers a global tool installs it with `dart pub global activate melos` and writes `melos run <script>`.
+
+The `melos: scripts:` block in the root `pubspec.yaml` uses the Melos 8 forms: `exec:` with `command:` and `concurrency:`, `packageFilters:` with the camel-cased `dirExists` and `dependsOn` names, and a `steps:` list for the `ci` composite. The entries of `steps:` are bare script names. A literal `melos run <script>` inside `steps:` is passed to the shell unchanged and fails when no global `melos` binary is on `PATH`.
+
+`build_runner` and `openai_dart` stay on their current lines. The `build_runner` pin is held by the `build ^4.0.4` ceiling of the generators and by the retraction of 2.17.0; the `openai_dart` pin is held by `genkit_openai` 1.0.0.
+
+## Alternatives
+- Melos 7 with a global installation. Rejected: the Dart SDK in Flutter stable no longer has `dart global activate`, so the scripts would depend on a tool that the lock file does not pin.
+- A global Melos in CI, installed with `dart pub global activate melos ^8.0.0`. Rejected: it puts a second, unpinned copy of Melos next to the one the lock file pins.
+- Keep the plain-string scripts and put the Melos 8 forms only in CI. Rejected: the scripts would behave differently in CI and on a workstation.
+- Upgrade `build_runner` and `openai_dart` to their latest versions. Rejected for now: the generators pin `build ^4.0.4` and `build_runner` 2.17.0 is retracted, and `genkit_openai` 1.0.0 pins `openai_dart: ^8.1.0`.
+
+## Consequences
+- The scripts are run as `dart run melos:melos run <script>`. The invocation is stated once, in `docs/spec/architecture.md`, section 5.2.
+- The `melos: scripts:` block is Melos 8 only. It does not run under Melos 7.
+- The lock file holds `platform` at 3.1.6, forced by the `platform: ">=3.1.6 <3.2.0"` constraint of melos 8.9.0.
+- The `build_runner` pin is a known ceiling. It is revisited when the generators move to `build` 5.

From 43358ce8bfce090bb58d987f816d330f469e99ba Mon Sep 17 00:00:00 2001
From: Dimoshka <dmytro.prylutskyi@outlook.com>
Date: Tue, 20 Oct 2026 14:21:20 +0000
Subject: [PATCH 05/12] docs(spec): state the Melos 8 tooling line once

The spec pinned Melos 7 in six places and repeated the number in files
that only need to point at it. Architecture section 4 now carries the
version and the new build_runner ceiling; product.md and the glossary
keep a pointer instead of a copy; roadmap.md names the new invocation
and the M0 line; open-questions.md closes Q2 and T12 and names
ADR-0011.

Section 5.2 is rewritten around the Melos 8 exec:/steps: forms and
drops the [VERIFY] line, because the result of that check now lives in
ADR-0011 and in open-questions.md instead of in a third place.

Signed-off-by: Dimoshka <dmytro.prylutskyi@outlook.com>
---
 docs/spec/architecture.md       | 45 +++++++++++++++++++++++++--------
 docs/spec/forbidden-glossary.md |  2 +-
 docs/spec/open-questions.md     |  7 +++--
 docs/spec/product.md            |  4 +--
 docs/spec/roadmap.md            |  4 +--
 5 files changed, 43 insertions(+), 19 deletions(-)

diff --git a/docs/spec/architecture.md b/docs/spec/architecture.md
index e4317b1..6018014 100644
--- a/docs/spec/architecture.md
+++ b/docs/spec/architecture.md
@@ -10,7 +10,7 @@ Minimum versions as of the date of writing. Check the current version on pub.dev
 |---|---|---|
 | Dart SDK | `^3.13.0` | fixed |
 | Dart workspace | globs in `workspace:` | globs since Dart 3.11; one `pubspec.lock` at the root |
-| Melos | 7.x | configured in the root `pubspec.yaml`; `melos.yaml` is not used [VERIFY current version] |
+| Melos | `^8.0.0` | configured in the root `pubspec.yaml`; `melos.yaml` is not used; the scripts are run from the workspace lock (section 5.2) |
 | bloc | `^9.2.0` | pure Dart. `flutter_bloc` only in the client |
 | bloc_concurrency | current | `sequential`, `droppable`, `restartable`, `concurrent` |
 | bloc_test | current | state tests [VERIFY compatibility with bloc 9] |
@@ -27,7 +27,7 @@ Minimum versions as of the date of writing. Check the current version on pub.dev
 | hive_ce | current | `Box` and `LazyBox` |
 | shelf | current | HTTP and HTTPS through `securityContext` [VERIFY signature] |
 | injectable | current | DI in `core` and `app`, environments `dev`, `prod`, `test` |
-| build_runner | current | code generation for schemantic and injectable |
+| build_runner | `>=2.16.1 <2.17.0` | code generation for schemantic and injectable; 2.17.0 is retracted, 2.17.1 needs `build` 5, and the generators pin `build` 4 |
 | yaml | current | configuration parsing |
 | http | current | client in `alteri_one_client` and providers |
 
@@ -35,7 +35,7 @@ All workspace members resolve together. Version conflicts appear immediately. Ke
 
 ## 5. Repository layout
 
-The monorepo is one Dart workspace (one `pubspec.lock`, shared dependency resolution) plus Melos 7 (scripts, filtering, versions, publishing). Packages are grouped by purpose and by publishing rules, not by technology.
+The monorepo is one Dart workspace (one `pubspec.lock`, shared dependency resolution) plus Melos 8 (scripts, filtering, versions, publishing). Packages are grouped by purpose and by publishing rules, not by technology.
 
 ```
 alteri-one/
@@ -100,7 +100,7 @@ alteri-one/
 
 ### 5.2 Melos configuration
 
-Melos 7 reads its settings from the root `pubspec.yaml`. There is no separate `melos.yaml`. Scripts are declared in `melos.scripts`.
+Melos 8 reads its settings from the root `pubspec.yaml`. There is no separate `melos.yaml`. Scripts are declared in `melos.scripts`.
 
 ```yaml
 # pubspec.yaml (root)
@@ -117,18 +117,43 @@ workspace:
   - e2e
   - tools/*
 dev_dependencies:
-  melos: ^7.0.0                    # [VERIFY current version on pub.dev]
+  melos: ^8.0.0
 melos:
   scripts:
-    analyze: melos exec -c 1 -- dart analyze --fatal-infos
-    test: melos exec -c 4 --dir-exists=test -- dart test
     format: dart format --set-exit-if-changed .
-    gen: melos exec -c 1 --depends-on build_runner -- dart run build_runner build --delete-conflicting-outputs
+    analyze:
+      exec:
+        command: dart analyze --fatal-infos
+        concurrency: 1
+    gen:
+      exec:
+        command: dart run build_runner build --delete-conflicting-outputs
+        concurrency: 1
+      packageFilters:
+        dependsOn: build_runner
     arch: dart run tools/arch_check/bin/arch_check.dart
-    ci: melos run format && melos run analyze && melos run arch && melos run test
+    test:
+      exec:
+        command: dart test
+        concurrency: 4
+      packageFilters:
+        dirExists: test
+    ci:
+      steps:
+        - format
+        - analyze
+        - arch
+        - test
 ```
 
-[VERIFY: syntax of `melos.scripts`, composite scripts, and `melos exec` flags in the selected Melos 7 version.]
+Melos is invoked from the workspace lock file: `dart run melos:melos run <script>`. No global installation is needed, and CI uses the same invocation. A contributor who prefers a global tool installs it with `dart pub global activate melos` and writes `melos run <script>` (ADR-0011).
+
+Melos 8 rules that the block above depends on:
+
+- `run` and `exec` are mutually exclusive. The command of an `exec` script goes into the `command` key.
+- The filter names in `packageFilters` are camel-cased: `dirExists`, `dependsOn`.
+- A composite script lists other scripts under `steps`, and the entries are bare script names. A literal `melos run <script>` inside `steps` is handed to the shell unchanged and fails when no global `melos` binary is on `PATH`.
+- `exec` scripts run in every package that the filters select. Private packages (`publish_to: none`) are included by default.
 
 Versions and publishing: `melos version` uses conventional commits for `packages/`, `providers/`, and `extensions/`. Publishing follows the dependency order. Packages with `publish_to: none` are never published.
 
diff --git a/docs/spec/forbidden-glossary.md b/docs/spec/forbidden-glossary.md
index aefff6a..98770de 100644
--- a/docs/spec/forbidden-glossary.md
+++ b/docs/spec/forbidden-glossary.md
@@ -12,7 +12,7 @@ Do not use anything listed here, even if you find it in old examples, articles,
 | MCP stdio as the extension transport | replaced by AOT modules and built-in mode | `Isolate.spawnUri` behind `ExtensionTransport`, or built-in mode |
 | `alterione-sdk` as the only package | replaced by a set of packages | `alteri_one_*` |
 | `alterione_*` as a package prefix | corrected | `alteri_one_*` |
-| `melos.yaml` and `pubspec_overrides.yaml` | Melos 7 and pub workspaces | root `pubspec.yaml` with `workspace:` and `melos:` |
+| `melos.yaml` and `pubspec_overrides.yaml` | Melos and pub workspaces | root `pubspec.yaml` with `workspace:` and `melos:` |
 | Node.js or npm as the agent runtime | project decision | Dart, native binary |
 | Multi-user mode, accounts, tenants | out of scope: a personal assistant | one owner, devices with tokens |
 | `sqlite`, `drift` | replaced | Hive CE |
diff --git a/docs/spec/open-questions.md b/docs/spec/open-questions.md
index bb9ffbc..59e97f6 100644
--- a/docs/spec/open-questions.md
+++ b/docs/spec/open-questions.md
@@ -9,17 +9,17 @@ Added during the M0 scaffold (2026-10-17). Until answered, the scaffold takes th
 | ID | Question | Conservative choice taken |
 |---|---|---|
 | Q1 | schemantic line: the spec pins 0.2.x ("do not use 1.0.0-rc.1 until verified"), but `genkit 1.0.0` declares `schemantic: ^1.0.0`, so 0.2.x cannot coexist with genkit in one workspace, and schemantic 1.0.0 is now a stable release. Confirm the move to the 1.0.0 line and update section 4. | pinned `schemantic: ^1.0.0` everywhere |
-| Q2 | Melos line: the spec pins Melos 7 everywhere; Melos 8.x is the current pub.dev release. Migrate to 8 and update sections 4 and 5.2? [VERIFY T12] covers script syntax on 7.x. | pinned `melos: ^7.0.0` (resolves 7.8.2) |
+| Q2 | ~~Melos line: the spec pins Melos 7 everywhere; Melos 8.x is the current pub.dev release. Migrate to 8 and update sections 4 and 5.2?~~ Resolved 2026-10-20: the owner approved the Melos 8 line. The workspace resolves `melos: ^8.0.0` (8.9.0), the scripts use the Melos 8 `exec:` and `steps:` forms, and Melos runs from the workspace lock as `dart run melos:melos` with no global install (ADR-0011). | resolved |
 | Q3 | `tools/docs_check` is required by `docs/spec/index.md` ("Rules for maintaining documents") but is missing from the repository layout in `docs/spec/architecture.md`, section 5. Add it to section 5? | scaffolded `tools/docs_check` |
 | Q4 | ~~Repository URL: the spec gives the repository name `alteri-one` but not the GitHub owner.~~ Resolved 2026-10-17: the owner is `dip-develop`; all pubspecs and docs use `https://github.com/dip-develop/alteri-one`. | resolved |
 | Q5 | `public_member_api_docs` cannot coexist with the primary-constructor style mandated by section 7.2: the Dart 3.13.5 analyzer does not attach `///` comments to primary-constructor parameters (the style used by every example in `domain.md` section 8). Re-enable the lint when the analyzer supports parameter docs. Until then, parameter dartdoc stays mandatory by convention; `packages/AGENTS.md` ("public classes and methods have English dartdoc") is enforced in review, not by the analyzer. | lint omitted from the shared set; docs kept by convention |
 | Q6 | Section 7.3 shows named `new` constructors with a dot (`new origin()`); the Dart 3.13.5 compiler rejects the dot and requires a space (`new origin() : x = 0, y = 0;`), named factories are written without the class name (`factory standard() { ... }`), and named `new` factories are illegal. Update section 7.3 with the compiler-verified forms. | code follows the compiler forms probed on 3.13.5 |
 
-Previously none were open. Decisions are recorded in ADR-0005, ADR-0006, and ADR-0009.
+Previously none were open. Decisions are recorded in ADR-0005, ADR-0006, ADR-0009, and ADR-0011.
 
 ## 25.2 Technical checks [VERIFY]
 
-T1 is closed (ADR-0007). T14 is closed: the `RunBloc` suite in `alteri_one_core` runs under `bloc_test` 10 with bloc 9.2.
+T1 is closed (ADR-0007). T12 is closed (ADR-0011): the workspace scripts use the Melos 8 `exec:` and `steps:` forms, and Melos runs from the workspace lock as `dart run melos:melos`. T14 is closed: the `RunBloc` suite in `alteri_one_core` runs under `bloc_test` 10 with bloc 9.2.
 
 | ID | What to verify | When | What to do on failure |
 |---|---|---|---|
@@ -34,7 +34,6 @@ T1 is closed (ADR-0007). T14 is closed: the `RunBloc` suite in `alteri_one_core`
 | T9 | `hive_ce` API names (`openLazyBox`, encryption) | M0 | adjust the adapter |
 | T10 | the `SKILL.md` format in `genkit_middleware` | M5 | a custom parser |
 | T11 | the `dart build cli` command on Dart 3.13 for each OS | M4 | `dart compile exe` |
-| T12 | `melos.scripts` syntax, composite scripts, `melos exec` flags | M0 | fix the root `pubspec.yaml` |
 | T13 | the `shelf_io.serve` signature with `securityContext` | M4b | a TLS proxy in front of the daemon |
 | T14 | `bloc_test` compatibility with bloc 9 | M2 | test transitions as pure functions |
 | T15 | `StatePublisher` queue limits and overflow behavior | M5 | tune limits per topic |
diff --git a/docs/spec/product.md b/docs/spec/product.md
index 46de629..ab6d725 100644
--- a/docs/spec/product.md
+++ b/docs/spec/product.md
@@ -9,12 +9,12 @@
 | Name | AlteriOne |
 | Purpose | personal universal assistant: `chat`, `task`, and `resident` modes in one runtime |
 | Domain | https://alteri.one |
-| Repository | `alteri-one`, monorepo: Dart workspace and Melos 7 |
+| Repository | `alteri-one`, monorepo: Dart workspace and Melos (version in `architecture.md`, section 4) |
 | Dart packages | prefix `alteri_one_*` |
 | Binary | `alterione` (core and CLI). Personal builds get their own names |
 | License | Apache-2.0 |
 | Dart SDK | `^3.13.0` |
-| Build and tasks | Dart pub workspace (dependency resolution) and Melos 7 (scripts, versions, publishing) |
+| Build and tasks | Dart pub workspace (dependency resolution) and Melos (scripts, versions, publishing; version in `architecture.md`, section 4) |
 | Website | Jaspr, SSR |
 | Configuration | YAML, schema from schemantic |
 | User model | one owner per instance, several devices of the owner; no accounts, no multi-user mode |
diff --git a/docs/spec/roadmap.md b/docs/spec/roadmap.md
index d55afd3..394bca0 100644
--- a/docs/spec/roadmap.md
+++ b/docs/spec/roadmap.md
@@ -10,11 +10,11 @@ Outside the MVP: public release (website, release pipeline, signing, public docu
 
 ## 24.2 Milestones
 
-Each milestone ends with a green `melos run ci`, updated documents (if decisions changed), and checked steps in `docs/plan/<milestone>.md`.
+Each milestone ends with a green `dart run melos:melos run ci` (section 5.2), updated documents (if decisions changed), and checked steps in `docs/plan/<milestone>.md`.
 
 | Milestone | Scope | In MVP |
 |---|---|---|
-| M0 | Skeleton: workspace with globs, Melos 7, `analysis_options.yaml`, `tools/arch_check`, `tools/codegen_check`, `tools/docs_check`, CI. Spikes: schemantic, Hive (`kill -9`, `flush`), llama-server, Melos syntax, `dart language-server`, `mcp_dart`, keyring libraries | yes |
+| M0 | Skeleton: workspace with globs, Melos 8, `analysis_options.yaml`, `tools/arch_check`, `tools/codegen_check`, `tools/docs_check`, CI. Spikes: schemantic, Hive (`kill -9`, `flush`), llama-server, Melos syntax, `dart language-server`, `mcp_dart`, keyring libraries | yes |
 | M1 | Contracts: `alteri_one_contracts`, `alteri_one_provider_api`, `alteri_one_sdk`, `alteri_one_client`, state projection types, golden tests | yes |
 | M2 | Domain and loop: `transition`, `PolicyGate` with taints and rights, journal, `RunBloc`, loop with a fake `LlmPort`, `chat` mode. Target metrics measured (section 2.8) | yes |
 | M3 | llama.cpp provider: adapter over `genkit_openai`, probe, conformance. Adapter decision recorded as an ADR | yes |

From 0293ba9d154f7520c5df9bb64693ae56de02d0ab Mon Sep 17 00:00:00 2001
From: Dimoshka <dmytro.prylutskyi@outlook.com>
Date: Tue, 20 Oct 2026 14:21:23 +0000
Subject: [PATCH 06/12] docs(plan): close T12 in M0

T12 checked the melos.scripts syntax and the melos exec flags. It is
verified on Melos 8.9.0 with the exec: and steps: forms, and Melos now
runs from the workspace lock, so the check is closed and the milestone
names the ADR that records the line.

The umbrella spike list stays unchecked: seven of those spikes are
still open, so the closure is recorded under Open checks, the same
pattern M1 uses for T2 and T14.

Signed-off-by: Dimoshka <dmytro.prylutskyi@outlook.com>
---
 docs/plan/M0.md | 6 ++++--
 1 file changed, 4 insertions(+), 2 deletions(-)

diff --git a/docs/plan/M0.md b/docs/plan/M0.md
index 00c1892..b029c93 100644
--- a/docs/plan/M0.md
+++ b/docs/plan/M0.md
@@ -2,7 +2,7 @@
 
 - Status: In progress
 - Specification: `docs/spec/architecture.md` (sections 4–6), `docs/spec/roadmap.md` (M0)
-- ADR: —
+- ADR: ADR-0011 (Melos 8 tooling line)
 
 ## Acceptance criteria
 - [x] Workspace with globs, one `pubspec.lock`, `resolution: workspace` in every member
@@ -29,7 +29,9 @@
 ## Open checks [VERIFY]
 - [x] T2 partially resolved: `genkit 1.0.0` requires `schemantic ^1.0.0`, so the workspace is pinned to schemantic 1.0, not 0.2.x (see `open-questions.md`, Q1)
 - [ ] T2: schemantic 1.0.0 annotations on SDK 3.13
-- [ ] T12: `melos.scripts` syntax and `melos exec` flags in Melos 7.8.x (see `open-questions.md`, Q2 on Melos 8)
+- [x] T12: `melos.scripts` syntax and `melos exec` flags — verified on Melos 8.9.0 with the `exec:` and `steps:` forms; Melos runs from the workspace lock as `dart run melos:melos` (ADR-0011; see `open-questions.md`, Q2)
 
 ## Outcome
 Scaffold created on 2026-10-17: 22 workspace members, root workspace + Melos 7 config, community files. Spikes and the three tools remain.
+
+The tooling line moved to Melos 8 on 2026-10-20 (ADR-0011): the scripts use the Melos 8 forms, CI runs Melos from the workspace lock, and the `build_runner` pin stays until the generators move to `build` 5.

From d7486b90d60100801671a87237737f670a451be7 Mon Sep 17 00:00:00 2001
From: Dimoshka <dmytro.prylutskyi@outlook.com>
Date: Tue, 20 Oct 2026 14:26:18 +0000
Subject: [PATCH 07/12] docs: use the workspace melos invocation in the
 contributor docs

The workspace moved to Melos 8 and the scripts now run from the workspace
lock file as 'dart run melos:melos run <script>'. The global 'melos run'
form needs 'dart pub global activate melos', which the Dart SDK shipped
with Flutter stable no longer provides, so the old invocations in
AGENTS.md, CONTRIBUTING.md, README.md, and the pull request template
would fail on a clean machine.

The canonical invocation is stated once, in docs/spec/architecture.md,
section 5.2. The contributor documents now point at it instead of
repeating a second form of it, and the requirements lines no longer
pin Melos 7 as a prerequisite.

Signed-off-by: Dimoshka <dmytro.prylutskyi@outlook.com>
---
 .github/PULL_REQUEST_TEMPLATE.md |  6 +++---
 AGENTS.md                        | 18 +++++++++---------
 CONTRIBUTING.md                  | 18 +++++++++---------
 README.md                        | 14 +++++++-------
 4 files changed, 28 insertions(+), 28 deletions(-)

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index 870647b..db61e07 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,7 +1,7 @@
 <!--
 Thank you for the contribution. Before opening:
 - Read AGENTS.md at the root; the invariants there are enforced in review.
-- Run `melos run ci` locally.
+- Run `dart run melos:melos run ci` locally.
 - Every commit must be signed off: `git commit -s` (DCO, no CLA).
 -->
 
@@ -19,11 +19,11 @@ What this PR changes and why, in a few sentences.
 ## Tests
 
 - [ ] Tests for the new behavior, including negative ones (refusal, error, boundary)
-- [ ] `melos run ci` is green
+- [ ] `dart run melos:melos run ci` is green
 
 ## Checklist
 
 - [ ] Commits are signed off (`git commit -s`) and follow Conventional Commits
-- [ ] Generated files were regenerated with `melos run gen`, not edited by hand
+- [ ] Generated files were regenerated with `dart run melos:melos run gen`, not edited by hand
 - [ ] Public packages got a semver-compatible changelog entry
 - [ ] No new dependency outside `docs/spec/architecture.md` (or the addition was approved)
diff --git a/AGENTS.md b/AGENTS.md
index 4ffc847..7149ea0 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -4,7 +4,7 @@ This file is read first. It is short on purpose: it contains the invariants, the
 
 ## What the project is
 
-AlteriOne is a personal universal assistant: one runtime with three modes (`chat`, `task`, `resident`), extensions (built-in or loaded as AOT modules), LLM providers, and LSP and MCP integrations in the MVP. It has a single owner and no multi-user mode. The stack is Dart 3.13 in a monorepo managed with the Dart workspace and Melos 7.
+AlteriOne is a personal universal assistant: one runtime with three modes (`chat`, `task`, `resident`), extensions (built-in or loaded as AOT modules), LLM providers, and LSP and MCP integrations in the MVP. It has a single owner and no multi-user mode. The stack is Dart 3.13 in a monorepo managed with the Dart workspace and Melos 8.
 
 ## Invariants (never break)
 
@@ -24,13 +24,13 @@ AlteriOne is a personal universal assistant: one runtime with three modes (`chat
 
 ## Commands
 
-Before M0, `dart pub get` in the root is enough. After M0, the Melos scripts defined in the root `pubspec.yaml` (section `melos.scripts`) are available:
-- `melos run format`: formatting;
-- `melos run analyze`: analyzer with fatal infos;
-- `melos run gen`: code generation;
-- `melos run arch`: dependency rules;
-- `melos run test`: tests;
-- `melos run ci`: all of the above.
+Before M0, `dart pub get` in the root is enough. After M0, the Melos scripts defined in the root `pubspec.yaml` (section `melos.scripts`) are available. They run as `dart run melos:melos run <script>`; the invocation is defined in `docs/spec/architecture.md`, section 5.2.
+- `format`: formatting;
+- `analyze`: analyzer with fatal infos;
+- `gen`: code generation;
+- `arch`: dependency rules;
+- `test`: tests;
+- `ci`: all of the above.
 
 ## Reading map
 
@@ -55,7 +55,7 @@ Before a task, open `docs/spec/index.md` and find the row for your task. Then re
 
 ## Definition of done
 
-- `melos run ci` is green;
+- `dart run melos:melos run ci` is green;
 - there are tests for the new behavior, including negative ones (refusal, error, boundary);
 - `docs/spec/` is updated if the behavior is described there, and an ADR is written if a decision changed;
 - steps in `docs/plan/` are checked off.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 9972211..682ea4d 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -25,16 +25,16 @@ Do not silently invent decisions that are missing from the spec: write the quest
 
 ## Development setup
 
-Requirements: Dart `^3.13.0` (a [Flutter](https://flutter.dev) SDK `3.47+` provides it), Melos 7.
+Requirements: Dart `^3.13.0` (a [Flutter](https://flutter.dev) SDK `3.47+` provides it). The workspace scripts run as `dart run melos:melos run <script>`; no global Melos install is needed (see [`docs/spec/architecture.md`, section 5.2](docs/spec/architecture.md)).
 
 ```sh
-flutter pub get        # one resolution for the whole workspace
-melos run format       # dart format --set-exit-if-changed
-melos run analyze      # dart analyze --fatal-infos
-melos run gen          # build_runner code generation
-melos run arch         # dependency rules
-melos run test         # dart test across the workspace
-melos run ci           # all of the above
+flutter pub get                  # one resolution for the whole workspace
+dart run melos:melos run format  # dart format --set-exit-if-changed
+dart run melos:melos run analyze # dart analyze --fatal-infos
+dart run melos:melos run gen     # build_runner code generation
+dart run melos:melos run arch    # dependency rules
+dart run melos:melos run test    # dart test across the workspace
+dart run melos:melos run ci      # all of the above
 ```
 
 Rules enforced in review:
@@ -57,7 +57,7 @@ docs(spec): clarify subtask rights intersection
 ## Pull requests
 
 - Keep PRs focused; one change per PR.
-- CI must be green (`melos run ci`).
+- CI must be green (`dart run melos:melos run ci`).
 - New behavior needs tests, including negative ones.
 - If the change touches an accepted decision, propose the ADR first in an issue or discussion.
 
diff --git a/README.md b/README.md
index 9815feb..647172c 100644
--- a/README.md
+++ b/README.md
@@ -60,17 +60,17 @@ One Dart workspace (one `pubspec.lock`, shared resolution) plus Melos. Packages
 
 ## Getting started
 
-Requirements: [Dart](https://dart.dev) `^3.13.0` (a Flutter SDK gives you Dart; the client also needs [Flutter](https://flutter.dev) `3.47+`), and [Melos](https://pub.dev/packages/melos) 7.
+Requirements: [Dart](https://dart.dev) `^3.13.0` (a Flutter SDK gives you Dart; the client also needs [Flutter](https://flutter.dev) `3.47+`). The workspace scripts run as `dart run melos:melos run <script>`; no global Melos install is needed (see [`docs/spec/architecture.md`, section 5.2](docs/spec/architecture.md)).
 
 ```sh
 git clone https://github.com/dip-develop/alteri-one.git
 cd alteri-one
-flutter pub get          # resolves the whole workspace, one lock file
-melos run format         # formatting
-melos run analyze        # analyzer with fatal infos
-melos run arch           # dependency rules (tools/arch_check)
-melos run test           # tests across the workspace
-melos run ci             # all of the above
+flutter pub get                  # resolves the whole workspace, one lock file
+dart run melos:melos run format  # formatting
+dart run melos:melos run analyze # analyzer with fatal infos
+dart run melos:melos run arch    # dependency rules (tools/arch_check)
+dart run melos:melos run test    # tests across the workspace
+dart run melos:melos run ci      # all of the above
 ```
 
 The repository is currently a scaffold: package metadata, workspace wiring, and documentation are in place; the runtime follows milestone by milestone (see the [roadmap](docs/spec/roadmap.md)).

From e333c365aa99e677f18b837a0aec595ade989bad Mon Sep 17 00:00:00 2001
From: Dimoshka <dmytro.prylutskyi@outlook.com>
Date: Tue, 20 Oct 2026 14:26:23 +0000
Subject: [PATCH 08/12] docs: add the project TODO

The workstation guide asks for a TODO.md in the project root: one item per
line, newest first, with a link to where each item is described. The
repository had none, so the open work was only visible in the milestone
plans and the open-questions table.

Every line was checked against the repository before it was written: the
four tools are still entry-point stubs, the listed spikes are still open
in docs/spec/open-questions.md, and the build_runner ceiling comes from
the generators pinning build 4.

Signed-off-by: Dimoshka <dmytro.prylutskyi@outlook.com>
---
 TODO.md | 17 +++++++++++++++++
 1 file changed, 17 insertions(+)
 create mode 100644 TODO.md

diff --git a/TODO.md b/TODO.md
new file mode 100644
index 0000000..2839f76
--- /dev/null
+++ b/TODO.md
@@ -0,0 +1,17 @@
+# TODO
+
+Open work of the AlteriOne repository, newest first, one item per line.
+The specification is `docs/spec/index.md`; milestone plans are in `docs/plan/`.
+
+- [x] Melos 8 tooling line: the scripts run from the workspace lock as `dart run melos:melos run <script>` (ADR-0011, `docs/spec/architecture.md`, section 5.2)
+- [ ] Implement `tools/arch_check` against the dependency table (`docs/spec/architecture.md`, section 6); the stub exits 0 (`docs/plan/M0.md`)
+- [ ] Implement `tools/codegen_check` and `tools/docs_check`, then enable their CI steps (`docs/plan/M0.md`)
+- [ ] Implement the `tools/signing` entry points (`docs/plan/M0.md`)
+- [ ] Spike T2: schemantic 1.0.0 annotations on SDK 3.13 (`docs/spec/open-questions.md`)
+- [ ] Spike T5 and T6: `llama-server` flags and structured output (`docs/spec/open-questions.md`)
+- [ ] Spike T7 and T9: Hive CE durability and API names (`docs/spec/open-questions.md`)
+- [ ] Spike T16: `mcp_dart` on protocol version 2026-07-28 (`docs/spec/open-questions.md`)
+- [ ] Spike T17: `dart language-server` pull diagnostics and position encodings (`docs/spec/open-questions.md`)
+- [ ] Spike T19: keyring libraries on macOS, Linux, and Windows (`docs/spec/open-questions.md`)
+- [ ] Record T21, the bloc transformer rule, as an ADR (`docs/spec/open-questions.md`, `docs/plan/M1.md`)
+- [ ] Lift the `build_runner` pin when `injectable_generator` and `schemantic_builder` move to `build` 5 (`docs/spec/architecture.md`, section 4)

From 141bd5377238d3428d205432761ed8c7eafc3ad9 Mon Sep 17 00:00:00 2001
From: Dimoshka <dmytro.prylutskyi@outlook.com>
Date: Tue, 20 Oct 2026 14:59:37 +0000
Subject: [PATCH 09/12] chore(deps): name the package that holds the build 4
 ceiling

schemantic_builder 1.0.0 is a dev-dependency of schemantic, and the
dev-dependencies of a dependency are not resolved. The only package in
this workspace's resolution that pins build: ^4.0.4 is
injectable_generator 3.1.3, so the previous wording named a package
that does not hold the pin. Name injectable_generator 3.1.3 in the five
member pubspecs, in the build_runner row of docs/spec/architecture.md,
and in ADR-0011, and state in ADR-0011 that schemantic_builder is not a
dependency of this workspace yet.

The same commit corrects three statements of ADR-0011 that the Melos 8
move left inaccurate: the Dart SDK only lost the `dart global activate`
shortcut (`dart pub global activate` still works), the lock file also
moved cli_util, pub_updater, and coverage, and docs/plan/M0.md still
listed the closed spike T12 among the open ones. TODO.md loses two
wordings that no longer match the recorded state.

Signed-off-by: Dimoshka <dmytro.prylutskyi@outlook.com>
---
 TODO.md                          | 6 +++---
 clients/app/pubspec.yaml         | 2 +-
 clients/site/pubspec.yaml        | 2 +-
 docs/adr/0011-melos-8-tooling.md | 9 +++++----
 docs/plan/M0.md                  | 4 ++--
 docs/spec/architecture.md        | 2 +-
 packages/contracts/pubspec.yaml  | 2 +-
 packages/design/pubspec.yaml     | 2 +-
 runtime/core/pubspec.yaml        | 2 +-
 9 files changed, 16 insertions(+), 15 deletions(-)

diff --git a/TODO.md b/TODO.md
index 2839f76..0d8f014 100644
--- a/TODO.md
+++ b/TODO.md
@@ -1,11 +1,11 @@
 # TODO
 
-Open work of the AlteriOne repository, newest first, one item per line.
+Work of the AlteriOne repository, newest first, one item per line.
 The specification is `docs/spec/index.md`; milestone plans are in `docs/plan/`.
 
 - [x] Melos 8 tooling line: the scripts run from the workspace lock as `dart run melos:melos run <script>` (ADR-0011, `docs/spec/architecture.md`, section 5.2)
 - [ ] Implement `tools/arch_check` against the dependency table (`docs/spec/architecture.md`, section 6); the stub exits 0 (`docs/plan/M0.md`)
-- [ ] Implement `tools/codegen_check` and `tools/docs_check`, then enable their CI steps (`docs/plan/M0.md`)
+- [ ] Implement `tools/codegen_check` and `tools/docs_check`, then enable the CI step (`docs/plan/M0.md`)
 - [ ] Implement the `tools/signing` entry points (`docs/plan/M0.md`)
 - [ ] Spike T2: schemantic 1.0.0 annotations on SDK 3.13 (`docs/spec/open-questions.md`)
 - [ ] Spike T5 and T6: `llama-server` flags and structured output (`docs/spec/open-questions.md`)
@@ -14,4 +14,4 @@ The specification is `docs/spec/index.md`; milestone plans are in `docs/plan/`.
 - [ ] Spike T17: `dart language-server` pull diagnostics and position encodings (`docs/spec/open-questions.md`)
 - [ ] Spike T19: keyring libraries on macOS, Linux, and Windows (`docs/spec/open-questions.md`)
 - [ ] Record T21, the bloc transformer rule, as an ADR (`docs/spec/open-questions.md`, `docs/plan/M1.md`)
-- [ ] Lift the `build_runner` pin when `injectable_generator` and `schemantic_builder` move to `build` 5 (`docs/spec/architecture.md`, section 4)
+- [ ] Lift the `build_runner` pin when `injectable_generator` moves to `build` 5 (`docs/spec/architecture.md`, section 4)
diff --git a/clients/app/pubspec.yaml b/clients/app/pubspec.yaml
index 7fe8ef0..a446495 100644
--- a/clients/app/pubspec.yaml
+++ b/clients/app/pubspec.yaml
@@ -17,6 +17,6 @@ dependencies:
   flutter_bloc: ^9.1.1
   injectable: ^3.0.0
 dev_dependencies:
-  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 and schemantic_builder 1.0.0 pin build ^4.0.4
+  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 pins build ^4.0.4
   flutter_lints: ^6.0.0
   injectable_generator: ^3.0.0
diff --git a/clients/site/pubspec.yaml b/clients/site/pubspec.yaml
index d7698f0..8ab16ca 100644
--- a/clients/site/pubspec.yaml
+++ b/clients/site/pubspec.yaml
@@ -12,4 +12,4 @@ dependencies:
   alteri_one_design: ^0.0.1
   jaspr: ^0.23.5
 dev_dependencies:
-  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 and schemantic_builder 1.0.0 pin build ^4.0.4
+  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 pins build ^4.0.4
diff --git a/docs/adr/0011-melos-8-tooling.md b/docs/adr/0011-melos-8-tooling.md
index 3faad3c..97253ee 100644
--- a/docs/adr/0011-melos-8-tooling.md
+++ b/docs/adr/0011-melos-8-tooling.md
@@ -4,11 +4,11 @@
 - Date: 2026-10-20
 
 ## Context
-The workspace was on Melos 7.8.2 while Melos 8.9.0 is the current pub.dev release, and the spec pinned the old line in several places. The question of the Melos line was open as Q2 in `docs/spec/open-questions.md`, with the technical check T12 covering the script syntax. The Dart SDK that ships with Flutter stable no longer has `dart global activate`, so a global Melos installation is no longer a practical way to run the scripts.
+The workspace was on Melos 7.8.2 while Melos 8.9.0 is the current pub.dev release, and the spec pinned the old line in several places. The question of the Melos line was open as Q2 in `docs/spec/open-questions.md`, with the technical check T12 covering the script syntax. The Dart SDK that ships with Flutter stable no longer has the `dart global activate` shortcut, so a global installation now needs `dart pub global activate`.
 
 Melos 8 also changed how the scripts are written. A nested Melos call is rewritten to `dart run melos:melos` only in the `exec:` and `steps:` forms. A legacy plain-string script is handed to the shell unchanged and fails with `melos: not found` when no global `melos` binary is on `PATH`.
 
-Two dependencies could not move to their latest versions. `build_runner` 2.17.1 requires `build >=5.0.0 <5.1.0`, while `injectable_generator` 3.1.3 and `schemantic_builder` 1.0.0 both pin `build: ^4.0.4`; `build_runner` 2.17.0 is retracted on pub.dev. `openai_dart` stays on the 8.1.x line because `genkit_openai` 1.0.0 pins `openai_dart: ^8.1.0`.
+Two dependencies could not move to their latest versions. `build_runner` 2.17.1 requires `build >=5.0.0 <5.1.0`, while `injectable_generator` 3.1.3, the only generator in this workspace, pins `build: ^4.0.4`; `build_runner` 2.17.0 is retracted on pub.dev. `schemantic_builder` 1.0.0, the builder this workspace will use for schemantic code generation (spike T2), also pins `build: ^4.0.4`, but it is not a dependency of this workspace yet and will hold the same ceiling once it is added. `openai_dart` stays on the 8.1.x line because `genkit_openai` 1.0.0 pins `openai_dart: ^8.1.0`.
 
 ## Decision
 The owner approved the Melos 8 line on 2026-10-20. This closes Q2 and the technical check T12.
@@ -17,16 +17,17 @@ Melos runs from the workspace lock file: `dart run melos:melos run <script>`. No
 
 The `melos: scripts:` block in the root `pubspec.yaml` uses the Melos 8 forms: `exec:` with `command:` and `concurrency:`, `packageFilters:` with the camel-cased `dirExists` and `dependsOn` names, and a `steps:` list for the `ci` composite. The entries of `steps:` are bare script names. A literal `melos run <script>` inside `steps:` is passed to the shell unchanged and fails when no global `melos` binary is on `PATH`.
 
-`build_runner` and `openai_dart` stay on their current lines. The `build_runner` pin is held by the `build ^4.0.4` ceiling of the generators and by the retraction of 2.17.0; the `openai_dart` pin is held by `genkit_openai` 1.0.0.
+`build_runner` and `openai_dart` stay on their current lines. The `build_runner` pin is held by the `build ^4.0.4` ceiling of `injectable_generator` 3.1.3 and by the retraction of 2.17.0; the `openai_dart` pin is held by `genkit_openai` 1.0.0.
 
 ## Alternatives
 - Melos 7 with a global installation. Rejected: the Dart SDK in Flutter stable no longer has `dart global activate`, so the scripts would depend on a tool that the lock file does not pin.
 - A global Melos in CI, installed with `dart pub global activate melos ^8.0.0`. Rejected: it puts a second, unpinned copy of Melos next to the one the lock file pins.
 - Keep the plain-string scripts and put the Melos 8 forms only in CI. Rejected: the scripts would behave differently in CI and on a workstation.
-- Upgrade `build_runner` and `openai_dart` to their latest versions. Rejected for now: the generators pin `build ^4.0.4` and `build_runner` 2.17.0 is retracted, and `genkit_openai` 1.0.0 pins `openai_dart: ^8.1.0`.
+- Upgrade `build_runner` and `openai_dart` to their latest versions. Rejected for now: `injectable_generator` pins `build ^4.0.4` and `build_runner` 2.17.0 is retracted, and `genkit_openai` 1.0.0 pins `openai_dart: ^8.1.0`.
 
 ## Consequences
 - The scripts are run as `dart run melos:melos run <script>`. The invocation is stated once, in `docs/spec/architecture.md`, section 5.2.
 - The `melos: scripts:` block is Melos 8 only. It does not run under Melos 7.
 - The lock file holds `platform` at 3.1.6, forced by the `platform: ">=3.1.6 <3.2.0"` constraint of melos 8.9.0.
+- The lock file also moves `cli_util` 0.5.2 -> 0.6.0 and `pub_updater` 0.5.0 -> 0.6.0, because melos 8.9.0 widens both to `>=0.5.0 <0.7.0`. `coverage` moves 1.15.1 -> 1.16.0, because coverage 1.16.0 needs `cli_util: ^0.6.0`, which melos 7's `cli_util: ^0.5.0` forbade.
 - The `build_runner` pin is a known ceiling. It is revisited when the generators move to `build` 5.
diff --git a/docs/plan/M0.md b/docs/plan/M0.md
index b029c93..64c2a23 100644
--- a/docs/plan/M0.md
+++ b/docs/plan/M0.md
@@ -10,7 +10,7 @@
 - [x] Shared `analysis_options.yaml` included by every member
 - [x] All workspace members exist with pubspecs, stub libraries, and metadata; no functional implementation
 - [x] `melos run ci` is green (stubs only)
-- [ ] Spikes: schemantic (T2), Hive durability (T7, T9), llama-server flags (T5, T6), Melos syntax (T12), `dart language-server` (T17), `mcp_dart` (T16), keyring libraries (T19)
+- [ ] Spikes: schemantic (T2), Hive durability (T7, T9), llama-server flags (T5, T6), `dart language-server` (T17), `mcp_dart` (T16), keyring libraries (T19)
 
 ## Steps
 - [x] Root `pubspec.yaml` (workspace globs, Melos scripts), `analysis_options.yaml`, `pubspec_overrides.yaml`, `.gitignore`
@@ -34,4 +34,4 @@
 ## Outcome
 Scaffold created on 2026-10-17: 22 workspace members, root workspace + Melos 7 config, community files. Spikes and the three tools remain.
 
-The tooling line moved to Melos 8 on 2026-10-20 (ADR-0011): the scripts use the Melos 8 forms, CI runs Melos from the workspace lock, and the `build_runner` pin stays until the generators move to `build` 5.
+The tooling line moved to Melos 8 on 2026-10-20 (ADR-0011): the scripts use the Melos 8 forms, CI runs Melos from the workspace lock, and the `build_runner` pin stays until `injectable_generator` moves to `build` 5.
diff --git a/docs/spec/architecture.md b/docs/spec/architecture.md
index 6018014..d98f4f2 100644
--- a/docs/spec/architecture.md
+++ b/docs/spec/architecture.md
@@ -27,7 +27,7 @@ Minimum versions as of the date of writing. Check the current version on pub.dev
 | hive_ce | current | `Box` and `LazyBox` |
 | shelf | current | HTTP and HTTPS through `securityContext` [VERIFY signature] |
 | injectable | current | DI in `core` and `app`, environments `dev`, `prod`, `test` |
-| build_runner | `>=2.16.1 <2.17.0` | code generation for schemantic and injectable; 2.17.0 is retracted, 2.17.1 needs `build` 5, and the generators pin `build` 4 |
+| build_runner | `>=2.16.1 <2.17.0` | code generation for schemantic and injectable; 2.17.0 is retracted, 2.17.1 needs `build` 5, and `injectable_generator` 3.1.3 pins `build` ^4.0.4 |
 | yaml | current | configuration parsing |
 | http | current | client in `alteri_one_client` and providers |
 
diff --git a/packages/contracts/pubspec.yaml b/packages/contracts/pubspec.yaml
index 1e24573..dfaedad 100644
--- a/packages/contracts/pubspec.yaml
+++ b/packages/contracts/pubspec.yaml
@@ -18,5 +18,5 @@ dependencies:
   schemantic: ^1.0.0
   meta: ^1.19.0
 dev_dependencies:
-  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 and schemantic_builder 1.0.0 pin build ^4.0.4
+  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 pins build ^4.0.4
   test: ^1.33.0
diff --git a/packages/design/pubspec.yaml b/packages/design/pubspec.yaml
index 1b96e0e..12fca5c 100644
--- a/packages/design/pubspec.yaml
+++ b/packages/design/pubspec.yaml
@@ -19,5 +19,5 @@ dependencies:
     sdk: flutter
   yaml: ^3.1.4
 dev_dependencies:
-  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 and schemantic_builder 1.0.0 pin build ^4.0.4
+  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 pins build ^4.0.4
   flutter_lints: ^6.0.0
diff --git a/runtime/core/pubspec.yaml b/runtime/core/pubspec.yaml
index be6173a..1c8caed 100644
--- a/runtime/core/pubspec.yaml
+++ b/runtime/core/pubspec.yaml
@@ -22,7 +22,7 @@ dependencies:
   shelf: ^1.4.3
   yaml: ^3.1.4
 dev_dependencies:
-  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 and schemantic_builder 1.0.0 pin build ^4.0.4
+  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 pins build ^4.0.4
   injectable_generator: ^3.0.0
   bloc_test: ^10.0.0
   mocktail: ^1.0.5

From 2ca28416bcc2c35b8d63a4221957fac6518b8f35 Mon Sep 17 00:00:00 2001
From: Dimoshka <dmytro.prylutskyi@outlook.com>
Date: Tue, 20 Oct 2026 14:59:46 +0000
Subject: [PATCH 10/12] docs: correct the remaining melos invocation references

`melos version` and `melos run` are melos CLI commands, not workspace
scripts. With no global melos installation they fail with
`melos: command not found`, so the reference has to be the workspace
invocation `dart run melos:melos`. State it in CONTRIBUTING.md, in the
versions and publishing paragraph of docs/spec/architecture.md, and in
the M0 acceptance criterion, which is a live criterion in a file this
branch edits.

docs/spec/governance.md keeps its bare `melos version`: there the
subcommand is named as part of a process description, not as a command
to type.

Signed-off-by: Dimoshka <dmytro.prylutskyi@outlook.com>
---
 CONTRIBUTING.md           | 2 +-
 docs/plan/M0.md           | 2 +-
 docs/spec/architecture.md | 2 +-
 3 files changed, 3 insertions(+), 3 deletions(-)

diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 682ea4d..87c0d03 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -46,7 +46,7 @@ Rules enforced in review:
 
 ## Commit messages
 
-Use [Conventional Commits](https://www.conventionalcommits.org/); `melos version` derives changelogs and version bumps from them. Scope by package where useful:
+Use [Conventional Commits](https://www.conventionalcommits.org/); `dart run melos:melos version` derives changelogs and version bumps from them. Scope by package where useful:
 
 ```
 feat(client): replay SSE from `since`
diff --git a/docs/plan/M0.md b/docs/plan/M0.md
index 64c2a23..eae8322 100644
--- a/docs/plan/M0.md
+++ b/docs/plan/M0.md
@@ -9,7 +9,7 @@
 - [x] Melos configured in the root `pubspec.yaml` (no `melos.yaml`), scripts: `format`, `analyze`, `gen`, `arch`, `test`, `ci`
 - [x] Shared `analysis_options.yaml` included by every member
 - [x] All workspace members exist with pubspecs, stub libraries, and metadata; no functional implementation
-- [x] `melos run ci` is green (stubs only)
+- [x] `dart run melos:melos run ci` is green (stubs only)
 - [ ] Spikes: schemantic (T2), Hive durability (T7, T9), llama-server flags (T5, T6), `dart language-server` (T17), `mcp_dart` (T16), keyring libraries (T19)
 
 ## Steps
diff --git a/docs/spec/architecture.md b/docs/spec/architecture.md
index d98f4f2..86a33fd 100644
--- a/docs/spec/architecture.md
+++ b/docs/spec/architecture.md
@@ -155,7 +155,7 @@ Melos 8 rules that the block above depends on:
 - A composite script lists other scripts under `steps`, and the entries are bare script names. A literal `melos run <script>` inside `steps` is handed to the shell unchanged and fails when no global `melos` binary is on `PATH`.
 - `exec` scripts run in every package that the filters select. Private packages (`publish_to: none`) are included by default.
 
-Versions and publishing: `melos version` uses conventional commits for `packages/`, `providers/`, and `extensions/`. Publishing follows the dependency order. Packages with `publish_to: none` are never published.
+Versions and publishing: `dart run melos:melos version` uses conventional commits for `packages/`, `providers/`, and `extensions/`. Publishing follows the dependency order. Packages with `publish_to: none` are never published.
 
 ### 5.3 Code generation
 

From b692f987e280b8140f22a206b83bca247ddc4a3d Mon Sep 17 00:00:00 2001
From: Dimoshka <dmytro.prylutskyi@outlook.com>
Date: Tue, 20 Oct 2026 15:01:45 +0000
Subject: [PATCH 11/12] docs(adr): name the package that holds the build
 ceiling

Signed-off-by: Dimoshka <dmytro.prylutskyi@outlook.com>
---
 docs/adr/0011-melos-8-tooling.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/docs/adr/0011-melos-8-tooling.md b/docs/adr/0011-melos-8-tooling.md
index 97253ee..2936dec 100644
--- a/docs/adr/0011-melos-8-tooling.md
+++ b/docs/adr/0011-melos-8-tooling.md
@@ -30,4 +30,4 @@ The `melos: scripts:` block in the root `pubspec.yaml` uses the Melos 8 forms: `
 - The `melos: scripts:` block is Melos 8 only. It does not run under Melos 7.
 - The lock file holds `platform` at 3.1.6, forced by the `platform: ">=3.1.6 <3.2.0"` constraint of melos 8.9.0.
 - The lock file also moves `cli_util` 0.5.2 -> 0.6.0 and `pub_updater` 0.5.0 -> 0.6.0, because melos 8.9.0 widens both to `>=0.5.0 <0.7.0`. `coverage` moves 1.15.1 -> 1.16.0, because coverage 1.16.0 needs `cli_util: ^0.6.0`, which melos 7's `cli_util: ^0.5.0` forbade.
-- The `build_runner` pin is a known ceiling. It is revisited when the generators move to `build` 5.
+- The `build_runner` pin is a known ceiling. It is revisited when `injectable_generator` moves to `build` 5.

From e6090eb2317509edc0148e041fb95ee1d3f9c7da Mon Sep 17 00:00:00 2001
From: Dimoshka <dmytro.prylutskyi@outlook.com>
Date: Tue, 20 Oct 2026 15:25:19 +0000
Subject: [PATCH 12/12] revert: Melos 8 tooling line (PR #36)

Reverts all 11 commits of PR #36 on the owner's request. The Melos 8 upgrade, the migration of the melos: scripts block to the Melos 8 forms, the removal of the global Melos install from CI, the ADR, the spec and contributor-doc updates, and the TODO.md are all undone.

This restores the pre-existing state of main, including the red CI caused by the removal of the dart global command. That problem is not addressed by this revert and needs a separate decision.

Refs #33

Signed-off-by: Dimoshka <dmytro.prylutskyi@outlook.com>
---
 .github/PULL_REQUEST_TEMPLATE.md |  6 ++--
 .github/workflows/ci.yml         | 12 ++++----
 AGENTS.md                        | 18 ++++++------
 CONTRIBUTING.md                  | 20 +++++++-------
 README.md                        | 14 +++++-----
 TODO.md                          | 17 ------------
 clients/app/pubspec.yaml         |  2 +-
 clients/site/pubspec.yaml        |  2 +-
 docs/adr/0011-melos-8-tooling.md | 33 ----------------------
 docs/plan/M0.md                  | 10 +++----
 docs/spec/architecture.md        | 47 ++++++++------------------------
 docs/spec/forbidden-glossary.md  |  2 +-
 docs/spec/open-questions.md      |  7 +++--
 docs/spec/product.md             |  4 +--
 docs/spec/roadmap.md             |  4 +--
 packages/contracts/pubspec.yaml  |  2 +-
 packages/design/pubspec.yaml     |  2 +-
 pubspec.lock                     | 20 +++++++-------
 pubspec.yaml                     | 30 +++++---------------
 runtime/core/pubspec.yaml        |  2 +-
 20 files changed, 82 insertions(+), 172 deletions(-)
 delete mode 100644 TODO.md
 delete mode 100644 docs/adr/0011-melos-8-tooling.md

diff --git a/.github/PULL_REQUEST_TEMPLATE.md b/.github/PULL_REQUEST_TEMPLATE.md
index db61e07..870647b 100644
--- a/.github/PULL_REQUEST_TEMPLATE.md
+++ b/.github/PULL_REQUEST_TEMPLATE.md
@@ -1,7 +1,7 @@
 <!--
 Thank you for the contribution. Before opening:
 - Read AGENTS.md at the root; the invariants there are enforced in review.
-- Run `dart run melos:melos run ci` locally.
+- Run `melos run ci` locally.
 - Every commit must be signed off: `git commit -s` (DCO, no CLA).
 -->
 
@@ -19,11 +19,11 @@ What this PR changes and why, in a few sentences.
 ## Tests
 
 - [ ] Tests for the new behavior, including negative ones (refusal, error, boundary)
-- [ ] `dart run melos:melos run ci` is green
+- [ ] `melos run ci` is green
 
 ## Checklist
 
 - [ ] Commits are signed off (`git commit -s`) and follow Conventional Commits
-- [ ] Generated files were regenerated with `dart run melos:melos run gen`, not edited by hand
+- [ ] Generated files were regenerated with `melos run gen`, not edited by hand
 - [ ] Public packages got a semver-compatible changelog entry
 - [ ] No new dependency outside `docs/spec/architecture.md` (or the addition was approved)
diff --git a/.github/workflows/ci.yml b/.github/workflows/ci.yml
index 41d2081..6807fdd 100644
--- a/.github/workflows/ci.yml
+++ b/.github/workflows/ci.yml
@@ -20,6 +20,9 @@ jobs:
         with:
           channel: stable
 
+      - name: Install Melos
+        run: dart global activate melos ^7.0.0
+
       - name: Resolve workspace
         run: flutter pub get
 
@@ -27,15 +30,14 @@ jobs:
       # - name: Check generated code is up to date
       #   run: dart run tools/codegen_check/bin/codegen_check.dart
 
-      # Melos comes from the workspace lock file: `dart run melos:melos`, no global install.
       - name: Format
-        run: dart run melos:melos run format
+        run: melos run format
 
       - name: Analyze
-        run: dart run melos:melos run analyze
+        run: melos run analyze
 
       - name: Architecture rules
-        run: dart run melos:melos run arch
+        run: melos run arch
 
       - name: Test
-        run: dart run melos:melos run test
+        run: melos run test
diff --git a/AGENTS.md b/AGENTS.md
index 7149ea0..4ffc847 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -4,7 +4,7 @@ This file is read first. It is short on purpose: it contains the invariants, the
 
 ## What the project is
 
-AlteriOne is a personal universal assistant: one runtime with three modes (`chat`, `task`, `resident`), extensions (built-in or loaded as AOT modules), LLM providers, and LSP and MCP integrations in the MVP. It has a single owner and no multi-user mode. The stack is Dart 3.13 in a monorepo managed with the Dart workspace and Melos 8.
+AlteriOne is a personal universal assistant: one runtime with three modes (`chat`, `task`, `resident`), extensions (built-in or loaded as AOT modules), LLM providers, and LSP and MCP integrations in the MVP. It has a single owner and no multi-user mode. The stack is Dart 3.13 in a monorepo managed with the Dart workspace and Melos 7.
 
 ## Invariants (never break)
 
@@ -24,13 +24,13 @@ AlteriOne is a personal universal assistant: one runtime with three modes (`chat
 
 ## Commands
 
-Before M0, `dart pub get` in the root is enough. After M0, the Melos scripts defined in the root `pubspec.yaml` (section `melos.scripts`) are available. They run as `dart run melos:melos run <script>`; the invocation is defined in `docs/spec/architecture.md`, section 5.2.
-- `format`: formatting;
-- `analyze`: analyzer with fatal infos;
-- `gen`: code generation;
-- `arch`: dependency rules;
-- `test`: tests;
-- `ci`: all of the above.
+Before M0, `dart pub get` in the root is enough. After M0, the Melos scripts defined in the root `pubspec.yaml` (section `melos.scripts`) are available:
+- `melos run format`: formatting;
+- `melos run analyze`: analyzer with fatal infos;
+- `melos run gen`: code generation;
+- `melos run arch`: dependency rules;
+- `melos run test`: tests;
+- `melos run ci`: all of the above.
 
 ## Reading map
 
@@ -55,7 +55,7 @@ Before a task, open `docs/spec/index.md` and find the row for your task. Then re
 
 ## Definition of done
 
-- `dart run melos:melos run ci` is green;
+- `melos run ci` is green;
 - there are tests for the new behavior, including negative ones (refusal, error, boundary);
 - `docs/spec/` is updated if the behavior is described there, and an ADR is written if a decision changed;
 - steps in `docs/plan/` are checked off.
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
index 87c0d03..9972211 100644
--- a/CONTRIBUTING.md
+++ b/CONTRIBUTING.md
@@ -25,16 +25,16 @@ Do not silently invent decisions that are missing from the spec: write the quest
 
 ## Development setup
 
-Requirements: Dart `^3.13.0` (a [Flutter](https://flutter.dev) SDK `3.47+` provides it). The workspace scripts run as `dart run melos:melos run <script>`; no global Melos install is needed (see [`docs/spec/architecture.md`, section 5.2](docs/spec/architecture.md)).
+Requirements: Dart `^3.13.0` (a [Flutter](https://flutter.dev) SDK `3.47+` provides it), Melos 7.
 
 ```sh
-flutter pub get                  # one resolution for the whole workspace
-dart run melos:melos run format  # dart format --set-exit-if-changed
-dart run melos:melos run analyze # dart analyze --fatal-infos
-dart run melos:melos run gen     # build_runner code generation
-dart run melos:melos run arch    # dependency rules
-dart run melos:melos run test    # dart test across the workspace
-dart run melos:melos run ci      # all of the above
+flutter pub get        # one resolution for the whole workspace
+melos run format       # dart format --set-exit-if-changed
+melos run analyze      # dart analyze --fatal-infos
+melos run gen          # build_runner code generation
+melos run arch         # dependency rules
+melos run test         # dart test across the workspace
+melos run ci           # all of the above
 ```
 
 Rules enforced in review:
@@ -46,7 +46,7 @@ Rules enforced in review:
 
 ## Commit messages
 
-Use [Conventional Commits](https://www.conventionalcommits.org/); `dart run melos:melos version` derives changelogs and version bumps from them. Scope by package where useful:
+Use [Conventional Commits](https://www.conventionalcommits.org/); `melos version` derives changelogs and version bumps from them. Scope by package where useful:
 
 ```
 feat(client): replay SSE from `since`
@@ -57,7 +57,7 @@ docs(spec): clarify subtask rights intersection
 ## Pull requests
 
 - Keep PRs focused; one change per PR.
-- CI must be green (`dart run melos:melos run ci`).
+- CI must be green (`melos run ci`).
 - New behavior needs tests, including negative ones.
 - If the change touches an accepted decision, propose the ADR first in an issue or discussion.
 
diff --git a/README.md b/README.md
index 647172c..9815feb 100644
--- a/README.md
+++ b/README.md
@@ -60,17 +60,17 @@ One Dart workspace (one `pubspec.lock`, shared resolution) plus Melos. Packages
 
 ## Getting started
 
-Requirements: [Dart](https://dart.dev) `^3.13.0` (a Flutter SDK gives you Dart; the client also needs [Flutter](https://flutter.dev) `3.47+`). The workspace scripts run as `dart run melos:melos run <script>`; no global Melos install is needed (see [`docs/spec/architecture.md`, section 5.2](docs/spec/architecture.md)).
+Requirements: [Dart](https://dart.dev) `^3.13.0` (a Flutter SDK gives you Dart; the client also needs [Flutter](https://flutter.dev) `3.47+`), and [Melos](https://pub.dev/packages/melos) 7.
 
 ```sh
 git clone https://github.com/dip-develop/alteri-one.git
 cd alteri-one
-flutter pub get                  # resolves the whole workspace, one lock file
-dart run melos:melos run format  # formatting
-dart run melos:melos run analyze # analyzer with fatal infos
-dart run melos:melos run arch    # dependency rules (tools/arch_check)
-dart run melos:melos run test    # tests across the workspace
-dart run melos:melos run ci      # all of the above
+flutter pub get          # resolves the whole workspace, one lock file
+melos run format         # formatting
+melos run analyze        # analyzer with fatal infos
+melos run arch           # dependency rules (tools/arch_check)
+melos run test           # tests across the workspace
+melos run ci             # all of the above
 ```
 
 The repository is currently a scaffold: package metadata, workspace wiring, and documentation are in place; the runtime follows milestone by milestone (see the [roadmap](docs/spec/roadmap.md)).
diff --git a/TODO.md b/TODO.md
deleted file mode 100644
index 0d8f014..0000000
--- a/TODO.md
+++ /dev/null
@@ -1,17 +0,0 @@
-# TODO
-
-Work of the AlteriOne repository, newest first, one item per line.
-The specification is `docs/spec/index.md`; milestone plans are in `docs/plan/`.
-
-- [x] Melos 8 tooling line: the scripts run from the workspace lock as `dart run melos:melos run <script>` (ADR-0011, `docs/spec/architecture.md`, section 5.2)
-- [ ] Implement `tools/arch_check` against the dependency table (`docs/spec/architecture.md`, section 6); the stub exits 0 (`docs/plan/M0.md`)
-- [ ] Implement `tools/codegen_check` and `tools/docs_check`, then enable the CI step (`docs/plan/M0.md`)
-- [ ] Implement the `tools/signing` entry points (`docs/plan/M0.md`)
-- [ ] Spike T2: schemantic 1.0.0 annotations on SDK 3.13 (`docs/spec/open-questions.md`)
-- [ ] Spike T5 and T6: `llama-server` flags and structured output (`docs/spec/open-questions.md`)
-- [ ] Spike T7 and T9: Hive CE durability and API names (`docs/spec/open-questions.md`)
-- [ ] Spike T16: `mcp_dart` on protocol version 2026-07-28 (`docs/spec/open-questions.md`)
-- [ ] Spike T17: `dart language-server` pull diagnostics and position encodings (`docs/spec/open-questions.md`)
-- [ ] Spike T19: keyring libraries on macOS, Linux, and Windows (`docs/spec/open-questions.md`)
-- [ ] Record T21, the bloc transformer rule, as an ADR (`docs/spec/open-questions.md`, `docs/plan/M1.md`)
-- [ ] Lift the `build_runner` pin when `injectable_generator` moves to `build` 5 (`docs/spec/architecture.md`, section 4)
diff --git a/clients/app/pubspec.yaml b/clients/app/pubspec.yaml
index a446495..7e4e198 100644
--- a/clients/app/pubspec.yaml
+++ b/clients/app/pubspec.yaml
@@ -17,6 +17,6 @@ dependencies:
   flutter_bloc: ^9.1.1
   injectable: ^3.0.0
 dev_dependencies:
-  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 pins build ^4.0.4
+  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, injectable_generator needs build 4
   flutter_lints: ^6.0.0
   injectable_generator: ^3.0.0
diff --git a/clients/site/pubspec.yaml b/clients/site/pubspec.yaml
index 8ab16ca..acca3e8 100644
--- a/clients/site/pubspec.yaml
+++ b/clients/site/pubspec.yaml
@@ -12,4 +12,4 @@ dependencies:
   alteri_one_design: ^0.0.1
   jaspr: ^0.23.5
 dev_dependencies:
-  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 pins build ^4.0.4
+  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, injectable_generator needs build 4
diff --git a/docs/adr/0011-melos-8-tooling.md b/docs/adr/0011-melos-8-tooling.md
deleted file mode 100644
index 2936dec..0000000
--- a/docs/adr/0011-melos-8-tooling.md
+++ /dev/null
@@ -1,33 +0,0 @@
-# 0011. Melos 8 tooling line
-
-- Status: Accepted
-- Date: 2026-10-20
-
-## Context
-The workspace was on Melos 7.8.2 while Melos 8.9.0 is the current pub.dev release, and the spec pinned the old line in several places. The question of the Melos line was open as Q2 in `docs/spec/open-questions.md`, with the technical check T12 covering the script syntax. The Dart SDK that ships with Flutter stable no longer has the `dart global activate` shortcut, so a global installation now needs `dart pub global activate`.
-
-Melos 8 also changed how the scripts are written. A nested Melos call is rewritten to `dart run melos:melos` only in the `exec:` and `steps:` forms. A legacy plain-string script is handed to the shell unchanged and fails with `melos: not found` when no global `melos` binary is on `PATH`.
-
-Two dependencies could not move to their latest versions. `build_runner` 2.17.1 requires `build >=5.0.0 <5.1.0`, while `injectable_generator` 3.1.3, the only generator in this workspace, pins `build: ^4.0.4`; `build_runner` 2.17.0 is retracted on pub.dev. `schemantic_builder` 1.0.0, the builder this workspace will use for schemantic code generation (spike T2), also pins `build: ^4.0.4`, but it is not a dependency of this workspace yet and will hold the same ceiling once it is added. `openai_dart` stays on the 8.1.x line because `genkit_openai` 1.0.0 pins `openai_dart: ^8.1.0`.
-
-## Decision
-The owner approved the Melos 8 line on 2026-10-20. This closes Q2 and the technical check T12.
-
-Melos runs from the workspace lock file: `dart run melos:melos run <script>`. No global installation is needed, neither in CI nor on a workstation. A contributor who prefers a global tool installs it with `dart pub global activate melos` and writes `melos run <script>`.
-
-The `melos: scripts:` block in the root `pubspec.yaml` uses the Melos 8 forms: `exec:` with `command:` and `concurrency:`, `packageFilters:` with the camel-cased `dirExists` and `dependsOn` names, and a `steps:` list for the `ci` composite. The entries of `steps:` are bare script names. A literal `melos run <script>` inside `steps:` is passed to the shell unchanged and fails when no global `melos` binary is on `PATH`.
-
-`build_runner` and `openai_dart` stay on their current lines. The `build_runner` pin is held by the `build ^4.0.4` ceiling of `injectable_generator` 3.1.3 and by the retraction of 2.17.0; the `openai_dart` pin is held by `genkit_openai` 1.0.0.
-
-## Alternatives
-- Melos 7 with a global installation. Rejected: the Dart SDK in Flutter stable no longer has `dart global activate`, so the scripts would depend on a tool that the lock file does not pin.
-- A global Melos in CI, installed with `dart pub global activate melos ^8.0.0`. Rejected: it puts a second, unpinned copy of Melos next to the one the lock file pins.
-- Keep the plain-string scripts and put the Melos 8 forms only in CI. Rejected: the scripts would behave differently in CI and on a workstation.
-- Upgrade `build_runner` and `openai_dart` to their latest versions. Rejected for now: `injectable_generator` pins `build ^4.0.4` and `build_runner` 2.17.0 is retracted, and `genkit_openai` 1.0.0 pins `openai_dart: ^8.1.0`.
-
-## Consequences
-- The scripts are run as `dart run melos:melos run <script>`. The invocation is stated once, in `docs/spec/architecture.md`, section 5.2.
-- The `melos: scripts:` block is Melos 8 only. It does not run under Melos 7.
-- The lock file holds `platform` at 3.1.6, forced by the `platform: ">=3.1.6 <3.2.0"` constraint of melos 8.9.0.
-- The lock file also moves `cli_util` 0.5.2 -> 0.6.0 and `pub_updater` 0.5.0 -> 0.6.0, because melos 8.9.0 widens both to `>=0.5.0 <0.7.0`. `coverage` moves 1.15.1 -> 1.16.0, because coverage 1.16.0 needs `cli_util: ^0.6.0`, which melos 7's `cli_util: ^0.5.0` forbade.
-- The `build_runner` pin is a known ceiling. It is revisited when `injectable_generator` moves to `build` 5.
diff --git a/docs/plan/M0.md b/docs/plan/M0.md
index eae8322..00c1892 100644
--- a/docs/plan/M0.md
+++ b/docs/plan/M0.md
@@ -2,15 +2,15 @@
 
 - Status: In progress
 - Specification: `docs/spec/architecture.md` (sections 4–6), `docs/spec/roadmap.md` (M0)
-- ADR: ADR-0011 (Melos 8 tooling line)
+- ADR: —
 
 ## Acceptance criteria
 - [x] Workspace with globs, one `pubspec.lock`, `resolution: workspace` in every member
 - [x] Melos configured in the root `pubspec.yaml` (no `melos.yaml`), scripts: `format`, `analyze`, `gen`, `arch`, `test`, `ci`
 - [x] Shared `analysis_options.yaml` included by every member
 - [x] All workspace members exist with pubspecs, stub libraries, and metadata; no functional implementation
-- [x] `dart run melos:melos run ci` is green (stubs only)
-- [ ] Spikes: schemantic (T2), Hive durability (T7, T9), llama-server flags (T5, T6), `dart language-server` (T17), `mcp_dart` (T16), keyring libraries (T19)
+- [x] `melos run ci` is green (stubs only)
+- [ ] Spikes: schemantic (T2), Hive durability (T7, T9), llama-server flags (T5, T6), Melos syntax (T12), `dart language-server` (T17), `mcp_dart` (T16), keyring libraries (T19)
 
 ## Steps
 - [x] Root `pubspec.yaml` (workspace globs, Melos scripts), `analysis_options.yaml`, `pubspec_overrides.yaml`, `.gitignore`
@@ -29,9 +29,7 @@
 ## Open checks [VERIFY]
 - [x] T2 partially resolved: `genkit 1.0.0` requires `schemantic ^1.0.0`, so the workspace is pinned to schemantic 1.0, not 0.2.x (see `open-questions.md`, Q1)
 - [ ] T2: schemantic 1.0.0 annotations on SDK 3.13
-- [x] T12: `melos.scripts` syntax and `melos exec` flags — verified on Melos 8.9.0 with the `exec:` and `steps:` forms; Melos runs from the workspace lock as `dart run melos:melos` (ADR-0011; see `open-questions.md`, Q2)
+- [ ] T12: `melos.scripts` syntax and `melos exec` flags in Melos 7.8.x (see `open-questions.md`, Q2 on Melos 8)
 
 ## Outcome
 Scaffold created on 2026-10-17: 22 workspace members, root workspace + Melos 7 config, community files. Spikes and the three tools remain.
-
-The tooling line moved to Melos 8 on 2026-10-20 (ADR-0011): the scripts use the Melos 8 forms, CI runs Melos from the workspace lock, and the `build_runner` pin stays until `injectable_generator` moves to `build` 5.
diff --git a/docs/spec/architecture.md b/docs/spec/architecture.md
index 86a33fd..e4317b1 100644
--- a/docs/spec/architecture.md
+++ b/docs/spec/architecture.md
@@ -10,7 +10,7 @@ Minimum versions as of the date of writing. Check the current version on pub.dev
 |---|---|---|
 | Dart SDK | `^3.13.0` | fixed |
 | Dart workspace | globs in `workspace:` | globs since Dart 3.11; one `pubspec.lock` at the root |
-| Melos | `^8.0.0` | configured in the root `pubspec.yaml`; `melos.yaml` is not used; the scripts are run from the workspace lock (section 5.2) |
+| Melos | 7.x | configured in the root `pubspec.yaml`; `melos.yaml` is not used [VERIFY current version] |
 | bloc | `^9.2.0` | pure Dart. `flutter_bloc` only in the client |
 | bloc_concurrency | current | `sequential`, `droppable`, `restartable`, `concurrent` |
 | bloc_test | current | state tests [VERIFY compatibility with bloc 9] |
@@ -27,7 +27,7 @@ Minimum versions as of the date of writing. Check the current version on pub.dev
 | hive_ce | current | `Box` and `LazyBox` |
 | shelf | current | HTTP and HTTPS through `securityContext` [VERIFY signature] |
 | injectable | current | DI in `core` and `app`, environments `dev`, `prod`, `test` |
-| build_runner | `>=2.16.1 <2.17.0` | code generation for schemantic and injectable; 2.17.0 is retracted, 2.17.1 needs `build` 5, and `injectable_generator` 3.1.3 pins `build` ^4.0.4 |
+| build_runner | current | code generation for schemantic and injectable |
 | yaml | current | configuration parsing |
 | http | current | client in `alteri_one_client` and providers |
 
@@ -35,7 +35,7 @@ All workspace members resolve together. Version conflicts appear immediately. Ke
 
 ## 5. Repository layout
 
-The monorepo is one Dart workspace (one `pubspec.lock`, shared dependency resolution) plus Melos 8 (scripts, filtering, versions, publishing). Packages are grouped by purpose and by publishing rules, not by technology.
+The monorepo is one Dart workspace (one `pubspec.lock`, shared dependency resolution) plus Melos 7 (scripts, filtering, versions, publishing). Packages are grouped by purpose and by publishing rules, not by technology.
 
 ```
 alteri-one/
@@ -100,7 +100,7 @@ alteri-one/
 
 ### 5.2 Melos configuration
 
-Melos 8 reads its settings from the root `pubspec.yaml`. There is no separate `melos.yaml`. Scripts are declared in `melos.scripts`.
+Melos 7 reads its settings from the root `pubspec.yaml`. There is no separate `melos.yaml`. Scripts are declared in `melos.scripts`.
 
 ```yaml
 # pubspec.yaml (root)
@@ -117,45 +117,20 @@ workspace:
   - e2e
   - tools/*
 dev_dependencies:
-  melos: ^8.0.0
+  melos: ^7.0.0                    # [VERIFY current version on pub.dev]
 melos:
   scripts:
+    analyze: melos exec -c 1 -- dart analyze --fatal-infos
+    test: melos exec -c 4 --dir-exists=test -- dart test
     format: dart format --set-exit-if-changed .
-    analyze:
-      exec:
-        command: dart analyze --fatal-infos
-        concurrency: 1
-    gen:
-      exec:
-        command: dart run build_runner build --delete-conflicting-outputs
-        concurrency: 1
-      packageFilters:
-        dependsOn: build_runner
+    gen: melos exec -c 1 --depends-on build_runner -- dart run build_runner build --delete-conflicting-outputs
     arch: dart run tools/arch_check/bin/arch_check.dart
-    test:
-      exec:
-        command: dart test
-        concurrency: 4
-      packageFilters:
-        dirExists: test
-    ci:
-      steps:
-        - format
-        - analyze
-        - arch
-        - test
+    ci: melos run format && melos run analyze && melos run arch && melos run test
 ```
 
-Melos is invoked from the workspace lock file: `dart run melos:melos run <script>`. No global installation is needed, and CI uses the same invocation. A contributor who prefers a global tool installs it with `dart pub global activate melos` and writes `melos run <script>` (ADR-0011).
+[VERIFY: syntax of `melos.scripts`, composite scripts, and `melos exec` flags in the selected Melos 7 version.]
 
-Melos 8 rules that the block above depends on:
-
-- `run` and `exec` are mutually exclusive. The command of an `exec` script goes into the `command` key.
-- The filter names in `packageFilters` are camel-cased: `dirExists`, `dependsOn`.
-- A composite script lists other scripts under `steps`, and the entries are bare script names. A literal `melos run <script>` inside `steps` is handed to the shell unchanged and fails when no global `melos` binary is on `PATH`.
-- `exec` scripts run in every package that the filters select. Private packages (`publish_to: none`) are included by default.
-
-Versions and publishing: `dart run melos:melos version` uses conventional commits for `packages/`, `providers/`, and `extensions/`. Publishing follows the dependency order. Packages with `publish_to: none` are never published.
+Versions and publishing: `melos version` uses conventional commits for `packages/`, `providers/`, and `extensions/`. Publishing follows the dependency order. Packages with `publish_to: none` are never published.
 
 ### 5.3 Code generation
 
diff --git a/docs/spec/forbidden-glossary.md b/docs/spec/forbidden-glossary.md
index 98770de..aefff6a 100644
--- a/docs/spec/forbidden-glossary.md
+++ b/docs/spec/forbidden-glossary.md
@@ -12,7 +12,7 @@ Do not use anything listed here, even if you find it in old examples, articles,
 | MCP stdio as the extension transport | replaced by AOT modules and built-in mode | `Isolate.spawnUri` behind `ExtensionTransport`, or built-in mode |
 | `alterione-sdk` as the only package | replaced by a set of packages | `alteri_one_*` |
 | `alterione_*` as a package prefix | corrected | `alteri_one_*` |
-| `melos.yaml` and `pubspec_overrides.yaml` | Melos and pub workspaces | root `pubspec.yaml` with `workspace:` and `melos:` |
+| `melos.yaml` and `pubspec_overrides.yaml` | Melos 7 and pub workspaces | root `pubspec.yaml` with `workspace:` and `melos:` |
 | Node.js or npm as the agent runtime | project decision | Dart, native binary |
 | Multi-user mode, accounts, tenants | out of scope: a personal assistant | one owner, devices with tokens |
 | `sqlite`, `drift` | replaced | Hive CE |
diff --git a/docs/spec/open-questions.md b/docs/spec/open-questions.md
index 59e97f6..bb9ffbc 100644
--- a/docs/spec/open-questions.md
+++ b/docs/spec/open-questions.md
@@ -9,17 +9,17 @@ Added during the M0 scaffold (2026-10-17). Until answered, the scaffold takes th
 | ID | Question | Conservative choice taken |
 |---|---|---|
 | Q1 | schemantic line: the spec pins 0.2.x ("do not use 1.0.0-rc.1 until verified"), but `genkit 1.0.0` declares `schemantic: ^1.0.0`, so 0.2.x cannot coexist with genkit in one workspace, and schemantic 1.0.0 is now a stable release. Confirm the move to the 1.0.0 line and update section 4. | pinned `schemantic: ^1.0.0` everywhere |
-| Q2 | ~~Melos line: the spec pins Melos 7 everywhere; Melos 8.x is the current pub.dev release. Migrate to 8 and update sections 4 and 5.2?~~ Resolved 2026-10-20: the owner approved the Melos 8 line. The workspace resolves `melos: ^8.0.0` (8.9.0), the scripts use the Melos 8 `exec:` and `steps:` forms, and Melos runs from the workspace lock as `dart run melos:melos` with no global install (ADR-0011). | resolved |
+| Q2 | Melos line: the spec pins Melos 7 everywhere; Melos 8.x is the current pub.dev release. Migrate to 8 and update sections 4 and 5.2? [VERIFY T12] covers script syntax on 7.x. | pinned `melos: ^7.0.0` (resolves 7.8.2) |
 | Q3 | `tools/docs_check` is required by `docs/spec/index.md` ("Rules for maintaining documents") but is missing from the repository layout in `docs/spec/architecture.md`, section 5. Add it to section 5? | scaffolded `tools/docs_check` |
 | Q4 | ~~Repository URL: the spec gives the repository name `alteri-one` but not the GitHub owner.~~ Resolved 2026-10-17: the owner is `dip-develop`; all pubspecs and docs use `https://github.com/dip-develop/alteri-one`. | resolved |
 | Q5 | `public_member_api_docs` cannot coexist with the primary-constructor style mandated by section 7.2: the Dart 3.13.5 analyzer does not attach `///` comments to primary-constructor parameters (the style used by every example in `domain.md` section 8). Re-enable the lint when the analyzer supports parameter docs. Until then, parameter dartdoc stays mandatory by convention; `packages/AGENTS.md` ("public classes and methods have English dartdoc") is enforced in review, not by the analyzer. | lint omitted from the shared set; docs kept by convention |
 | Q6 | Section 7.3 shows named `new` constructors with a dot (`new origin()`); the Dart 3.13.5 compiler rejects the dot and requires a space (`new origin() : x = 0, y = 0;`), named factories are written without the class name (`factory standard() { ... }`), and named `new` factories are illegal. Update section 7.3 with the compiler-verified forms. | code follows the compiler forms probed on 3.13.5 |
 
-Previously none were open. Decisions are recorded in ADR-0005, ADR-0006, ADR-0009, and ADR-0011.
+Previously none were open. Decisions are recorded in ADR-0005, ADR-0006, and ADR-0009.
 
 ## 25.2 Technical checks [VERIFY]
 
-T1 is closed (ADR-0007). T12 is closed (ADR-0011): the workspace scripts use the Melos 8 `exec:` and `steps:` forms, and Melos runs from the workspace lock as `dart run melos:melos`. T14 is closed: the `RunBloc` suite in `alteri_one_core` runs under `bloc_test` 10 with bloc 9.2.
+T1 is closed (ADR-0007). T14 is closed: the `RunBloc` suite in `alteri_one_core` runs under `bloc_test` 10 with bloc 9.2.
 
 | ID | What to verify | When | What to do on failure |
 |---|---|---|---|
@@ -34,6 +34,7 @@ T1 is closed (ADR-0007). T12 is closed (ADR-0011): the workspace scripts use the
 | T9 | `hive_ce` API names (`openLazyBox`, encryption) | M0 | adjust the adapter |
 | T10 | the `SKILL.md` format in `genkit_middleware` | M5 | a custom parser |
 | T11 | the `dart build cli` command on Dart 3.13 for each OS | M4 | `dart compile exe` |
+| T12 | `melos.scripts` syntax, composite scripts, `melos exec` flags | M0 | fix the root `pubspec.yaml` |
 | T13 | the `shelf_io.serve` signature with `securityContext` | M4b | a TLS proxy in front of the daemon |
 | T14 | `bloc_test` compatibility with bloc 9 | M2 | test transitions as pure functions |
 | T15 | `StatePublisher` queue limits and overflow behavior | M5 | tune limits per topic |
diff --git a/docs/spec/product.md b/docs/spec/product.md
index ab6d725..46de629 100644
--- a/docs/spec/product.md
+++ b/docs/spec/product.md
@@ -9,12 +9,12 @@
 | Name | AlteriOne |
 | Purpose | personal universal assistant: `chat`, `task`, and `resident` modes in one runtime |
 | Domain | https://alteri.one |
-| Repository | `alteri-one`, monorepo: Dart workspace and Melos (version in `architecture.md`, section 4) |
+| Repository | `alteri-one`, monorepo: Dart workspace and Melos 7 |
 | Dart packages | prefix `alteri_one_*` |
 | Binary | `alterione` (core and CLI). Personal builds get their own names |
 | License | Apache-2.0 |
 | Dart SDK | `^3.13.0` |
-| Build and tasks | Dart pub workspace (dependency resolution) and Melos (scripts, versions, publishing; version in `architecture.md`, section 4) |
+| Build and tasks | Dart pub workspace (dependency resolution) and Melos 7 (scripts, versions, publishing) |
 | Website | Jaspr, SSR |
 | Configuration | YAML, schema from schemantic |
 | User model | one owner per instance, several devices of the owner; no accounts, no multi-user mode |
diff --git a/docs/spec/roadmap.md b/docs/spec/roadmap.md
index 394bca0..d55afd3 100644
--- a/docs/spec/roadmap.md
+++ b/docs/spec/roadmap.md
@@ -10,11 +10,11 @@ Outside the MVP: public release (website, release pipeline, signing, public docu
 
 ## 24.2 Milestones
 
-Each milestone ends with a green `dart run melos:melos run ci` (section 5.2), updated documents (if decisions changed), and checked steps in `docs/plan/<milestone>.md`.
+Each milestone ends with a green `melos run ci`, updated documents (if decisions changed), and checked steps in `docs/plan/<milestone>.md`.
 
 | Milestone | Scope | In MVP |
 |---|---|---|
-| M0 | Skeleton: workspace with globs, Melos 8, `analysis_options.yaml`, `tools/arch_check`, `tools/codegen_check`, `tools/docs_check`, CI. Spikes: schemantic, Hive (`kill -9`, `flush`), llama-server, Melos syntax, `dart language-server`, `mcp_dart`, keyring libraries | yes |
+| M0 | Skeleton: workspace with globs, Melos 7, `analysis_options.yaml`, `tools/arch_check`, `tools/codegen_check`, `tools/docs_check`, CI. Spikes: schemantic, Hive (`kill -9`, `flush`), llama-server, Melos syntax, `dart language-server`, `mcp_dart`, keyring libraries | yes |
 | M1 | Contracts: `alteri_one_contracts`, `alteri_one_provider_api`, `alteri_one_sdk`, `alteri_one_client`, state projection types, golden tests | yes |
 | M2 | Domain and loop: `transition`, `PolicyGate` with taints and rights, journal, `RunBloc`, loop with a fake `LlmPort`, `chat` mode. Target metrics measured (section 2.8) | yes |
 | M3 | llama.cpp provider: adapter over `genkit_openai`, probe, conformance. Adapter decision recorded as an ADR | yes |
diff --git a/packages/contracts/pubspec.yaml b/packages/contracts/pubspec.yaml
index dfaedad..2a0b118 100644
--- a/packages/contracts/pubspec.yaml
+++ b/packages/contracts/pubspec.yaml
@@ -18,5 +18,5 @@ dependencies:
   schemantic: ^1.0.0
   meta: ^1.19.0
 dev_dependencies:
-  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 pins build ^4.0.4
+  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, injectable_generator needs build 4
   test: ^1.33.0
diff --git a/packages/design/pubspec.yaml b/packages/design/pubspec.yaml
index 12fca5c..12cf59f 100644
--- a/packages/design/pubspec.yaml
+++ b/packages/design/pubspec.yaml
@@ -19,5 +19,5 @@ dependencies:
     sdk: flutter
   yaml: ^3.1.4
 dev_dependencies:
-  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 pins build ^4.0.4
+  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, injectable_generator needs build 4
   flutter_lints: ^6.0.0
diff --git a/pubspec.lock b/pubspec.lock
index 5895e3b..a09401e 100644
--- a/pubspec.lock
+++ b/pubspec.lock
@@ -173,10 +173,10 @@ packages:
     dependency: transitive
     description:
       name: cli_util
-      sha256: "89b8801ba49f8b593fbf2d3e59efd0f566c46cd4ba6837ae2610c72b52a0f899"
+      sha256: "71e43f1976c3eae2d9468a5b4d6600bf8cae61508b87f27fa1799228935d48ab"
       url: "https://pub.dev"
     source: hosted
-    version: "0.6.0"
+    version: "0.5.2"
   clock:
     dependency: transitive
     description:
@@ -221,10 +221,10 @@ packages:
     dependency: transitive
     description:
       name: coverage
-      sha256: ff89e37c19355194e279d26dafe8e4bece46c9ea63a30be4dc68214f5bc290d3
+      sha256: "956a3de0725ca232ad353565a8290d3357592bf4250f6f298a185e2d949c5d3d"
       url: "https://pub.dev"
     source: hosted
-    version: "1.16.0"
+    version: "1.15.1"
   crypto:
     dependency: transitive
     description:
@@ -538,10 +538,10 @@ packages:
     dependency: "direct dev"
     description:
       name: melos
-      sha256: "140e51d7990b5134663e64b39e19d3b64ead16382e69127c205942c91e752b16"
+      sha256: "5fc1a858e3d90fdc42f2f423b95f901214bbc3d9e80c99125d9352f12453721d"
       url: "https://pub.dev"
     source: hosted
-    version: "8.9.0"
+    version: "7.8.2"
   meta:
     dependency: transitive
     description:
@@ -626,10 +626,10 @@ packages:
     dependency: transitive
     description:
       name: platform
-      sha256: "5d6b1b0036a5f331ebc77c850ebc8506cbc1e9416c27e59b439f917a902a4984"
+      sha256: a36d119c13416516a7b5913fbe8af8531e11633d784c550b2125f76c758524ec
       url: "https://pub.dev"
     source: hosted
-    version: "3.1.6"
+    version: "3.2.0"
   pool:
     dependency: transitive
     description:
@@ -674,10 +674,10 @@ packages:
     dependency: transitive
     description:
       name: pub_updater
-      sha256: "3aadeb8c68d15ef9d117b36474ddcc543b48ae1e64f7dd71407da26df66bf7c8"
+      sha256: "739a0161d73a6974c0675b864fb0cf5147305f7b077b7f03a58fa7a9ab3e7e7d"
       url: "https://pub.dev"
     source: hosted
-    version: "0.6.0"
+    version: "0.5.0"
   pubspec_parse:
     dependency: transitive
     description:
diff --git a/pubspec.yaml b/pubspec.yaml
index 4328c70..c5722ab 100644
--- a/pubspec.yaml
+++ b/pubspec.yaml
@@ -20,31 +20,15 @@ workspace:
   - tools/*
 
 dev_dependencies:
-  melos: ^8.0.0
+  # [VERIFY T12] Melos 8.x exists; the specification pins the 7.x line.
+  # See docs/spec/open-questions.md before moving to 8.
+  melos: ^7.0.0
 
 melos:
   scripts:
     format: dart format --set-exit-if-changed .
-    analyze:
-      exec:
-        command: dart analyze --fatal-infos
-        concurrency: 1
-    gen:
-      exec:
-        command: dart run build_runner build --delete-conflicting-outputs
-        concurrency: 1
-      packageFilters:
-        dependsOn: build_runner
+    analyze: melos exec -c 1 -- dart analyze --fatal-infos
+    gen: melos exec -c 1 --depends-on build_runner -- dart run build_runner build --delete-conflicting-outputs
     arch: dart run tools/arch_check/bin/arch_check.dart
-    test:
-      exec:
-        command: dart test
-        concurrency: 4
-      packageFilters:
-        dirExists: test
-    ci:
-      steps:
-        - format
-        - analyze
-        - arch
-        - test
+    test: melos exec -c 4 --dir-exists=test -- dart test
+    ci: melos run format && melos run analyze && melos run arch && melos run test
diff --git a/runtime/core/pubspec.yaml b/runtime/core/pubspec.yaml
index 1c8caed..ae5ed93 100644
--- a/runtime/core/pubspec.yaml
+++ b/runtime/core/pubspec.yaml
@@ -22,7 +22,7 @@ dependencies:
   shelf: ^1.4.3
   yaml: ^3.1.4
 dev_dependencies:
-  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, but injectable_generator 3.1.3 pins build ^4.0.4
+  build_runner: ">=2.16.1 <2.17.0"  # 2.17.0 retracted; 2.17.1 needs build 5, injectable_generator needs build 4
   injectable_generator: ^3.0.0
   bloc_test: ^10.0.0
   mocktail: ^1.0.5