@cassiomc1/forgeloop 1.11.0 → 1.12.0

package/GUIDE_ROUTER.md

@@ -52,6 +52,7 @@ project commands.
 | `accessibility` | [Accessibility](./ENG/accessibility-eng.md) | WCAG, keyboard access, focus, semantics, and assistive technology |
 | `games` | [Web games](./ENG/games-code-design-web-eng.md) | Architecture and operation of 2D, 3D, and procedural web games |
 | `documentation` | [Documentation quality](./ENG/documentation-quality-eng.md) | Accuracy, architecture, freshness, accessibility, and verifiable technical documentation |
+| `flutter` | [Flutter application engineering](./ENG/flutter-development-eng.md) | Architecture, implementation, testing, performance, accessibility, platform integration, and release of production Flutter applications |
 
 ## Domain rules
 
@@ -205,6 +206,22 @@ rg -n '^## |accuracy|completeness|Diátaxis|tutorial|how-to|reference|explanatio
 
 **Expected evidence:** documentation purpose and audience are clear, factual claims are cross-checked against canonical project sources, changed documentation surfaces are complete, relevant examples/links/builds are validated when available, and unavailable required checks are recorded as `NOT_VERIFIED`.
 
+### `flutter` — Flutter application engineering
+
+**Activate when:** a confirmed project root has a structurally parsed `pubspec.yaml` with `dependencies.flutter.sdk: flutter`, and the task scope intersects that root. Once the root is confirmed, every claim under it matches, including lockfiles, localization/configuration files, source, tooling, and native platform configuration; confirmed nested project roots remain isolated. The guide then provides the Flutter-specific architecture, implementation, testing, performance, accessibility, platform integration, and release context.
+
+**Do not activate merely because:** prose, Markdown, a lockfile, a transitive package name, an arbitrary directory name, a hosted package named `flutter`, or an unrelated monorepo project mentions Flutter. `flutter_test` and platform/source signals are supporting evidence only; they cannot replace the primary SDK dependency signal.
+
+**Usually combine with:** `clean` and `test`; add `design`, `accessibility`, `security`, or `performance` when the affected surface or risk requires them.
+
+The route command obtains this evidence from `src/core/project-detection.js`. It walks bounded, non-symlinked project manifests, parses dependency structure, and matches task write claims against confirmed project roots. An unscoped route can inspect all detected projects; an explicit claim that does not reach a Flutter project produces `NO_FLUTTER_SCOPE_MATCH` and does not activate the guide. Documentation and UI-copy exclusions remain routing decisions, not project-detection heuristics.
+
+```bash
+rg -n '^## |architecture|testing|performance|accessibility|platform|release|Flutter' ENG/flutter-development-eng.md
+```
+
+**Expected evidence:** a confirmed affected Flutter project, a scoped route, platform-appropriate tests, measured performance or accessibility checks when relevant, and honest `NOT_VERIFIED` reporting for unavailable Flutter tooling.
+
 ## Work-type matrix
 
 | Work | Primary guide | Common complements | Exclude when |
@@ -214,6 +231,7 @@ rg -n '^## |accuracy|completeness|Diátaxis|tutorial|how-to|reference|explanatio
 | Code or bug without UI | `clean` | `test`; risk may add `security` or `performance` | The surface is unchanged |
 | Backend, API, or data | `clean` | `test`, `security`; `performance` for a critical path | That layer does not exist |
 | Web, mobile, or desktop UI | `design` | `accessibility`, `clean`, `test`; risk defines the rest | Users cannot observe the change |
+| Flutter application | `flutter` | `clean`, `test`; add `design`, `accessibility`, `security`, or `performance` as applicable | No primary Flutter SDK dependency in the affected project scope |
 | Complete website | `premium` | `design`, `accessibility`, `clean`, `test`, `security`, `performance` | The deliverable is not a complete site |
 | Web game | `games` | `clean`, `test`, `security`, `performance`, `accessibility`; `design` with UI | The product is not a game |
 | HTML video or motion | `design` | `accessibility`, `performance`, `test`, `security` | There is no audiovisual composition |
@@ -226,7 +244,9 @@ HyperFrames is optional and may be used only when requested or already available
 The active agent may classify natural language, but it must pass declared
 signals to the deterministic evaluator in `src/core/router.js`. The evaluator
 does not parse natural language, call a model, or infer a stack from a word in
