aw-spec-cli 0.1.21 → 0.1.22

package/assets/.appweaver/stack-profiles/java-spring.json

@@ -13,5 +13,24 @@
   "detect": [
     "pom.xml",
     "build.gradle"
+  ],
+  "reserved_names": [
+    "Character",
+    "Class",
+    "Enum",
+    "Error",
+    "Exception",
+    "Integer",
+    "Module",
+    "Number",
+    "Object",
+    "Package",
+    "Process",
+    "Record",
+    "Runtime",
+    "String",
+    "System",
+    "Thread",
+    "Void"
   ]
 }

package/assets/.appweaver/stack-profiles/nextjs.json

@@ -12,5 +12,31 @@
   "prototype_run": "npm run dev --prefix prototype",
   "detect": [
     "web/next.config.*"
+  ],
+  "reserved_names": [
+    "Array",
+    "Date",
+    "Document",
+    "Element",
+    "Error",
+    "Event",
+    "Headers",
+    "History",
+    "Image",
+    "Location",
+    "Map",
+    "Node",
+    "Notification",
+    "Object",
+    "Option",
+    "Range",
+    "Record",
+    "Request",
+    "Response",
+    "Selection",
+    "Set",
+    "Storage",
+    "Text",
+    "Worker"
   ]
 }

package/assets/.appweaver/stack-profiles/node-express.json

@@ -12,5 +12,31 @@
   "detect": [
     "package.json",
     "src/**/*.ts"
+  ],
+  "reserved_names": [
+    "Array",
+    "Date",
+    "Document",
+    "Element",
+    "Error",
+    "Event",
+    "Headers",
+    "History",
+    "Image",
+    "Location",
+    "Map",
+    "Node",
+    "Notification",
+    "Object",
+    "Option",
+    "Range",
+    "Record",
+    "Request",
+    "Response",
+    "Selection",
+    "Set",
+    "Storage",
+    "Text",
+    "Worker"
   ]
 }

package/assets/.appweaver/stack-profiles/python-fastapi.json

@@ -13,5 +13,20 @@
     "pyproject.toml",
     "requirements.txt",
     "app/main.py"
+  ],
+  "reserved_names": [
+    "Any",
+    "Callable",
+    "Dict",
+    "Generator",
+    "Iterator",
+    "List",
+    "Mapping",
+    "Optional",
+    "Sequence",
+    "Set",
+    "Text",
+    "Type",
+    "Union"
   ]
 }

package/assets/.appweaver/stack-profiles/react-vite.json

@@ -13,5 +13,31 @@
   "detect": [
     "web/package.json",
     "web/vite.config.*"
+  ],
+  "reserved_names": [
+    "Array",
+    "Date",
+    "Document",
+    "Element",
+    "Error",
+    "Event",
+    "Headers",
+    "History",
+    "Image",
+    "Location",
+    "Map",
+    "Node",
+    "Notification",
+    "Object",
+    "Option",
+    "Range",
+    "Record",
+    "Request",
+    "Response",
+    "Selection",
+    "Set",
+    "Storage",
+    "Text",
+    "Worker"
   ]
 }

package/assets/.appweaver/stack-profiles/sveltekit.json

@@ -12,5 +12,31 @@
   "prototype_run": "npm run dev --prefix prototype",
   "detect": [
     "web/svelte.config.*"
+  ],
+  "reserved_names": [
+    "Array",
+    "Date",
+    "Document",
+    "Element",
+    "Error",
+    "Event",
+    "Headers",
+    "History",
+    "Image",
+    "Location",
+    "Map",
+    "Node",
+    "Notification",
+    "Object",
+    "Option",
+    "Range",
+    "Record",
+    "Request",
+    "Response",
+    "Selection",
+    "Set",
+    "Storage",
+    "Text",
+    "Worker"
   ]
 }

package/assets/.appweaver/stack-profiles/vue-vite.json

