Update prompts

Author: GedMarc

GLOSSARY.md

@@ -3,6 +3,7 @@
 Use this file as the host index; topic glossaries override root definitions. Follow Glossary Precedence Policy: topic glossaries > root terms; duplicate only enforced prompt-language mappings.
 
 ## Topic Glossaries
+- JWebMP Typescript Client (canonical): `rules/generative/frontend/jwebmp/typescript/GLOSSARY.md`
 - Enterprise base: `rules/GLOSSARY.md`
 - Java 25/Maven: `rules/generative/language/java/java-25.rules.md`
 - TypeScript/Angular: `rules/generative/language/typescript/GLOSSARY.md`, `rules/generative/language/angular/GLOSSARY.md`, override: `rules/generative/language/angular/angular-20.rules.md`

PROMPT_ADOPT_EXISTING_PROJECT.md

@@ -171,7 +171,7 @@ Fill before running.
     - Angular (choose exactly one)
       - [ ] Angular 17
       - [ ] Angular 19
-      - [X] Angular 20
+      - [ ] Angular 20
     - Other frameworks
       - [ ] React
         - [ ] Next.js

PROMPT_LIBRARY_RULES_UPDATE.md

@@ -157,7 +157,7 @@ Fill before running.
   - Angular (choose exactly one)
     - [ ] Angular 17
     - [ ] Angular 19
-    - [x] Angular 20
+    - [ ] Angular 20
   - Other frameworks
     - [ ] React
       - [ ] Next.js

README.md

@@ -10,6 +10,16 @@ A Maven Java 25 library that exposes Ng* annotations and helpers so JWebMP compo
 - Architecture diagrams: `docs/architecture/README.md`
 - Prompt reference for future runs: `docs/PROMPT_REFERENCE.md`
 
+## How to use these rules
+- Library rules index: `rules/generative/frontend/jwebmp/typescript/README.md` (annotations, scanning/runtime, configuration/rendering, testing, CI/release).
+- Follow stage gates: Stage 1–3 are documentation; Stage 4 (implementation) is allowed because blanket approval is recorded in `PACT.md`.
+- Keep host docs outside `rules/`; reference diagrams under `docs/architecture/` and topic glossary under `rules/generative/frontend/jwebmp/typescript/GLOSSARY.md`.
+- Generated TypeScript is read-only; change Java annotations/configuration and rerun the generator instead of editing outputs.
+
+## Prompt language alignment & glossary
+- Canonical topic glossary: `rules/generative/frontend/jwebmp/typescript/GLOSSARY.md` (Ng* metadata, CRTP fluency, LLM guidance).
+- Root glossary router: `GLOSSARY.md` links to enterprise glossaries (`rules/`) and the topic glossary above. Host projects should copy only enforced prompt-language mappings and link back for everything else.
+
 ## Rules Repository
 - The enterprise rules live in the `rules/` submodule (`.gitmodules` already configured). Keep host project docs outside that directory.
 - Follow behavioral/technical/forward-only/modularity guidance from `rules/RULES.md` plus stack-specific rule links in `RULES.md`.

docs/PROMPT_REFERENCE.md

@@ -22,9 +22,11 @@ Load this file before future AI runs. It captures selected stacks, glossary rout
 - Context: `docs/architecture/c4-context.md`
 - Container: `docs/architecture/c4-container.md`
 - Component (Angular metadata pipeline): `docs/architecture/c4-component-angular-metadata.md`
+- Dependency map: `rules/generative/frontend/jwebmp/typescript/dependency-map.md`
 - Sequences: `docs/architecture/sequence-startup-scan.md`, `docs/architecture/sequence-component-config.md`
 - ERD: `docs/architecture/erd-angular-metadata.md`
 
 ## Policies
 - Forward-only; documentation-first stage gates recorded (blanket approval active for this run).
 - Host docs stay outside `rules/` submodule.
+- Glossary composition (topic-first): root `GLOSSARY.md` links to topic glossaries; library topic glossary lives at `rules/generative/frontend/jwebmp/typescript/GLOSSARY.md` and should remain canonical for Ng* metadata terms and LLM alignment.

docs/architecture/README.md

@@ -8,7 +8,11 @@ All diagrams are text-first (Mermaid) and map to observed code in this repositor
 - Sequence — startup scan: `docs/architecture/sequence-startup-scan.md`
 - Sequence — component config build: `docs/architecture/sequence-component-config.md`
 - ERD — annotation to configuration: `docs/architecture/erd-angular-metadata.md`
+- Dependency map (trusted boundaries and external stacks): `rules/generative/frontend/jwebmp/typescript/dependency-map.md`
 
-Trust boundary (observed): Host app inputs (annotated components) cross into this library’s scan/render pipeline; Guice/Vert.x execution is trusted infrastructure; generated TypeScript is consumed by downstream builds and should not execute unvalidated runtime inputs.
+Trust boundary (observed)
+- Inputs: annotated host classes. Processing happens inside trusted library/Guice/Vert.x workers using ClassGraph.
+- Outputs: generated TypeScript is a build artifact for the Angular toolchain; do not treat it as runtime input.
+- Logging: Log4j2 inside the library; no external network calls are present.
 
 These diagrams are referenced by PACT/GLOSSARY/RULES/GUIDES/IMPLEMENTATION for traceability.