-the repository.
+the repository. `runRoute` may also pass `projectEvidence` from
+`src/core/project-detection.js`; that evidence is produced by structural
+manifest parsing and scope intersection, not by prose or model confidence.
 
 The first routing contract is versioned as `schemaVersion: 1`. It accepts:
 
@@ -243,19 +263,28 @@ The first routing contract is versioned as `schemaVersion: 1`. It accepts:
 - `platforms`: `web`, `mobile`, `desktop`, `server`, `ci`, or
   `cross-platform`;
 - optional boolean `behaviorChange` and `executableChange` signals.
+- optional `projectEvidence` with a schema version, a scope result, detected
+  framework IDs, affected project roots, primary signals, and supporting
+  signals. The current framework ID is `flutter`; its primary signal is an
+  affected `dependencies.flutter.sdk: flutter` entry in `pubspec.yaml`.
 
 Rule precedence is deterministic: the work type establishes the primary
 closure; affected surfaces add mandatory complements; risks add security,
 performance, or accessibility; executable/behavior changes add clean and
 test; required rules win over optional exclusions; and the evaluator preserves
-canonical insertion order. Unknown or duplicate signals fail with a routing
-error.
+canonical insertion order. A matching Flutter project adds `flutter` plus the
+`clean`/`test` baseline before ordinary work-type complements; documentation
+and UI-copy work do not activate the specialist. Unknown or duplicate signals
+fail with a routing error.
 
 Every selected guide has stable reason codes such as
 `WORK_COMPLETE_WEBSITE`, `SURFACE_UI`, `RISK_UNTRUSTED_INPUT`, and
 `CHANGE_EXECUTABLE_CONFIG`. Exclusions use stable codes such as
 `NO_TRUST_BOUNDARY`, `NO_MEASURABLE_PERFORMANCE_RISK`, and
-`NO_DOCUMENTATION_SURFACE`.
+`NO_DOCUMENTATION_SURFACE`. Flutter uses
+`PROJECT_FLUTTER_SDK_DEPENDENCY`, `PROJECT_FLUTTER_BASELINE`,
+`NO_FLUTTER_PRIMARY_EVIDENCE`, `NO_FLUTTER_SCOPE_MATCH`, and
+`NO_FLUTTER_EXECUTABLE_WORK`.
 
 Platform signals are contextual, not automatic guide activators:
 
@@ -280,6 +309,10 @@ Negative routing guarantees:
 - a backend refactor does not activate `design` or `accessibility`;
 - static UI copy does not activate `security` without a trust-boundary signal;
 - a package file alone does not prove that Node is an affected task surface;
+- `flutter_test`, a Flutter word in documentation, or a lockfile package does
+  not replace the primary Flutter SDK dependency signal;
+- an unrelated monorepo project does not activate Flutter when task claims do
+  not intersect its confirmed project root; nested project roots remain isolated;
 - an explicit executable-change signal adds `clean` and `test` even when the
   semantic work type is documentation.
 
@@ -323,6 +356,15 @@ Verify the game loop, authoritative server, reconciliation, input, assets, fallb
 
 Verify Markdown, links, paths, commands, and examples.
 
+### Flutter application feature
+
+<!-- route:flutter-app-feature=flutter,clean,test -->
+
+Verify the affected `pubspec.yaml` contains the Flutter SDK dependency, confirm
+the task claim reaches that project, and cover widget/state behavior, platform
+integration, accessibility, performance, and release checks according to the
+changed surface. Supporting signals alone must leave `flutter` excluded.
+
 ## Route changes
 
 If investigation reveals a new surface, update the guide set before editing that area. Record only the concise reason; do not create a versioned task log.

package/LOOP_SYSTEM_DESIGN.md

@@ -242,7 +242,7 @@ presented as a completed protocol state.
 
 ### `ENG/*.md`
 
-Nine canonical guides cover:
+Eleven canonical guides cover:
 
 - clean code;
 - testing;
@@ -252,7 +252,9 @@ Nine canonical guides cover:
 - accessibility;
 - premium website production;
 - web games;
-- contextual frontend taste.
+- contextual frontend taste;
+- technical documentation quality;
+- Flutter application engineering.
 
 Each guide has exact English frontmatter and a stable guide ID.
 
