Converge Wave A surfaces on bounded shared UI primitives

[alexeygrigorev]

Converge Wave A surfaces on bounded shared UI primitives

Status: accepted and committed locally — exact accepted commit 0c89588df809b2e84af02e796d1910a25eea0165; not merged, pushed, deployed, shipped, or closed
Tags: enhancement, portal, frontend, testing, design, P1
Parent: #162, Wave A slice 1
Depends on: satisfied — accepted #180 increments e684162 and b045739 plus the accepted #161 foundation are present in parent baseline 78e9122
Blocks: implementation of #162 Wave A slices 2–5 on overlapping frontend presentation paths
Next owner: Orchestrator — when coordinated publication resumes, merge the accepted local Wave A chain in order, push main, then hand off to On-Call; no implementation or review rerun is pending for #218
Resume condition: local main is clean and the Orchestrator is ready to publish the accepted Wave A chain; #218 requires no rerun unless commit 0c89588df809b2e84af02e796d1910a25eea0165 changes

Product outcome

Give the dependency-independent Wave A surfaces one small, explicit presentation vocabulary for page headers, section framing, action rows, fields/form footers, semantic status labels, and honest loading/empty/partial/error states.

An operator moving among Templates, Recurring, Process Docs/search, Bookkeeping, Sponsors, Newsletter, Calendar, and Mailing exports should see the same hierarchy and state language without changing any route, API, mutation, authorization, lifecycle, or domain behavior.

This is gap-only convergence. It is not a redesign of those surfaces and not a repository-wide CSS cleanup.

PM scope amendment after review

• Screenshot files 09 and 10 prove only the Newsletter READY presentation state for the shared page/header/action/form/status primitives. They do not require or authorize validation copy, error-focus ownership, conflict recovery, Calendar keyboard behavior, or any other Newsletter/Calendar behavior change.
• Preserve all Newsletter/Calendar domain copy, validation/error text, focus ownership, routes/history, dialog/mutation/conflict/recovery behavior, and Calendar keyboard behavior unchanged for Converge Newsletter, Calendar, and Mailing Export presentation #222.
• Generic validation, announcement, and useful-focus criteria in Converge Wave A surfaces on bounded shared UI primitives #218 may be proven by another already-in-scope dialog/state; Newsletter and Calendar are not required evidence vehicles for those criteria.
• backend/scripts/sam-workspace-isolation.test.mjs is outside Converge Wave A surfaces on bounded shared UI primitives #218 write ownership. Its clean-workspace isolation command is not an Converge Wave A surfaces on bounded shared UI primitives #218 acceptance gate. The required SAM/build/parity/make ci command list in this issue remains unchanged.
• The prior frozen candidate and review verdicts are superseded only for this scope correction. The authorized path is: remove the behavior changes and verifier change, regenerate exactly the amended 12 screenshots, freeze new fingerprints, then repeat Designer, independent Tester, and PM reviews.

Frozen baseline and dependency reconciliation

The PM inventory was performed read-only at clean local SHA 78e91223203aa54376a318fd1a3214ce0242e0c3.

That baseline already contains:

• Restore behavior-based browser coverage and fix canonical UI accessibility races #180 increment e684162: accepted focus, refresh, notification, Recurring accessibility, fixture, and browser-race repairs.
• Restore behavior-based browser coverage and fix canonical UI accessibility races #180 increment b045739: accepted behavior-based browser coverage convergence.
• Finalize the canonical scan-first Operations Home #161 accepted Home/shared-shell foundation, finalized by 7d77632 and closed by 64476d2.

#218 must preserve those behaviors. It does not reopen #180 or #161.

