aw-spec-cli 0.1.2 → 0.1.3

package/assets/docs/components/QrGenerator/integration.md

@@ -10,8 +10,12 @@
 ## Agent workflow — execute in order
 
 1. **Load context.** Read [README.md](./README.md) and this file.
-2. **Locate target projects** (see [[folder-structure]]): `…Application` (injects `IQRGenerator`),
-   `…Infrastructure` (does the registration), `…Service` (API endpoints).
+2. **Resolve the host project** `<HostProject>` (see [[folder-structure]], [[components-readme]] R0.2):
+   the single startup project that owns **`Program.cs`** + the ASP.NET Core web SDK —
+   `<SampleProjectName>.Service` (Vertical Slice foundation), `<SampleProjectName>.API` (Modular
+   Monolith foundation), or another name in a future template. **Find it by locating `Program.cs`, not
+   by assuming the name.** There is **no** separate `…Application` / `…Infrastructure` project in these
+   foundations; `<HostProject>` is the target for C1–C3 below and holds the API endpoints.
 3. **Present the implementation catalog (below) as a selection list and ASK the user which
    implementation(s) to integrate.** Use a multi-select prompt (`AskUserQuestion`,
    `multiSelect: true`) for consistency with the other components.
@@ -21,7 +25,10 @@
 5. **For each selected implementation, apply its block** (§Implementation blocks).
 6. **Set the provider:** `configureOptions: options => options.Provider = "<selected key>"`.
 7. **(Optional) Build the feature slice** (§Usage) — DTO + Command + Handler + Endpoint.
-8. **Verify** (§Verification) and report what was added.
+8. **Offer the bundled sample endpoint (ASK).** After the wiring above, ask the user (single-select
+   yes/no via `AskUserQuestion`) whether to add the ready-made sample endpoint. If **yes**, copy it
+   into the host project — see §Sample reference endpoint. If **no**, skip silently.
+9. **Verify** (§Verification) and report what was added.
 
 > **Guardrail — namespace casing.** Package IDs use `QrGenerator` (lower `r`); **namespaces/types
 > use `QRGenerator` (upper `R`)**. `using AppWeaver.QRGenerator;` is correct — getting this wrong is
@@ -53,8 +60,8 @@
 
 ### C2 — Project references (no `Version=`)
 
-**File:** `src/<SampleProjectName>.Application/<SampleProjectName>.Application.csproj`
-**File:** `src/<SampleProjectName>.Infrastructure/<SampleProjectName>.Infrastructure.csproj`
+**File:** `src/<HostProject>/<HostProject>.csproj` (the host project resolved in step 2 — single
+project, no separate Application/Infrastructure).
 
 ```xml
 <ItemGroup>
@@ -65,7 +72,10 @@
 
 ### C3 — Registration scaffold
 
-**File:** `src/<SampleProjectName>.Infrastructure/Extensions/InfrastructureServiceRegistration.cs`
+**File:** the host project `<HostProject>` (step 2) — register in its
+`Extensions/InfrastructureServiceRegistration.cs` (`AddInfrastructure`) when that file exists (it does
+in the Vertical Slice / Modular Monolith foundations), otherwise directly in `Program.cs` **before**
+`builder.Build()`.
 
 ```csharp
 using AppWeaver.QRGenerator.Extensions;   // AddQRGenerator  (capital R)