@@ -265,6 +267,7 @@ Records external provenance, trademarks, licenses, and reuse boundaries. It is r
 | Work type | Guide set |
 | --- | --- |
 | Documentation | Related domain and documentation checks |
+| Flutter application | `flutter` with `clean` and `test`; add surface-specific guides as needed |
 | General code or bug fix | `clean`, `test`; add `security` or `performance` when the surface requires it |
 | Backend, API, authentication, or data | `clean`, `test`, `security`; add `performance` for critical paths |
 | Web, mobile, or desktop interface | `clean`, `test`, `design`, `accessibility`; add `security` and `performance` according to product risk |
@@ -418,7 +421,7 @@ The documentation workflow verifies:
 
 - every file referenced by an adapter exists;
 - repository-relative links resolve;
-- exactly nine canonical English guides exist;
+- exactly eleven canonical English guides exist;
 - guide IDs, filenames, frontmatter keys, and `language: en` match the catalog;
 - no legacy language tree or bilingual metadata remains;
 - all route contracts contain valid guide IDs;
@@ -428,14 +431,15 @@ The documentation workflow verifies:
 - secrets and credential-like assignments are absent;
 - `THIRD_PARTY_NOTICES.md` is present.
 
-The validator also exercises six routing scenarios:
+The validator also exercises seven routing scenarios:
 
 1. premium landing page;
 2. authenticated API;
 3. bug fix without UI;
 4. mobile app with UI;
 5. multiplayer web game;
-6. documentation-only change.
+6. documentation-only change;
+7. Flutter application feature with a primary SDK dependency signal.
 
 ## Distribution
 
@@ -527,7 +531,7 @@ is orthogonal to lifecycle phases and does not authorize the receiving harness.
 - The repository and its maintained content are English-only.
 - Common project instruction surfaces and generic bootstrap mechanisms have a
   documented entry into one canonical loop.
-- The router selects every relevant guide and excludes irrelevant guides in the six defined scenarios.
+- The router selects every relevant guide and excludes irrelevant guides in the seven defined scenarios.
 - The profile contains verifiable facts, sources, and real commands without secrets.
 - The loop requires evidence before completion claims and exits safely when blocked.
 - Structural, Markdown, link, and secret checks pass locally and in CI.

package/QUALITY_SCORECARD.md

@@ -94,6 +94,7 @@ are both present:
 | Dimension | Implementation evidence | Executable evidence |
 | --- | --- | --- |
 | Routing | `src/core/router.js`, route schemas, stable reason codes, and exclusions | `tests/router.test.js`, `tests/fixtures/routes/` |
+| Flutter project detection and routing | `src/core/project-detection.js`, `src/core/router.js`, `src/config/guides.json`, and scoped manifest evidence | `tests/project-detection.test.js`, `tests/guide-registry.test.js`, `tests/router.test.js` |
 | Observability | `src/core/receipt.js`, `src/core/inspect.js`, `src/core/evidence.js`, and schema health | `tests/observability.test.js`, `tests/receipt-semantics.test.js`, `tests/schema-health.test.js` |
 | Resume/checkpoint | `src/core/work-state.js`, `EXECUTION_STATE.md`, shared loaded-state classifier, contract/artifact classifiers, and atomic writes | `tests/work-state.test.js`, `tests/checkpoint-freshness.test.js`, status, validate-state, and validate-protocol tests |
 | Delegation | `src/core/delegation.js`, delegation-set validator, and `DELEGATION_PROTOCOL.md` | `tests/delegation.test.js`, `tests/delegation-set.test.js` |

package/README.md

@@ -45,16 +45,11 @@ relevant guides.
 
 ## Real execution proof
 
-ForgeLoop includes a public real-execution PoC with the workload,
-protocol artifacts, trusted command provenance, execution receipt,
-event history, cryptographic evidence manifest, and technical audit.
+Public [execution PoC](./poc/README.md) covers workload, protocol
+artifacts, trusted provenance, receipts, evidence, and audit. It reached
+validator-backed `COMPLETE / VALID` and preserves a later
+`E_RECEIPT_PATH_MISMATCH` after publication changed the repository.
 
