jobtrackingapp/docs/p10-entry-final/OWNER_REVIEW.md

Owner decisions still required

No human result or approval has been supplied. Phase10 remains NO-GO. Use synthetic data; do not upload a personal CV or commit credentials/signatures. The final ENTRY_PROPOSAL.json names the exact published candidate and pending decisions. A model-written status cannot approve it.

Priority / decision	Exact action and expected result	Evidence / blocking scope
1. PDF metric disposition	Read DIAGNOSIS.md and the per-document classification; inspect annotated preview/PDF name crops and full PDFs in the review package. Decide whether to approve the same2mm bound measured baseline-to-baseline for revised S01, retaining the original range-vs-cell oracle/results plus all other font/content/page/color checks. Reject or request revision if visible text, title gaps or layout are wrong	Concrete recorded decision naming metric, design version2, source/report hashes and accepted samples. Blocks disposition of the mandatory failed PDF criterion until approved or corrected; not a general visual/release waiver
2. Template appearance	Review all nine short first pages and long/dense first/final pages, including modern, ATS classic, code and sidebar/photo themes; compare historical originals and revised designs. Inspect the candidate-native PDFs immediately. Interactive confirmation requires the published candidate in an isolated development build, using a new CV or explicit Apply of design2; the existing jobbjakt.local runtime has not been replaced by this task. Check name/title gap, section/paragraph rhythm, margins, bullets, columns, photo alignment, page breaks, diacritics and final-page whitespace	Annotated synthetic PDF or screenshot with template/profile/page/platform and specific PASS/revise decision. Human aesthetic approval pending; applicability to a cleanup candidate must be explicit. Existing designs must not change automatically
3. Exact cleanup entry/scope	Review final candidate SHA/publication, retained19-item inventory and all mandatory blockers. Approve only a concrete scope with callers/routes/old-data/rollback/tests identified. Current inventory establishes no safe product deletion. Assessment-only permission must not become implementation permission	Protected controller entry/candidate decision bound to exact baseline and policy/artifact hashes; mandatory before cleanup implementation. This workstream will not start it
4. Runtime/adapter	In your own operator terminal, follow the separate controller's current instructions for dedicated same-account sign-in, actual protected owner key and fresh current-context qualification. Qualify the actual composite application test adapter; review signed baseline/policy activation separately	Real-key host-positive/worker-negative evidence, current qualification and independently approved test adapter. Blocks automatic execution, not evidence-only PDF inspection. No login/key/activation performed here
5. Physical/AT/language	On a real phone/tablet, use touch/rotation and keyboard-only/NVDA or VoiceOver through CV editing/import/template dialogs/dashboard; have proficient EN/Bokmål reviewers inspect labels/errors/dates	Device/OS/browser/AT version, exact steps, result and safe screenshot/notes. Genuine unfinished checks may remain source-authorised release debt for unrelated assessment; affected candidate controls still require preservation/disposition. Automation is not human approval
6. Actual print	Print short and multipage A4/Letter CV/letter at intended scale. Compare actual margins, fonts, breaks, sidebar continuity and full content with the PDF	Printer/driver/settings and synthetic print photos. Production print gate; PDF rendering/download is insufficient

Possible conditional-development deferrals are individually requested in ENTRY_PROPOSAL.json: unfinished human checks, disabled CV AI qualification, deterministic recall breadth, scoped Python vendor-audit debt and quarantined hosted CI. Existing source authority permits only their stated scope. They are not granted by this document; the current controller has no declared executable checkpoint deferrals. A protected policy decision is required before any automatic conditional advancement, and it cannot hide a mandatory automated failure.

Production-only MySqlConnector/TLS, native/image security, filesystem/off-disk backup/recovery and release/operator work stays blocked independently. Broader models, generic-AI canonical-profile compatibility, later product features, provider integrations and roadmap initiatives remain separate. No real CV-model quality acceptance, production risk acceptance or deployment permission is requested through a typography decision.