@@ -78,6 +88,12 @@ services.AddQRGenerator(
     configureOptions: options => options.Provider = "<selected key>");   // step 6
 ```
 
+> **Dual local/Aspire startup ([[components-readme]] R0.2a).** If the host project also has an
+> `AddAspireInfrastructure` method (`Extensions/AspireInfrastructureExtensions.cs`) selected by
+> `if (isAspire) … else …` in `Program.cs`, add this **same** `AddQRGenerator(...)` block to **both**
+> `AddInfrastructure` and `AddAspireInfrastructure` (it is DB-agnostic — identical in both), or
+> `IQRGenerator` is unresolvable when the app runs under Aspire.
+
 No `appsettings.json` entry is required — there is nothing to configure.
 
 ---
@@ -169,6 +185,32 @@ public class GenerateQrRequest { public string Content { get; set; } = string.Em
 
 ---
 
+## Sample reference endpoint
+
+The §Usage slice above routes through a command + handler. For a quick, self-contained sample there
+is also a ready-to-run FastEndpoint bundled in this component folder at
+[`ReferenceEndpoints/GenerateQrEndpoint.cs`](./ReferenceEndpoints/GenerateQrEndpoint.cs). It injects
+`IQRGenerator` directly and does the **full sequence inline** — no command/handler/mediator. It is
+**not** wired automatically; it is offered in workflow step 8.
+
+**When the user opts in (step 8) — copy procedure:**
+
+1. Confirm `docs/components/QrGenerator/ReferenceEndpoints/GenerateQrEndpoint.cs` exists. If it is
+   missing, tell the user and skip (do not hand-write a replacement).
+2. Create `src/<HostProject>/ReferenceEndpoints/` if it does not exist (`<HostProject>` = the project
+   resolved in step 2).
+3. Copy the file to `src/<HostProject>/ReferenceEndpoints/GenerateQrEndpoint.cs`, replacing the
+   namespace token `__HOSTPROJECT__` with `<HostProject>`'s root namespace (e.g.
+   `AppWeaver.Health.Service`). Keep the `using AppWeaver.QRGenerator;` (capital R) — do not "fix" it
+   to match the package id. Change nothing else.
+4. Do **not** touch the C1–C3 wiring. FastEndpoints auto-discovers the endpoint by assembly scan, so
+   no extra registration is required.
+
+**Endpoint:** `POST /reference/qr-codes` — body `{ "content" }` — returns an `image/png` body.
+An empty `content` string is valid (returns a small PNG); `null` is rejected with 400.
+
+---
+
 ## Verification
 
 1. **Builds** — `dotnet build` succeeds; `using` directives use `AppWeaver.QRGenerator…`; no
@@ -178,6 +220,9 @@ public class GenerateQrRequest { public string Content { get; set; } = string.Em
 4. **Generates** — `GenerateQR("test")` returns a non-empty `byte[]`; `POST /qr-codes` returns an
    `image/png` body that opens as a scannable QR image. (`null` content throws; empty string is
    valid and returns a PNG.)
+5. **Sample endpoint (only if copied in step 8)** — the build still succeeds with
+   `ReferenceEndpoints/GenerateQrEndpoint.cs` added, the `__HOSTPROJECT__` token was replaced, and
+   `POST /reference/qr-codes` returns an `image/png`.
 
 ## Related
 

package/assets/docs/components/README.md

@@ -42,8 +42,25 @@ Every folder contains two independent, agent-readable files:
 
 - **R0.1** — NuGet versions live in `Directory.Packages.props` only (`<PackageVersion>`); project
   files reference the package **without** a `Version=` attribute (see [[dependency-policy]]).
-- **R0.2** — Register the component in the **Infrastructure** registration extension, never in a
-  feature slice or domain code (see [[clean-architecture]]).
+- **R0.2** — Register the component in the **startup/host project** — the one project that owns
+  `Program.cs` + the ASP.NET Core web SDK. Its name is template-dependent: `<App>.Service` (Vertical
+  Slice foundation), `<App>.API` (Modular Monolith foundation), and possibly other names as templates
+  are added — so **resolve it by locating `Program.cs`, never by assuming a fixed project name**.
+  These foundations have **no** separate `…Application` / `…Infrastructure` project. Put the
+  `AddXxx(...)` registration in that project's `Extensions/InfrastructureServiceRegistration.cs`
+  (`AddInfrastructure`) when that extension exists, otherwise directly in `Program.cs` before
+  `builder.Build()`. Never register in a feature slice or domain code (see [[clean-architecture]]).
+- **R0.2a** — *(dual local/Aspire startup)* Some foundations split infrastructure registration across
+  **two** methods that `Program.cs` selects at runtime — `if (isAspire) AddAspireInfrastructure(...)`
+  (the Aspire path: `Extensions/AspireInfrastructureExtensions.cs`, typically PostgreSQL + Redis)
+  `else AddInfrastructure(...)` (the local/dev path:
+  `Extensions/InfrastructureServiceRegistration.cs`, typically SQLite + in-memory cache). When
+  **both** methods exist, add the component registration to **both**, or the abstraction is
+  unresolvable in whichever run mode you skipped (e.g. `IEmailService` throws at runtime under
+  Aspire). The registration block is **identical** in both — copy it verbatim — *except*
+  provider-specific calls (connection strings, `UseSqlite(...)` vs `UseNpgsql(...)`, cache provider),
+  which must match each method's existing provider. If only `AddInfrastructure` (or only `Program.cs`)
+  exists, register once as in R0.2.
 - **R0.3** — Inject the **abstraction** (`IEmailService`, `IQRGenerator`, `IJobScheduler`) into
   handlers — never the concrete provider type (see [[cqrs]]).
 - **R0.4** — Always set `options.Provider = "<Key>"` explicitly. Do not rely on the implicit

package/assets/docs/domainspecs/healthcare/comandrulemap.md

@@ -104,6 +104,51 @@ domain-specific ones to load **in addition** for a healthcare project.
 - docs/domainspecs/healthcare/api-versioning.domain.md
 - docs/domainspecs/healthcare/ai-rules.domain.md
 
+## /aw-spec-fast-implement
+
+> Fast path that collapses plan + tasks + analyze + implement into one pass. This list is the
+> **deduplicated union** of those four commands' headings above (here, equal to `/aw-spec-plan`).
+> Load it **once** for the whole pass — do not reload per phase.
+
+- docs/domainspecs/healthcare/folder-structure.domain.md
+- docs/domainspecs/healthcare/cqrs.domain.md
+- docs/domainspecs/healthcare/vertical-slices.domain.md
+- docs/domainspecs/healthcare/persistence.domain.md
+- docs/domainspecs/healthcare/testing.domain.md
+- docs/domainspecs/healthcare/eventing.domain.md
+- docs/domainspecs/healthcare/domain-driven-design.domain.md
+- docs/domainspecs/healthcare/fhir.md
+- docs/domainspecs/healthcare/hl7.md
+- docs/domainspecs/healthcare/dicom.md
+- docs/domainspecs/healthcare/terminology.md
+- docs/domainspecs/healthcare/hipaa.md
+- docs/domainspecs/healthcare/consent.md
+- docs/domainspecs/healthcare/zero-trust.domain.md
+- docs/domainspecs/healthcare/authorization.domain.md
+- docs/domainspecs/healthcare/auditing.domain.md
+- docs/domainspecs/healthcare/data-classification.domain.md
+- docs/domainspecs/healthcare/coding-standards.domain.md
+- docs/domainspecs/healthcare/dependency-policy.domain.md
+- docs/domainspecs/healthcare/api-versioning.domain.md
+- docs/domainspecs/healthcare/ai-rules.domain.md
+
+## /aw-spec-minimal-implementation
+
+> Single-step set for healthcare — the **per-domain knob** (edit freely). `/aw-spec-minimal-implementation`
+> loads these to interpret and implement the requirement in one pass; genuinely-external runtime
+> services (terminology server, FHIR endpoint) are stubbed behind ports. For an audited build use
+> `## /aw-spec-fast-implement`.
+
+- docs/domainspecs/healthcare/clinical-terms.md
+- docs/domainspecs/healthcare/domain-driven-design.domain.md
+- docs/domainspecs/healthcare/folder-structure.domain.md
+- docs/domainspecs/healthcare/vertical-slices.domain.md
+- docs/domainspecs/healthcare/fhir.md
+- docs/domainspecs/healthcare/hl7.md
+- docs/domainspecs/healthcare/terminology.md
+- docs/domainspecs/healthcare/hipaa.md
+- docs/domainspecs/healthcare/ai-rules.domain.md
+
 ---
 
 ## Quick reference (command → file count)