-The original task reached validator-backed `COMPLETE / VALID`.
-The evidence package also preserves a later
-`E_RECEIPT_PATH_MISMATCH`, detected after evidence publication itself
-changed the repository.
-
-- [PoC overview](./poc/README.md)
 - [Canonical technical audit](./poc/reports/poc-20260826-real-execution-technical-audit-v2.md)
 - [Evidence package](./poc/evidence/poc-20260826-real-execution/)
 
@@ -72,10 +67,14 @@ changed the repository.
 | Accessibility | [`ENG/accessibility-eng.md`](./ENG/accessibility-eng.md) |
 | Web games | [`ENG/games-code-design-web-eng.md`](./ENG/games-code-design-web-eng.md) |
 | Documentation quality | [`ENG/documentation-quality-eng.md`](./ENG/documentation-quality-eng.md) |
+| Flutter | [guide](./ENG/flutter-development-eng.md) |
 | Structural quality feedback | [`docs/STRUCTURAL_QUALITY.md`](./docs/STRUCTURAL_QUALITY.md) |
 
-Each guide declares its name, language, version, and review date in
-frontmatter. Repository validators keep the catalog and metadata synchronized.
+Guide metadata is validator-checked.
+
+Parsed `pubspec.yaml` with `dependencies.flutter.sdk: flutter` selects
+Flutter; mentions, lockfiles, hosted packages, and unrelated monorepos do not.
+See [guide](./ENG/flutter-development-eng.md).
 
 ## Quickstart
 
@@ -459,9 +458,11 @@ and [visual review](./docs/diagrams/reviews/forgeloop-code-attestation-flow.revi
 show exact content binding, optional signing, and separate revision-range
 coverage.
 
-Text-only fallback: discovery creates the contract and route; required gates
-and `PREFLIGHT_READY` authorize execution; verification creates structured
-evidence; failures enter diagnosis and correction; review precedes
+Text-only fallback: discovery creates the contract and route; parsed
+`dependencies.flutter.sdk: flutter` selects Flutter for that root; routing is
+not verification/completion evidence. Gates and
+`PREFLIGHT_READY` authorize execution; verification creates
+structured evidence; failures enter diagnosis and correction; review precedes
 validator-backed completion. Drift reopens verification, and migration keeps
 modified or unmanaged files for review. The terminal result is one of
 `VALID`, `INCOMPLETE`, `STALE`, `INCONSISTENT`, or `INVALID`.

package/docs/AGENT_PROTOCOL_SUMMARY.md

@@ -7,7 +7,7 @@
 ForgeLoop is a portable protocol and support CLI for verifiable engineering workflows. It records and validates task state, contracts, routing, checks, evidence, continuity, and optional code attestations. It does not become an agent scheduler, delegation service, source-control authority, or secret manager.
 
 Protocol version: 1
-Package version: 1.11.0
+Package version: 1.12.0
 
 ## Canonical loop
 

package/docs/CLI_REFERENCE.md

@@ -838,7 +838,7 @@ Updates the managed instruction kit to match the current ForgeLoop package versi
 
 Calculates and persists deterministic engineering guide routing.
 
-- **Purpose**: Selects relevant technical guides (e.g. `clean`, `test`, `security`, `design`) based on declared work attributes.
+- **Purpose**: Selects relevant technical guides (e.g. `clean`, `test`, `security`, `design`) from declared work attributes and bounded structural project evidence such as an affected Flutter SDK dependency.
 - **When to use**: During discovery before preflight.
 - **Mutation**: Writes `.forgeloop/task-state/<taskKey>/routing-result.json`.
 - **Options**:

package/docs/MCP.md

@@ -150,7 +150,7 @@ forgeloop-mcp-http --project /repo --mode safe          # 127.0.0.1:3333
 
 | Component | Current contract |
 | --- | --- |
-| ForgeLoop core package | `>=1.5.0 <2` dependency range; current release candidate `1.11.0` |
+| ForgeLoop core package | `>=1.5.0 <2` dependency range; current release `1.12.0` |
 | ForgeLoop protocol | `1` |
 | Integration API | `1` |
 | MCP package | `0.1.x` initial package |

package/docs/PACKAGE_CONTENTS.md

@@ -27,6 +27,11 @@ The published tarball includes the following consumer-facing groups:
   This includes the provider-neutral Repository Index runtime and its pinned
   `src/repository-index/tgrep-manifest.json`; native engine binaries are
   provisioned outside the npm tarball.
+- **Specialist guidance:** every registered consumer guide under `ENG/`,
+  including `ENG/flutter-development-eng.md`, ships with the guide registry
+  and is resolved from a package-local path. The Flutter specialist is
+  selected only for an affected root with the structural SDK dependency
+  signal; the package does not install or invoke Flutter tooling.
 - **Initialization material:** the root protocol and integration documents,
   legal notices, the target profile template, and every path listed by
   `src/core/templates.js`. These files are read by `init` and `update`, so
@@ -87,7 +92,9 @@ npm run pack:smoke
 
 `pack:smoke` installs the candidate tarball into a temporary consumer and
 exercises the CLI, public Integration API, initialization, schemas, and
-packaged documentation references. The tag-triggered publication workflow
+packaged documentation references. The package-boundary tests also assert
+that every registered guide path, including the Flutter specialist, is
+present in the candidate. The tag-triggered publication workflow
 runs the same smoke gate before `npm publish --provenance --access public`.
 Publication therefore remains owned by the trusted GitHub Actions OIDC
 workflow; local package inspection proves the candidate boundary but does not

package/docs/RELEASE_CHECKLIST.md

@@ -3,14 +3,24 @@
 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.
+- [ ] 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,
@@ -37,6 +47,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 the registered Flutter 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.
@@ -89,8 +102,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/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"
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@cassiomc1/forgeloop",
-  "version": "1.11.0",
+  "version": "1.12.0",
   "description": "Portable, verifiable engineering protocol for AI coding environments and developer workflows",
   "repository": {
     "type": "git",

package/schemas/routing-input.schema.json

@@ -11,7 +11,20 @@
     "risks": { "type": "array", "items": { "type": "string" } },
     "platforms": { "type": "array", "items": { "type": "string" } },
     "behaviorChange": { "type": "boolean" },
-    "executableChange": { "type": "boolean" }
+    "executableChange": { "type": "boolean" },
+    "projectEvidence": {
+      "type": "object",
+      "required": ["schemaVersion", "scope", "frameworks", "projectRoots", "primarySignals", "supportingSignals"],
+      "properties": {
+        "schemaVersion": { "const": 1 },
+        "scope": { "enum": ["MATCH", "UNSCOPED", "NO_MATCH", "NONE"] },
+        "frameworks": { "type": "array", "items": { "enum": ["flutter"] } },
+        "projectRoots": { "type": "array", "items": { "type": "string", "minLength": 1 } },
+        "primarySignals": { "type": "array", "items": { "type": "string", "minLength": 1 } },
+        "supportingSignals": { "type": "array", "items": { "type": "string", "minLength": 1 } }
+      },
+      "additionalProperties": false
+    }
   },
   "additionalProperties": false
 }