Accepted but separately held #158 and #164 work is not part of 78e9122 and is not scope for this issue. Those branches overlap shared files including frontend/src/styles.css, frontend/src/surfaces/knowledge/search.js, frontend/src/surfaces/planning.js, task tests, the capability catalog, and canonical browser specs. The Orchestrator must serialize writers. If #158 or #164 is integrated before #218 freezes, the engineer must first re-run this issue's gap/overlap inventory on the reviewed containing SHA, retain only still-unmet #218 gaps, and send the reconstructed fingerprint through Designer, Tester, and PM again. Do not resolve overlap by reverting, absorbing, or silently rewriting dependency-owned behavior.

Current-source inventory

Already compliant — preserve, do not rebuild

• frontend/src/styles.css already owns the canonical light/dark tokens, spacing/density tokens, 6px shared radius, focus ring, 34px desktop and 44px mobile density concepts, content width, and overlay shadow.
• Existing shared primitives already include .primary-button, .danger-button, .surface-dialog, .section-header, .section-kicker, .surface-actions, .surface-status, .status-label, and .honest-state.
• Wave A routes already use native headings, labels, status/alert regions, dialogs, semantic status text, public-safe synthetic browser fixtures, canonical URLs, and real local backend calls.
• The capability catalog already has durable runtime states for Templates, Recurring, Process Docs, Bookkeeping, Sponsors, Newsletter, Calendar, and Mailing exports. No new capability identity is needed merely for visual convergence.
• Restore behavior-based browser coverage and fix canonical UI accessibility races #180 already owns and proves Recurring state semantics and interaction/accessibility race fixes. Finalize the canonical scan-first Operations Home #161 already owns Home and shell composition.

Concrete gaps owned by #218

The 11,695-line stylesheet contains later route-specific layers that restate the same shared presentation contract:

1. Page header duplication. .bookkeeping-header, .crm-header, .mailing-exports-surface > header, .planner-header, and .ops-surface-header independently repeat title, description, divider, spacing, and trailing-action behavior.
2. Action-row duplication. .surface-actions, .row-actions, .finance-actions, .mailing-export-actions, .planner-form-actions, .ops-template-actions, and .recurring-row-actions repeat wrapping, spacing, alignment, footer borders, and mobile target rules.
3. Form duplication. .dialog-fields, .planner-form-grid, and .ops-field repeat stacked labels, control dimensions, helper/error placement, and responsive one-column behavior.
4. Status-label duplication. .status-label, .finance-status, .evidence-state, .mailing-export-status, .planner-status, and Recurring status presentation repeat compact semantic pills and success/warning/danger/info variants.
5. Honest-state duplication. .ops-runtime-state, .ops-docs-state, .ops-empty, .ops-inline-error, .surface-status, .planner-load-state, and route-scoped .honest-state rules express overlapping loading, empty, partial, failure, and recovery presentation.
6. Responsive duplication. Several late media blocks independently restore 44px controls and one-column form/action behavior, leaving equivalent Wave A controls visually inconsistent and making later slices likely to add more local overrides.

Converge those five primitive families and their responsive rules. Route-specific classes may remain only where they carry a real route layout, behavior hook, or test locator; they must not retain a duplicate shared visual declaration.

Dependency-owned — preserve exactly

• Restore behavior-based browser coverage and fix canonical UI accessibility races #180: shell/navigation/notification focus behavior, Inbox draft survival, Recurring programmatic status and mutation behavior, canonical journey isolation, fixtures, and diagnostics.
• Finalize the canonical scan-first Operations Home #161: Home, scan-first queue, shell integration, Home route/history/focus, and Home visual reference behavior.
• Show signed-in identity and authorized teammates’ Task/Card work #164: actor identity, selected owner/team scope, authorization, attribution, Users/Admin behavior, and work visibility.
• Make assistant output review safe and lifecycle-complete #158: Assistant/Artifact lifecycle, review/approval/access behavior, and related presentation.
• Restore canonical frontend behavior coverage and SAM parity gates #159: capability evidence schema, collector/reporter, source/SAM parity machinery, and evidence policy.
• Own visible feedback in each workspace surface #204: owning-surface feedback behavior. Converge Wave A surfaces on bounded shared UI primitives #218 may make its presentation consistent but must not move feedback back into global chrome or change when it appears.

