DocFast session 115: QA audit + template tests + state update

projects/business/memory/bugs.md

@@ -1,3 +1,10 @@
+## BUG-092: Footer missing "Change Email" link on landing page
+- **Date:** 2026-03-01
+- **Severity:** LOW
+- **Issue:** The email change modal exists in the DOM but the footer has no link to trigger it. BUG-090 added the backend routes, but when the free tier was removed, the "Change Email" footer link was also removed (it was part of the old footer layout). Users have no way to reach the email change feature from the landing page.
+- **Fix:** Add "Change Email" link back to footer with `class="open-email-change"`.
+- **Status:** OPEN
+
 ## BUG-090: Email Change modal calls non-existent backend routes — feature broken
 - **Date:** 2026-02-27
 - **Severity:** HIGH
@@ -948,3 +955,36 @@ Container restart appears to have been clean. All services came back online prop
 - **Issue:** Go example says `go get github.com/docfast/docfast-go` (404 on GitHub). PHP example says `composer require docfast/docfast-php` (doesn't exist on Packagist). SDKs haven't been published yet — blocked on npm/PyPI/Go/Packagist tokens.
 - **Fix:** Either publish SDKs or change examples to use plain HTTP (curl/fetch) without SDK install instructions until packages are published.
 - **Status:** ✅ FIXED (commit 1c0c8a3) — replaced with "SDK coming soon" notes, kept HTTP examples
+
+## BUG-091: Demo endpoint accepts invalid scale value (scale:99) without error
+- **Date:** 2026-03-01
+- **Severity:** MEDIUM
+- **Issue:** `POST /v1/demo/html` with `{"html":"<h1>test</h1>","options":{"scale":99}}` returns HTTP 200 and generates a PDF instead of returning 400 validation error. Chromium's valid scale range is 0.1–2.0. Scale of 99 should be rejected.
+- **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
+
+## BUG-092: Footer missing "Change Email" link
+- **Date:** 2026-03-01
+- **Severity:** LOW
+- **Issue:** The task spec expects a "Change Email" link in the footer, but it's not present. The change email modal (`emailChangeModal`) exists in the DOM but there's no footer link to trigger it. Users have no discoverable way to access the email change feature from the landing page.
+- **Steps to reproduce:** Visit https://staging.docfast.dev/ → scroll to footer → no "Change Email" link
+- **Expected:** Footer should include a "Change Email" link
+- **Actual:** Footer has: Home, Docs, Examples, API Status, Support, Impressum, Privacy Policy, Terms of Service — no Change Email
+- **Status:** OPEN
+
+## BUG-093: Signup modal removed but "Get Pro API Key" button text is misleading
+- **Date:** 2026-03-01
+- **Severity:** LOW
+- **Issue:** Free signup was discontinued (API returns 410). The signup modal (`signupModal`) has been removed from the DOM. However, the "Get Pro API Key — €9/mo" button now redirects directly to Stripe checkout, which is correct behavior. Not a bug per se, but the old "signup modal" test case is no longer applicable — documenting for awareness.
+- **Status:** NOT A BUG — by design after free tier removal
+
+## BUG-094: email-change endpoint returns unhelpful error without auth
+- **Date:** 2026-03-01
+- **Severity:** LOW
+- **Issue:** `POST /v1/email-change` without authentication returns `{"error":"apiKey is required."}` with HTTP 400. Should return 401 for consistency with other auth-required endpoints (`/v1/convert/html` and `/v1/usage` return 401).
+- **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