@@ -13,5 +13,31 @@
   "detect": [
     "web/vite.config.*",
     "web/src/App.vue"
+  ],
+  "reserved_names": [
+    "Array",
+    "Date",
+    "Document",
+    "Element",
+    "Error",
+    "Event",
+    "Headers",
+    "History",
+    "Image",
+    "Location",
+    "Map",
+    "Node",
+    "Notification",
+    "Object",
+    "Option",
+    "Range",
+    "Record",
+    "Request",
+    "Response",
+    "Selection",
+    "Set",
+    "Storage",
+    "Text",
+    "Worker"
   ]
 }

package/assets/.appweaver/templates/ui-model-template.md

@@ -0,0 +1,67 @@
+# UI Model: [Feature Name]
+
+**Aggregate (feature)**: `[Aggregate]`
+**Spec Reference**: `specs/[Aggregate]/spec.md`
+**Workflow Reference**: `specs/[Aggregate]/ui/workflow-model.md`
+**Version**: v1.0
+**Status**: Active
+
+## Overview
+
+[Information architecture mapping user workflows into concrete UI surfaces, routes, interaction states, and component hierarchy.]
+
+## UI Surfaces
+
+### Surface 1: [Surface Title — e.g. Project Directory & Workspace]
+
+- **Surface Type**: `Page` | `Sub-Page` | `Dialog` | `Drawer` | `Modal` | `View`
+- **Route / Mount Path**: `/projects`
+- **Supported Workflows**: [WF-1, WF-2]
+- **Target Personas**: [Project Manager, PMO Member]
+- **Required Interaction States**:
+  - `Loading`: Skeleton placeholders during data retrieval
+  - `Empty`: Zero-state graphic with call-to-action
+  - `Populated`: Structured table / card layout displaying primary entities
+  - `Filtered / Searched`: Dynamic filtering view
+  - `Error`: Inline error notification banner
+- **User Actions & Events**:
+  - Search & filter inputs
+  - Action trigger (e.g. "Create Project" → opens Surface 2)
+  - Row item selection (→ opens Surface 3)
+- **Transitions**:
+  - `On Click [Action]` → Navigates to or opens `[Surface Name]`
+
+---
+
+### Surface 2: [Surface Title — e.g. Create Project Form]
+
+- **Surface Type**: `Drawer` | `Dialog` | `Page`
+- **Route / Mount Path**: `/projects/create` (or Modal on `/projects`)
+- **Supported Workflows**: [WF-1]
+- **Target Personas**: [Project Manager]
+- **Required Interaction States**:
+  - `Initial / Ready`: Blank form with active validation rules
+  - `Validation Error`: Inline field error callouts (e.g. invalid date range)
+  - `Submitting`: Button loading spinner with disabled inputs
+  - `Success`: Dismisses modal & appends item to active list with toast confirmation
+- **User Actions & Events**:
+  - Input fields & attachment uploads
+  - Submit & Cancel controls
+- **Transitions**:
+  - `On Submit Success` → Return to `Surface 1` (Populated state)
+  - `On Cancel` → Close surface without saving
+
+---
+
+### Surface 3: [Surface Title — e.g. Action Confirmation Modal]
+
+- **Surface Type**: `Dialog`
+- **Supported Workflows**: [WF-3]
+- **Target Personas**: [Authorized Roles]
+- **Required Interaction States**:
+  - `Prompt`: Mandatory confirmation text & action buttons
+  - `Executing`: Disables actions during execution
+- **User Actions & Events**:
+  - Confirm & Cancel buttons
+- **Transitions**:
+  - `On Confirm` → Execute state transition & update parent surface UI

package/assets/.appweaver/templates/workflow-model-template.md