package/src/commands/route.js

@@ -2,6 +2,7 @@ import { evaluateRoute } from "../core/router.js";
 import { persistRoute } from "../core/route-artifact.js";
 import { readContract } from "../core/contract.js";
 import { readConfig } from "../core/config.js";
+import { detectProjectEvidence } from "../core/project-detection.js";
 import { withTaskMutation } from "../core/task-command.js";
 
 export async function runRoute({ target, packageRoot, workType, surfaces, risks, platforms, behaviorChange, executableChange, executionProfile = null, taskId, task }) {
@@ -19,6 +20,9 @@ export async function runRoute({ target, packageRoot, workType, surfaces, risks,
     } catch (error) {
       if (error.code !== "ARTIFACT_MISSING") throw error;
     }
+    const projectEvidence = target
+      ? await detectProjectEvidence(target, { claims: ctx?.descriptor?.writeClaims ?? [] })
+      : null;
     const route = evaluateRoute({
       workType,
       surfaces,
@@ -26,6 +30,7 @@ export async function runRoute({ target, packageRoot, workType, surfaces, risks,
       platforms,
       behaviorChange,
       executableChange,
+      ...(projectEvidence ? { projectEvidence } : {}),
     }, {
       contract,
       taskDescriptor: ctx?.descriptor ?? null,

package/src/config/guides.json

@@ -38,5 +38,9 @@
   "documentation": {
     "path": "ENG/documentation-quality-eng.md",
     "install": true
+  },
+  "flutter": {
+    "path": "ENG/flutter-development-eng.md",
+    "install": true
   }
 }