docs(P48): vision gaps + badge system + substrate→engine + CR format + agentic tags

9 requirements implemented across presentation decks and project docs:

1. DX closing slide: added 'Infrastructure as a utility, not a craft' bullet
   to convey the full vision (infrastructure consumed, not maintained;
   platform compounds value over time).
2. PW Problem slide: 'moving a merged change' → 'promoting a change'.
3. PW Problem slide: added 'Red tape' and 'Scalability without increasing
   headcount' bullets (4 frictions, not 2).
4. PW Roadmap slide: redesigned with side-by-side HTML table layout
   (Testing | Planned), 16px font, no overflow.
5. PW deck: added new slide 'What This Platform Is — and Isn't' after North
   Star (sovereign boundary, infrastructure as utility, 4 anti-goals).
   PW deck now 16 slides (was 15).
6. Maturity nomenclature: 'Available today'/'shipped' → 'Testing' across
   both decks + source markdown. New .testing badge (blue/teal #DBEAFE).
   Roadmap title: 'Testing vs. Planned'. The platform has 0 consumer
   adoption — 'shipped' was inaccurate.
7. Global: 'substrate' → 'engine' across entire project (88 matches, 30+
   files including .ciagent/, docs/, modules/, adapters/, schemas/, code).
8. Presentation files only: 'forge' → 'VCS' / 'version control system'
   (6 occurrences in 4 files). 'forge' retained in all technical docs and
   code as the industry-standard term.
9. New .agentic badge (purple/violet #EDE9FE) appended to agentic features
   in both decks: confidence signal, autonomous dev, pattern recognition,
   dynamic module creation, citizen developer surface, auto-promotion.

Also: Change Request ID format changed from 'CR-2026-001' to 'CHG0678912'
across presentation files, consumer guide, and test fixtures.

HTML re-rendered. PPTX rendered for release upload.

---ci---
phase: 48
milestone: v1.9
status: complete
requirements:
  covered: []
  partial: []
---/ci---

modules/STANDARDS.md

@@ -4,7 +4,7 @@ Standards for authoring and reviewing ACDL modules. These standards
 govern the two module tiers — **L1 primitives** (single cloud resource
 or small group of related resources) and **L2 modules** (compositions
 that reference L1 primitives to deploy a complete stack) — and the
-substrate adapter that compiles them to Terraform. They are written for
+engine adapter that compiles them to Terraform. They are written for
 **platform engineers** and **AI agents** that author or review new
 modules against the existing corpus (12 L1 primitives and 2 L2 modules
 shipped in v1.8).
@@ -21,7 +21,7 @@ modules `static-assets` and `microservice`). They exist so that:
 - platform engineers can review a new module against a fixed checklist;
 - AI agents authoring modules produce code that passes review without
   iteration; and
-- the substrate adapter (`adapters/terraform/adapter.py`) can compile a
+- the engine adapter (`adapters/terraform/adapter.py`) can compile a
   module instance with no module-specific code in the adapter beyond the
   three tables in §8.
 
@@ -34,7 +34,7 @@ bump and requires a migration plan.
 
 An L1 primitive is a single cloud resource or a small group of related
 resources (e.g. a VPC with subnets and a route table). It is declared by
-an `interface.json` and realized by the substrate adapter; it does not
+an `interface.json` and realized by the engine adapter; it does not
 own Terraform code.
 
 ### 2.1 Required files
@@ -43,7 +43,7 @@ Every L1 primitive MUST contain, at minimum:
 
 | File | Purpose |
 |------|---------|
-| `interface.json` | Substrate-agnostic declaration: inputs, outputs, NFRs, optional multi-resource graph. |
+| `interface.json` | Angine-agnostic declaration: inputs, outputs, NFRs, optional multi-resource graph. |
 | `instance.json` | A concrete instance used as the adapter regression baseline. |
 | `README.md` | Plain-language documentation following `README-TEMPLATE.md` (see §7). |
 | `examples/simple.yaml` | A minimal contract that uses the primitive with required inputs only. |
@@ -207,7 +207,7 @@ declares intra-refs from the subnet and route table to the VPC's
   - `aws:wafv2:webacl`
   - `aws:rds:instance`
   - `aws:kms:key`, `aws:kms:alias`
-- The substrate adapter's `TYPE_MAP` is the registry of stack types the
+- The engine adapter's `TYPE_MAP` is the registry of stack types the
   adapter can compile (see §8). A new stack type requires a `TYPE_MAP`
   entry before the primitive can be deployed.
 
@@ -363,7 +363,7 @@ accidental teardown of production infrastructure.
 
 1. Every L1 MUST declare a `deletion_protection` NFR (boolean, default
    `true`) in `interface.json`. See §2.5.
-2. When `deletion_protection` is `true`, the substrate adapter emits a
+2. When `deletion_protection` is `true`, the engine adapter emits a
    `lifecycle { prevent_destroy = true }` block on the corresponding
    Terraform resource. A `terraform destroy` against a protected
    resource fails with an error naming the resource.