cesnimda
8.3 KiB
30 October2026 — final owner visual approval and development-entry review. PDF/UI appearance is owner-approved for development; metric36/36 per platform retained. Pre-Phase10 preparation conditionally closed. FINAL_DEVELOPMENT_ENTRY.md identifies only the remaining adapter, signed scope/baseline policy and protected activation barriers. Physical printing/device/AT remain unperformed; production NO-GO. Fresh public status confirms a configured owner key and matching real-key qualification, superseding earlier missing-key claims. No Phase10 execution occurred.
30 October 2026 — metric-only owner approval recorded. See S01_APPROVAL.md. Revised S01 now passes36/36 per platform under the approved same2mm vertical baseline metric; original28/20 failures remain unchanged. Human PDF spacing remains PARTIAL; Phase10 and production NO-GO. This supersedes only the metric-pending statements below.
P10-ENTRY-FINAL addendum — 30 October 2026 (Europe/Paris). The revised-name clipping correction is application commit154a9e8; the current source-bound candidate is in ACCEPTANCE.json/ENTRY_PROPOSAL.json. Read the complete current report, native PDF guide and owner actions. Original S01 failures28Windows/20Linux remain FAIL pending explicit metric disposition; actual accent clipping is fixed on the finite corpus. Phase10 and production NO-GO; automatic execution false. No deletion scope, protected approval, model qualification or controller activation is supplied.
Current native evidence reruns1448backend/1031frontend,51affected Windows browser(2+49, exact membership), separate import8/MariaDB90+3/RD216/PDF admission1/Linux8, offline83+realDocling14, baseline math5, TypeScript/lint/build and both-platform PDF checks. The preceding380ordinary/53specialized/browser/helper/runtime/model totals below describe the historical accepted26d531c snapshot, not fresh current executions. The19combined handoff tests replace overlapping bootstrap7/old18. Current report/process/source binding is authoritative; original historical bytes remain in Git26d531c.
Prioritised owner acceptance
All human rows are NOT TESTED until the owner supplies actual evidence through the protected approval mechanism. Do not commit approval tokens/signatures or personal CVs. Use fictional data and http://jobbjakt.local; admin scenarios require an existing Admin account, AI scenarios require consent/entitlement and the workflow's existing CV-text precondition. For revised spacing, use a new CV or explicitly Apply the updated design v2; historical v1 designs remain unchanged. Capture date, exact source/image, device/OS/browser/assistive technology, steps, result and synthetic-only screenshot/PDF where appropriate. Never include passwords, cookies or personal documents.
| ID / priority | Workflow and preconditions | Steps and expected pass criterion | Evidence and gate |
|---|---|---|---|
| HUMAN-01 / P0 | CV Builder; blank and seeded fictional Career Profile | Create Blank: no inherited name/contact/photo/summary/job/empty headings. Choose From Career Profile and select sections explicitly; save, refresh and verify only selected facts. Reorder, Undo/Redo, type with native undo, switch documents. Pass if no cross-document or unintended inherited facts and saved content survives refresh | Screen recording plus safe save/readback; blocks affected cleanup acceptance if behavior changes; broad human release gate remains |
| HUMAN-02 / P0 | Same CV open in two sessions | Save a change in sessionA, then stale sessionB. Pass if B clearly reports conflict, retains draft/recovery and never overwrites A. Exercise failed save/retry; successful UI must correspond to durable reload | Synthetic before/after/version evidence; data-integrity failure blocks development immediately |
| HUMAN-03 / P0 | Career Profile import with synthetic PDF/DOCX and existing matching job | Upload; observe real stages; compare original/evidence; correct employer/title/date; reject an unsupported field; resolve duplicate conservatively; approve. Refresh profile and open CV Editor/export. Pass if approved facts persist, unapproved/unknown facts stay absent, existing unrelated details/old CVs remain | Source, corrections and final synthetic profile/PDF; actual integrity defects block development; human usability completion remains open |
| HUMAN-04 / P1 | Physical phone and tablet, each light/dark | CV editor, import source/review switching, templates, jobs and dashboard. Use touch/software keyboard and rotate. Pass if primary actions remain reachable, no clipped content or accidental data loss; dashboard mobile order must not rewrite desktop geometry | Real device names/OS/browser and screenshots; production human/device gate; emulated viewport is not evidence |
| HUMAN-05 / P1 | Keyboard only, then actual NVDA/VoiceOver (name/version required) | Navigate upload/review, editor dialogs/history, template selection, dashboard drag/resize/show-hide/save and admin filters/details/poll pause. Pass if labels/status announcements/focus order/dialog return work and no keyboard trap occurs | AT observations and failures; production accessibility gate, candidate-specific affected controls must be preserved |
| HUMAN-06 / P1 | Every CV and matching letter theme, short/dense EN/NB, with/without optional photo | Inspect review package's actual PDF/preview images, then open current app. Check title clearance, section rhythm, font weights/diacritics, bullets, margins/columns, page breaks, footer/sidebar height, missing/clipped text and excessive whitespace. Pass requires recorded decisions per template/case, not blanket approval | Annotated synthetic PDF/screenshots; S01 remains failed until measured correction or explicit criterion disposition; no automatic waiver |
| HUMAN-07 / P1 | Actual printer; A4 and Letter as supported | Print representative single/sidebar/multipage CV and letter at intended scale; compare PDF preview. Pass if margins, page breaks, typography and all content survive actual printing | Printer/driver/settings and photos of synthetic printouts; production print gate; PDF download is insufficient |
| HUMAN-08 / P1 | Proficient English and Norwegian Bokmål reviewers | Review jobs, Career Profile/import, CV editor, template/letter labels, dashboard, account/settings and admin/error/progress copy. Pass if terminology, dates, instructions and errors read naturally and preserve meaning | Reviewer language competence and concrete corrections; production linguistic gate. Other locales must not be represented as implemented without catalog/runtime evidence |
| HUMAN-09 / P1 | Dashboard edit mode and jobs workspace | Drag/resize/show/hide; save/reload, cross-session conflict and narrow viewport; track a fictional job through existing statuses. Pass if widgets/data/filters persist and keyboard alternatives match | Synthetic steps/screenshots; confirmed regression blocks affected cleanup |
| HUMAN-10 / P1 | Admin and non-admin accounts | Compare submitting owner and linked import/job; filters, stages, duration/failure/event history, pause/reconnect. Attempt non-admin access. Pass if attribution is correct, private source/prompt/result/lease/path data is absent and non-admin is denied | Safe status/authorization observations, never raw sensitive logs; disclosure/auth defect blocks development |
| HUMAN-11 / P1 | Explicitly consented local generic AI on fictional job/profile | Inspect saved strategy/enrichment and source facts. Pass only the reviewed sample if suggestions are appropriate, no invented candidate proof and structured failures are understandable. Never approve an entire model from one result | Source/output comparison, sample-specific decision; blocks AI quality/activation claims, not unrelated cleanup assessment |
Human aesthetic preferences may be returned as specific revisions. None of these rows grants cleanup entry. Before Phase10 implementation, the owner must approve the resolved published baseline and exact candidate scope, with any permitted deferral identified and signed through the separate controller's protected approval flow. The current manifest declares no checkpoint deferrable gates; changing that policy itself requires its signed policy-update process. Do not answer these questions by editing ACCEPTANCE.json.