unoverse 0.1.144 → 0.1.145

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.
@@ -212,7 +212,11 @@
212
212
  echo "HTTP $RESULT"
213
213
  [ "$RESULT" -ge 200 ] && [ "$RESULT" -lt 500 ]
214
214
  loop:
215
- - { name: "Canvas", sub: "", path: "/" }
215
+ # canvas.<domain>, NEVER the bare apex. Neither ground creates an apex record
216
+ # (aws/main.tf and digitalocean/main.tf publish api.<domain> and canvas.<domain>
217
+ # only), so `sub: ""` asked for a hostname that has no DNS at all and reported
218
+ # HTTP 000 FAILED on every healthy deploy.
219
+ - { name: "Canvas", sub: "canvas.", path: "/" }
216
220
  - { name: "API Server", sub: "api.", path: "/health" }
217
221
  register: domain_checks
218
222
  ignore_errors: yes
@@ -963,7 +963,11 @@ EOF
963
963
  # Embed doorway is served AND compressed (identity-encoded JS was a live outage).
964
964
  _smoke "embed.js gzipped" sh -c "curl -sf -m 10 -H 'accept-encoding: gzip' -D - '$smoke_api/embed.js' -o /dev/null | grep -qi '^content-encoding: gzip'"
965
965
  # MCP lane accepts an initialize (every external connector dies here first).
966
- _smoke "MCP initialize" sh -c "curl -sf -m 10 -X POST '$smoke_api/mcp' -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2025-06-18\",\"capabilities\":{},\"clientInfo\":{\"name\":\"smoke\",\"version\":\"0\"}}}' -o /dev/null"
966
+ # 200 (auth off) or 401 (auth on) prove the lane is ALIVE, the same judgement the
967
+ # database canary below makes. This used `curl -sf`, which fails on any error status,
968
+ # so a universe that boots "JWT enforced on /mcp" — every Cognito/AWS deployment —
969
+ # reported FAIL on a correctly protected endpoint and turned a healthy deploy red.
970
+ _smoke "MCP initialize" sh -c "code=\$(curl -s -m 10 -o /dev/null -w '%{http_code}' -X POST '$smoke_api/mcp' -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{\"jsonrpc\":\"2.0\",\"id\":1,\"method\":\"initialize\",\"params\":{\"protocolVersion\":\"2025-06-18\",\"capabilities\":{},\"clientInfo\":{\"name\":\"smoke\",\"version\":\"0\"}}}'); [ \"\$code\" = 200 ] || [ \"\$code\" = 401 ]"
967
971
  # Engine → Postgres canary: 200 (auth off) or 401 (auth on) prove the chain; a 500
968
972
  # is the DB-unreachable incident that hides behind an otherwise healthy stack.
969
973
  _smoke "engine reaches database" sh -c "code=\$(curl -s -m 10 -o /dev/null -w '%{http_code}' '$smoke_api/marketplace'); [ \"\$code\" = 200 ] || [ \"\$code\" = 401 ]"
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "unoverse",
3
- "version": "0.1.144",
3
+ "version": "0.1.145",
4
4
  "description": "The Unoverse front door — create a Studio project, a universe, or a client app, and launch Studio.",
5
5
  "license": "SEE LICENSE IN README.md",
6
6
  "type": "module",