@cassiomc1/forgeloop 1.11.1 → 1.13.0

package/docs/RECIPES.md

@@ -35,6 +35,18 @@ Concise, copy-paste friendly recipes for common ForgeLoop tasks.
 
 ### Recipe 1 — Start a New Task
 
+When the task shape is known but the final contract has not been written, first
+request a read-only preset proposal:
+
+```bash
+forgeloop task-create --task task-001 --claim src --claim tests \
+  --preset feature --preview --json
+```
+
+Review the bounded proposal, then repeat without `--preview` before continuing
+with the task workflow below. Preview creates no task namespace and acquires no
+project claim lock.
+
 <!-- FORGELOOP EXAMPLE: recipes:create-task | exit=0 | json.taskId=task-001 -->
 ```bash
 forgeloop task-create --task task-001 --claim src --claim tests --json
@@ -243,6 +255,12 @@ forgeloop task-create --task billing-feature --claim src/billing --claim tests/b
 # 3. List active tasks
 forgeloop task-list --json
 
+# 3a. Filter and page the read-only ownership-aware projection
+forgeloop task-list --active --limit 20 --offset 0 --json
+
+# 3b. Ask for a bounded blocker/recovery explanation when needed
+forgeloop next --task auth-feature --explain --json
+
 # 4. Work on task-1
 forgeloop route --task auth-feature --work clean-code --surface backend
 forgeloop preflight --task auth-feature --json
@@ -256,6 +274,11 @@ forgeloop complete --task auth-feature --json
 forgeloop task-unlock --task auth-feature --force --json
 ```
 
+`task-list` discovers all valid task namespaces before applying filters and
+pagination. Its JSON response reports `total` and `hasMore`; filtering does not
+skip ownership or corruption checks, and listing never deletes ledger or
+recovery evidence.
+
 ---
 
 ### Recipe 12 — Migrate Legacy 1.0 Single-Task Layout

package/docs/RELEASE_CHECKLIST.md

@@ -3,14 +3,35 @@
 This is the current release checklist for `@cassiomc1/forgeloop`. It is a
 preparation and verification checklist; it does not authorize publication.
 
-## ForgeLoop 1.11.0 candidate scope
+## ForgeLoop 1.12.0 candidate scope
 
-The 1.11.0 candidate refreshes the public documentation architecture around
-the managed Repository Index and CLI-only persistent search transport. The
-candidate must keep these boundaries explicit:
+The 1.12.0 candidate carries the first-class Flutter guide and deterministic,
+scope-aware project routing added by PR #165. The candidate must keep these
+boundaries explicit:
 
-- [ ] README architecture visual and text fallback describe CLI persistent
-      search separately from direct Integration API/MCP access.
+- [ ] README catalog and architecture fallback identify
+      `ENG/flutter-development-eng.md` and explain that the specialist is
+      selected only from a structurally parsed
+      `dependencies.flutter.sdk: flutter` entry in affected scope.
+- [ ] README catalog and architecture fallback identify
+      `ENG/rust-development-eng.md` and explain that the specialist is
+      selected only from a structurally parsed `[package]` or `[workspace]`
+      table in an affected `Cargo.toml`.
+- [ ] README catalog and architecture fallback identify
+      `ENG/nodejs-backend-development-eng.md` and explain that Node.js
+      backend/runtime evidence is distinct from build, test, and configuration
+      tooling executed under Node.js.
+- [ ] README catalog and architecture fallback identify the C, C++, Java, SQL,
+      Go, TypeScript, PHP, and Swift specialists and explain their bounded
+      structural evidence and same-root composition rules.
+- [ ] The canonical engineering-flow source and regenerated HTML/SVG diagram
+      explain project detection as routing context, not verification or
+      completion evidence.
+- [ ] Positive clean-room package routing selects `flutter`, `clean`, and
+      `test` for a Flutter root.
+- [ ] Documentation-only mentions, lockfiles, hosted packages, malformed
+      dependency shapes, symlink traversal, and unrelated monorepo roots do
+      not activate the Flutter specialist.
 - [ ] [`docs/REPOSITORY_INDEX.md`](./REPOSITORY_INDEX.md) and
       [`docs/PERSISTENT_SEARCH_TRANSPORT.md`](./PERSISTENT_SEARCH_TRANSPORT.md)
       agree on tgrep management, no-fallback behavior, local IPC, ownership,