@@ -0,0 +1,62 @@
+# Workflow Model: [Feature Name]
+
+**Aggregate (feature)**: `[Aggregate]`
+**Spec Reference**: `specs/[Aggregate]/spec.md`
+**Version**: v1.0
+**Status**: Active
+
+## Overview
+
+[Summary of the user workflows derived from the feature specification.]
+
+## Workflows
+
+### WF-1 - [Workflow Title]
+
+- **Actor / Persona**: [Primary user role executing this workflow — e.g. Project Manager]
+- **Goal**: [What the user is trying to accomplish]
+- **Preconditions**: [Initial system state or permissions required]
+
+#### Primary Flow
+
+1. [Step 1: User initiates or accesses interaction]
+2. [Step 2: System presents data or inputs]
+3. [Step 3: User enters parameters or performs action]
+4. [Step 4: System processes and validates]
+5. [Step 5: User views confirmation or resulting state]
+
+#### Alternative Paths & Decision Points
+
+- **If [Condition / Decision A]**: [Alternative interaction path]
+- **If [Condition / Decision B]**: [Cancellation / Exit path without state mutation]
+
+#### Validation & Error Handling
+
+- **If [Validation Rule Fails]**: System blocks progression and displays inline error feedback.
+
+#### State Transitions
+
+- **Initial State**: `[State A]`
+- **Resulting State**: `[State B]`
+
+---
+
+### WF-2 - [Next Workflow Title]
+
+- **Actor / Persona**: [User role]
+- **Goal**: [User goal]
+- **Preconditions**: [Preconditions]
+
+#### Primary Flow
+
+1. [Step 1]
+2. [Step 2]
+
+#### Alternative Paths & Decision Points
+
+- **If [Condition]**: [Flow]
+
+#### State Transitions
+
+- **Initial State**: `[State]`
+- **Resulting State**: `[State]`

package/assets/guardrails/technology/dotnet-webapi/framework-api-map.md

@@ -50,6 +50,50 @@ The auditing interfaces are the ones most often reported missing: they are in a
 package from the aggregate types, so a project that references `AppWeaver.DomainAbstraction`
 alone cannot see `IAggregateChild` at all. A rule that requires one requires its package.
 
+## The other direction — framework types that shadow DOMAIN names
+
+The map above is about a framework type the code cannot find. The opposite failure is a
+framework type it finds *too easily*: a domain noun that the ambient scope already defines.
+
+`Microsoft.NET.Sdk.Web` turns on implicit usings, so `System`, `System.Collections.Generic`,
+`System.IO`, `System.Threading.Tasks`, `Microsoft.AspNetCore.Http` and
+`Microsoft.AspNetCore.Routing` are in scope in **every** file without appearing in any
+`using` line. A domain type sharing a name with one of theirs — `Route`, `Task`, `Activity`,
+`Path`, `File`, `Timer`, `Index`, `Range`, `Version`, `Results`, `Endpoint`, `Environment`,
+`Stream`, `Type`, `Queue`, `Stack` — is then an **ambiguous reference, CS0104**:
+
+```csharp
+using Acme.Clinic.Service.Care.Domain;     // brings in the domain Route
+
+public static Route? Route(string? value)  // CS0104: Care.Domain.Route
+                                           //      vs Microsoft.AspNetCore.Routing.Route
+```
+
+The conflict is invisible in the file. Nothing in it names `Microsoft.AspNetCore.Routing`,
+so the bare name reads as correct and fails only at build.
+
+**The domain name is not the problem and never changes.** It is the ubiquitous language,
+the plan spells it, and the code spells it back verbatim. What changes is how it is
+written at the use site:
+
+```csharp
+public static Domain.Route? Route(string? value) =>
+    string.IsNullOrWhiteSpace(value) ? null : Domain.Route.From(value);
+```
+
+- **Qualify with the type's own enclosing namespace segment** — `Domain.Route` — at every
+  site the type is named: declarations, parameters, return types, generic arguments and
+  `<see cref="…"/>` comments.
+- **Not a `using` alias and not the full namespace path.** One convention, so two features
+  never disambiguate the same name two ways.
+- **Never rename the domain type** to avoid the clash, and never drop the domain type in
+  favour of the framework one.
+
+`/aw-spec-implement` is told which of *this* plan's element names are affected before it
+writes anything — the list comes from the lane's stack profile (`reserved_names` in
+`.appweaver/stack-profiles/<id>.json`), so it is the same answer on every run rather than
+something each pass has to notice for itself.
+
 ## Rules
 
 - **Cite a framework type with its namespace** in plans and generated code, and add the

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "aw-spec-cli",
-  "version": "0.1.21",
+  "version": "0.1.22",
   "description": "AppWeaver Spec-Driven Development CLI - scaffolds projects with vertical slices, DDD, CQRS, and agent skills",
   "type": "module",
   "main": "dist/index.js",