Current verified state — 2026-09-07
Actual hosted guest generation is recovered on source 18c041f4c795af5281d6c82ef96e75c775acac3b, deployment 34143940332, Worker fe163417-64ed-462a-80c5-a4b8d7cf99f5 at 100%, exact tag verified. CI34143647744 and Docs34143647730 passed; all 467 tests and full local quality passed.
A fresh guest workflow created and saved a synthetic resume, added a manual job description, generated a tailored result in 6.4 seconds, accepted it and restored byte-exact output after reload. Dates, education, employer and the 240/160 ms metric survived; unsupported AWS/Kubernetes skills were not added. This is sample evidence, not a general truthfulness guarantee.
Repairs and cause
The original HTTP 500 was made into a safe expected error value, with sanitized diagnostics and token refunds retained. The guest cover-letter route now resolves local jobs. Its Worker module-load EvalError was fixed by replacing the scraper's module-scope new Function() imports.
The default @cf/meta/llama-3.1-8b-instruct was retired on 2026-05-30 and rejected an isolated one-word request. Source switched to supported Llama 3.3 70B FP8. Full requests initially timed out at 90 seconds; bounding output and edit metadata recovered hosted generation. Source also restores HTML line breaks to Markdown and filters explanation excerpts absent from the output or unchanged from the original. Explicit BYOK remains intact. Variable probe timings do not establish an SDK adapter bug.
Remaining acceptance
Fleet now qualifies the browser-local guest workflow as a shareable experiment, with medium confidence; this does not qualify account sync, imports or the broader application suite. The public keyword checker alone does not qualify the product. No real application, outreach, payment or credential changes were performed. Rollback predecessor for the generation release is Worker 6fa2a6f1-40c2-4914-9bb0-ad9f3efdf5d0 (source 1df7f0bb); pre-exercise rollback remains 4a926a7e-2b63-470f-a56a-73ff745f282a.
The local AI probe server and disposable browser are closed. Current checkout is clean main, synced with origin. The final CSS-only release retains the generation implementation qualified above.
Export repair specification
Why
A guest can generate and save a tailored resume but cannot take that result into a document for an application. The base editor already supports browser Print; preserve that private local-data design.
What and design
Add one browser-local export control to tailored results and the guest editor. Support Print / Save PDF through a standalone print-ready document, plus downloadable Markdown/plain text, HTML and Word-compatible .doc. Preserve signed-in server export. Share a pure Markdown-to-HTML module with the existing renderer; exclude executable raw HTML, unsafe links, external images and CSS injection. No new dependencies, public rendering endpoint, D1 writes or production configuration.
Requirements and scenarios
- WHEN a guest exports the current edited or tailored source, THEN the document SHALL contain that source rather than an older server or saved version.
- WHEN Print / Save PDF is selected, THEN a standalone print-ready document SHALL open using the existing templates, with no app navigation in print output. Browser print must allow PDF saving.
- WHEN HTML, text or Word is selected, THEN a correctly named local download SHALL contain the candidate facts and relevant formatting. Word SHALL be labeled .doc, not DOCX.
- WHEN resume input contains script tags, event handlers, dangerous links, external images or malformed render configuration, THEN exported HTML SHALL not execute or fetch those resources.
- WHEN the browser blocks a print window, THEN the UI SHALL explain recovery without discarding source.
- Existing signed-in ownership checks and server exports SHALL remain intact.
Tasks
Export release verified
Source d28b05a34766aced89c11d138a2d5654c9b568c2 passed all 473 tests/full quality and exact CI34146323861/Docs34146323938. Deployment34146632823 succeeded; Worker faaa3a1f-da95-4009-967c-0f3c3091dda1 at 100%, exact tag confirmed.
A fresh UI-created guest resume and manual job generated in 5.229 seconds; reviewed facts/metrics survived. Save/reload and text download were byte-exact. HTML and Word-compatible .doc downloads succeeded. The actual print popup produced a readable one-page resume and a two-page 8075-character unsaved editor fixture through Chromium's print engine, with all 36 items and final section intact. The saved original remained unchanged. All PDF pages and desktop/mobile controls were visually inspected. Native OS print dialog and Microsoft Word opening were not automated.
An initial disposable Chrome process crashed with macOS display errors; its incomplete post-release pass was discarded. The successful full pass used a fresh browser with GPU disabled. Signed-in automation remains unavailable. Local Turbopack could not decode the existing favicon; Webpack matched production and passed. These limits remain visible; no broader pass or issue closure is claimed.
Current verified state — 2026-09-07
Actual hosted guest generation is recovered on source
18c041f4c795af5281d6c82ef96e75c775acac3b, deployment 34143940332, Workerfe163417-64ed-462a-80c5-a4b8d7cf99f5at 100%, exact tag verified. CI34143647744 and Docs34143647730 passed; all 467 tests and full local quality passed.A fresh guest workflow created and saved a synthetic resume, added a manual job description, generated a tailored result in 6.4 seconds, accepted it and restored byte-exact output after reload. Dates, education, employer and the 240/160 ms metric survived; unsupported AWS/Kubernetes skills were not added. This is sample evidence, not a general truthfulness guarantee.
Repairs and cause
The original HTTP 500 was made into a safe expected error value, with sanitized diagnostics and token refunds retained. The guest cover-letter route now resolves local jobs. Its Worker module-load EvalError was fixed by replacing the scraper's module-scope
new Function()imports.The default
@cf/meta/llama-3.1-8b-instructwas retired on 2026-05-30 and rejected an isolated one-word request. Source switched to supported Llama 3.3 70B FP8. Full requests initially timed out at 90 seconds; bounding output and edit metadata recovered hosted generation. Source also restores HTML line breaks to Markdown and filters explanation excerpts absent from the output or unchanged from the original. Explicit BYOK remains intact. Variable probe timings do not establish an SDK adapter bug.Remaining acceptance
1cf2c875a6e3ffd27dc3ea85884106e92a7a73d0passed CI34144569758/Docs34144569768; deployment 34144865225 succeeded. Workerf5303141-f245-4ad7-aa39-2ae208ea0cb2serves the exact tag at 100%. A fresh 390px reload with no inline override scrolled the diff to its final Skills section; no horizontal overflow or browser errors.985dfd1f11a3c617482c49f05bf59708b9d7fd6bpassed exact main CI34353340640 and deploy34353678503. Worker667026d3-f9c7-4630-a709-cf2f3f0239cfserves that tag at 100%. Real hosted PDF/DOCX imports opened the editor in 9.2/9.1 seconds, preserved sampled dates/metrics and survived reload byte-exactly at 390px. PDF mobile layout was visually inspected with zero page errors. Both outputs added an unnecessary missing-contact placeholder; broader fidelity and account persistence remain open. Full local quality passed 483 tests. Evidence:docs/operations/evidence/resume-hosted-import-2026-09-09.json. Temporary browsers and files cleaned.Fleet now qualifies the browser-local guest workflow as a shareable experiment, with medium confidence; this does not qualify account sync, imports or the broader application suite. The public keyword checker alone does not qualify the product. No real application, outreach, payment or credential changes were performed. Rollback predecessor for the generation release is Worker
6fa2a6f1-40c2-4914-9bb0-ad9f3efdf5d0(source1df7f0bb); pre-exercise rollback remains4a926a7e-2b63-470f-a56a-73ff745f282a.The local AI probe server and disposable browser are closed. Current checkout is clean main, synced with origin. The final CSS-only release retains the generation implementation qualified above.
Export repair specification
Why
A guest can generate and save a tailored resume but cannot take that result into a document for an application. The base editor already supports browser Print; preserve that private local-data design.
What and design
Add one browser-local export control to tailored results and the guest editor. Support Print / Save PDF through a standalone print-ready document, plus downloadable Markdown/plain text, HTML and Word-compatible .doc. Preserve signed-in server export. Share a pure Markdown-to-HTML module with the existing renderer; exclude executable raw HTML, unsafe links, external images and CSS injection. No new dependencies, public rendering endpoint, D1 writes or production configuration.
Requirements and scenarios
Tasks
Export release verified
Source
d28b05a34766aced89c11d138a2d5654c9b568c2passed all 473 tests/full quality and exact CI34146323861/Docs34146323938. Deployment34146632823 succeeded; Workerfaaa3a1f-da95-4009-967c-0f3c3091dda1at 100%, exact tag confirmed.A fresh UI-created guest resume and manual job generated in 5.229 seconds; reviewed facts/metrics survived. Save/reload and text download were byte-exact. HTML and Word-compatible .doc downloads succeeded. The actual print popup produced a readable one-page resume and a two-page 8075-character unsaved editor fixture through Chromium's print engine, with all 36 items and final section intact. The saved original remained unchanged. All PDF pages and desktop/mobile controls were visually inspected. Native OS print dialog and Microsoft Word opening were not automated.
An initial disposable Chrome process crashed with macOS display errors; its incomplete post-release pass was discarded. The successful full pass used a fresh browser with GPU disabled. Signed-in automation remains unavailable. Local Turbopack could not decode the existing favicon; Webpack matched production and passed. These limits remain visible; no broader pass or issue closure is claimed.