@@ -24,6 +45,22 @@ This branch prepares the candidate and its pull request. npm publication,
 tagging, GitHub Release, deployment, and merge remain separately authorized
 actions.
 
+## CI minimization validation
+
+- [ ] `npm run verify:fast` passes for edit-time feedback.
+- [ ] `npm run verify:prepush` passes before the release pull request; MCP
+      setup, when needed, was run explicitly with `npm run mcp:setup`.
+- [ ] Ordinary PR validation uses `.github/workflows/pr-core.yml` with the
+      unchanged required contexts `audit`, `CodeQL`, `Verify generated Archify
+      diagram`, `validate (22)`, `tarball smoke (ubuntu-latest)`, and
+      `dependency-review`.
+- [ ] `validate (22)` is always present and fails closed on an applicable
+      prerequisite failure, cancellation, or unexpected skip.
+- [ ] Path classification scenarios cover README-only, ordinary source,
+      Repository Index, package-export, and forced release validation.
+- [ ] Main-branch documentation, Node compatibility, package smoke, audit,
+      and Windows full-suite workflows remain available for broader validation.
+
 ## Contract and package identity
 
 - [ ] `package.json` and `package-lock.json` contain the same package version.
@@ -37,6 +74,9 @@ actions.
 - [ ] [`docs/PACKAGE_CONTENTS.md`](./PACKAGE_CONTENTS.md) matches the current
       `package.json` file list and documents intentional inclusions and
       exclusions.
+- [ ] The candidate tarball includes every registered specialist guide and every
+      other `src/config/guides.json` path; no repository-only guide state is
+      packaged.
 - [ ] Every maintained `src/**/*.js` module is present in the candidate
       tarball; only the four explicitly retired compatibility helpers are
       excluded.
@@ -57,7 +97,8 @@ actions.
 - [ ] Stale contract/route identity rejects handoff creation or acceptance.
 - [ ] An invalid event ledger projects `INCONSISTENT`.
 - [ ] Continuity lint remains non-authoritative and non-evidence.
-- [ ] `npm run dependency:policy` passes without adding runtime dependencies.
+- [ ] `npm run dependency:policy` passes with only the approved exact runtime
+      parser dependency and approved development dependencies.
 - [ ] `npm run lint` passes.
 - [ ] `npm test` passes.
 - [ ] `npm run benchmark:profiles:check` passes; absent provider/host history
@@ -89,8 +130,9 @@ actions.
 ## Integration and cross-platform evidence
 
 - [ ] `npm run pack:check` and `npm run pack:smoke` pass.
-- [ ] `npm pack --dry-run` includes Repository Index runtime/manifest/docs and
-      excludes native release binaries and derived `.forgeloop` index data.
+- [ ] `npm pack --dry-run` includes the Flutter guide, Repository Index
+      runtime/manifest/docs, and excludes native release binaries and derived
+      `.forgeloop` index data.
 - [ ] The npm publication workflow runs `npm run pack:smoke` before its
       provenance-backed publish step.
 - [ ] `npm run mcp:test` either runs the configured MCP tests or reports the

package/docs/TROUBLESHOOTING.md