@@ -117,3 +162,5 @@ domain-specific ones to load **in addition** for a healthcare project.
 | /aw-spec-tasks | 13 |
 | /aw-spec-analyze | 5 |
 | /aw-spec-implement | 20 |
+| /aw-spec-fast-implement | 21 |
+| /aw-spec-minimal-implementation | 9 |

package/assets/docs/domainspecs/pharma/comandrulemap.md

@@ -121,6 +121,54 @@ domain-specific ones to load **in addition** for a medicinal-product-registratio
 - docs/domainspecs/pharma/api-versioning.domain.md
 - docs/domainspecs/pharma/ai-rules.domain.md
 
+## /aw-spec-fast-implement
+
+> Fast path that collapses plan + tasks + analyze + implement into one pass. This list is the
+> **deduplicated union** of those four commands' headings above (here, equal to `/aw-spec-plan`).
+> Load it **once** for the whole pass — do not reload per phase.
+
+- docs/domainspecs/pharma/folder-structure.domain.md
+- docs/domainspecs/pharma/cqrs.domain.md
+- docs/domainspecs/pharma/vertical-slices.domain.md
+- docs/domainspecs/pharma/persistence.domain.md
+- docs/domainspecs/pharma/testing.domain.md
+- docs/domainspecs/pharma/eventing.domain.md
+- docs/domainspecs/pharma/domain-driven-design.domain.md
+- docs/domainspecs/pharma/product-lifecycle.domain.md
+- docs/domainspecs/pharma/ndc.md
+- docs/domainspecs/pharma/idmp.md
+- docs/domainspecs/pharma/fhir.md
+- docs/domainspecs/pharma/hl7.md
+- docs/domainspecs/pharma/terminology.md
+- docs/domainspecs/pharma/atc.md
+- docs/domainspecs/pharma/regulatory-compliance.md
+- docs/domainspecs/pharma/data-provenance.md
+- docs/domainspecs/pharma/zero-trust.domain.md
+- docs/domainspecs/pharma/authorization.domain.md
+- docs/domainspecs/pharma/auditing.domain.md
+- docs/domainspecs/pharma/data-classification.domain.md
+- docs/domainspecs/pharma/coding-standards.domain.md
+- docs/domainspecs/pharma/dependency-policy.domain.md
+- docs/domainspecs/pharma/api-versioning.domain.md
+- docs/domainspecs/pharma/ai-rules.domain.md
+
+## /aw-spec-minimal-implementation
+
+> Single-step set for pharma — the **per-domain knob** (edit freely). `/aw-spec-minimal-implementation`
+> loads these to interpret and implement the requirement in one pass; genuinely-external runtime
+> services (terminology server, FHIR endpoint) are stubbed behind ports. For an audited build use
+> `## /aw-spec-fast-implement`.
+
+- docs/domainspecs/pharma/pharma-terms.md
+- docs/domainspecs/pharma/domain-driven-design.domain.md
+- docs/domainspecs/pharma/folder-structure.domain.md
+- docs/domainspecs/pharma/cqrs.domain.md
+- docs/domainspecs/pharma/vertical-slices.domain.md
+- docs/domainspecs/pharma/product-lifecycle.domain.md
+- docs/domainspecs/pharma/ndc.md
+- docs/domainspecs/pharma/idmp.md
+- docs/domainspecs/pharma/atc.md
+
 ---
 
 ## Quick reference (command → file count)
@@ -134,3 +182,5 @@ domain-specific ones to load **in addition** for a medicinal-product-registratio
 | /aw-spec-tasks | 15 |
 | /aw-spec-analyze | 7 |
 | /aw-spec-implement | 24 |
+| /aw-spec-fast-implement | 24 |
+| /aw-spec-minimal-implementation | 9 |

package/package.json

@@ -1,11 +1,14 @@
 {
   "name": "aw-spec-cli",
-  "version": "0.1.2",
+  "version": "0.1.3",
   "description": "AppWeaver Spec-Driven Development CLI - scaffolds projects with vertical slices, DDD, CQRS, and agent skills",
   "type": "module",
   "main": "dist/index.js",
+  "exports": {
+    ".": "./dist/index.js"
+  },
   "bin": {
-    "aw-spec": "dist/index.js"
+    "aw-spec": "./dist/index.js"
   },
   "files": [
     "dist",