-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathdeploy-checklist.yaml
More file actions
81 lines (65 loc) · 2.51 KB
/
Copy pathdeploy-checklist.yaml
File metadata and controls
81 lines (65 loc) · 2.51 KB
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
version: 1
# Post-deploy smoke checks for archonhq.ai.
# Run automatically after `navi-ops release deploy`.
# Run manually: `navi-ops release verify` (prod) or `navi-ops release verify --dev`
#
# Each epic should add its own checks when new routes ship.
checks:
# ── Core pages ────────────────────────────────────────────
- name: "Landing page"
url: /
expect_status: 200
content_contains: "Mission Control"
- name: "Roadmap page"
url: /roadmap
expect_status: 200
content_contains: "Roadmap"
- name: "Insights page"
url: /insights
expect_status: 200
content_contains: "Mission Control Insights"
- name: "Sign-in page"
url: /signin
expect_status: 200
# ── Docs (Fumadocs) ───────────────────────────────────────
- name: "Docs redirect"
url: /docs
expect_status: 307
- name: "Docs introduction"
url: /docs/guides/introduction
expect_status: 200
content_contains: "Mission Control"
- name: "Docs getting started"
url: /docs/guides/getting-started
expect_status: 200
- name: "Docs AI routing"
url: /docs/features/ai-routing
expect_status: 200
# ── SEO assets ───────────────────────────────────────────
- name: "Sitemap"
url: /sitemap.xml
expect_status: 200
content_contains: "<loc>"
- name: "Robots.txt"
url: /robots.txt
expect_status: 200
content_contains: "User-Agent"
- name: "OG image"
url: /opengraph-image
expect_status: 200
# ── API auth gates ────────────────────────────────────────
- name: "Tasks API (401 expected)"
url: /api/tasks
expect_status: 401
- name: "Events API (401 expected)"
url: /api/events
expect_status: 401
- name: "Gateway proxy (401 expected)"
url: /api/gateway
expect_status: 401
# ── AiPipe ───────────────────────────────────────────────
# 401 = route exists + auth middleware active (proxy to AiPipe is wired up).
# For a full AiPipe liveness check, use: curl http://127.0.0.1:8082/healthz from the host.
- name: "AiPipe proxy route (401 expected)"
url: /api/aipipe/health
expect_status: 401