@@ -7,6 +7,7 @@ This guide provides symptom-first recovery procedures for common ForgeLoop proto
 ## Quick Symptom Index
 
 - [`preflight` is `BLOCKED`](#symptom-preflight-is-blocked)
+- [Project-aware .NET routing is missing](#symptom-project-aware-net-routing-is-missing)
 - [`forgeloop next` returns `RESOLVE_BLOCKER`](#symptom-forgeloop-next-returns-resolve_blocker)
 - [`forgeloop next` returns `RECORD_DIAGNOSIS`](#symptom-forgeloop-next-returns-record_diagnosis)
 - [Progress is `STALLED` or `forgeloop next` returns `CHANGE_STRATEGY`](#symptom-progress-is-stalled)
@@ -37,6 +38,7 @@ This guide provides symptom-first recovery procedures for common ForgeLoop proto
 - [Repository search fails](#symptom-repository-search-fails)
 - [Persistent search host is unavailable](#symptom-persistent-search-host-is-unavailable)
 - [Persistent search host ownership is unverified or stale](#symptom-persistent-search-host-ownership-is-unverified-or-stale)
+- [Local validation tier is unavailable or reports `NOT_VERIFIED`](#symptom-local-validation-tier-is-unavailable-or-reports-not_verified)
 - [Another harness cannot resume the task](#symptom-another-harness-cannot-resume)
 - [Task claim conflict or recovered task](#symptom-task-creation-blocked-by-a-write-claim-conflict-e_task_scope_conflict)
 - [Stable Error & Reason Code Reference](#stable-error-and-reason-codes)
@@ -54,6 +56,102 @@ forgeloop protocol-info --json
 ```
 <!-- END FORGELOOP EXAMPLE -->
 
+### Symptom: local validation tier is unavailable or reports `NOT_VERIFIED`
+
+#### What it means
+
+The selected local validation tier could not run a required external validator
+or setup prerequisite. `NOT_VERIFIED` is an explicit limitation, not a test
+pass and not permission to install tools implicitly.
+
+#### Safe recovery
+
+1. Check the tier and its command list with `node scripts/run-validation.mjs
+   --tier <fast|local|prepush|release> --list`.
+2. Run `npm run mcp:setup` explicitly when MCP dependencies are in scope and
+   installation is authorized.
+3. Confirm Python 3.9 or newer is available for the frozen validators.
+4. Re-run the tier and record any still-unavailable check as `NOT_VERIFIED` in
+   the validation report.
+
+The ordinary PR workflow remains path-aware and always publishes the required
+status contexts; its `validate (22)` aggregator fails closed on an applicable
+job failure, cancellation, or unexpected skip. Local success cannot substitute
+for a required remote security or cross-platform check.
+
+### Symptom: the Node.js test suite is slow locally
+
+#### Inspect
+
+Use the fast, watch, and CI-specific entry points before running the full
+coverage gate:
+
+```bash
+npm run test:quick
+npm run test:watch
+npm run test:ci
+npm run coverage
+```
+
+`npm test` remains the complete no-coverage suite. `test:ci` runs the same
+discovered files with a two-worker cap for small CI runners; it does not remove
+tests or change assertions. Local coverage remains an explicit command because
+instrumentation adds measurable overhead; the PR unit lane wraps that same
+`test:ci` process across four deterministic shards, then aggregates coverage
+without running the suite again. Docs-only changes run the quick suite only on
+the first Node 24 shard; the other shards and the Node 20 lane do not install.
+
+#### Native Windows guidance
+
+Repeated Node process startup can be slowed by Windows Defender scanning the
+repository and dependency tree. If local policy permits, request narrowly
+scoped exclusions for the trusted `node.exe`, this repository root, and its
+`node_modules` directory. Never disable Defender globally or exclude an
+untrusted path. WSL2 can be used when native Windows remains slow, while
+Windows CI continues to cover native path and process behavior.
+
+### Symptom: Project-aware .NET routing is missing
+
+#### What it means
+
+The route command did not find confirmed, affected SDK-style .NET project
+evidence, or the task scope does not reach the confirmed project root. ASP.NET
+Core and ABP are conditional overlays on the `dotnet` specialist; they are not
+standalone guides.
+
+#### Inspect
+
+```bash
+forgeloop route --task <task-id> --work code --surface backend --json
+forgeloop task-show --task <task-id> --json
+```
+
+Then inspect the affected scope for a structurally valid `*.csproj`, `*.fsproj`,
+or `*.vbproj` using the supported SDK allowlist. ASP.NET Core requires a web,
+Razor, or Blazor SDK or a `FrameworkReference Include="Microsoft.AspNetCore.App"`.
+ABP requires a structural `PackageReference Include="Volo.Abp..."` in the
+confirmed .NET project.
+
+#### Common causes
+
+- The repository contains only prose, source snippets, Dockerfiles, lockfiles,
+  package names, or a malformed/oversized/non-SDK-style project file.
+- A write claim points outside the project root, outside the applicable shared
+  `Directory.Build.*`/NuGet scope, or at a non-member of the named `.sln`/`.slnx`.
+- A mixed Flutter/.NET monorepo was treated as one root; nested project roots
+  remain isolated.
+- `projectEvidence.frameworks` contains `aspnetcore` or `abp` without
+  `dotnet`; route validation rejects that input.
+
+#### Safe recovery
+
+Do not add a manual `projectEvidence` claim to force specialist activation.
+Correct the task scope or project structure, rerun the canonical route command,
+and inspect its reason/exclusion codes. Project discovery is bounded and
+non-symlinked; budget exhaustion fails closed. See
+[`GUIDE_ROUTER.md`](../GUIDE_ROUTER.md) for the exact limits and reason-code
+contract.
+
 ### Symptom: `preflight` is `BLOCKED`
 
 #### What it means
@@ -1332,7 +1430,7 @@ package/process recovery boundary. The relevant stable codes are
 | `E_RECONCILE_EVIDENCE_FAILED` | The executed objective-satisfaction evidence command did not pass. | Inspect the execution artifact; reconciliation is refused until evidence passes in the current repository. |
 | `E_RECONCILE_LEDGER_INVALID` | The append-only event ledger is not valid, so reconciliation cannot be recorded. | Inspect the ledger errors and repair before reconciling. |
 | `E_RECONCILE_NOT_STALE` | reconcile-closure was invoked for a work-state checkpoint that is already fresh. | No reconciliation is required; continue the normal lifecycle. |
-| `E_RECONCILE_PHASE_INVALID` | reconcile-closure was invoked for a task that is not EXECUTING or VERIFYING. | reconcile-closure supports EXECUTING or VERIFYING tasks whose objective is already satisfied. |
+| `E_RECONCILE_PHASE_INVALID` | reconcile-closure was invoked for a task that is not EXECUTING, VERIFYING, or REVIEWING. | reconcile-closure supports EXECUTING, VERIFYING, or REVIEWING tasks whose objective is already satisfied. |
 | `E_RECONCILE_REQUIREMENT_UNKNOWN` | The supplied check id and requirement text do not exactly match a contract verification item of type VERIFICATION. | Supply the exact id and requirement text of an existing contract verification item. |
 | `E_RECONCILE_UNSUPPORTED_DRIFT` | Work-state drift includes kinds other than REPOSITORY_CHANGED (contract or required-artifact drift). | Resolve contract or artifact drift through their dedicated recovery surfaces; reconcile-closure only refreshes repository fingerprint drift. |
 | `E_REPOSITORY_CHANGED` | The repository fingerprint (branch or HEAD) moved after the work-state checkpoint was recorded. | If the task objective is already satisfied in the current repository, run forgeloop reconcile-closure; otherwise resume from a checkpoint that matches the current repository. |
@@ -1372,7 +1470,7 @@ package/process recovery boundary. The relevant stable codes are
 | `E_STATE_LEDGER_DIVERGENCE` | A ForgeLoop protocol validation or lifecycle condition was not satisfied. | Inspect the structured command result, correct the named artifact or prerequisite, then run forgeloop next --json. |
 | `E_STATE_MISSING` | A ForgeLoop protocol validation or lifecycle condition was not satisfied. | Inspect the structured command result, correct the named artifact or prerequisite, then run forgeloop next --json. |
 | `E_STATE_MISSING_AFTER_PREFLIGHT_READY` | A ForgeLoop protocol validation or lifecycle condition was not satisfied. | Inspect the structured command result, correct the named artifact or prerequisite, then run forgeloop next --json. |
-| `E_STATE_REVALIDATION_REQUIRED` | The work-state checkpoint must be revalidated before the lifecycle can continue. | Run forgeloop reconcile-closure for externally satisfied EXECUTING tasks, or inspect the freshness reasons for other drift. |
+| `E_STATE_REVALIDATION_REQUIRED` | The work-state checkpoint must be revalidated before the lifecycle can continue. | Run forgeloop reconcile-closure for externally satisfied EXECUTING, VERIFYING, or REVIEWING tasks, or inspect the freshness reasons for other drift. |
 | `E_STATE_TASK_MISMATCH` | A ForgeLoop protocol validation or lifecycle condition was not satisfied. | Inspect the structured command result, correct the named artifact or prerequisite, then run forgeloop next --json. |
 | `E_STRATEGY_OSCILLATION` | Correction history oscillates between previously exhausted strategies without new information. | Gather a genuinely new observation or test a materially different falsifiable hypothesis. |
 | `E_STRUCTURAL_QUALITY_BASELINE_BINDING_MISMATCH` | Structural-quality evidence did not satisfy its provider, artifact, comparison, or lifecycle boundary. | Reconcile contract, route, policy, scope, provider, or rules drift before using the baseline. |

package/docs/assets/diagrams/forgeloop-engineering-flow.html

@@ -1,7 +1,7 @@
 <!DOCTYPE html>
 <html lang="en" data-theme="dark" data-preset="signal-flow" data-present="true">
 <head>
-      <meta name="forgeloop-diagram-source-sha256" content="0bfd5bbf8d6bbeaec23db543deb1e99844321c77b3c7feb21ee0cc877bbba9a9">
+      <meta name="forgeloop-diagram-source-sha256" content="3c35fbe4e144cd7fb60632996839bcf32b0b503e8a4add2270f29c3bf3e8a658">
     <meta name="forgeloop-diagram-renderer" content="archify@2.15.0 (e1ac748f19cf805e44bf74fb93c796662152e273)">
 <meta charset="UTF-8">
   <meta name="viewport" content="width=device-width, initial-scale=1.0">
@@ -4874,7 +4874,7 @@
         <div class="pulse-dot"></div>
         <h1>ForgeLoop Evidence-First Engineering Flow</h1>
       </div>
-      <p class="subtitle">Structured intent → project-bound work → observed evidence → valid closure</p>
+      <p class="subtitle">Structured intent → deterministic project scope → observed evidence → valid closure</p>
     </div>
 
     <script id="archify-guided-views-data" type="application/json">[{"id":"contract-to-work","label":"Contract to work","focus":["request","profile","contract","route","gates","preflight","work"],"note":"Structured obligations and explicit risks set the profile; exclusions do not create required actions."},{"id":"evidence-to-close","label":"Evidence to close","focus":["work","evidence","review","valid"],"note":"See the evidence and review boundary that makes completion trustworthy."},{"id":"recovery-loop","label":"Recovery loop","focus":["evidence","diagnose","correct","preflight","blocked"],"note":"Before execution, blocked refresh needs a valid ledger and revised route. Later failures use diagnosis and correction."}]</script>
@@ -4922,7 +4922,7 @@
     <div class="diagram-container" data-detail-level="read">
       <svg viewBox="0 0 850 900" role="img" aria-labelledby="archify-diagram-title archify-diagram-description" data-animation="trace" data-preset="signal-flow" data-quality-profile="showcase">
         <title id="archify-diagram-title">ForgeLoop Evidence-First Engineering Flow</title>
-        <desc id="archify-diagram-description">Structured intent → project-bound work → observed evidence → valid closure</desc>
+        <desc id="archify-diagram-description">Structured intent → deterministic project scope → observed evidence → valid closure</desc>
         <!-- Definitions -->
         <defs>
           <marker id="arrowhead" markerWidth="10" markerHeight="7" refX="9" refY="3.5" orient="auto">
@@ -5012,15 +5012,15 @@
           <text data-detail="context" x="88" y="131" class="t-muted" font-size="8" text-anchor="middle">intent</text>
         </g>
 
-        <g id="node-profile" data-node-id="profile" data-node-label="Profile" tabindex="0" role="button" aria-label="Focus Profile, discover, Intent + Context › Discover + scope" aria-pressed="false" data-node-kind="backend" data-node-sublabel="discover" data-node-context="Intent + Context › Discover + scope">
-          <title>Profile · discover · Intent + Context › Discover + scope</title>
+        <g id="node-profile" data-node-id="profile" data-node-label="Profile" tabindex="0" role="button" aria-label="Focus Profile, scope, Intent + Context › Discover + scope" aria-pressed="false" data-node-kind="backend" data-node-sublabel="scope" data-node-context="Intent + Context › Discover + scope">
+          <title>Profile · scope · Intent + Context › Discover + scope</title>
           <rect x="195" y="93" width="50" height="52" rx="6" class="c-mask"/>
           <rect x="195" y="93" width="50" height="52" rx="6" class="c-backend" data-animate="node" style="--step:1" stroke-width="1.5"/>
           <g aria-hidden="true" data-semantic-sigil="backend" class="semantic-sigil s-backend" transform="translate(201 99) scale(0.6875)">
             <path d="M6 3 3 8l3 5M10 3l3 5-3 5"/>
           </g>
           <text data-detail-anchor x="220" y="114" class="t-primary" font-size="10" font-weight="600" text-anchor="middle">Profile</text>
-          <text data-detail="context" x="220" y="131" class="t-muted" font-size="8" text-anchor="middle">discover</text>
+          <text data-detail="context" x="220" y="131" class="t-muted" font-size="8" text-anchor="middle">scope</text>
         </g>
 
         <g id="node-contract" data-node-id="contract" data-node-label="Contract" tabindex="0" role="button" aria-label="Focus Contract, scope, Intent + Context › Discover + scope" aria-pressed="false" data-node-kind="security" data-node-sublabel="scope" data-node-tag="saved" data-node-context="Intent + Context › Discover + scope">
@@ -5396,6 +5396,19 @@
         </ul>
       </div>
 
+      <div class="card">
+        <div class="card-header">
+          <div class="card-dot amber"></div>
+          <h3>Deterministic project routing</h3>
+        </div>
+        <ul>
+          <li>&bull; Repository evidence feeds bounded project and surface detection</li>
+          <li>&bull; A parsed dependencies.flutter.sdk: flutter entry proves Flutter project scope</li>
+          <li>&bull; The router selects the Flutter specialist only for an affected scoped root</li>
+          <li>&bull; Detection context is routing input, not verification or completion evidence</li>
+        </ul>
+      </div>
+
       <div class="card">
         <div class="card-header">
           <div class="card-dot cyan"></div>

package/docs/assets/diagrams/forgeloop-engineering-flow.receipt.json

@@ -15,17 +15,17 @@
     "license": "MIT"
   },
   "input": {
-    "sha256": "0bfd5bbf8d6bbeaec23db543deb1e99844321c77b3c7feb21ee0cc877bbba9a9",
-    "bytes": 9779
+    "sha256": "3c35fbe4e144cd7fb60632996839bcf32b0b503e8a4add2270f29c3bf3e8a658",
+    "bytes": 10229
   },
   "artifacts": {
     "html": {
-      "sha256": "251e09f3cc36d54c4b8567dd3e6dd8a890a2621cdd12667fb80cc61e7dbf4b7c",
-      "bytes": 648281
+      "sha256": "26e82be933acaca0d7f07e917413d87135b901195aef22bd42ef974fe1548ad3",
+      "bytes": 648893
     },
     "svg": {
-      "sha256": "ef3effe7e756494c7dffef9ee315e970bbbdb9fddc0ee0a1e4bfccfbb0c05534",
-      "bytes": 211373
+      "sha256": "040fc511d09be1532ff7173baf46a98503e89734460a516582426aa426eea888",
+      "bytes": 211370
     }
   },
   "staticSvg": {

package/docs/assets/diagrams/forgeloop-engineering-flow.svg

@@ -1,4 +1,4 @@
-<svg data-archify-version="2.15.0" data-forgeloop-source-sha256="0bfd5bbf8d6bbeaec23db543deb1e99844321c77b3c7feb21ee0cc877bbba9a9" data-theme="dark" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 850 900" role="img" aria-labelledby="archify-diagram-title archify-diagram-description" data-animation="trace" data-preset="signal-flow" data-quality-profile="showcase">
+<svg data-archify-version="2.15.0" data-forgeloop-source-sha256="3c35fbe4e144cd7fb60632996839bcf32b0b503e8a4add2270f29c3bf3e8a658" data-theme="dark" xmlns="http://www.w3.org/2000/svg" viewBox="0 0 850 900" role="img" aria-labelledby="archify-diagram-title archify-diagram-description" data-animation="trace" data-preset="signal-flow" data-quality-profile="showcase">
     <style>
       .c-bg-rect { fill: var(--bg); }
 /* Keep boundary labels clear of the first node in each group. */
@@ -4732,7 +4732,7 @@
     </style>
     <rect width="100%" height="100%" class="c-bg-rect" />
         <title id="archify-diagram-title">ForgeLoop Evidence-First Engineering Flow</title>
-        <desc id="archify-diagram-description">Structured intent → project-bound work → observed evidence → valid closure</desc>
+        <desc id="archify-diagram-description">Structured intent → deterministic project scope → observed evidence → valid closure</desc>
         <!-- Definitions -->
         <defs>
           <marker id="arrowhead" markerWidth="10" markerHeight="7" refX="9" refY="3.5" orient="auto">
@@ -4822,15 +4822,15 @@
           <text data-detail="context" x="88" y="131" class="t-muted" font-size="8" text-anchor="middle">intent</text>
         </g>
 
-        <g id="node-profile" data-node-id="profile" data-node-label="Profile" tabindex="0" role="button" aria-label="Focus Profile, discover, Intent + Context › Discover + scope" aria-pressed="false" data-node-kind="backend" data-node-sublabel="discover" data-node-context="Intent + Context › Discover + scope">
-          <title>Profile · discover · Intent + Context › Discover + scope</title>
+        <g id="node-profile" data-node-id="profile" data-node-label="Profile" tabindex="0" role="button" aria-label="Focus Profile, scope, Intent + Context › Discover + scope" aria-pressed="false" data-node-kind="backend" data-node-sublabel="scope" data-node-context="Intent + Context › Discover + scope">
+          <title>Profile · scope · Intent + Context › Discover + scope</title>
           <rect x="195" y="93" width="50" height="52" rx="6" class="c-mask"/>
           <rect x="195" y="93" width="50" height="52" rx="6" class="c-backend" data-animate="node" style="--step:1" stroke-width="1.5"/>
           <g aria-hidden="true" data-semantic-sigil="backend" class="semantic-sigil s-backend" transform="translate(201 99) scale(0.6875)">
             <path d="M6 3 3 8l3 5M10 3l3 5-3 5"/>
           </g>
           <text data-detail-anchor="true" x="220" y="114" class="t-primary" font-size="10" font-weight="600" text-anchor="middle">Profile</text>
-          <text data-detail="context" x="220" y="131" class="t-muted" font-size="8" text-anchor="middle">discover</text>
+          <text data-detail="context" x="220" y="131" class="t-muted" font-size="8" text-anchor="middle">scope</text>
         </g>
 
         <g id="node-contract" data-node-id="contract" data-node-label="Contract" tabindex="0" role="button" aria-label="Focus Contract, scope, Intent + Context › Discover + scope" aria-pressed="false" data-node-kind="security" data-node-sublabel="scope" data-node-tag="saved" data-node-context="Intent + Context › Discover + scope">

package/docs/diagrams/forgeloop-engineering-flow.workflow.json

@@ -3,7 +3,7 @@
   "diagram_type": "workflow",
   "meta": {
     "title": "ForgeLoop Evidence-First Engineering Flow",
-    "subtitle": "Structured intent \u2192 project-bound work \u2192 observed evidence \u2192 valid closure",
+    "subtitle": "Structured intent \u2192 deterministic project scope \u2192 observed evidence \u2192 valid closure",
     "animation": "trace",
     "visual_preset": "signal-flow",
     "quality_profile": "showcase",
@@ -180,7 +180,7 @@
       "col": 1,
       "type": "backend",
       "label": "Profile",
-      "sublabel": "discover",
+      "sublabel": "scope",
       "width": 50
     },
     {
@@ -419,6 +419,16 @@
         "Blocked pre-execution refresh requires a valid ledger and revised route"
       ]
     },
+    {
+      "dot": "amber",
+      "title": "Deterministic project routing",
+      "items": [
+        "Repository evidence feeds bounded project and surface detection",
+        "A parsed dependencies.flutter.sdk: flutter entry proves Flutter project scope",
+        "The router selects the Flutter specialist only for an affected scoped root",
+        "Detection context is routing input, not verification or completion evidence"
+      ]
+    },
     {
       "dot": "cyan",
       "title": "Evidence contract",

package/docs/diagrams/reviews/forgeloop-engineering-flow.review.json

@@ -3,8 +3,8 @@
   "diagramId": "forgeloop-engineering-flow",
   "status": "approved",
   "binding": {
-    "sourceSha256": "0bfd5bbf8d6bbeaec23db543deb1e99844321c77b3c7feb21ee0cc877bbba9a9",
-    "svgSha256": "ef3effe7e756494c7dffef9ee315e970bbbdb9fddc0ee0a1e4bfccfbb0c05534"
+    "sourceSha256": "3c35fbe4e144cd7fb60632996839bcf32b0b503e8a4add2270f29c3bf3e8a658",
+    "svgSha256": "040fc511d09be1532ff7173baf46a98503e89734460a516582426aa426eea888"
   },
   "checks": {
     "darkThemeLegible": true,
@@ -16,5 +16,5 @@
     "accessibleMetadataPresent": true
   },
   "reviewedBy": "Codex visual review",
-  "reviewedAt": "2026-09-05"
+  "reviewedAt": "2026-09-09"
 }