@mesh-tech/mesh-cli 0.34.0 → 0.34.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/README.md CHANGED
@@ -92,8 +92,9 @@ It writes a tenant **platform** repo (the core + platform Pulumi layers on
92
92
  `@mesh-tech/infra-components`) that deploys with `mesh deploy` unmodified, asks
93
93
  for the per-install values, offers to create the Pulumi state bucket, and prints
94
94
  the deploy sequence — including the one manual step in the middle: **delegating
95
- the NS records** of the new public zone, without which the deploy stalls on its
96
- ACM certificate.
95
+ the NS records** of the new public zone. The deploy stops at the mesh-gateway
96
+ Ingress until ACM issues the wildcard certificate, which it does on its own once
97
+ that delegation resolves.
97
98
 
98
99
  The platform layer builds service images with Docker by default, so it needs a
99
100
  working Docker daemon; the core layer does not. On a machine without Docker (a
@@ -19,7 +19,7 @@ const INTENT_COMMAND_PATTERN = /(?:^|&&|\|\||;|\|)\s*((?:bunx\s+@tanstack\/inten
19
19
 
20
20
  // LOCAL HARDENING: this file started as `intent install` output, but it
21
21
  // is committed and CLI-managed — `mesh skills sync` (and `mesh init app-tenant --fix`)
22
- // overwrite it from the mesh-cli asset (libs/mesh-cli/assets/intent/intent-claude-gate.mjs
22
+ // overwrite it from the mesh-cli asset (packages/mesh-cli/assets/intent/intent-claude-gate.mjs
23
23
  // in mesh-platform). Never fix one copy without the other; in mesh-platform,
24
24
  // scripts/check-intent-hook-sync.mjs fails CI when they diverge. The gate
25
25
  // deliberately fails OPEN — it must never block a session or an edit on a bug in