openclawd/config
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

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

Browse source
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
Download patch file Download diff file Expand all files Collapse all files

4
projects/business/memory/bugs.md
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.