cesnimda
4.4 KiB
Account sections and editor hierarchy — active qualification
4 November 2026. Continuation from published/independently verified 1c88cacb4d4d6137ba82e74e53fa27faadb86c1e, which qualifies flat application source c9138af01e6dd7cc407a9b71c921914d8c1299f0 with65 selected tests and36-configuration/216-state browser evidence. Those captures are bound to their original source, not automatically to this successor.
Account changes: remove seven decorative PageSection surfaces from account navigation/identity/details/password, two-factor/session management and mail connection collection. Keep provider objects, recovery-code presentation, every form/control/ref, mounted draft, permission guard and confirmation dialog. The redundant inner Profile heading becomes the paired EN/NB Identity / Identitet label; shell Profile h1 remains. Canonical Career Profile and legacy careerOnly behaviour remain separate and unchanged.
Editor hierarchy: only canonical numeric job-detail routes use the existing editor-width token (100%). Keep the shell h1/focus target but render its generic route label/description compactly; recorded role h2 uses the existing page-title type scale. This follows approved A3 role hierarchy and makes more useful desktop space without fetching/duplicating domain data or changing navigation. List/Settings/unrelated route headings retain their existing styles.
PASSED:81 selected account/provider/security/export/catalogue tests/eight suites;16 shell/navigation/layout/theme tests/four suites; full lint and export build. Independent read-only reviews found no actionable findings in the seven surface removals, verifier branches, or scoped editor hierarchy. New Identity label is checked by the updated heading contract and paired translation catalogue; native-language acceptance remains a human qualification.
Initial phone pilots passed seven account states (before final Identity copy) and six editor states including role-title visual hierarchy. Required final runs on the settled export: 36 configurations /252 account scans (focused details/connections/security, summary, cancelled session confirmation, cancelled data confirmation with fixture403 export, mail connections), plus 36 /216 application scans to qualify the changed role heading. No production account, actual deletion/revocation/export, provider activation or model is permitted by these fixtures. Skipped admin/processing checks explicitly remain NOT RUN in account-only mode.
PASSED on settled source b6d830f27951271ac2d1acb8855adc43b77cbec0:36 configurations /252 account accessibility scans and captures, plus36 /216 application scans and captures. Account journeys preserve an unsaved display-name draft across section jumps; cancel session and data confirmations; exercise one fixture403 export each. Application journeys retain36 synthetic status updates,36 visible keyboard-focus checks and three canonical alias checks. These runs supersede overlapping earlier captures rather than adding to them.
Capture correction: the first account run composed scrolled desktop full-page screenshots with fixed navigation in misleading positions. Retained BROWSER-CAPTURE-FAILURE.json and one named failure screenshot document the issue. The corrected full252-state run captures focused sections as viewports and top-of-page desktop states as full pages. A corrected1440px focused details capture was visually inspected: navigation remains at the viewport top, fields span useful columns and the purple section outline denotes keyboard focus. Phone security and earlier editor captures were inspected separately. Automated scans do not establish owner visual acceptance.
Limitations: account-only mode does not execute admin/processing scenarios. The fixture deliberately rejects shared companies reads (/api/companies,108 recorded unavailable reads) and external Google Fonts; those are not qualified integrations. No real account export, revocation, deletion, provider, model or security/release acceptance. Account and application reports have no browser errors, unexpected writes or accessibility violations. ACCOUNT_EDITOR_SOURCE_MANIFEST.json binds runtime sources to the immutable commit, verifier scripts and evidence to the receipt commit, and80 raw export files to the export tested before public-auth development is built.
Next: qualify the public sign-in/recovery language controls and remaining rendered route families. Keep full34-route/57-group, human/device/native-language and final owner visual acceptance OPEN.