Out of scope

• Shell information architecture, Home, account/team identity, global navigation, Settings, notifications, or mobile drawer.
• Show signed-in identity and authorized teammates’ Task/Card work #164 authorization, teammate/work-scope, Task/Card/Inbox execution, Admin, or Users behavior.
• Make assistant output review safe and lifecycle-complete #158 Assistant or Artifact lifecycle, permission, review, archive, or rehydration behavior.
• Route, history, focus-ownership, API, backend, DynamoDB, persisted schema, mutation, copy, domain state, or access-policy changes.
• Broad CSS rewrite, stylesheet splitting, framework/component-library adoption, new router/runtime abstraction, or a second token vocabulary.
• A compatibility layer: no alias-only selectors, duplicate old/new primitives, legacy fallbacks, or “temporary” dual styling.
• Raw operational knowledge, private/provider data, real identifiers, provider calls, production writes, imports, exports, migrations, restores, AWS/infrastructure changes, manual deploys, or source-repository edits.
• Committed screenshots, screenshot goldens, pixel/byte assertions, or public issue attachments containing generated evidence.

Write ownership

The implementation may edit only these production paths, and only for class/presentation convergence:

• frontend/src/styles.css
• frontend/src/surfaces/tasks/templates.js
• frontend/src/surfaces/tasks/recurring.js
• frontend/src/surfaces/knowledge/list.js
• frontend/src/surfaces/knowledge/process-docs.js
• frontend/src/surfaces/knowledge/search.js
• frontend/src/surfaces/knowledge/navigation.js
• frontend/src/surfaces/finance/bookkeeping.js
• frontend/src/surfaces/finance/mailing.js
• frontend/src/surfaces/finance/sponsor-layout.js
• frontend/src/surfaces/finance/sponsor-alerts.js
• frontend/src/surfaces/finance/sponsor-communications.js
• frontend/src/surfaces/finance/sponsor-finance.js
• frontend/src/surfaces/finance/sponsors.js
• frontend/src/surfaces/planning.js

Allowed test/evidence paths are the corresponding focused frontend tests, one dedicated backend/e2e/issue-218-shared-primitives.spec.js, and existing capability journey files only where needed to emit already-defined durable state IDs. Do not add new capability IDs for style-only states or alter #159's schema/reporting machinery.

A newly required production path needs a PM amendment before editing. Do not create a shared JavaScript component abstraction merely to rename CSS classes.

Acceptance criteria

Bounded convergence

• The engineer posts a fresh criterion-to-source/test inventory before editing, using the exact starting SHA and classifying every item as already compliant, concrete gap, dependency-owned, or out of scope.
• One canonical CSS contract owns page header, section framing, action row, field/form footer, semantic status, and honest-state presentation for all in-scope Wave A surfaces.
• In-scope markup consumes that contract. Redundant route-specific declarations are deleted in the same change; retained route classes have a documented route-layout, behavior, or locator purpose.
• No new hard-coded color, radius, shadow, spacing scale, or control-height vocabulary is introduced. Both themes use the existing tokens.
• There is no compatibility alias, duplicate old/new selector contract, framework, runtime helper, API change, or behavior refactor.

Desktop and mobile

• At 1440×900, every in-scope page has one dominant heading, adjacent description, content-width primary action, consistent section frame, and no nested-card or duplicated-status hierarchy introduced by Converge Wave A surfaces on bounded shared UI primitives #218.
• At 390×844, header/actions and form footers wrap in reading order; fields become one column; every in-scope interactive control is at least 44×44 CSS pixels; there is no page-level horizontal scroll, clipping, overlap, or unreachable action.
• At 390×844, each evidence route shows its first meaningful record, state, or recovery action within the initial viewport after route heading/controls; empty decorative containers do not push the decision below the fold.
• Light and dark themes preserve semantic contrast and the same hierarchy. Reduced motion causes no lost state or focus cue.

