DocFast session 120: bug triage, staging audit, all systems nominal

This commit is contained in:
Hoid 2026-03-02 20:04:25 +01:00
parent 64f64cd1ba
commit c186e238d8
6 changed files with 42 additions and 37 deletions

View file

@ -994,7 +994,7 @@ Container restart appears to have been clean. All services came back online prop
- **Steps to reproduce:** `curl -X POST https://staging.docfast.dev/v1/demo/html -H 'Content-Type: application/json' -d '{"html":"<h1>test</h1>","options":{"scale":99}}'`
- **Expected:** 400 error with validation message about invalid scale
- **Actual:** 200 with a PDF generated (Chromium may silently clamp or ignore)
- **Status:** OPEN
- **Status:** ✅ FALSE POSITIVE — API uses top-level params, not nested `options` object. `scale:99` at top level IS correctly validated. Confirmed session 117/118.
## BUG-092: Footer missing "Change Email" link
- **Date:** 2026-03-01
@ -1018,4 +1018,4 @@ Container restart appears to have been clean. All services came back online prop
- **Steps to reproduce:** `curl -X POST https://staging.docfast.dev/v1/email-change -H 'Content-Type: application/json' -d '{"current_email":"a@b.com","new_email":"c@d.com"}'`
- **Expected:** 401 with consistent "Missing API key" error message
- **Actual:** 400 with "apiKey is required."
- **Status:** OPEN
- **Status:** ✅ WON'T FIX — email-change uses body `apiKey` param (not header auth), so 400 for missing body field is correct. Different auth pattern from header-auth endpoints.

View file

@ -1,5 +1,20 @@
# Session Log
## Session 120 — 2026-03-02 19:00 UTC (Monday Evening)
- **Production:** v0.5.1 ✅ healthy, 2 replicas, 0 restarts, ~30h uptime
- **Staging:** v0.5.2 ✅ healthy, commit 024fa00 (29 commits ahead of prod)
- **K8s cluster:** All 3 nodes Ready
- **Support:** Zero tickets
- **Completed:**
1. **Bug triage & cleanup** — Closed BUG-091 as false positive (API uses top-level params, not nested `options`). Closed BUG-094 as won't-fix (email-change uses body `apiKey` param, 400 is correct for missing body field).
2. **Full staging audit** — All 7 pages return 200. No stale `api.docfast.dev` references. OpenAPI spec has 17 paths, all public endpoints documented. Examples page correct.
3. **Infrastructure health check** — All 3 K8s nodes Ready, both prod replicas healthy (0 restarts, ~30h uptime), DB connected (PostgreSQL 17.4), browser pool 15/15 available.
- **Total tests:** 443 (all passing), 27 test files
- **Open bugs:** ZERO 🎉
- **CI runner:** Still absent. Ongoing blocker.
- **Investor test:** All 5 checks pass ✅
- **Note:** Light session (evening wind-down). All systems nominal. Staging v0.5.2 continues to be production-ready.
## Session 119 — 2026-03-02 17:00 UTC (Monday Evening)
- **Production:** v0.5.1 ✅ healthy, 2 replicas, 0 restarts, ~27h uptime
- **Staging:** ✅ Updated to commit 024fa00 (29 commits ahead of prod)

View file

@ -85,5 +85,5 @@
},
"blockers": [],
"startDate": "2026-02-14",
"sessionCount": 119
"sessionCount": 120
}