# Requirements Checklist: Spec 387 - Review Publication Resolution Decision UX v1

**Purpose**: Preparation-readiness checklist for Spec 387 artifacts only.
**Created**: 2026-06-18
**Feature**: `specs/387-review-publication-resolution-decision-ux-v1/spec.md`

## Candidate Selection And Scope

- [x] CHK001 The candidate source is the direct user-provided Spec 387 draft attachment.
- [x] CHK002 The active auto-prep queue in `docs/product/spec-candidates.md` is acknowledged as empty/no-safe-automatic-target, and this spec is treated as manual user-provided promotion.
- [x] CHK003 Completed Spec 386 is treated as implementation context only and is not rewritten or normalized.
- [x] CHK004 The original draft is narrowed to residual UX/copy/state/confirmation/readonly hardening already not fully covered by repo truth.
- [x] CHK005 Close alternatives are deferred instead of hidden inside the scope.

## Constitution And Architecture Fit

- [x] CHK006 The spec forbids new persistence, migrations, route families, global search resources, navigation entries, workflow engines, adapter registries, and auto-publish behavior.
- [x] CHK007 The spec requires existing Spec 386 RBAC, audit, source-owned actions, failure redaction, and no-auto-publish guarantees to remain intact.
- [x] CHK008 The plan keeps OperationRun start/completion/link UX delegated to existing helpers and services.
- [x] CHK009 Provider-specific details remain behind existing proof/diagnostic boundaries.
- [x] CHK010 Proportionality review rejects a new generic presenter/framework by default.

## UI/Productization Coverage

- [x] CHK011 UI Surface Impact is explicit and consistent with an existing page/copy/action-modal hardening pass without claiming a new modal/action or planned customer-facing surface change.
- [x] CHK012 UI/Productization Coverage reuses UI-101, UI-040, and UI-006 context without inventing a new route taxonomy.
- [x] CHK013 Decision-first surface role, audience-aware disclosure, UI classification, and operator surface contract are complete for the affected surfaces.
- [x] CHK014 Technical proof is required to stay collapsed/default-secondary.
- [x] CHK015 Customer-safe non-leakage is a required negative regression, not a new customer resolution feature.

## Filament / Livewire / Actions

- [x] CHK016 Filament v5 / Livewire v4 compliance is stated.
- [x] CHK017 Laravel 12 panel provider location is stated as `apps/platform/bootstrap/providers.php`, with no provider change planned.
- [x] CHK018 No global-searchable Resource is added.
- [x] CHK019 Destructive/high-impact actions remain `->action(...)` actions with `->requiresConfirmation()`, server authorization, audit, and tests.
- [x] CHK020 Asset strategy is stated as no new registered Filament assets expected.

## Tests And Validation

- [x] CHK021 Tasks include tests before implementation tasks.
- [x] CHK022 Tasks include focused Feature/Filament assertions for decision copy, internal term absence, confirmation copy, readonly execution denial, and no Publish action.
- [x] CHK023 Tasks include browser smoke/screenshot coverage for desktop, mobile, modal, proof disclosure, readonly, and customer no-leakage states.
- [x] CHK024 Validation commands use Sail-first paths and include focused Spec 387, Spec 386 regression, browser, Pint, and `git diff --check`.
- [x] CHK025 No full-suite success is implied by the preparation artifacts.

## Analyze Outcome

- [x] CHK026 Preparation artifacts are consistent on scope: residual UX hardening only.
- [x] CHK027 No requirement in `tasks.md` expands beyond `spec.md` or `plan.md`.
- [x] CHK028 Open questions are non-blocking.
- [x] CHK029 Candidate Selection Gate passes with scope reduction.
- [x] CHK030 Spec Readiness Gate passes for a later implementation loop.

## Review Outcome

- [x] CHK031 Review outcome class: `acceptable-special-case`.
- [x] CHK032 Workflow outcome: `keep`.
- [x] CHK033 Final note location: active feature PR close-out entry `Smoke Coverage / UX Hardening / No New Workflow Mechanics`.

## Notes

- This checklist validates preparation readiness only.
- No application implementation, runtime tests, browser smoke execution, or application code changes have been performed in this preparation step.