Accessibility and honest states

• Each changed route retains one main, one page h1/owned primary heading contract, correctly nested section headings, native labels, and semantic list/table/dialog structure.
• Loading is announced without displaying a false zero; empty states explain what is absent and retain a safe next action; partial failures retain successful records and identify the unavailable source with retry guidance.
• In an already-in-scope dialog/state other than Newsletter or Calendar, generic validation and conflict presentation retains entered values and useful focus; blocking errors use role="alert", non-blocking progress uses role="status"/appropriate live state, and success names the durable result. Newsletter/Calendar domain copy, focus, route, recovery, and keyboard behavior remain unchanged for Converge Newsletter, Calendar, and Mailing Export presentation #222.
• Status meaning is expressed in text and programmatically, never by color alone. Repeated status pills are not added where status does not affect the next decision.
• Keyboard operation, visible focus, dialog focus containment/restoration, and zoom remain intact; automated scans report zero critical or serious WCAG A/AA findings on every captured changed state.

Behavior and parity

• All existing route, API, mutation, concurrency, authorization, focus, history, and close/return behavior remains unchanged.
• A real-server Playwright journey exercises each in-scope family through existing durable capability states, without request interception, fixed sleeps, source-string assertions, incidental copy pins, broad 404 swallowing, test-order dependence, or screenshot assertions.
• The successful full browser run emits passing evidence for every existing capability state and role; no state is covered by screenshots, source inspection, or parity alone.
• Source, backend/dist, and packaged SAM frontend assets are identical for every changed asset, and the normal source/SAM parity run passes with all evidence records accounted for.
• Synthetic evidence contains no operational knowledge, real person/contact/provider data, credentials, private links, or production identifiers.

Test scenarios

Shared hierarchy across Wave A

Given an authenticated synthetic operator/admin and populated local fixtures
When Templates, Recurring, Process Docs, Bookkeeping, Sponsors, Newsletter, Calendar, and Mailing exports are opened directly and through their existing routes
Then each retains its domain behavior while page header, sections, actions, fields, semantic status, and honest-state hierarchy use the one shared contract

Honest partial and failure state

Given successful synthetic records plus one deterministic local source failure
When the affected Process Docs/search, finance, planning, or export surface settles
Then successful data remains visible, unavailable data is named, zero/success is not fabricated, and a safe retry or return action is reachable and focused appropriately

Generic validation without data loss

Given an already-in-scope dialog or editor other than Newsletter or Calendar with public-safe entered values
When local validation, conflict, or save failure occurs
Then the dialog remains open, values remain, the first useful field/error owns focus, the error is announced, and a retry produces at most one intended mutation

Responsive action hierarchy

Given the same ready and critical fixtures at 1440×900 and 390×844
When the operator traverses headings, fields, action rows, statuses, and dialogs by keyboard
Then reading/focus order is stable, desktop actions remain content-width, mobile targets are at least 44×44, and no control or recovery path is clipped or off-canvas

Source/SAM identity

Given the frozen source candidate and a clean SAM build
When the same public-safe routes and changed assets are verified from source and packaged targets
Then route behavior and durable capability evidence agree and every changed frontend asset is byte-identical

Synthetic screenshot evidence

Capture exactly these 12 untracked native-size PNGs under .tmp/screenshots/issue-218/; delete stale extras before review:

• 01-templates-ready-desktop-1440x900.png
• 02-templates-ready-mobile-390x844.png
• 03-recurring-referenced-delete-desktop-1440x900.png
• 04-recurring-referenced-delete-mobile-390x844.png
• 05-process-docs-partial-desktop-1440x900.png
• 06-process-docs-partial-mobile-390x844.png
• 07-bookkeeping-ready-desktop-1440x900.png
• 08-bookkeeping-ready-mobile-390x844.png
• 09-newsletter-ready-desktop-1440x900.png
• 10-newsletter-ready-mobile-390x844.png
• 11-mailing-exports-failed-desktop-1440x900.png
• 12-mailing-exports-failed-mobile-390x844.png

Use normal local backend behavior and synthetic public-safe records. Files 09 and 10 capture Newsletter READY presentation only and prove shared page/header/action/form/status primitives; they must not depend on validation copy, error focus, conflict recovery, Calendar keyboard behavior, or any Newsletter/Calendar behavior change. Tester and Designer inspect every image at native resolution for hierarchy, copy ownership, visible state, theme/contrast, target sizing, overflow, clipping, overlap, and first-decision visibility. Screenshots are visual evidence only; they are not committed, attached publicly, or used as behavior/parity proof.

Verification

Engineer uses focused tests while iterating. backend/scripts/sam-workspace-isolation.test.mjs is outside #218 and must not be edited; its clean-workspace isolation command is not an #218 acceptance gate. The required SAM/build/parity/make ci list below remains unchanged. Tester runs the complete relevant workflow on one frozen fingerprint and records commands, exit codes, observed counts, capability-state accounting, and evidence paths:

npm run test:frontend:unit
npm run test:frontend:coverage
npm --prefix backend test
npm --prefix backend run typecheck
npm --prefix backend run build
node backend/scripts/verify-frontend-artifact.mjs --source frontend --artifact backend/dist
npm --prefix backend run test:e2e
npm --prefix backend run test:e2e:frontend-parity
make sam-validate
make sam-build
node backend/scripts/verify-frontend-artifact.mjs --source frontend --artifact .aws-sam/build/BackendFunction
make ci
git diff --check

The dedicated #218 browser spec must be included in the normal full Playwright run. Existing behavior suites remain authoritative for the durable capability states; do not create a parallel screenshot-only or intercepted test harness.

Lifecycle gates

• PM inventory completed read-only at 78e9122
• Accepted Restore behavior-based browser coverage and fix canonical UI accessibility races #180 increments and Finalize the canonical scan-first Operations Home #161 foundation reconciled
• PM amendment narrows Newsletter evidence to READY presentation, excludes the SAM workspace verifier, and authorizes a new freeze plus repeated reviews
• Orchestrator records exact starting SHA and resolves shared-path writer order
• Software Engineer posts refreshed inventory and implements only concrete gaps
• Software Engineer posts frozen diff/status/content fingerprints and READY FOR TEST
• Designer inspects exactly 12 screenshots and posts DESIGN PASS
• Independent Tester verifies every criterion and posts TESTER PASS on the same fingerprint
• PM reviews the operator experience and posts ACCEPTED on the same fingerprint
• Software Engineer commits only accepted issue-owned paths with Closes #218
• Orchestrator merges locally in the recorded Replace the transitional Tasks table with the final cardId schema #166-safe order and pushes main
• On-Call verifies CI/CD, deployment, source/SAM identity, and smoke evidence before Converge Wave A surfaces on bounded shared UI primitives #218 is called shipped or closed

No HUMAN gate is required for this local, synthetic, provider-free slice.

[alexeygrigorev]

PM GROOMED — agent-ready bounded Wave A shared-primitives slice

I completed a read-only current-source/test inventory at clean local baseline 78e91223203aa54376a318fd1a3214ce0242e0c3 and reconciled accepted #180 increments e684162/b045739 plus the accepted #161 foundation.

The issue now owns only five proven presentation gaps across dependency-independent Wave A surfaces: shared page headers, action rows, fields/form footers, semantic status labels, and honest loading/empty/partial/error states. Existing tokens and shared components are preserved; redundant route-level presentation declarations are migrated and deleted without compatibility aliases. Route/API/mutation/auth/history/focus/domain behavior is frozen.

The spec includes:

• exact production and test write ownership;
• explicit already-compliant, concrete-gap, dependency-owned, and out-of-scope classifications;
• serialization/reconstruction rules for held Make assistant output review safe and lifecycle-complete #158/Show signed-in identity and authorized teammates’ Task/Card work #164 overlap;
• measurable 1440×900, 390×844, accessibility, reduced-motion, honest-state, and no-overflow criteria;
• real-server behavior evidence using existing durable capability IDs;
• source, build, and SAM identity/parity gates;
• exactly 12 public-safe synthetic screenshots under .tmp/screenshots/issue-218/;
• full Designer → Tester → PM → commit → merge/push → On-Call lifecycle gates;
• strict exclusions for shell IA, Home, account/team identity, global navigation, Show signed-in identity and authorized teammates’ Task/Card work #164 work-scope/authorization, Make assistant output review safe and lifecycle-complete #158 Assistant/Artifact lifecycle, broad CSS rewrites, backend/data/provider work, tracked screenshots, and compatibility layers.

Labels are enhancement, portal, frontend, testing, design, and P1. needs grooming was removed because the issue is self-contained and implementable once the Orchestrator records the exact starting SHA and serializes overlapping shared-file writers.

No repository file, worktree, commit, push, deployment, provider, production/private data, or HUMAN gate was touched.

Next owner: Orchestrator records the starting SHA and writer order, then Software Engineer posts the required refreshed inventory before editing.

[alexeygrigorev]

SWE PRE-EDIT INVENTORY — frozen baseline 78e91223203aa54376a318fd1a3214ce0242e0c3

I verified the worktree is clean on issue-218-shared-primitives, with HEAD exactly equal to the PM baseline. This inventory is from current production source before any edit.

Criterion / family	Classification	Current-source and test evidence	Bounded #218 action
Existing tokens, themes, focus, density, radius, and overlay vocabulary	Already compliant	frontend/src/styles.css defines the canonical light/dark semantic tokens, var(--radius), focus treatment, desktop controls, and mobile 44px rules.	Reuse only existing tokens; add no color/radius/shadow/spacing/control-height vocabulary.
Canonical page hierarchy	Concrete gap	.bookkeeping-header, .crm-header, .mailing-exports-surface > header, .planner-header, .ops-surface-recurring .ops-surface-header, and .ops-surface-docs > .ops-surface-header repeat flex/grid, title, description, divider, spacing, trailing-action, and mobile rules across late stylesheet layers.	Make in-scope markup consume one page-header class; retain route names only as behavior/layout locators and delete their shared visual declarations.
Section framing	Concrete gap	.bookkeeping-section, CRM panels, .ops-recurring-section, mailing history sections, and docs panels independently repeat border/radius/background/overflow framing; .section-header already provides a viable shared header vocabulary.	Apply one shared section-frame contract where the repeated declaration is presentation-only; preserve genuine route grid/detail/list layout.
Action rows and form footers	Concrete gap	.surface-actions, .row-actions, .finance-actions, .mailing-export-actions, .planner-form-actions, .ops-template-actions, and .recurring-row-actions repeat flex/wrap/gap/alignment/footer/mobile declarations.	Consume one shared action-row class and one footer modifier; retain route classes only for behavior locators or genuine route positioning.
Fields and form grids	Concrete gap, bounded	.dialog-fields and .planner-form-grid repeat field label/control/helper/error/one-column behavior. .ops-field is used by excluded Admin/Users code in frontend/src/surfaces/operations/admin.js, which is not an authorized production path.	Converge only in-scope dialog/planner fields and form grids. Leave .ops-field and Admin/Users untouched as dependency-owned/out of scope.
Semantic status labels	Concrete gap	.status-label, .finance-status, .evidence-state, .mailing-export-status, and .planner-status repeat the same pill geometry and semantic token variants. Existing text and state attributes already carry meaning.	Make in-scope statuses consume .status-label; keep route classes only for state/locator hooks and delete duplicate geometry/variant declarations. Preserve Recurring’s accepted programmatic semantics.
Honest loading/empty/partial/error presentation	Concrete gap	.honest-state, .ops-runtime-state, .ops-docs-state, .ops-empty, .ops-inline-error, .surface-status, and .planner-load-state restate overlapping containers/text/semantic variants. Existing modules already use role=status/alert and retain useful data in tested failure paths.	Make in-scope state markup consume one honest-state contract plus semantic modifiers; retain route classes only where runtime behavior or locators require them. No copy, API, retry, focus, or mutation change.
Native semantics, labels, dialogs, status text, and behavior	Already compliant; preserve	Current modules use native headings/forms/labels/dialogs and live roles. Existing focused suites are tasks-surface.test.mjs, knowledge-surface.test.mjs, finance-surface.test.mjs, and planning-surface.test.mjs; canonical real-server behavior lives in canonical-capability-behavior.spec.js and route-specific production-portal specs.	Add focused production-module class/semantics units without replacing behavior assertions; run existing suites unchanged.
Templates, Recurring, Process Docs, Bookkeeping, Sponsors, Newsletter, Calendar, and Mailing exports durable states	Already compliant identity; evidence gap for this slice	backend/e2e/frontend-capabilities.json already defines all required surface/state IDs. Existing capability journeys emit behavior evidence. There is no #218 journey yet.	Add backend/e2e/issue-218-shared-primitives.spec.js using normal local server behavior and existing IDs only; do not alter the #159 schema or add style-only IDs.
Desktop/mobile hierarchy and first-decision visibility	Concrete verification gap	Existing route-specific design specs cover portions of finance/planning/tasks, but no single bounded 1440x900/390x844 #218 journey or exact 12-image inventory exists.	Add synthetic real-server responsive assertions; capture exactly the 12 specified untracked PNGs and inspect all natively.
Accessibility, keyboard/focus, zoom, reduced motion, contrast	Already compliant behavior plus concrete changed-state evidence gap	#180 and existing browser suites cover focus/races; current tokens and native controls preserve theme/reduced-motion behavior. No #218 changed-state scan exists.	Run automated accessibility scans for every captured state, assert 44px controls/no overflow/heading/landmark contracts, and preserve existing focus/dialog behavior.
Route/API/mutation/concurrency/auth/history/close-return contracts	Dependency-owned and frozen	#180/#161 behavior is in the exact base; #158/#164 are separately held. Current browser/unit suites are authoritative.	No behavior refactor. Full regression run must pass on the frozen candidate.
Home, shell IA, navigation, identity/team/Admin/Users/Settings, #164 work scope, #158 assistant lifecycle, backend/data/provider/AWS	Out of scope	These surfaces are outside the issue write-ownership list and/or live on held branches.	No edits, no provider access, no backend contracts, no compatibility layer.
Source/build/SAM identity and complete capability accounting	Already-supported machinery; concrete candidate verification gap	verify-frontend-artifact.mjs, normal capability reporter, and frontend-parity scripts already provide #159 machinery.	Run build identity, full E2E capability accounting, parity, SAM build/identity, and make ci on one frozen fingerprint.
Synthetic/public-safe evidence	Already compliant fixture policy; concrete artifact task	Existing browser fixtures use synthetic records; screenshots are gitignored under .tmp.	Use only synthetic records, keep exactly 12 untracked PNGs under .tmp/screenshots/issue-218/, attach none publicly, and remove stale extras.

Planned canonical class consumption

• Page hierarchy: shared page-header class on the six in-scope header families.
• Sections: shared section-frame/header presentation while retaining route layout hooks.
• Actions: shared action-row and form-footer classes; route hooks stay only where tests/runtime positioning need them.
• Forms: shared field-grid/field presentation for in-scope dialogs and planner editors; excluded .ops-field remains unchanged.
• Statuses: .status-label plus existing semantic state classes/attributes.
• Honest states: .honest-state plus existing role/state attributes and bounded semantic modifiers.

No files have been edited, staged, committed, pushed, deployed, or sent to a provider. I will now implement only the concrete gaps above.